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. R4, Expected FPGA compatibility number 9, but got 8
(Lapointe, Benjamin - 1008 - MITLL)
2. Re: R4, Expected FPGA compatibility number 9, but got 8
(Josh Blum)
3. Re: R4, Expected FPGA compatibility number 9, but got 8
(Lapointe, Benjamin - 1008 - MITLL)
4. Re: R4, Expected FPGA compatibility number 9, but got 8
(Josh Blum)
5. Timed Commands support image - compatibility number 10 (Marius)
6. E100 USB host reliability (Nathan Dumont)
7. Re: E100 USB host reliability (Patrik Tast)
8. Parsing GPSDO with gpsd (Joel Parker)
----------------------------------------------------------------------
Message: 1
Date: Mon, 7 May 2012 16:13:31 -0400
From: "Lapointe, Benjamin - 1008 - MITLL" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] R4, Expected FPGA compatibility number 9, but
got 8
Message-ID:
<mailman.50.1336492819.544.usrp-users_lists.ettus....@lists.ettus.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
I am getting the "Expected FPGA compatibility number 9, but got 8: The FPGA
build is not compatible with the host code build" error when I use
uhd_usrp_probe.
I am using UHD_003.004.000 with a USRP N210 R4.
I had previously modified the FPGA code by adding a custom module, and was
previously using a USRP N210 R3.
To move to a new USRP N210 R4 I made the following changes: included
capture_ddrlvds.v and set Verilog Macros to LVDS=1. I thought that worked
with a USRP N210 R4 that I was using. I am trying to load the FPGA firmware
onto a new N210 R4, and that is when I get the error mentioned above. I
verified that the updates to the FPGA code to support R4 were made, and I
still get the error.
Does anybody have an idea for how to fix this error?
Thanks,
-Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120507/e1e5c0b4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5414 bytes
Desc: not available
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120507/e1e5c0b4/attachment.p7s>
------------------------------
Message: 2
Date: Mon, 07 May 2012 13:24:10 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] R4, Expected FPGA compatibility number 9,
but got 8
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 05/07/2012 01:13 PM, Lapointe, Benjamin - 1008 - MITLL wrote:
> Hi,
>
>
>
> I am getting the "Expected FPGA compatibility number 9, but got 8: The FPGA
> build is not compatible with the host code build" error when I use
> uhd_usrp_probe.
>
>
>
> I am using UHD_003.004.000 with a USRP N210 R4.
>
>
>
> I had previously modified the FPGA code by adding a custom module, and was
> previously using a USRP N210 R3.
>
>
>
> To move to a new USRP N210 R4 I made the following changes: included
> capture_ddrlvds.v and set Verilog Macros to LVDS=1. I thought that worked
> with a USRP N210 R4 that I was using. I am trying to load the FPGA firmware
> onto a new N210 R4, and that is when I get the error mentioned above. I
> verified that the updates to the FPGA code to support R4 were made, and I
> still get the error.
>
>
>
> Does anybody have an idea for how to fix this error?
>
>
Take a look at the code you built from. What is the compat_num in
top/N2x0/u2plus_core.v? It should be 9 to work with the host code you
mentioned above.
-josh
------------------------------
Message: 3
Date: Mon, 7 May 2012 17:51:07 -0400
From: "Lapointe, Benjamin - 1008 - MITLL" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] R4, Expected FPGA compatibility number 9,
but got 8
Message-ID:
<mailman.51.1336492819.544.usrp-users_lists.ettus....@lists.ettus.com>
Content-Type: text/plain; charset="us-ascii"
Josh,
Thanks for the quick reply! My compat_num was 8, and I changed it to 9. I am
assuming the minor value in compat_num doesn't affect anything?
I now have no errors when I run uhd_usrp_probe.
Thanks,
-Ben
________________________________________
From: [email protected] [[email protected]]
On Behalf Of Josh Blum [[email protected]]
Sent: Monday, May 07, 2012 4:24 PM
To: [email protected]
Subject: Re: [USRP-users] R4, Expected FPGA compatibility number 9, but got 8
On 05/07/2012 01:13 PM, Lapointe, Benjamin - 1008 - MITLL wrote:
> Hi,
>
>
>
> I am getting the "Expected FPGA compatibility number 9, but got 8: The FPGA
> build is not compatible with the host code build" error when I use
> uhd_usrp_probe.
>
>
>
> I am using UHD_003.004.000 with a USRP N210 R4.
>
>
>
> I had previously modified the FPGA code by adding a custom module, and was
> previously using a USRP N210 R3.
>
>
>
> To move to a new USRP N210 R4 I made the following changes: included
> capture_ddrlvds.v and set Verilog Macros to LVDS=1. I thought that worked
> with a USRP N210 R4 that I was using. I am trying to load the FPGA firmware
> onto a new N210 R4, and that is when I get the error mentioned above. I
> verified that the updates to the FPGA code to support R4 were made, and I
> still get the error.
>
>
>
> Does anybody have an idea for how to fix this error?
>
>
Take a look at the code you built from. What is the compat_num in
top/N2x0/u2plus_core.v? It should be 9 to work with the host code you
mentioned above.
-josh
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 4
Date: Mon, 07 May 2012 15:19:41 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] R4, Expected FPGA compatibility number 9,
but got 8
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 05/07/2012 02:51 PM, Lapointe, Benjamin - 1008 - MITLL wrote:
> Josh,
>
> Thanks for the quick reply! My compat_num was 8, and I changed it to 9. I
> am assuming the minor value in compat_num doesn't affect anything?
>
minor doesnt matter, I just increment it when there are
fixes/non-breaking changes
However, simply changing the number to 9 isnt the real solution. There
are breaking compatibility changes when that number is incremented.
You should really pick a uhd commit and re-apply your custom changes.
Use the matching host code and images together.
-josh
> I now have no errors when I run uhd_usrp_probe.
>
> Thanks,
> -Ben
>
> ________________________________________
> From: [email protected] [[email protected]]
> On Behalf Of Josh Blum [[email protected]]
> Sent: Monday, May 07, 2012 4:24 PM
> To: [email protected]
> Subject: Re: [USRP-users] R4, Expected FPGA compatibility number 9, but got 8
>
> On 05/07/2012 01:13 PM, Lapointe, Benjamin - 1008 - MITLL wrote:
>> Hi,
>>
>>
>>
>> I am getting the "Expected FPGA compatibility number 9, but got 8: The FPGA
>> build is not compatible with the host code build" error when I use
>> uhd_usrp_probe.
>>
>>
>>
>> I am using UHD_003.004.000 with a USRP N210 R4.
>>
>>
>>
>> I had previously modified the FPGA code by adding a custom module, and was
>> previously using a USRP N210 R3.
>>
>>
>>
>> To move to a new USRP N210 R4 I made the following changes: included
>> capture_ddrlvds.v and set Verilog Macros to LVDS=1. I thought that worked
>> with a USRP N210 R4 that I was using. I am trying to load the FPGA firmware
>> onto a new N210 R4, and that is when I get the error mentioned above. I
>> verified that the updates to the FPGA code to support R4 were made, and I
>> still get the error.
>>
>>
>>
>> Does anybody have an idea for how to fix this error?
>>
>>
>
> Take a look at the code you built from. What is the compat_num in
> top/N2x0/u2plus_core.v? It should be 9 to work with the host code you
> mentioned above.
>
> -josh
>
> _______________________________________________
> 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: 5
Date: Tue, 8 May 2012 12:36:32 +0200
From: Marius <[email protected]>
To: [email protected]
Subject: [USRP-users] Timed Commands support image - compatibility
number 10
Message-ID:
<CAFKryZMGLsMpt1mXZd_5tdguDYff+0A=jjekzaiy0r2hime...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi!
I'm building an FPGA image for my USRP2s:
? ~/source/uhd/fpga/usrp2/top/USRP2/ master* git show
commit 869e5ff110a56c597acff5e493e603eef2bde366
Merge: 6ca39ad c42c02f
Author: Josh Blum <[email protected]>
Date: Wed Apr 25 19:15:21 2012 -0700
Merge branch 'maint'
When I make this I get into failed constraints
Process "Check Syntax" failed
INFO:TclTasksC:1850 - process run : Check Syntax is done.
python /home/marius/source/uhd/fpga/usrp2/top/python/check_timing.py
/home/marius/source/uhd/fpga/usrp2/top/USRP2/build/u2_rev3.twr
Derived Constraint Report
Derived Constraints for TS_clk_to_mac
+-------------------------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+
| | Period | Actual Period
| Timing Errors | Paths Analyzed |
| Constraint | Requirement
|-------------+-------------|-------------+-------------|-------------+-------------|
| | | Direct |
Derivative | Direct | Derivative | Direct | Derivative |
+-------------------------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+
|TS_clk_to_mac | 8.000ns| 5.987ns|
7.909ns| 0| 0| 0| 11618|
| TS_clk125_ext_clk0 | 8.000ns| 1.316ns|
N/A| 0| 0| 0| 0|
| TS_clk125_ext_clk180 | 8.000ns| 1.316ns|
N/A| 0| 0| 0| 0|
| TS_clk125_int | 8.000ns| 7.909ns|
N/A| 0| 0| 11618| 0|
+-------------------------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+
Derived Constraints for TS_clk_fpga_p
+-------------------------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+
| | Period | Actual Period
| Timing Errors | Paths Analyzed |
| Constraint | Requirement
|-------------+-------------|-------------+-------------|-------------+-------------|
| | | Direct |
Derivative | Direct | Derivative | Direct | Derivative |
+-------------------------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+
|TS_clk_fpga_p | 10.000ns| 5.987ns|
10.168ns| 0| 5| 6| 1212679|
| TS_dcm_out | 10.000ns| 10.168ns|
N/A| 5| 0| 1123887| 0|
| TS_clk_div | 20.000ns| 19.654ns|
N/A| 0| 0| 88792| 0|
+-------------------------------+-------------+-------------+-------------+-------------+-------------+-------------+-------------+
1 constraint not met.
Mainly I need the compatibility number 10, but the newest released build has 9.
Could someone build me an FPGA image, that works, or help me fix this issue?
Some nightly build here or something would do fine. I know it might be unstable.
Best,
Marius
------------------------------
Message: 6
Date: Tue, 8 May 2012 12:53:12 +0100
From: Nathan Dumont <[email protected]>
To: [email protected]
Subject: [USRP-users] E100 USB host reliability
Message-ID:
<cac4hy_otbfljxzdxvepkhzhf38zob_nevfx7x+4t8a+wrao...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
We've been running some processing and logging on an E100 with the latest
kernel images. To store the logged data we're using a USB hard disk or
flash drive (only need about 20MB/day). Unfortunately we're seeing random
disconnects, they happen infrequently (once or twice a day) and there's
nothing very helpful in the logs, it just lists a disconnect then
re-connect. We've tried a couple of different full USB-A from the USB-OTG
connector (not using OTG, using Host port), several different hard disk and
flash drive combos and now have a powered high-speed USB hub between the
USRP and peripherals. Anyone else seeing anything like this?
I disabled the auto-mounting probe on the drive to see if polling was
causing the disconnect but it doesn't seem to have been the cause of the
error (hal-disable-polling).
/usr/var/syslog:
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: state 7 ports 3 chg 0000 evt 0004
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: GetStatus port:2 status
001809 0 ACK POWER sig=j PEC CONNECT
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: port 2 enable change, status 00000501
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: port 2 disabled by hub (EMI?),
re-enabling...
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: port 2, status 0501, change 0002,
480 Mb/s
May 4 08:34:50 usrp-e1xx usb 2-2: USB disconnect, device number 15
May 4 08:34:50 usrp-e1xx usb 2-2.3: USB disconnect, device number 17
May 4 08:34:50 usrp-e1xx usb 2-2.3: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2.3: unregistering interface 2-2.3:1.0
May 4 08:34:50 usrp-e1xx usb 2-2.3: unlink qh256-0001/de0cc700 start 8
[1/0 us]
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: shutdown urb de0f7dc0
ep1in-intr
May 4 08:34:50 usrp-e1xx usb 2-2.3: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx usb 2-2.4: USB disconnect, device number 18
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: USB disconnect, device number 19
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: unregistering interface 2-2.4.2:1.0
May 4 08:34:50 usrp-e1xx FAT-fs (sda1): unable to read inode block for
updating (i_pos 244801)
May 4 08:34:50 usrp-e1xx usrp_e release called
May 4 08:34:50 usrp-e1xx Waiting for DMA to become inactive
May 4 08:34:50 usrp-e1xx Freeing gpio irq's
May 4 08:34:50 usrp-e1xx Freeing DMA channels
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx usb 2-2.4: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2.4: unregistering interface 2-2.4:1.0
May 4 08:34:50 usrp-e1xx usb 2-2.4: unlink qh256-0001/de2c5b80 start 9
[1/0 us]
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: shutdown urb de0f78c0
ep1in-intr
May 4 08:34:50 usrp-e1xx usb 2-2.4: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx usb 2-2: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2: unregistering interface 2-2:1.0
May 4 08:34:50 usrp-e1xx usb 2-2: unlink qh256-0001/de2c5e40 start 7 [1/0
us]
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: shutdown urb de0f70c0
ep1in-intr
May 4 08:34:50 usrp-e1xx usb 2-2: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: debounce: port 2: total 100ms stable
100ms status 0x501
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: port 2 high speed
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: GetStatus port:2 status
001005 0 ACK POWER sig=se0 PE CONNECT
May 4 08:34:50 usrp-e1xx usb 2-2: new high speed USB device number 20
using ehci-omap
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: port 2 high speed
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: GetStatus port:2 status
001005 0 ACK POWER sig=se0 PE CONNECT
May 4 08:34:50 usrp-e1xx usb 2-2: default language 0x0409
May 4 08:34:50 usrp-e1xx usb 2-2: udev 20, busnum 2, minor = 147
May 4 08:34:50 usrp-e1xx usb 2-2: New USB device found, idVendor=05e3,
idProduct=0608
May 4 08:34:50 usrp-e1xx usb 2-2: New USB device strings: Mfr=0,
Product=1, SerialNumber=0
May 4 08:34:50 usrp-e1xx usb 2-2: Product: USB2.0 Hub
May 4 08:34:50 usrp-e1xx usb 2-2: usb_probe_device
May 4 08:34:50 usrp-e1xx usb 2-2: configuration #1 chosen from 1 choice
May 4 08:34:50 usrp-e1xx usb 2-2: adding 2-2:1.0 (config #1, interface 0)
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: usb_probe_interface
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: usb_probe_interface - got id
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: USB hub found
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: 4 ports detected
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: standalone hub
...
Continues with a normal connect as if the devices had just been plugged.
Nathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120508/804ee653/attachment-0001.html>
------------------------------
Message: 7
Date: Tue, 8 May 2012 16:41:58 +0300
From: "Patrik Tast" <[email protected]>
To: <[email protected]>
Subject: Re: [USRP-users] E100 USB host reliability
Message-ID: <51E4E9567D4D4FE7A67F03A4353E9F90@hp>
Content-Type: text/plain; charset="iso-8859-1"
Hi Nathan,
USB is powered from your AC->DC (your PSU) they both use the same ground, this
will mess up your USB system sometimes and report disconnected if it gives
feedback when you write to it (most likely a webcam wont generate this error,
since it is an endpoint).
I have figthed with this problem also and solved it by using an external
battery to power it, now I/we have different GND:s.
First, try to use as short as possible USB cables. If you use long cables, add
an USB amplifier. If that doesn't work add a battery inbetween powers.
You (hopefully) wont see this problem using a laptop (since it is battery
driven), you might see it using a PC.
http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/drivers/usb/core/hub.c#L3172
Patrik
----- Original Message -----
From: Nathan Dumont
To: [email protected]
Sent: Tuesday, May 08, 2012 14:53
Subject: [USRP-users] E100 USB host reliability
We've been running some processing and logging on an E100 with the latest
kernel images. To store the logged data we're using a USB hard disk or flash
drive (only need about 20MB/day). Unfortunately we're seeing random
disconnects, they happen infrequently (once or twice a day) and there's nothing
very helpful in the logs, it just lists a disconnect then re-connect. We've
tried a couple of different full USB-A from the USB-OTG connector (not using
OTG, using Host port), several different hard disk and flash drive combos and
now have a powered high-speed USB hub between the USRP and peripherals. Anyone
else seeing anything like this?
I disabled the auto-mounting probe on the drive to see if polling was causing
the disconnect but it doesn't seem to have been the cause of the error
(hal-disable-polling).
/usr/var/syslog:
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: state 7 ports 3 chg 0000 evt 0004
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: GetStatus port:2 status
001809 0 ACK POWER sig=j PEC CONNECT
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: port 2 enable change, status 00000501
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: port 2 disabled by hub (EMI?),
re-enabling...
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: port 2, status 0501, change 0002, 480
Mb/s
May 4 08:34:50 usrp-e1xx usb 2-2: USB disconnect, device number 15
May 4 08:34:50 usrp-e1xx usb 2-2.3: USB disconnect, device number 17
May 4 08:34:50 usrp-e1xx usb 2-2.3: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2.3: unregistering interface 2-2.3:1.0
May 4 08:34:50 usrp-e1xx usb 2-2.3: unlink qh256-0001/de0cc700 start 8 [1/0
us]
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: shutdown urb de0f7dc0
ep1in-intr
May 4 08:34:50 usrp-e1xx usb 2-2.3: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx usb 2-2.4: USB disconnect, device number 18
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: USB disconnect, device number 19
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: unregistering interface 2-2.4.2:1.0
May 4 08:34:50 usrp-e1xx FAT-fs (sda1): unable to read inode block for
updating (i_pos 244801)
May 4 08:34:50 usrp-e1xx usrp_e release called
May 4 08:34:50 usrp-e1xx Waiting for DMA to become inactive
May 4 08:34:50 usrp-e1xx Freeing gpio irq's
May 4 08:34:50 usrp-e1xx Freeing DMA channels
May 4 08:34:50 usrp-e1xx usb 2-2.4.2: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx usb 2-2.4: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2.4: unregistering interface 2-2.4:1.0
May 4 08:34:50 usrp-e1xx usb 2-2.4: unlink qh256-0001/de2c5b80 start 9 [1/0
us]
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: shutdown urb de0f78c0
ep1in-intr
May 4 08:34:50 usrp-e1xx usb 2-2.4: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx usb 2-2: unregistering device
May 4 08:34:50 usrp-e1xx usb 2-2: unregistering interface 2-2:1.0
May 4 08:34:50 usrp-e1xx usb 2-2: unlink qh256-0001/de2c5e40 start 7 [1/0 us]
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: shutdown urb de0f70c0
ep1in-intr
May 4 08:34:50 usrp-e1xx usb 2-2: usb_disable_device nuking all URBs
May 4 08:34:50 usrp-e1xx hub 2-0:1.0: debounce: port 2: total 100ms stable
100ms status 0x501
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: port 2 high speed
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: GetStatus port:2 status
001005 0 ACK POWER sig=se0 PE CONNECT
May 4 08:34:50 usrp-e1xx usb 2-2: new high speed USB device number 20 using
ehci-omap
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: port 2 high speed
May 4 08:34:50 usrp-e1xx ehci-omap ehci-omap.0: GetStatus port:2 status
001005 0 ACK POWER sig=se0 PE CONNECT
May 4 08:34:50 usrp-e1xx usb 2-2: default language 0x0409
May 4 08:34:50 usrp-e1xx usb 2-2: udev 20, busnum 2, minor = 147
May 4 08:34:50 usrp-e1xx usb 2-2: New USB device found, idVendor=05e3,
idProduct=0608
May 4 08:34:50 usrp-e1xx usb 2-2: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
May 4 08:34:50 usrp-e1xx usb 2-2: Product: USB2.0 Hub
May 4 08:34:50 usrp-e1xx usb 2-2: usb_probe_device
May 4 08:34:50 usrp-e1xx usb 2-2: configuration #1 chosen from 1 choice
May 4 08:34:50 usrp-e1xx usb 2-2: adding 2-2:1.0 (config #1, interface 0)
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: usb_probe_interface
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: usb_probe_interface - got id
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: USB hub found
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: 4 ports detected
May 4 08:34:50 usrp-e1xx hub 2-2:1.0: standalone hub
...
Continues with a normal connect as if the devices had just been plugged.
Nathan
------------------------------------------------------------------------------
_______________________________________________
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/20120508/1c649438/attachment-0001.html>
------------------------------
Message: 8
Date: Tue, 8 May 2012 08:53:51 -0700 (PDT)
From: Joel Parker <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Parsing GPSDO with gpsd
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Anyone have any sample code for parsing GPGGA with gpsd ?
I can get the GPGGA with the USRP API :
usrp->get_mboard_sensor("gps_gpgga");
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120508/68b1ce8e/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 21, Issue 8
*****************************************
