Ok.
Didn't think it would be in there. Ran the script and it seems to be
working correctly now. The bcdDevice is now 1.04 though. I assume this
is correct. Looks like it only takes the 4 from the value.
Thanks so much for the help guys.
Regards
Craig Tong
Radar Remote Sensing
Hi
bcdDevice is 0.00 for the verbose lsusb output. Also there doesn't seem
to a be a burn-usrp4-eeprom anymore but there is a burn-db-eeprom,
unless I'm missing something.
Craig Tong
Radar Remote Sensing Group
University of Cape Town
On 23/07/2010 19:49, Thomas Tsou wrote:
On F
Hi Philip
its 712
Craig Tong
Radar Remote Sensing Group
University of Cape Town
On 23/07/2010 15:36, Philip Balister wrote:
On 07/23/2010 04:51 AM, Craig Tong wrote:
This USRP has been here since before my time but the other guys in the
lab seem to think that it was bought directly from
ffe:0002
similar to lsusb for the working USRP.
Craig Tong
Radar Remote Sensing Group
University of Cape Town
On 22/07/2010 20:15, Thomas Tsou wrote:
On Thu, Jul 22, 2010 at 4:35 AM, Craig Tong wrote:
Hi,
Thanks for the help, I tracked through the functions that are used to load
up the f
4 so my code seems to work correctly.
Is this likely to be an EPROM corruption ?
Craig Tong
Radar Remote Sensing Group
University of Cape Town
On 21/07/2010 19:15, Thomas Tsou wrote:
On Wed, Jul 21, 2010 at 1:36 AM, Craig Tong wrote:
Hi,
I'm having some trouble getting my USRP
Hi,
I'm having some trouble getting my USRP board running with just about
any software. It always seems to die with "Can't find firmware:
std.ihx". I've tried a whole array of applications including usrp_fft.py
and similar, usrp_probe and then also the C++ progs
(test_usrp_standard_rx and the
