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. Streaming 50Mhz - Multiple Channels ([email protected])
2. Re: Streaming 50Mhz - Multiple Channels (Josh Blum)
3. UHD and flash install problem (Michael Hartje)
4. E100 : e1xx-003 image problem: specified model string "E" is
not recognized (Richard Clarke)
5. Re: UHD and flash install problem (Josh Blum)
6. Re: E100 : e1xx-003 image problem: specified model string "E"
is not recognized (Josh Blum)
7. Re: E100 : e1xx-003 image problem: specified model string "E"
is not recognized (Richard Clarke)
8. Re: E100 : e1xx-003 image problem: specified model string "E"
is not recognized (Josh Blum)
9. Re: E100 : e1xx-003 image problem: specified model string "E"
is not recognized (Richard Clarke)
10. Re: Fwd: problem with the firmware update of a USRP2
(iratxe.redondo)
11. loading fpga image (Ahmed Alsawi)
12. Re: loading fpga image (Josh Blum)
----------------------------------------------------------------------
Message: 1
Date: Thu, 12 Apr 2012 21:42:43 +0200
From: "[email protected]" <[email protected]>
To: "usrp" <[email protected]>
Subject: [USRP-users] Streaming 50Mhz - Multiple Channels
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
Hi,
I was wondering what exactly has to be done to stream 50 Mhz of bandwidth.
As far as I can tell from the documentation using
stream_args("sc16", "sc16"); should work on the N210 to stream 50Mhz.
However even when using sc8 as the wire format the bandwidth utilization is 80%
of the full duplex gbit link. With sc16 I do get constant overflows.
Additionally, is there any code or future planned support to automatically
split the bandwidth into multiple
channels on the FPGA already?
Say receiving 2 1mbit streams 10mhz apart without getting the data in between?
Thanks
------------------------------
Message: 2
Date: Thu, 12 Apr 2012 12:53:29 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Streaming 50Mhz - Multiple Channels
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 04/12/2012 12:42 PM, [email protected] wrote:
> Hi,
>
> I was wondering what exactly has to be done to stream 50 Mhz of bandwidth.
> As far as I can tell from the documentation using
> stream_args("sc16", "sc16"); should work on the N210 to stream 50Mhz.
>
> However even when using sc8 as the wire format the bandwidth utilization is
> 80%
> of the full duplex gbit link. With sc16 I do get constant overflows.
>
You have to select sc8 mode to stream 50Msps.
sc16 = 32bits per complex sample
32 bits/samp * 50 Msamps/s > 1 gigabit/s
>
> Additionally, is there any code or future planned support to automatically
> split the bandwidth into multiple
> channels on the FPGA already?
> Say receiving 2 1mbit streams 10mhz apart without getting the data in between?
>
The USRP has 2 RX DSP chains for this purpose.
See rx_multi_samples.cpp as an example
-josh
------------------------------
Message: 3
Date: Thu, 12 Apr 2012 21:59:10 +0200
From: Michael Hartje <[email protected]>
To: [email protected]
Subject: [USRP-users] UHD and flash install problem
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
I sent the follwing to discuss-gnuradio-list -- but it has never been
published..
so I will try it here:
After compiling Gnuradio 3.5.3, I got errors (seg faults) and other
indication to upgrade the very old uhd and fpga firmware software for
USRP N200 r2.
I got the images 003.004.000 and uhd source. I compiled and installed
the source on ubuntu 11.10
every step as expected from the building guides.
But trying to update the firmware-fpga fails
After powerdown und hold S2, the N200 did work with the follwing output
-------------------8<------------------
> ./usrp_n2xx_net_burner.py --addr=192.168.10.2
> --fw=uhd-images_003.004.000-release/share/uhd/images/usrp_n200_fw.bin
> USRP-N2XX found.
> Flash size: 4194304
> Sector size: 65536
>
> Begin firmware write: this should take about 1 second...
> Erasing 31744 bytes at 3145728
> Writing image
> Verifying data
> Read back 16383 bytes
> Success.
> Time elapsed: 1.149688 seconds
>
> ./usrp_n2xx_net_burner.py --addr=192.168.10.2
> --fpga=uhd-images_003.004.000-release/share/uhd/images/usrp_n200_r2_fpga.bin
>
>
> USRP-N2XX found.
> Flash size: 4194304
> Sector size: 65536
>
> Begin FPGA write: this should take about 1 minute...
> Erasing 1572864 bytes at 1572864
> Traceback (most recent call last):
> File "./usrp_n2xx_net_burner.py", line 522, in <module>
> else: burner.burn_fw(fw=options.fw, fpga=options.fpga,
> reset=options.reset, safe=options.overwrite_safe, check_rev=not
> options.dont_check_rev)
> File "./usrp_n2xx_net_burner.py", line 310, in burn_fw
> self.erase_image(image_location, FPGA_IMAGE_SIZE_BYTES)
> File "./usrp_n2xx_net_burner.py", line 452, in erase_image
> in_pkt = self.send_and_recv(out_pkt)
> File "./usrp_n2xx_net_burner.py", line 245, in send_and_recv
> return self._sock.recv(UDP_MAX_XFER_BYTES)
> socket.timeout: timed out
-------------------8<------------------
this leaves the system without the expeceted functionality
help is very welcome to get the system working again
thanks in advance
Michael Hartje
--
Prof. Dr.-Ing. Michael Hartje
Labor Hochspannungstechnik / Labor elektrische Messtechnik
Neustadtswall 30; D-28199 Bremen
Tel +49 421 5905-3444 FAX +49 421 5905-3476
------------------------------
Message: 4
Date: Fri, 13 Apr 2012 15:51:38 +1200
From: Richard Clarke <[email protected]>
To: [email protected]
Subject: [USRP-users] E100 : e1xx-003 image problem: specified model
string "E" is not recognized
Message-ID:
<CAAWhvb1VXfQ2jOiMDFNOzmXu8UBfpmMrwCxj+u=yw7shpkp...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
a few days ago I update my sd card image to the latest and greatest version
3 image for the E100, using the MakeEttusSDCard.sh script to do all the
partitioning, formatting and image writing. I've just tried to run some of
the example/utility scripts to make sure everything was working as before,
however I'm getting the following error when I run "uhd_usrp_probe":
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.004.000-0-unknown
-- Opening device node /dev/usrp_e0...
Error: RuntimeError:
The specified model string "E" is not recognized.
Perhaps the EEPROM is uninitialized, missing, or damaged.
Or, a monitor is pirating the I2C address of the EEPROM.
Can anyone shed any light on what might be going on?
Thanks very much
Cheers
Richard
--
*SCOTT ADAMS: Normal people believe that if it ain't broke, don't fix it.
Engineers believe that if it ain't broke, it doesn't have enough features
yet.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120413/b0e5f98b/attachment-0001.html>
------------------------------
Message: 5
Date: Thu, 12 Apr 2012 21:07:48 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] UHD and flash install problem
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
>> Begin FPGA write: this should take about 1 minute...
>> Erasing 1572864 bytes at 1572864
>> Traceback (most recent call last):
>> File "./usrp_n2xx_net_burner.py", line 522, in <module>
>> else: burner.burn_fw(fw=options.fw, fpga=options.fpga,
>> reset=options.reset, safe=options.overwrite_safe, check_rev=not
>> options.dont_check_rev)
>> File "./usrp_n2xx_net_burner.py", line 310, in burn_fw
>> self.erase_image(image_location, FPGA_IMAGE_SIZE_BYTES)
>> File "./usrp_n2xx_net_burner.py", line 452, in erase_image
>> in_pkt = self.send_and_recv(out_pkt)
>> File "./usrp_n2xx_net_burner.py", line 245, in send_and_recv
>> return self._sock.recv(UDP_MAX_XFER_BYTES)
>> socket.timeout: timed out
>
Looks like a packet is lost during the burning process. Can you try this
with a different PC or ethernet card? Does the problem follow?
-josh
------------------------------
Message: 6
Date: Thu, 12 Apr 2012 21:09:16 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] E100 : e1xx-003 image problem: specified
model string "E" is not recognized
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 04/12/2012 08:51 PM, Richard Clarke wrote:
> Hi,
>
> a few days ago I update my sd card image to the latest and greatest version
> 3 image for the E100, using the MakeEttusSDCard.sh script to do all the
> partitioning, formatting and image writing. I've just tried to run some of
> the example/utility scripts to make sure everything was working as before,
> however I'm getting the following error when I run "uhd_usrp_probe":
>
> linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
> UHD_003.004.000-0-unknown
>
> -- Opening device node /dev/usrp_e0...
> Error: RuntimeError:
> The specified model string "E" is not recognized.
> Perhaps the EEPROM is uninitialized, missing, or damaged.
> Or, a monitor is pirating the I2C address of the EEPROM.
>
> Can anyone shed any light on what might be going on?
>
Its having trouble reading the EEPROM. Do you have a monitor attached?
If so, does the problem go away when you detach the monitor.
-Josh
------------------------------
Message: 7
Date: Fri, 13 Apr 2012 16:24:05 +1200
From: Richard Clarke <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [USRP-users] E100 : e1xx-003 image problem: specified
model string "E" is not recognized
Message-ID:
<CAAWhvb1q1AV_Qc0esWeyP6vT4AqKDP46h3=auzccgnbrtun...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Thanks for that Josh, that does indeed seem to be the problem. Is there any
work around to allow me to use the E100 with my current monitor or do I
need to hunt out another monitor to use it with? I have successfully used
it with a different monitor previously but don't have that anymore.
Thanks
Cheers
Richard
On 13 April 2012 16:09, Josh Blum <[email protected]> wrote:
>
>
> On 04/12/2012 08:51 PM, Richard Clarke wrote:
> > Hi,
> >
> > a few days ago I update my sd card image to the latest and greatest
> version
> > 3 image for the E100, using the MakeEttusSDCard.sh script to do all the
> > partitioning, formatting and image writing. I've just tried to run some
> of
> > the example/utility scripts to make sure everything was working as
> before,
> > however I'm getting the following error when I run "uhd_usrp_probe":
> >
> > linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
> > UHD_003.004.000-0-unknown
> >
> > -- Opening device node /dev/usrp_e0...
> > Error: RuntimeError:
> > The specified model string "E" is not recognized.
> > Perhaps the EEPROM is uninitialized, missing, or damaged.
> > Or, a monitor is pirating the I2C address of the EEPROM.
> >
> > Can anyone shed any light on what might be going on?
> >
>
> Its having trouble reading the EEPROM. Do you have a monitor attached?
> If so, does the problem go away when you detach the monitor.
>
> -Josh
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
--
*SCOTT ADAMS: Normal people believe that if it ain't broke, don't fix it.
Engineers believe that if it ain't broke, it doesn't have enough features
yet.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120413/e16c6c76/attachment-0001.html>
------------------------------
Message: 8
Date: Thu, 12 Apr 2012 21:44:44 -0700
From: Josh Blum <[email protected]>
To: Richard Clarke <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] E100 : e1xx-003 image problem: specified
model string "E" is not recognized
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 04/12/2012 09:24 PM, Richard Clarke wrote:
> Thanks for that Josh, that does indeed seem to be the problem. Is there any
> work around to allow me to use the E100 with my current monitor or do I
> need to hunt out another monitor to use it with? I have successfully used
> it with a different monitor previously but don't have that anymore.
>
So, the gumstix module shares an i2c line with the HDMI and eeprom.
Unfortunately, you have a monitor that is responding on an address it
shouldn't. Even if we could get UHD to bypass having to read the eeprom,
there is critical stuff in the eeprom used by the bootloader.
So, unless there is such a thing as a fw update for your monitor that
fixes this, you probably have to find a different monitor for use with E100.
-josh
------------------------------
Message: 9
Date: Fri, 13 Apr 2012 16:58:51 +1200
From: Richard Clarke <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [USRP-users] E100 : e1xx-003 image problem: specified
model string "E" is not recognized
Message-ID:
<caawhvb3wvgcycc4a6damxvp2tvnn-nda6u1votc2rtk8pvu...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Ok, many thanks Josh.
Cheers
Richard
On 13 April 2012 16:44, Josh Blum <[email protected]> wrote:
>
>
> On 04/12/2012 09:24 PM, Richard Clarke wrote:
> > Thanks for that Josh, that does indeed seem to be the problem. Is there
> any
> > work around to allow me to use the E100 with my current monitor or do I
> > need to hunt out another monitor to use it with? I have successfully used
> > it with a different monitor previously but don't have that anymore.
> >
>
> So, the gumstix module shares an i2c line with the HDMI and eeprom.
> Unfortunately, you have a monitor that is responding on an address it
> shouldn't. Even if we could get UHD to bypass having to read the eeprom,
> there is critical stuff in the eeprom used by the bootloader.
>
> So, unless there is such a thing as a fw update for your monitor that
> fixes this, you probably have to find a different monitor for use with
> E100.
>
> -josh
>
--
*SCOTT ADAMS: Normal people believe that if it ain't broke, don't fix it.
Engineers believe that if it ain't broke, it doesn't have enough features
yet.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120413/41c3d47b/attachment-0001.html>
------------------------------
Message: 10
Date: Fri, 13 Apr 2012 09:14:19 +0200
From: "iratxe.redondo" <[email protected]>
To: <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Fwd: problem with the firmware update of a
USRP2
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
problem solved!!!! thank you very much for your help!!!
On Wed, 11 Apr 2012 21:24:44 -0700, Josh Blum <[email protected]> wrote:
> If its simpler:
>
> http://pastebin.com/TssEFfqv
>
> or
>
> http://pastebin.com/XjU73dCU
>
> -Josh
>
> On 04/11/2012 07:56 AM, [email protected] wrote:
>>
>>
>> A user actually found that this mod fixed this problem:
>>
>> Just now
>> I modified the usrp2_card_burner_gui.py by adding the following codes:
>>
>> "import sys
>> default_encoding = 'utf-8'
>> if sys.getdefaultencoding() !=
>> default_encoding:
>> reload(sys)
>>
>> sys.setdefaultencoding(default_encoding)"
>>
>> On Wed, 11 Apr 2012 06:33:45
>> -0700, Nick Foster wrote:
>>
>>> On Wed, Apr 11, 2012 at 2:39 AM,
>> iratxe.redondo wrote:
>>>
>>>> Hi,
>>>>
>>>> I?m trying to update the firmware
>> and fpga images of my USRP2 with ubuntu 11.10, and after creating the
>> firmware image in the zpu carpet without problems when I do sudo
>> ./usrp2_card_burner.py --dev=dev/sdb
>> --fpga=/home/tecnalia/uhd/firmware/zpu/build/usrp2/ursp2_txrx_uhd.bin it
>> appears the next error "'ascii' codec can?t decode byte 0xc3 in position
>> 17: ordinal not in range(128). i?ve confirmed that the path to dev is
>> correct.
>>>>
>>>> I?ve tried with the function usrp2_card_burner_gui.py
>> but it also appears the same error. Can someone help me??Thanks a
>> lot!!
>>>
>>> Try /dev/sdb instead of dev/sdb.
>>>
>>> --n
>>>
>>>>
>> _______________________________________________
>>>> USRP-users mailing
>> list
>>>> [email protected] [1]
>>>>
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com [2]
>>
>>
>>
>>
>> Links:
>> ------
>> [1] mailto:[email protected]
>> [2]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>> [3]
>> mailto:[email protected]
>>
>>
>>
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 11
Date: Fri, 13 Apr 2012 12:08:25 +0200
From: Ahmed Alsawi <[email protected]>
To: [email protected]
Subject: [USRP-users] loading fpga image
Message-ID:
<ca+9pi22vkortjcuxkxezb0uwo98ofw2mcqf1zg2pzn+fmks...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Dear all,
in this man page http://files.ettus.com/uhd_docs/manual/html/usrp_e1xx.html ,it
is said regarding E100 fpga image
UHD will automatically select the USRP-Embedded FPGA image from the
installed images package. The FPGA image selection can be overridden with
the *--fpga=* device address parameter.
which utility i pass --fpga to ?
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120413/65f51da1/attachment-0001.html>
------------------------------
Message: 12
Date: Fri, 13 Apr 2012 08:10:08 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] loading fpga image
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 04/13/2012 03:08 AM, Ahmed Alsawi wrote:
> Dear all,
> in this man page http://files.ettus.com/uhd_docs/manual/html/usrp_e1xx.html
> ,it
> is said regarding E100 fpga image
>
> UHD will automatically select the USRP-Embedded FPGA image from the
> installed images package. The FPGA image selection can be overridden with
> the *--fpga=* device address parameter.
>
> which utility i pass --fpga to ?
>
For the example apps, there is often a --args parameter to pass device
address as a string. Example --args="fpga=<path to new fpga.bin>"
When you use the C++ api:
device_address_t dev_addr;
dev_addr["fpga"] = "<path to new fpga.bin>";
multi_usrp::sptr usrp = multi_usrp::make(dev_addr);
-josh
------------------------------
_______________________________________________
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 13
******************************************
