Remix.run Logo
▲ Doohickey-d 20 minutes ago

At least from the eevblog post, it seems like the only re-implemented part is the "host" side, so Linux. A scope also has an FPGA, which is where the signal processing, sample memory, and acquisition happens. This one is much harder to reverse engineer, because it's effectively impossible to decompile the bitstream back to code (verilog), it's not possible to debug it in any meaningful way, so you're really starting from scratch in the dark. And it's extra hard, because you need to know what's connected to which pin on the FPGA, which is impossible to do without desoldering it or destroying the board.

▲torginus 4 minutes ago | parent | next [-]

If he can get a black-box spec for what the FPGA's supposed to do, he can write a cleanroom implementation (or perhaps even add features), or rebuild the whole thing, including what the FPGA actually does and how.

I don't know what FPGA is in these (edit: it's Xilinx), but the usual problem is that toolchains tend to be highly proprietary.

▲guenthert 8 minutes ago | parent | prev [-]

Well, the github repository makes it look like much more was accomplished: Linux on the host was actually already done by someone else, he (and his AI agent) apparently reverse-engineered the custom application of Rigol which controls the FPGA (I suppose he left the FPGA configuration file alone) and is able to perform measurements.