[USRP-users] problem with UHD driver 'no control response' and image burner for USRP2
john.malsbury at ettus.com
Tue Feb 14 18:50:25 EST 2012
This is a link from the UHD manual, which we link to from our Resources
page. This link describes, among other things, how to use the card
This link, also found in the UHD manual, describes where you can find
I will have to defer any Matlab specific questions to someone from
On 2/14/2012 3:31 PM, sam berhanu wrote:
> I am using the USRP2 hardware with simulink matlab version 2011b.
> what prompted for me to look for the latest firmware was that I was
> getting an error. The setup is as rudimentary as it could be, a sine
> wave from a signal generator received on the BasicX A port, but I keep
> getting the error:
> "could not execute UHD driver command in 'ReceiveData_C" RunTimeError.
> I am not really sure what that means. I am not doing anything exotic,
> just a simple receive on the radio of a sine wave at 45 MHz, power of
> -7 dbm.
> Another quesiton that is tied to the above though is:
> I went on the ettus website (which most previous links are no more
> there, please please fix the help or knowledge base section) to find
> the latest firmwares for the USRP2 at
> the image burner GUI I found from
> I installed first python, then tried to run the python burner. I tried
> to run the image burner for the gui but nothing seems to happen. I
> tried this on 4 different computers in the lab. What's bizarre is that
> I did this about two weeks ago. I would love for the instructions on
> how to burn the image onto the SD cards be found somewhere as the link
> is there no more
> I could definitely use specific information on how to get this thing
> going, i.e the error with the 'no control response'.
> I also would like to know how to correctly use the image burner.
> and another question I have,
> the data that I saw from the receive USRP2 block in simulink (2011a
> version with a different firmware than above and works relatively
> smoothly),- the frame size was set at 358 and couldn't be changed. the
> data type I was using for the block output was an int16 (signed). I
> felt as though there was no Q channel information even though both the
> I & Q paths were connected to QPSK modulated signal paths. it felt as
> if the channel concatanated the 16 wide I and 16 wide Q and sent on
> the firmware with 2011b but the 2011a version I was using completely
> ignored the Q channel.
> Would be great if someone could inform how the data is exactly sent? (
> i realize they are interleaved IQ but does that mean 8I8Q for int16 or
> does it mean [16I16Q] 358 samples?
> sorry for rambling...i know i'm a noob but someone has to start somewhere
> USRP-users mailing list
> USRP-users at lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the USRP-users