Send USRP-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."


Today's Topics:

   1. USRP2 to Simulink communication failure - RAMMA SHAMI
      (Rammah Shami)
   2. Re: USRP2 to Simulink communication failure - RAMMA SHAMI
      (Jason Abele)
   3. UHD Announcement - March 18th 2011 (Josh Blum)
   4. Regarding 10Mhz External Clock for USRP2 (abhinav anand)


----------------------------------------------------------------------

Message: 1
Date: Fri, 18 Mar 2011 17:10:18 -0000
From: "Rammah Shami" <[email protected]>
To: [email protected]
Subject: [USRP-users] USRP2 to Simulink communication failure - RAMMA
        SHAMI
Message-ID:
        <441573c3e84b6bc798c87d1ae7feffc1.squir...@www.squirrelmail.ucl.ac.uk>
Content-Type: text/plain;charset=iso-8859-1


Dear Users,

 I am currenly a research student at University College London (Department
of Security Science/Physics/EE). My current project requires the use of a
USRP2 reciever with Simulink. I came across a post which was similar to a
problem I am experiencing:
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2011-January/000433.html


I am having the exact same problem documented by "yqluo", except I am
having it despite downloading the relevant firmware:
http://www.mathworks.com/support/solutions/en/data/1-CUN7JZ/?solution=1-CUN7JZ


My Method:

I have a new Kingston SD card(identical to the one provided with the USRP2
device)
I have a FujiFilm SD/HC, USB 2.0 Card Reader

With the card reader inserted into my computer (running Windows 7
profesional) I follow the steps given in the site above. I can complete
the task - both catogeries are verified and testes passed.

However, when I insert this into the USRP2, only the 'F' light is on, the
others do not flicker on boot-up and lights 'D&E' remain off - which seeing
the USRP2's operation on GNUradio software I know should be ON!
When trying to run the receiver mode demos on MatLab, I get a message
saying that communication is not possible -
xxxxxxxxxxxxxxxxxxxxxxxx
Embedded MATLAB Runtime Error: Board did not reply to a host query or
configuration. Cannot run simulation. Please ensure you have a connection by
opening the block mask and examining the Hardware section.
xxxxxxxxxxxxxxxxxxxxxxxx (as shown on the forum)

Have I forgotten anything? Do I need to install some basic GNU firmware
before using the Simulink dedicated ones or something?


-- 
Rammah Shami

MRes/PhD Taught Doctoral student

UCL SECReT Doctorate training centre
Jill Dando institute and department of Security and Crime Science
Brook House
2-16 Torrington Place
London
WC1E 7HN
http://www.cscs.ucl.ac.uk/







------------------------------

Message: 2
Date: Fri, 18 Mar 2011 10:49:48 -0700
From: Jason Abele <[email protected]>
To: Rammah Shami <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] USRP2 to Simulink communication failure -
        RAMMA SHAMI
Message-ID: <20110318174948.GR2526@manzanita>
Content-Type: text/plain; charset=us-ascii

> However, when I insert this into the USRP2, only the 'F' light is on, the
> others do not flicker on boot-up and lights 'D&E' remain off - which seeing
> the USRP2's operation on GNUradio software I know should be ON!

Correct, so then either your SD card is incompatible or you have an
error programming the SD card.

Please try programming the card again.  Also, be sure you are using the
SD sold by Ettus Research.  More modern SD cards are known to not work
and even cards that look the same can be very different inside.  It is
the unfortunate nature of the SD card market

Jason



------------------------------

Message: 3
Date: Fri, 18 Mar 2011 17:36:44 -0700
From: Josh Blum <[email protected]>
To: "[email protected]" <[email protected]>,
        "[email protected]" <[email protected]>
Subject: [USRP-users] UHD Announcement - March 18th 2011
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Hello list,

New code has been pushed to master and new images have been uploaded.
This effects USRP2, USRP-N210, and USRP-E100.
http://www.ettus.com/downloads/uhd_images/UHD-images-most-recent/

E100 Users: expect a follow-up announcement for an updated kernel and
instructions.

-----------------------------------------------------------------------
-- Stability
-----------------------------------------------------------------------
The gr-uhd component is now part of the gnuradio master branch; the
gnuradio-master branch and the uhd master branch are now compatible.

At this point, we intend to keep the master branch of UHD stable. The
master branch will only be changed for bug fixes, and new hardware
support. Other than that, API and implementation code will not be changed.

After an initial trial period to discover bugs and provide fixes, we
plan to provide UHD installers for the various platforms (rpm, deb, exe).

-----------------------------------------------------------------------
-- New feature - second DDC in USRP2 and N210
-----------------------------------------------------------------------
The USRP2 and N210 now features a second receiver chain the FPGA. This
will allow one to simultaneously receive from daughterboards with
multiple subdevices (Ex: Basic-RX, TVRX2). Or, have two channels with
different frequency offsets on one subdevice. Both channels will have
the same sample rate.

To use the second receiver, set the appropriate RX subdevice
specification. For example, to get get subdevice A on channel 0 and
subdevice B on channel 1 on a BasicRX, use ":A :B". The behavior is
identical for anyone using multi channel UHD on a USRP1.

There is also a multi-channel receive example in uhd:
http://code.ettus.com/redmine/ettus/projects/uhd/repository/revisions/master/entry/host/examples/rx_multi_samples.cpp

-----------------------------------------------------------------------
-- New feature - jumbo frames with USRP2 and N210
-----------------------------------------------------------------------
After some refactoring of the buffering in the device, we have not only
freed additional block rams, but the internal buffering now supports
larger frames sizes up to 4K. In order to use jumbo frames, you must
have an ethernet card that supports the large frame size. Usually this
can be set with ifconfig <dev> mtu <size>

The default frame size will not exceed 2K unless the user overrides this
with special transport options:
http://www.ettus.com/uhd_docs/manual/html/transport.html#udp-transport-sockets

-----------------------------------------------------------------------
Testing and feedback is always welcome!

Thanks,
-Josh



------------------------------

Message: 4
Date: Sat, 19 Mar 2011 04:38:50 -0700
From: abhinav anand <[email protected]>
To: [email protected]
Subject: [USRP-users] Regarding 10Mhz External Clock for USRP2
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

Hi Group,

I am in a need of using a function generator to provide 10Mhz reference
clock to USRP2. I am using *standalone UHD*
with USRP2, and not the Gnuradio-UHD.

I want to know how to *enable locking* in USRP2 to use 10Mhz external clock
instead of 100Mhz internal one.
Is there any python script to be executed or any firmware change in UHD
required for the same ??

Please suggest me a way to do it.


Thanks,

Abhinav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20110319/59b5df21/attachment-0001.html>

------------------------------

_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com


End of USRP-users Digest, Vol 7, Issue 32
*****************************************

Reply via email to