steve_m

Sometimes, Claude decides that he doesn't need an assembler...

Claude, port gr-fosphor to Android. 30min later...

fosphor-cl: [+] Available device: 0:0 Mali-G715 r0p0
fosphor-cl: [+] Selected device: Mali-G715 r0p0
fosphor : [+] GL_RENDERER: Mali-G715
fosphor : [+] GL_VERSION: OpenGL ES 3.2 v1.r54p2-00eac0.c8c70f02abaa302607998c919face0f4

Crazy times we live in..

After quite some reverse-engineering, the recent MS2130S-based capture dongles are now supported by hsdaoh: https://github.com/steve-m/hsdaoh/commit/13d832966bd95d44fcfb5295defc3efb5b232596

They completely changed the register layout and I had to figure out (again) how to enable raw YUV capture. The fun part was also extending emu8051 with code-banking support to be able to emulate the (now bigger) firmware. In theory raw RGB capture should be possible now, but this will take some more effort.

Currently playing with Semtech SX1250 as SDR. 2 bit I/Q output @ 32 MHz. Has anyone already played with this chip? I know of https://github.com/M17-Project/SX1255_HAT-hw - but the SX1250 is newer and has a much broader freq range (150M - 960M).

@__luna Using the PIO and DMA

The first time I've seen GPLv1 licensed code in the wild so far...

Here's the source: https://github.com/steve-m/Pico-100BASE-TX

If anyone wants to play around with the bit-banged 100 MBit/s Ethernet for the Pico, here you go: https://github.com/steve-m/Pico-100BASE-TX

@agowa338@chaos.social @uint8_t@chaos.social So far it works with all devices and switches I've tested. Of course your could add a matching network and proper magnetics to get close to a 'real' 100Base-TX transmitter, but unless you're using tens of meters of cable it's not required. EMI might be a different issue, though. As for the interrupts, this is not a problem - the PIO does clock-accurate output of the bits supplied by the DMA.

@agowa338@chaos.social @cyb3rm0shp1t@social.xenofem.me Although the output is performed by a PIO state machine, which is fed with a 32 bit DMA. So the second CPU core, which I reserved for all the encoding, is not used 100% of the time, and the first core is available for the main 'user' application.

@kkarhan@infosec.space Yeah, I'll release it as OSS in the next weeks after ironing out some things and doing some proper host-side receive code.

@jiub@not.an.evilcyberhacker.net Fast Ethernet (100BASE-TX) is MLT-3 encoded, so there are 3 signal levels: -1, 0, +1. If you take the voltage between two digital GPIOs, you can emulate this by using 0b10, 0b00, 0b01.

@kkarhan@infosec.space What do you mean? The MCU is running at 250 MHz (double the Ethernet bit rate), with normal core voltage. It doesn't even get warm.

I've implemented bit-banged 100 Mbit/s Ethernet UDP transmission on the RP2040/RP2350. That is sufficient to transfer the data of the internal ADC overclocked to 5 MSPS and digitize some IF signal...

Following up on my previous post, I'm pleased to release hsdaoh-rp2350, which includes an example application that streams the samples of a 12-bit ADC out of a Pico2 at 40 MS/s (or more!): https://github.com/steve-m/hsdaoh-rp2350

First success with porting hsdaoh to the RP2350 HSTX: Streaming out 72 MByte/s from the Pico2 via HDMI to a $5 MS2130 capture dongle. Time to hook up an ADC!