On 10/31/25 18:51, John wrote:
Thank you. That at least clarifies the position on any starting code.
The chips on the PCB have their numbers filed off, although I suspected
one of them might be an FPGA. Not knowing the part numbers is not at all
helpful. I was going to see whether it can be probed via JTAG or an
on-board UART or something but haven't got around to that yet. It a
shame there is no Linux software for it. I got rather mis-lead by their
Github repository thinking that there was O/S software available only to
later find just an empty tar.gz file.
This instrument initially comes up on USB as :
Bus 002 Device 089: ID 16c0:4e21 Van Ooijen Technische Informatica
But subsequently on Windows that changes to:
QuantAsylum QA100 Oscilloscope
According to what I have been able to find online, the VID is shared for
"hobbyist or custom projects" and the device ID would be defined by the
creator of the device. There is apparently no generic driver. I have
already discovered that getting information from the developer is
impossible. There is a suggestion that it might be possible to access
the device with libusb, but I have not looked into that yet.
That just means that the fx2 initially loaded some firmware from an
on-board flash chip. This is certainly the case, as without firmware the
FX2 announces itself with VID/PID 04b4:8613. The VID/PID you saw is also
documented here: https://sigrok.org/wiki/QuantAsylum_QA100/Info
Did that VID/PID change on windows? If so, that means something on your
windows computer (a QuantAsylum driver) uploaded firmware to it.
If you capture that upload, you have the FX2's firmware. If you capture
the QuantAsylum software on Windows talking to that firmware, you have
the protocol.
But even if possible, it would be difficult to go further without
any information about the protocol. Not a good start and the odds of
getting anywhere seem a bit steep.
Oh no, that's not at all a problem. Many (most?) sigrok drivers were
written only after reverse engineering the protocol. It's the most fun
part of writing a driver, and not that hard.
--
Bert Vermeulen
[email protected]
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
