I tested the usrp2 using uhd_usrp_probe, why is there a warning about
unknown dboard-id or dboard-id combination and Unknown value for RX
Subdev and TX Subdev (antenna?)?is there some miss when I assembled the
device?or it’s needed to configure through software?
[[email protected] host]# /usr/local/bin/uhd_usrp_probe
Current recv sock buff size: 50000000 bytes
Current send sock buff size: 50000000 bytes
Warning: unknown dboard-id or dboard-id combination: unknown (0x0002)
-> defaulting to the unknown board type
Warning: unknown dboard-id or dboard-id combination: unknown (0xffff)
-> defaulting to the unknown board type
Using: Unknown - unknown (0x0002)
Using: Unknown - unknown (0xffff)
RX samples per packet: 362
TX samples per packet: 363
Recv pirate num frames: 33967
The dbsrx is not yet supported under UHD. That is why dboard id 0x0002
is not recognized. Our daughterboard engineer is working on it this very
day; though I cannot make promises as to its release.
Is my impression right, that the dboard id 2 is for the original dbsrx
variant
and the dboard id 13 ist for the usrp2 patched variant?
I was wondering if the programming was successful or not.
The modification instructions have no comment about this.
With the id 13 now it’s working with the ursp2 (standard driver).
I just understand the different of UHD based and USRP2-gnuradio, so
tried using non-uhd firmware and fpga (txrx_raw_eth_20100608.bin,
u2_rev3-20100603.bin) on sd card, and run usrp2_fft.py, it works as gui
is shown up. But I still see 0x002 displayed there (in bottom of window,
between “[email protected]” and “analog bb”).
And also, I am very newbie on this stuff so probably following question
would be silly here. I tried to read the link for clock modification but
had no idea what it’s talking about (what to be removed?), do you have
link with comprehensive picture? And as usrp2_fft.py is working now, do
I still need to modify the clock?what’s the effect?
Is my impression right, that the dboard id 2 is for the original dbsrx variant
and the dboard id 13 ist for the usrp2 patched variant?
Yes
I was wondering if the programming was successful or not.
The modification instructions have no comment about this.
With the id 13 now it’s working with the ursp2 (standard driver).
If it reads ID #13 then it was successful.
Matt
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.