usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsUSRP E100 error
Hi,
I'm getting an error when I try running uhd_usrp_probe on my E100:
root@usrp-e1xx:~# uhd_usrp_probe
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.003.001-3116368
-- Opening device node /dev/usrp_e0...
Error: LookupError: KeyError: key "E" not found in dict(Ss, Ss)
I re-imaged my SD card using the latest images at:
http://files.ettus.com/e1xx_images/
I also download and build the UHD from source using the 3.3.1
directions and later at:
http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/FAQ#How-do-I-install-UHD-from-source
but these didn't help.
I tried re-seating the gumstix module, but that didn't seem to help.
Here is the boot-up info:
Texas Instruments X-Loader 1.4.4ss (Oct 24 2011 - 07:06:23)
No NAND detected
OMAP3530-GP ES3.1
Board revision: 1
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2011.06-00575-g6b73deb (Sep 07 2011 - 07:26:10)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
Board revision: 1
Direct connection on mmc2
Recognized Ettus Research USRP-E (rev 4 E)
Die ID #5a160004000000000403990c0a00b00f
Net: smc911x-0
Warning: failed to set MAC address
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2963060 bytes read
Booting from mmc ...
Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.0.0+
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2962996 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
When I run uhd_find_devices, I get the following:
root@usrp-e1xx:~# uhd_find_devices
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.003.001-3116368
-- UHD Device 0
Device Address:
type: e100
node: /dev/usrp_e0
name: FP
serial:
Any idea what could be going on? Is the gumstix failing to talk to the USRP?
The only LED that is lit is F.
Also is it suppose to detect NAND flash on the board?
I noticed that the OMAP banner doesn't match what listed on the
Versions wiki page:
from: http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/Versions
Texas Instruments X-Loader 1.4.4ss (Sep 21 2011 - 14:25:55)
OMAP3630/3730-GP ES2.1
Board revision: 2
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2011.06-00575-g6b73deb (Sep 07 2011 - 07:26:10)
OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
Thanks,
Tom
On 11/16/2011 02:41 PM, Tom . wrote:
Hi,
I'm getting an error when I try running uhd_usrp_probe on my E100:
I've seen this, and have been having a devil of a time trying to get
some boundaries around the issue.
As a note, we expect to see:
Recognized Ettus Research USRP-E (rev 3 E100)
In the u-boot messages. (If you have a recent E100, you will see rev 4).
Can you run:
root@usrp-e1xx:~# i2cdump -y 3 0x51
And send in the results? You may need to do:
opkg update
opkg install i2c-tools
to get the i2c utilities.
Philip
root@usrp-e1xx:~# uhd_usrp_probe
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.003.001-3116368
-- Opening device node /dev/usrp_e0...
Error: LookupError: KeyError: key "E" not found in dict(Ss, Ss)
I re-imaged my SD card using the latest images at:
http://files.ettus.com/e1xx_images/
I also download and build the UHD from source using the 3.3.1
directions and later at:
http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/FAQ#How-do-I-install-UHD-from-source
but these didn't help.
I tried re-seating the gumstix module, but that didn't seem to help.
Here is the boot-up info:
Texas Instruments X-Loader 1.4.4ss (Oct 24 2011 - 07:06:23)
No NAND detected
OMAP3530-GP ES3.1
Board revision: 1
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2011.06-00575-g6b73deb (Sep 07 2011 - 07:26:10)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
Board revision: 1
Direct connection on mmc2
Recognized Ettus Research USRP-E (rev 4 E)
Die ID #5a160004000000000403990c0a00b00f
Net: smc911x-0
Warning: failed to set MAC address
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2963060 bytes read
Booting from mmc ...
Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.0.0+
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2962996 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
When I run uhd_find_devices, I get the following:
root@usrp-e1xx:~# uhd_find_devices
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.003.001-3116368
-- UHD Device 0
Device Address:
type: e100
node: /dev/usrp_e0
name: FP
serial:
Any idea what could be going on? Is the gumstix failing to talk to the USRP?
The only LED that is lit is F.
Also is it suppose to detect NAND flash on the board?
I noticed that the OMAP banner doesn't match what listed on the
Versions wiki page:
from: http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/Versions
Texas Instruments X-Loader 1.4.4ss (Sep 21 2011 - 14:25:55)
OMAP3630/3730-GP ES2.1
Board revision: 2
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2011.06-00575-g6b73deb (Sep 07 2011 - 07:26:10)
OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
Thanks,
Tom
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
On Wed, Nov 16, 2011 at 3:02 PM, Philip Balister philip@balister.org wrote:
On 11/16/2011 02:41 PM, Tom . wrote:
Hi,
I'm getting an error when I try running uhd_usrp_probe on my E100:
I've seen this, and have been having a devil of a time trying to get
some boundaries around the issue.
As a note, we expect to see:
Recognized Ettus Research USRP-E (rev 3 E100)
In the u-boot messages. (If you have a recent E100, you will see rev 4).
Can you run:
root@usrp-e1xx:~# i2cdump -y 3 0x51
And send in the results? You may need to do:
opkg update
opkg install i2c-tools
to get the i2c utilities.
Philip
Philip,
Thanks for the help.
Here is the dump:
root@usrp-e1xx:~# i2cdump -y 3 0x51
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 03 00 01 04 00 45 00 10 20 00 40 56 59 42 41 .?.??.E.? .@VYBA
10: 03 10 01 03 80 26 1e 78 ee de 95 a3 54 4c 99 26 ?????&?x????TL?&
20: 0f 50 54 a5 4b 00 71 4f 81 80 01 01 01 01 01 01 ?PT?K.qO????????
30: 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70 ??????0*.?Q.*@0p
40: 13 00 78 2d 11 00 00 1e 00 00 00 ff 00 44 43 33 ?.x-?..?.....DC3
50: 32 33 36 31 4a 41 42 59 56 0a 00 00 00 fc 00 00 2361JABYV?...?..
60: 40 00 00 00 30 01 30 37 46 50 0a 20 00 00 00 fd @...0?07FP? ...?
70: 00 38 4c 1e 51 0e 00 0a 20 20 20 20 20 20 00 c8 .8L?Q?.? .?
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff 00 04 a3 2d 91 38 ...........??-?8
The system is fairly new. The sticker on the back says it is a rev 4.
- Tom
Thanks for the data.
uhd_usrp_probe --args="model=E100" should succeed. You can try to
rewrite the model string in the eeprom with:
root@usrp-e1xx:~# /usr/share/uhd/utils/usrp_burn_mb_eeprom
--args="model=E100" --key=model --val=E100
If that doesn't work, it is ok to use the --args.. trick to force UHD to
treat it as an E100 while we sort out what is going on.
Philip
On 11/17/2011 08:07 AM, Tom . wrote:
On Wed, Nov 16, 2011 at 3:02 PM, Philip Balister philip@balister.org wrote:
On 11/16/2011 02:41 PM, Tom . wrote:
Hi,
I'm getting an error when I try running uhd_usrp_probe on my E100:
I've seen this, and have been having a devil of a time trying to get
some boundaries around the issue.
As a note, we expect to see:
Recognized Ettus Research USRP-E (rev 3 E100)
In the u-boot messages. (If you have a recent E100, you will see rev 4).
Can you run:
root@usrp-e1xx:~# i2cdump -y 3 0x51
And send in the results? You may need to do:
opkg update
opkg install i2c-tools
to get the i2c utilities.
Philip
Philip,
Thanks for the help.
Here is the dump:
root@usrp-e1xx:~# i2cdump -y 3 0x51
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 03 00 01 04 00 45 00 10 20 00 40 56 59 42 41 .?.??.E.? .@VYBA
10: 03 10 01 03 80 26 1e 78 ee de 95 a3 54 4c 99 26 ?????&?x????TL?&
20: 0f 50 54 a5 4b 00 71 4f 81 80 01 01 01 01 01 01 ?PT?K.qO????????
30: 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70 ??????0*.?Q.*@0p
40: 13 00 78 2d 11 00 00 1e 00 00 00 ff 00 44 43 33 ?.x-?..?.....DC3
50: 32 33 36 31 4a 41 42 59 56 0a 00 00 00 fc 00 00 2361JABYV?...?..
60: 40 00 00 00 30 01 30 37 46 50 0a 20 00 00 00 fd @...0?07FP? ...?
70: 00 38 4c 1e 51 0e 00 0a 20 20 20 20 20 20 00 c8 .8L?Q?.? .?
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff 00 04 a3 2d 91 38 ...........??-?8
The system is fairly new. The sticker on the back says it is a rev 4.
- Tom
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
On Thu, Nov 17, 2011 at 9:00 AM, Philip Balister philip@balister.org wrote:
Thanks for the data.
uhd_usrp_probe --args="model=E100" should succeed. You can try to
rewrite the model string in the eeprom with:
root@usrp-e1xx:~# /usr/share/uhd/utils/usrp_burn_mb_eeprom
--args="model=E100" --key=model --val=E100
If that doesn't work, it is ok to use the --args.. trick to force UHD to
treat it as an E100 while we sort out what is going on.
Philip
I ran the commands:
root@usrp-e1xx:~# uhd_usrp_probe --args="model=E100"
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.003.001-3116368
-- Opening device node /dev/usrp_e0...
-- Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga_v2.bin... done = 1
-- Configuration complete.
-- Opening device node /dev/usrp_e0...
-- Initializing FPGA clock to 64.000000MHz...
-- USRP-E100 clock control: 10
-- r_counter: 2
-- a_counter: 0
-- b_counter: 20
-- prescaler: 8
-- vco_divider: 5
-- chan_divider: 5
-- vco_rate: 1600.000000MHz
-- chan_rate: 320.000000MHz
-- out_rate: 64.000000MHz
-- Performing wishbone readback test... pass
Error: TypeError: Cannot call set on wax obj base class
-key=model --val=E100r/share/uhd/utils/usrp_burn_mb_eeprom --args="model=E100" -
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.003.001-3116368
Creating USRP device from address: model=E100
-- Opening device node /dev/usrp_e0...
-- Initializing FPGA clock to 64.000000MHz...
-- USRP-E100 clock control: 10
-- r_counter: 2
-- a_counter: 0
-- b_counter: 20
-- prescaler: 8
-- vco_divider: 5
-- chan_divider: 5
-- vco_rate: 1600.000000MHz
-- chan_rate: 320.000000MHz
-- out_rate: 64.000000MHz
-- Performing wishbone readback test... pass
Fetching current settings from EEPROM...
EEPROM ["model"] is "E"
Setting EEPROM ["model"] to "E100"...
Power-cycle the USRP device for the changes to take effect.
I did a reboot and got this:
root@usrp-e1xx:~# reboot
Broadcast message from root (ttyO2) (Thu Nov 17 09:30:19 2011):
The system is going down for reboot NOW!
INIT: Sending pStopping Dropbear SSH server: dropbear.
- Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ]
Stopping advanced power management daemon: No /usr/sbin/apmd found
running; none killed.
apmd.
Stopping Hardware abstraction layer hald
run-parts: /etc/dbus-1/event.d/20hal exited with return code 1
Stopping Distributed Compiler Daemon: distcc/etc/rc6.d/K20distcc: stop
failed with error code 1
Stopping GNOME Display Manager gdm
Stopping Samba: smbd nmbd.
Stopping internet superserver: xinetd.
Stopping Network connection manager daemon: NetworkManager.
ALSA: Storing mixer settings...
Stopping PVR
ERROR: Module bufferclass_ti does not exist in /proc/modules
Deconfiguring network interfaces... done.
Stopping Vixie-cron.
Stopping syslog-ng:.
Sending all processes the TERM signal...
modem-manager: Caught signal 15, shutting down...
Sending all processes the KILL signal...
Unmounting remote filesystems...
Stopping portmap daemon: portmap.
Deactivating swap...
Unmounting local filesystems...
Rebooting... musb-hdrc musb-hdrc: remove, state 1
usb usb1: USB disconnect, device number 1
------------[ cut here ]------------
WARNING: at arch/arm/mach-omap2/omap_l3_smx.c:162 omap3_l3_app_irq+0xfc/0x144()
In-band Error seen by MPU at address 0
Modules linked in: usrp_e ipv6 twl4030_madc_hwmon
[<c0041094>] (unwind_backtrace+0x0/0xe0) from [<c0062cb4>]
(warn_slowpath_common+0x4c/0x64)
[<c0062cb4>] (warn_slowpath_common+0x4c/0x64) from [<c0062d4c>]
(warn_slowpath_fmt+0x2c/0x3c)
[<c0062d4c>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0052cf8>]
(omap3_l3_app_irq+0xfc/0x144)
[<c0052cf8>] (omap3_l3_app_irq+0xfc/0x144) from [<c0094f00>]
(handle_irq_event_percpu+0x30/0x174)
[<c0094f00>] (handle_irq_event_percpu+0x30/0x174) from [<c0095098>]
(handle_irq_event+0x54/0x74)
[<c0095098>] (handle_irq_event+0x54/0x74) from [<c0096dc8>]
(handle_level_irq+0xb4/0x100)
[<c0096dc8>] (handle_level_irq+0xb4/0x100) from [<c0094980>]
(generic_handle_irq+0x30/0x44)
[<c0094980>] (generic_handle_irq+0x30/0x44) from [<c0037060>]
(asm_do_IRQ+0x60/0x84)
[<c0037060>] (asm_do_IRQ+0x60/0x84) from [<c003c1c8>] (__irq_svc+0x48/0xb8)
Exception stack(0xde097d98 to 0xde097de0)
7d80: fa0ab00a 00001028
7da0: c02c2c80 60000013 0000040f 00000008 dec97a14 c062cf54 c003c8c4 20000113
7dc0: 00000000 00000000 00000000 de097de0 c003c120 c003c148 20000113 ffffffff
[<c003c1c8>] (__irq_svc+0x48/0xb8) from [<c003c148>] (__dabt_svc+0x68/0xa0)
[<c003c148>] (__dabt_svc+0x68/0xa0) from [<c02c2c80>]
(musb_generic_disable.clone.5+0x14/0x24)
[<c02c2c80>] (musb_generic_disable.clone.5+0x14/0x24) from
[<c02c2f44>] (musb_stop+0x24/0x44)
[<c02c2f44>] (musb_stop+0x24/0x44) from [<c02c3720>] (musb_h_stop+0x10/0x1c)
[<c02c3720>] (musb_h_stop+0x10/0x1c) from [<c02a60fc>]
(usb_remove_hcd+0x108/0x188)
[<c02a60fc>] (usb_remove_hcd+0x108/0x188) from [<c02c2d0c>]
(musb_shutdown+0x7c/0xb0)
[<c02c2d0c>] (musb_shutdown+0x7c/0xb0) from [<c025c8f4>]
(platform_drv_shutdown+0x14/0x18)
[<c025c8f4>] (platform_drv_shutdown+0x14/0x18) from [<c0259e68>]
(device_shutdown+0x98/0xe8)
[<c0259e68>] (device_shutdown+0x98/0xe8) from [<c0072628>]
(kernel_restart_prepare+0x28/0x38)
[<c0072628>] (kernel_restart_prepare+0x28/0x38) from [<c0072644>]
(kernel_restart+0xc/0x48)
[<c0072644>] (kernel_restart+0xc/0x48) from [<c0072780>] (sys_reboot+0xf8/0x1d8)
[<c0072780>] (sys_reboot+0xf8/0x1d8) from [<c003c740>]
(ret_fast_syscall+0x0/0x30)
---[ end trace cef2291013d42742 ]---
Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab00a
Internal error: : 1028 [#1] PREEMPT
Modules linked in: usrp_e ipv6 twl4030_madc_hwmon
CPU: 0 Tainted: G W (3.0.0+ #170)
PC is at musb_generic_disable.clone.5+0x14/0x24
LR is at musb_stop+0x24/0x44
pc : [<c02c2c80>] lr : [<c02c2f44>] psr: 60000013
sp : de097e28 ip : 00000000 fp : 00000000
r10: 00000000 r9 : de096000 r8 : c003c8c4
r7 : c062cf54 r6 : dec97a14 r5 : decfb874 r4 : decfb8f4
r3 : 00000000 r2 : c01f3e78 r1 : decfb874 r0 : fa0ab000
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: 99210019 DAC: 00000015
Process reboot (pid: 793, stack limit = 0xde0962f0)
Stack: (0xde097e28 to 0xde098000)
7e20: decfb800 c02c3720 decfb800 c02a60fc decfb800 00000000
7e40: de097e50 decfb8f4 40000013 c02c2d0c dec97a08 de096000 dec97a14 c025c8f4
7e60: c025c8e0 c0259e68 00000000 28121969 01234567 bef2d4a4 c003c8c4 c0072628
7e80: 00000000 c0072644 c05a5f50 c0072780 def62940 00000000 decfb000 dee24800
7ea0: 00000000 dee2480c de097ed0 c0394e20 c062f850 c0352c48 bef2d4a0 0666a8c0
7ec0: 30687465 00000000 00000000 00000000 00000002 0666a8c0 00000000 00000000
7ee0: 00000002 0666a8c0 00000000 00000000 00000007 00008914 c0590dd0 debdb860
7f00: c0590b08 deb95c98 60000013 c00ce97c c0590b08 deb95c98 debdb860 00000000
7f20: de096000 c00e39b0 deb95c98 00000000 00000000 deb95c98 00000000 deb95c98
7f40: 00000008 c00e44e4 d916c1c0 debdb860 deb95c98 c00d3454 00000000 00000000
7f60: 00011ee0 c00eb1cc d916c1c0 00000000 de0ba200 00000001 00000003 c00d0288
7f80: de096000 de0ba200 d916c1c0 c00d032c 00000002 00000001 00000004 00000000
7fa0: 00000058 c003c740 00000001 00000004 fee1dead 28121969 01234567 bef2d4a4
7fc0: 00000001 00000004 00000000 00000058 00000001 00000000 00011ed8 00000000
7fe0: 401f98b0 bef2dcac 00009204 401f98d0 60000010 fee1dead 00000000 00000000
[<c02c2c80>] (musb_generic_disable.clone.5+0x14/0x24) from
[<c02c2f44>] (musb_stop+0x24/0x44)
[<c02c2f44>] (musb_stop+0x24/0x44) from [<c02c3720>] (musb_h_stop+0x10/0x1c)
[<c02c3720>] (musb_h_stop+0x10/0x1c) from [<c02a60fc>]
(usb_remove_hcd+0x108/0x188)
[<c02a60fc>] (usb_remove_hcd+0x108/0x188) from [<c02c2d0c>]
(musb_shutdown+0x7c/0xb0)
[<c02c2d0c>] (musb_shutdown+0x7c/0xb0) from [<c025c8f4>]
(platform_drv_shutdown+0x14/0x18)
[<c025c8f4>] (platform_drv_shutdown+0x14/0x18) from [<c0259e68>]
(device_shutdown+0x98/0xe8)
[<c0259e68>] (device_shutdown+0x98/0xe8) from [<c0072628>]
(kernel_restart_prepare+0x28/0x38)
[<c0072628>] (kernel_restart_prepare+0x28/0x38) from [<c0072644>]
(kernel_restart+0xc/0x48)
[<c0072644>] (kernel_restart+0xc/0x48) from [<c0072780>] (sys_reboot+0xf8/0x1d8)
[<c0072780>] (sys_reboot+0xf8/0x1d8) from [<c003c740>]
(ret_fast_syscall+0x0/0x30)
Code: e5c0300b e1c030b6 e1c030b8 e5c03060 (e5d0300a)
---[ end trace cef2291013d42743 ]---
Segmentation fault
Give root password for system maintenance
(or type Control-D for normal startup):
I logged in and did an init 0 followed by a power cycle. I lost my
first set of power up logs, so i did another init 0.
Power cycled again.
root@usrp-e1xx:~# /usr/share/uhd/utils/usrp_burn_mb_eeprom
--args="model=E100" --key="model" --val="E100"
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.003.001-3116368
Creating USRP device from address: model=E100
-- Opening device node /dev/usrp_e0...
-- Initializing FPGA clock to 64.000000MHz...
-- USRP-E100 clock control: 10
-- r_counter: 2
-- a_counter: 0
-- b_counter: 20
-- prescaler: 8
-- vco_divider: 5
-- chan_divider: 5
-- vco_rate: 1600.000000MHz
-- chan_rate: 320.000000MHz
-- out_rate: 64.000000MHz
-- Performing wishbone readback test... pass
Fetching current settings from EEPROM...
EEPROM ["model"] is "E"
Setting EEPROM ["model"] to "E100"...
Power-cycle the USRP device for the changes to take effect.
Done
Here is the power-up console output:
Texas Instruments X-Loader 1.4.4ss (Oct 24 2011 - 07:06:23)
No NAND detected
OMAP3530-GP ES3.1
Board revision: 1
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2011.06-00575-g6b73deb (Sep 07 2011 - 07:26:10)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
Board revision: 1
Direct connection on mmc2
Recognized Ettus Research USRP-E (rev 4 E)
Die ID #5a160004000000000403990c0a00b00f
Net: smc911x-0
Warning: failed to set MAC address
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2963060 bytes read
Booting from mmc ...
Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.0.0+
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2962996 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
I'm currently trying to get the kalibrate-uhd program to work on my E100.
Can I do something like this (from kalibrate-uhd src/usrp_source.cc )
to work around this:
/*
-
open() should be called before multiple threads access usrp_source.
*/
int usrp_source::open(unsigned int subdev) {if(!m_dev) {
uhd::device_addr_t dev_addr("type=e100 model=E100");
if (!(m_dev = uhd::usrp::single_usrp::make(dev_addr))) {
fprintf(stderr, "error: single_usrp::make: failed!\n");
return -1;
}
- Tom