On 10/08/2020 12:51 PM, David Taylor (manx.net) via USRP-users wrote:
Thanks Marcus,
I have had a look at the GPIO example source. It contains some useful
code, but I have not compiled and run it.
Other example code in “Synchronising USRP Events using Timed Commands
(17 April 2020)” has been used in the OOT block.
1) I have configured my B210(NI) EEPROM with the correct USB vid =
0x2500 and pid = 0x0814.
The device is clearly identifiable and usable over USB3.
2). I have tried to identify the USRP using the following code prior
to making an object:-
uhd:: device_addr_t hint;
hint[“serial”] = “3150322”;
uhd:: device_addrs_t dev_addrs = uhd:: device::find(hint);
3). Or the following to create the object directly:-
uhd::usrp::multi_usrp:: sptr device =
uhd::usrp::multi_usrp::make(“vid=0x2500, pid=0x7814”);
The codes are placed in the OOT constructor, compile and link with the
appropriate headers.
In both cases the flow-graph fails to run with the usual ‘block’
attribute error message. There are no USRP source or sink blocks in
the flow-graph that could possibly conflict.
Regards,
David
COuld you just use one of the standard test tools like
"rx_samples_to_file" and specify "type=b200" in the device arguments?
There should NEVER have been any reason to change the VID and PID on the
device.
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
