thunderscope identification chunk #222

New Issue

Open

opened 2022-01-04 00:09:27 +00:00 by profezzorn · 1 comment

profezzorn commented

2022-01-04 00:09:27 +00:00

(Migrated from github.com)

It would be great if we could have:

a magic number to identify without a doubt that we're talking to a thunderscope, not some other xilinx-based device.
hardware revision (major/minor)
firmware revision (major/minor)
serial number

Accessible from the USER handle. This would let us keep the software compatible if/when we make new versions of the hardware and firmware, and it would simplify enumeration and selection of scopes in those cases where is more than one scope present.

It would be great if we could have: 1. a magic number to identify without a doubt that we're talking to a thunderscope, not some other xilinx-based device. 2. hardware revision (major/minor) 3. firmware revision (major/minor) 4. serial number Accessible from the USER handle. This would let us keep the software compatible if/when we make new versions of the hardware and firmware, and it would simplify enumeration and selection of scopes in those cases where is more than one scope present.

profezzorn commented

2022-01-05 08:25:05 +00:00

(Migrated from github.com)

One more thing that would be handy to get from the scope somehow: The size of the RAM buffer that we're fetching data from.
It could just be a table in the client based on the hardware major/minor I suppose, but getting it from the scope would be nice I think.

One more thing that would be handy to get from the scope somehow: The size of the RAM buffer that we're fetching data from. It could just be a table in the client based on the hardware major/minor I suppose, but getting it from the scope would be nice I think.