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. Re: Time/Clock source and GPSDO (Josh Blum)
2. Re: network storage drive for N210 (Khalid Jamil)
3. Re: network storage drive for N210 ([email protected])
4. "Timed Commands" feature (Jason Roehm)
5. Re: "Timed Commands" feature (Josh Blum)
6. Problems building the B100 FPGA (Mark Cottrell)
7. Job openings that might interest list members (Marc Epard)
8. PLC and USRP (Deepjyoti Deka)
9. Re: Problems building the B100 FPGA (Ian Buckley)
10. Re: Problems building the B100 FPGA (Mark Cottrell)
11. How to connect USRP N210 to FPGA with Ethernet IP core via
Ethernet Phy chip? (Jiao Xianjun)
12. Re: Problems building the B100 FPGA (Ian Buckley)
13. USRP N210 using code without console output.
(Andrey Krasheninnikov)
14. GPSDO trouble (Nowlan, Sean)
15. Re: USRP N210 using code without console output. (Jason Roehm)
----------------------------------------------------------------------
Message: 1
Date: Mon, 02 Apr 2012 09:01:58 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Time/Clock source and GPSDO
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 03/31/2012 05:21 PM, John Shields wrote:
> (Ubuntu 10.04, UHD_003.004.000-1gea19de0b, GNURadio v3.5.2.1-61-gfc115e6a)
>
> I have a GPSDO equipped N210 Rev 4 and when I do a uhd_usrp_probe I get:
>
> gpsdo: internal
> ....
> Time Sources: none, external,_external_,mimo
> Clock Sources: internal, external, mimo
> Sensors: gps_gpgga, .... gps_time, gps_locked, mimo_locked, ref_locked
>
>
> but when I go to populate options in GRC, I get
>
> Clock Source: Default, Internal, External, MIMO cable, O/B GPSDO
> Time Source: Default, External, MIMO cable, O/B GPSDO
>
> For the paired/ganged USRP, which is connected to the master through a
> MIMO-cable, I put Clock and Time - MIMO but for the first it baulks at init
> time with set_clock_source("gpsdo",0).
>
> Back when I got the unit, I did the 'patch' to enable getting time from GPSDO
> in addition to PPS.
>
> Why would I not put Clock and Time source for master as "O/B
> GPSDO" and why doesn't it work?
>
To the the internal GPSDO, specify the "external" clock and time source.
The onboard gpsdo option in the GRC block was meant to compliment a
"gpsdo" source option that did not get implemented. The intention was
the "gpsdo" would alias the "external" setting when an onboard GPSDO is
present. FWIW, I still think implementing this is a good idea.
-josh
------------------------------
Message: 2
Date: Mon, 2 Apr 2012 21:08:25 +0300
From: Khalid Jamil <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] network storage drive for N210
Message-ID:
<CAMoB=ragh6ds9yzm8m-5sk-inrawqouwm16cx22bn9cear3...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Cc:
Date: Sun, 01 Apr 2012 16:23:06 -0400
Subject: Re: [USRP-users] network storage drive for N210
On 04/01/2012 04:16 PM, Khalid Jamil wrote:
> Hi,
>
> With the recent release of uhd driver, it is possible to stream date to a
> network location.
>
> Does this mean that we can use a network hard drive to stream/record data?
>
> Can anyone recommend an example system for this purpose?
>
> I have eight USRP N210s. Can I connect them to eight different network
> hard drives through a switch to store at the maximum data rate?
>
> Thanks,
>
> Khalid.
>
>
> > Only if you can convince your NAS to speak the VRT-inside-UDP protocol
that the N210 "speaks". But in principle, yes.
So, I understand that the packets will be sent to a
network-attached-storage device. The thing I don't understand how NAS will
put this data to a specific file?
What is VRT-inside-UDP, btw? What should I look for in the specifications
if I want to buy a NAS drive?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120402/5307b7f0/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 02 Apr 2012 14:15:10 -0400
From: [email protected]
To: <[email protected]>
Subject: Re: [USRP-users] network storage drive for N210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
There's isn't a NAS device on the planet that will "understand"
VRT-over-UDP. VRT is part of the Vita-49 protocol suite for carrying
digitized radio samples over network-like things.
You'd have to
"teach" it how to understand VRT-over-UDP (along with Ettus' little
tweaks). It would be up to the program you design to do this to decide
which files are created at which times, what your disk-resident sample
format should be, etc, etc.
The "send it somewhere else" feature in
the latest UHD code isn't particularly targetted at a NAS, it's just a
way to send the samples "somewhere else". You might need an ordinary
coimputer in front of your NAS to take the samples and turn them into
files for the NAS.
The source code for UHD is the ultimate reference
for how the wire protocols work.
-Marcus
On Mon, 2 Apr 2012 21:08:25
+0300, Khalid Jamil wrote:
> From: "Marcus D. Leech"
>
> To:
[email protected] [2]
>
> Cc:
>
> Date: Sun, 01 Apr 2012
16:23:06 -0400
>
> Subject: Re: [USRP-users] network storage drive for
N210
>
> On 04/01/2012 04:16 PM, Khalid Jamil wrote:
>
>> Hi,
>>
>>
With the recent release of uhd driver, it is possible to stream date to
a network location.
>>
>> Does this mean that we can use a network hard
drive to stream/record data?
>>
>> Can anyone recommend an example
system for this purpose?
>>
>> I have eight USRP N210s. Can I connect
them to eight different network hard drives through a switch to store at
the maximum data rate?
>>
>> Thanks,
>>
>> Khalid.
> > Only if you can
convince your NAS to speak the VRT-inside-UDP protocol that the N210
"speaks". But in principle, yes.
>
> So, I understand that the packets
will be sent to a network-attached-storage device. The thing I don't
understand how NAS will put this data to a specific file?
>
> What is
VRT-inside-UDP, btw? What should I look for in the specifications if I
want to buy a NAS drive?
Links:
------
[1]
mailto:[email protected]
[2] mailto:[email protected]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120402/4ad457ae/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 02 Apr 2012 14:35:54 -0400
From: Jason Roehm <[email protected]>
To: [email protected]
Subject: [USRP-users] "Timed Commands" feature
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I'm interested in using the timed commands functionality on my USRP
N200. Since it is still under development and I'm not interested in
being on the bleeding edge, I haven't pulled the "next" branch to try it
out. Based on Josh Blum's description of the feature in the last UHD
release announcement, it sounds very powerful. I had a couple questions
regarding what it will provide:
- Will queueing of timed commands be supported? I envision a scenario
where I want to tell my USRP to synchronously sweep across a specified
band of spectrum and collect fixed-length packets of samples. The
command sequence would look something like this:
- At time T, set RX tune frequency to 1 GHz
- At time T + 2 msec (or some other period of time, to allow the LO
to settle), issue stream command to stream N samples and then stop
- At time T + 2 msec + N/(Rx rate), set tune frequency to 1.01 GHz
- ...
It would be nice if I could program a whole sequence of these queued
commands into the USRP and allow it to execute a sweep almost
automatically. I understand that there would need to be at a minimum
some reasonable limit to the number of commands that be queued, but it
was unclear from the description whether multiple commands with
different execution times could be outstanding at any given time.
- Can timed commands be interleaved with un-timed commands? For
instance, if I tell the USRP to tune to a new frequency in 10 msec, can
I issue other commands in the meantime that will be executed immediately?
Thanks for reading.
Jason
------------------------------
Message: 5
Date: Mon, 02 Apr 2012 12:30:40 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] "Timed Commands" feature
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 04/02/2012 11:35 AM, Jason Roehm wrote:
> I'm interested in using the timed commands functionality on my USRP
> N200. Since it is still under development and I'm not interested in
> being on the bleeding edge, I haven't pulled the "next" branch to try it
> out. Based on Josh Blum's description of the feature in the last UHD
> release announcement, it sounds very powerful. I had a couple questions
> regarding what it will provide:
>
> - Will queueing of timed commands be supported? I envision a scenario
> where I want to tell my USRP to synchronously sweep across a specified
> band of spectrum and collect fixed-length packets of samples. The
> command sequence would look something like this:
>
> - At time T, set RX tune frequency to 1 GHz
> - At time T + 2 msec (or some other period of time, to allow the LO
> to settle), issue stream command to stream N samples and then stop
> - At time T + 2 msec + N/(Rx rate), set tune frequency to 1.01 GHz
> - ...
>
> It would be nice if I could program a whole sequence of these queued
> commands into the USRP and allow it to execute a sweep almost
> automatically. I understand that there would need to be at a minimum
> some reasonable limit to the number of commands that be queued, but it
> was unclear from the description whether multiple commands with
> different execution times could be outstanding at any given time.
>
> - Can timed commands be interleaved with un-timed commands? For
> instance, if I tell the USRP to tune to a new frequency in 10 msec, can
> I issue other commands in the meantime that will be executed immediately?
>
The current implementation is basically a single command queue (64
entries). All commands back-up behind the newest command in queue, and
then after that it blocks in the host past 64 entries.
When a command is completed, the next packet in the queue is processed.
Any packets with "late" time are sent ASAP. This means that although you
get determinism, but poor scheduling can yield undesired results.
So, I you see how multiple queues might give greater flexibility. On the
other hand, it does use a non-trivial amount of resources. It would be
nice to see what can be done with one queue implementation first. :-)
-Josh
------------------------------
Message: 6
Date: Tue, 3 Apr 2012 09:55:37 +1200
From: Mark Cottrell <[email protected]>
To: [email protected]
Subject: [USRP-users] Problems building the B100 FPGA
Message-ID:
<cajv9sbeo7ahubyqjfsu4ssspwvrm5kxinsoo1dpsw8uhbhf...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I have been trying to build the unmodified B100 FPGA in order to verify my
build environment is set up correctly and working, before attempting to
build a modified FPGA. However, I have not been having much luck.
I am using Xilinx ISE WebPACK 13.4 in Ubuntu 10.04 x64 and uhd
release_003_004_000-24-g8630807. As far as I can tell nothing failed
during the build, but there were a lot of warnings. At the end of the
build I get a B100.bin file that is 581KB (compared to the pre-built image,
which is 506KB), but when attempting to load this image into the FPGA
(using device_addr="fgpa=B100.bin") I am unsuccessful and get the errors in
the gnuradio_fpga_failure.log file. I have also attached the logs from the
FPGA build (b100_fpga_build.log.gz).
Any pointers as to what I could be doing wrong would be greatly appreciated.
Thanks,
Mark
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/a42fda66/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: b100_fpga_build.log.gz
Type: application/x-gzip
Size: 144921 bytes
Desc: not available
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/a42fda66/attachment-0001.gz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gnuradio_fpga_failure.log
Type: application/octet-stream
Size: 1728 bytes
Desc: not available
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/a42fda66/attachment-0001.log>
------------------------------
Message: 7
Date: Mon, 02 Apr 2012 17:27:09 -0500
From: Marc Epard <[email protected]>
To: [email protected]
Subject: [USRP-users] Job openings that might interest list members
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
We have two job openings here at Horizon Analog. We're a small outfit in
downtown Lawrence, Kansas, a great college town. One position is more RF
hardware oriented and one is more software and DSP related. We're developing
non-linear technology and use Ettus radios for a lot of our work, partially
with GNU Radio, partially with MATLAB, with some C++ and Verilog HDL for fun.
http://www.horizonanalog.com/Career_Opportunities.htm
-Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120402/5f769cfc/attachment-0001.html>
------------------------------
Message: 8
Date: Mon, 2 Apr 2012 21:08:31 -0500
From: Deepjyoti Deka <[email protected]>
To: [email protected]
Subject: [USRP-users] PLC and USRP
Message-ID:
<CAJ-7s1Z2dg2+CAS4bw23c21_XKyXDNaZZuRvjg=hakvwkdt...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi, I wanted to know if anyone has come across papers discussing coupler
design 9should be very basic) for using USRPs on LV side.
Thanks,
Deepjyoti
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120402/4cb549b6/attachment-0001.html>
------------------------------
Message: 9
Date: Mon, 2 Apr 2012 20:16:07 -0700
From: Ian Buckley <[email protected]>
To: Mark Cottrell <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Problems building the B100 FPGA
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Mark,
I build a lot of different USRP images but I never use B100 so I can only add
so much here.
Pre-built images from Ettus are currently built using ISE12, if I build B100
from next branch HEAD under ISE13.1 B100.bin it's 516K in size...I wouldn't
read too much into that in other words, you're unlikely to get a bit for bit
identical image from different ISE versions.
Building all the USRP's under ISE is very SPAMy I'm afraid, there are always
way too many spurious warnings..one day it will irritate me enough again that
I'll attack it, but for the moment it's expected behavior and it can conceal
important warnings when you're doing custom FPGA work. I did glance through and
grep your log file and I didn't see any glaring problems, it looks like a sane
build at first glance. Could there be a miss-match of firmware and FPGA image
perhaps ...are you build fimrware from teh same UHD version?
-Ian
On Apr 2, 2012, at 2:55 PM, Mark Cottrell wrote:
> I have been trying to build the unmodified B100 FPGA in order to verify my
> build environment is set up correctly and working, before attempting to build
> a modified FPGA. However, I have not been having much luck.
>
> I am using Xilinx ISE WebPACK 13.4 in Ubuntu 10.04 x64 and uhd
> release_003_004_000-24-g8630807. As far as I can tell nothing failed during
> the build, but there were a lot of warnings. At the end of the build I get a
> B100.bin file that is 581KB (compared to the pre-built image, which is
> 506KB), but when attempting to load this image into the FPGA (using
> device_addr="fgpa=B100.bin") I am unsuccessful and get the errors in the
> gnuradio_fpga_failure.log file. I have also attached the logs from the FPGA
> build (b100_fpga_build.log.gz).
>
> Any pointers as to what I could be doing wrong would be greatly appreciated.
>
> Thanks,
> Mark
> =======================================================================
> This email, including any attachments, is only for the intended
> addressee. It is subject to copyright, is confidential and may be
> the subject of legal or other privilege, none of which is waived or
> lost by reason of this transmission.
> If the receiver is not the intended addressee, please accept our
> apologies, notify us by return, delete all copies and perform no
> other act on the email.
> Unfortunately, we cannot warrant that the email has not been
> altered or corrupted during transmission.
> =======================================================================
>
> <b100_fpga_build.log.gz><gnuradio_fpga_failure.log>_______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 10
Date: Tue, 3 Apr 2012 17:19:40 +1200
From: Mark Cottrell <[email protected]>
To: Ian Buckley <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Problems building the B100 FPGA
Message-ID:
<cajv9sbgl8cjmztcfkspkuvxs-ynvu34ytyqdylgynx7lswb...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Ian,
Nick from Ettus sent me an email earlier saying that B100 build has only
been verified in ISE12.1, so I grabbed that and the image it produced
worked fine on my B100. I also built a very slightly modified FPGA which
seems to be working.
Thanks for your reply,
Mark
On Tue, Apr 3, 2012 at 3:16 PM, Ian Buckley <[email protected]> wrote:
> Mark,
> I build a lot of different USRP images but I never use B100 so I can only
> add so much here.
> Pre-built images from Ettus are currently built using ISE12, if I build
> B100 from next branch HEAD under ISE13.1 B100.bin it's 516K in size...I
> wouldn't read too much into that in other words, you're unlikely to get a
> bit for bit identical image from different ISE versions.
> Building all the USRP's under ISE is very SPAMy I'm afraid, there are
> always way too many spurious warnings..one day it will irritate me enough
> again that I'll attack it, but for the moment it's expected behavior and it
> can conceal important warnings when you're doing custom FPGA work. I did
> glance through and grep your log file and I didn't see any glaring
> problems, it looks like a sane build at first glance. Could there be a
> miss-match of firmware and FPGA image perhaps ...are you build fimrware
> from teh same UHD version?
> -Ian
>
> On Apr 2, 2012, at 2:55 PM, Mark Cottrell wrote:
>
> > I have been trying to build the unmodified B100 FPGA in order to verify
> my build environment is set up correctly and working, before attempting to
> build a modified FPGA. However, I have not been having much luck.
> >
> > I am using Xilinx ISE WebPACK 13.4 in Ubuntu 10.04 x64 and uhd
> release_003_004_000-24-g8630807. As far as I can tell nothing failed
> during the build, but there were a lot of warnings. At the end of the
> build I get a B100.bin file that is 581KB (compared to the pre-built image,
> which is 506KB), but when attempting to load this image into the FPGA
> (using device_addr="fgpa=B100.bin") I am unsuccessful and get the errors in
> the gnuradio_fpga_failure.log file. I have also attached the logs from the
> FPGA build (b100_fpga_build.log.gz).
> >
> > Any pointers as to what I could be doing wrong would be greatly
> appreciated.
> >
> > Thanks,
> > Mark
> > =======================================================================
> > This email, including any attachments, is only for the intended
> > addressee. It is subject to copyright, is confidential and may be
> > the subject of legal or other privilege, none of which is waived or
> > lost by reason of this transmission.
> > If the receiver is not the intended addressee, please accept our
> > apologies, notify us by return, delete all copies and perform no
> > other act on the email.
> > Unfortunately, we cannot warrant that the email has not been
> > altered or corrupted during transmission.
> > =======================================================================
> >
> >
> <b100_fpga_build.log.gz><gnuradio_fpga_failure.log>_______________________________________________
> > USRP-users mailing list
> > [email protected]
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/cd9f269f/attachment-0001.html>
------------------------------
Message: 11
Date: Tue, 3 Apr 2012 13:39:19 +0800
From: Jiao Xianjun <[email protected]>
To: [email protected]
Subject: [USRP-users] How to connect USRP N210 to FPGA with Ethernet
IP core via Ethernet Phy chip?
Message-ID:
<CABs6FUrEU_MONG2HKL7kd3U8F8S0Jtn1J=nedzzxpgxkwyu...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
Instead of computer, I want to use standalone FPGA to do signal processing.
I have a FPGA dev board with 1000M Ethernet port, and the board can
send/recv UDP packet with computer now.
If I want to use the FPGA board to control and use USRP N210 directly, what
should I do?
I have to implement a CPU in FPGA and run Linux on it? Or is there a simple
way?
Is there any information on protocol (between USRP and computer).?
Thanks!
BR
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/3ed48d22/attachment-0001.html>
------------------------------
Message: 12
Date: Mon, 2 Apr 2012 22:48:55 -0700
From: Ian Buckley <[email protected]>
To: Mark Cottrell <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Problems building the B100 FPGA
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Mark, All right I'll chat with Nick and put that in my low priority queue to go
look at, we need to get every thing migrated onto newer ISE versions soon.
-Ian
On Apr 2, 2012, at 10:19 PM, Mark Cottrell wrote:
> Hi Ian,
>
> Nick from Ettus sent me an email earlier saying that B100 build has only been
> verified in ISE12.1, so I grabbed that and the image it produced worked fine
> on my B100. I also built a very slightly modified FPGA which seems to be
> working.
>
> Thanks for your reply,
> Mark
>
> On Tue, Apr 3, 2012 at 3:16 PM, Ian Buckley <[email protected]> wrote:
> Mark,
> I build a lot of different USRP images but I never use B100 so I can only add
> so much here.
> Pre-built images from Ettus are currently built using ISE12, if I build B100
> from next branch HEAD under ISE13.1 B100.bin it's 516K in size...I wouldn't
> read too much into that in other words, you're unlikely to get a bit for bit
> identical image from different ISE versions.
> Building all the USRP's under ISE is very SPAMy I'm afraid, there are always
> way too many spurious warnings..one day it will irritate me enough again that
> I'll attack it, but for the moment it's expected behavior and it can conceal
> important warnings when you're doing custom FPGA work. I did glance through
> and grep your log file and I didn't see any glaring problems, it looks like a
> sane build at first glance. Could there be a miss-match of firmware and FPGA
> image perhaps ...are you build fimrware from teh same UHD version?
> -Ian
>
> On Apr 2, 2012, at 2:55 PM, Mark Cottrell wrote:
>
> > I have been trying to build the unmodified B100 FPGA in order to verify my
> > build environment is set up correctly and working, before attempting to
> > build a modified FPGA. However, I have not been having much luck.
> >
> > I am using Xilinx ISE WebPACK 13.4 in Ubuntu 10.04 x64 and uhd
> > release_003_004_000-24-g8630807. As far as I can tell nothing failed
> > during the build, but there were a lot of warnings. At the end of the
> > build I get a B100.bin file that is 581KB (compared to the pre-built image,
> > which is 506KB), but when attempting to load this image into the FPGA
> > (using device_addr="fgpa=B100.bin") I am unsuccessful and get the errors in
> > the gnuradio_fpga_failure.log file. I have also attached the logs from the
> > FPGA build (b100_fpga_build.log.gz).
> >
> > Any pointers as to what I could be doing wrong would be greatly appreciated.
> >
> > Thanks,
> > Mark
> > =======================================================================
> > This email, including any attachments, is only for the intended
> > addressee. It is subject to copyright, is confidential and may be
> > the subject of legal or other privilege, none of which is waived or
> > lost by reason of this transmission.
> > If the receiver is not the intended addressee, please accept our
> > apologies, notify us by return, delete all copies and perform no
> > other act on the email.
> > Unfortunately, we cannot warrant that the email has not been
> > altered or corrupted during transmission.
> > =======================================================================
> >
> > <b100_fpga_build.log.gz><gnuradio_fpga_failure.log>_______________________________________________
> > USRP-users mailing list
> > [email protected]
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
> =======================================================================
> This email, including any attachments, is only for the intended
> addressee. It is subject to copyright, is confidential and may be
> the subject of legal or other privilege, none of which is waived or
> lost by reason of this transmission.
> If the receiver is not the intended addressee, please accept our
> apologies, notify us by return, delete all copies and perform no
> other act on the email.
> Unfortunately, we cannot warrant that the email has not been
> altered or corrupted during transmission.
> =======================================================================
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120402/6e57d011/attachment-0001.html>
------------------------------
Message: 13
Date: Tue, 03 Apr 2012 13:32:13 +0400
From: Andrey Krasheninnikov <[email protected]>
To: [email protected]
Subject: [USRP-users] USRP N210 using code without console output.
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
In Windows I would like to use uhd.dll with GUI application without
output to console. Can I disable output to console (don't use instruction
"cout" and "cerr") for USRP N210?
Yours faithfully A.Krasheninnnikov
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/506136c7/attachment-0001.html>
------------------------------
Message: 14
Date: Tue, 3 Apr 2012 11:38:19 +0000
From: "Nowlan, Sean" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] GPSDO trouble
Message-ID: <195933287DC65748BA7AE867BA8E430B621768F3@apatlisdmbx02>
Content-Type: text/plain; charset="iso-8859-1"
I attempted to roll back from a recent git download of UHD (master branch) to
release 003.004.000-0. I'm observing weirdness with GPSDO. calling
usrp->get_mboard_sensor("gps_lock") returns locked, but "ref_lock" doesn't.
Also, running uhd/utils/test_pps_input gives an error:
Attempt to detect the PPS and set the time...
-- 1) catch time transition at pps edge
Error: RuntimeError: Board 0 may not be getting a PPS signal!
No PPS detected within the time interval.
See the application notes for your device.
Finally, I tried ./usrp_burn_mb_eeprom --args="addr=192.168.10.2" --key=gpsdo
--val=internal just in case this value had been hosed somehow, but it didn't
fix the problem.
Jumper is correct. Any idea what else might be happening? uhd_usrp_probe output
attached.
Thanks,
Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/8e8cac44/attachment-0001.html>
------------------------------
Message: 15
Date: Tue, 03 Apr 2012 08:42:54 -0400
From: Jason Roehm <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] USRP N210 using code without console output.
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
The UHD manual tells how to redirect the UHD's logging from stdout
through a handler function that you write, allowing you to make the
output go wherever you want:
http://files.ettus.com/uhd_docs/manual/html/general.html#disabling-or-redirecting-prints-to-stdout
Jason
On 04/03/2012 05:32 AM, Andrey Krasheninnikov wrote:
> In Windows I would like to use uhd.dll with GUI application without
> output to console. Can I disable output to console (don't use instruction
> "cout" and "cerr") for USRP N210?
>
>
> Yours faithfully A.Krasheninnnikov
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120403/22a5bac7/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 20, Issue 3
*****************************************
