I get an error running uhd_usrp_probe and can't figure out why, I would definitely appreciate any insight into this error and how to resolve it. Thanks! root@ettus-e1xx:/apps# uhd_usrp_probe linux; GNU C++ version 4.7.2; Boost_105300; UHD_003.005.002-0-unknown -- Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga_v2.bin... done = 1 -- 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 -- Error: basic_string::at Thanks, Taylor

On 01/06/2014 10:06 AM, Taylor Centers wrote: > I get an error running uhd_usrp_probe and can't figure out why, I > would definitely appreciate any insight into this error and how to > resolve it. Thanks! Do you have a monitor attached? Can you try this without a monitor by logging in over the serial port? I'd like to see the messages from u-boot at the start of the boot process. Thanks, Philip > > > root@ettus-e1xx:/apps# uhd_usrp_probe > linux; GNU C++ version 4.7.2; Boost_105300; UHD_003.005.002-0-unknown > > -- Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga_v2.bin... done = 1 > > -- 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 > > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >

I'm using the screen command to connect via serial through the console port. I can't scroll up to copy the whole boot message, but pasted below are the very beginning and very end that I had time to grab and copy. I'll try and figure out how to get the whole picture for you, but hopefully you can deduce something from this. U-Boot 2011.12-00010-ga3eb89c (Jan 29 2012 - 14:53:43) OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle Rev Ax/Bx timed out in wait_for_pin: I2C_STAT=0 I2C read: I/O error Unrecognized expansion board: 0 timed out in wait_for_pin: I2C_STAT=0 I2C read: I/O error Unrecognized expansion board: 0 Die ID #0a300004000000000403730510014003 Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: ////////////////////////////////////////////MISSING STUFF HERE///////////////////////////////////////////////// [ 3.762786] Key type dns_resolver registered [ 3.767822] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 [ 3.783386] ThumbEE CPU extension supported. [ 3.787994] sr_init: No PMIC hook to init smartreflex [ 3.793762] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized [ 3.802276] mmc0: new SDHC card at address e624 [ 3.807495] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized [ 3.816528] mmcblk0: mmc0:e624 SU08G 7.40 GiB [ 3.831420] mmcblk0: p1 p2 [ 3.836425] clock: disabling unused clocks to save power [ 3.844238] registered taskstats version 1 [ 3.850128] fbcvt: 640x480@60: CVT Name - .307M3-R [ 3.865692] Console: switching to colour frame buffer device 80x30 [ 3.881072] VDAC: incomplete constraints, leaving on [ 3.888549] twl_rtc twl_rtc: setting system clock to 2013-12-19 02:27:37 UTC (1387420057) [ 3.897399] ALSA device list: [ 3.900665] #0: omap3beagle [ 3.909027] EXT3-fs (mmcblk0p2): recovery required on readonly filesystem [ 3.916320] EXT3-fs (mmcblk0p2): write access will be enabled during recovery [ 4.325744] kjournald starting. Commit interval 5 seconds [ 4.336456] EXT3-fs (mmcblk0p2): recovery complete [ 4.341613] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode [ 4.349151] VFS: Mounted root (ext3 filesystem) readonly on device 179:2. [ 4.360687] devtmpfs: mounted [ 4.364501] Freeing init memory: 224K INIT: version 2.88 booting Starting udev [ 5.420043] udevd[72]: starting version 182 Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. [ 10.349182] EXT3-fs (mmcblk0p2): using internal journal ALSA: Restoring mixer settings... Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device Starting rpcbind daemon...[ 12.370544] NET: Registered protocol family 10 done. INIT: Entering runlevel: 5 Starting system message bus: dbus. Starting OpenBSD Secure Shell server: sshd done. Starting Distributed Compiler Daemon: distcc. Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Telephony daemon Starting Linux NFC daemon Starting OProfileUI server Stopping Bootlog daemon: bootlogd. On Mon, Jan 6, 2014 at 12:20 PM, Philip Balister <philip@opensdr.com> wrote: > On 01/06/2014 10:06 AM, Taylor Centers wrote: > > I get an error running uhd_usrp_probe and can't figure out why, I > > would definitely appreciate any insight into this error and how to > > resolve it. Thanks! > > Do you have a monitor attached? > > Can you try this without a monitor by logging in over the serial port? > > I'd like to see the messages from u-boot at the start of the boot process. > > Thanks, > > Philip > > > > > > > root@ettus-e1xx:/apps# uhd_usrp_probe > > linux; GNU C++ version 4.7.2; Boost_105300; UHD_003.005.002-0-unknown > > > > -- Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga_v2.bin... > done = 1 > > > > -- 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 > > > > > > > > _______________________________________________ > > USRP-users mailing list > > USRP-users@lists.ettus.com > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > >

On 01/06/2014 01:37 PM, Taylor Centers wrote: > I'm using the screen command to connect via serial through the console > port. I can't scroll up to copy the whole boot message, but pasted below > are the very beginning and very end that I had time to grab and copy. I'll > try and figure out how to get the whole picture for you, but hopefully you > can deduce something from this. > > U-Boot 2011.12-00010-ga3eb89c (Jan 29 2012 - 14:53:43) > > OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz > OMAP3 Beagle board + LPDDR/NAND > I2C: ready > DRAM: 256 MiB > NAND: 0 MiB > MMC: OMAP SD/MMC: 0 > *** Warning - readenv() failed, using default environment > > In: serial > Out: serial > Err: serial > Beagle Rev Ax/Bx > timed out in wait_for_pin: I2C_STAT=0 > I2C read: I/O error > Unrecognized expansion board: 0 > timed out in wait_for_pin: I2C_STAT=0 > I2C read: I/O error > Unrecognized expansion board: 0 OK, this stuff is bad. It means the Overo can't read some data from the onboard i2c EEPROM. The first thing to try is re-seating the Overo on the motherboard. Philip > Die ID #0a300004000000000403730510014003 > Net: Net Initialization Skipped > No ethernet found. > Hit any key to stop autoboot: > > > ////////////////////////////////////////////MISSING STUFF > HERE///////////////////////////////////////////////// > > > [ 3.762786] Key type dns_resolver registered > [ 3.767822] VFP support v0.3: implementor 41 architecture 3 part 30 > variant c rev 1 > [ 3.783386] ThumbEE CPU extension supported. > [ 3.787994] sr_init: No PMIC hook to init smartreflex > [ 3.793762] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver > initialized > [ 3.802276] mmc0: new SDHC card at address e624 > [ 3.807495] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver > initialized > [ 3.816528] mmcblk0: mmc0:e624 SU08G 7.40 GiB > [ 3.831420] mmcblk0: p1 p2 > [ 3.836425] clock: disabling unused clocks to save power > [ 3.844238] registered taskstats version 1 > [ 3.850128] fbcvt: 640x480@60: CVT Name - .307M3-R > [ 3.865692] Console: switching to colour frame buffer device 80x30 > [ 3.881072] VDAC: incomplete constraints, leaving on > [ 3.888549] twl_rtc twl_rtc: setting system clock to 2013-12-19 02:27:37 > UTC (1387420057) > [ 3.897399] ALSA device list: > [ 3.900665] #0: omap3beagle > [ 3.909027] EXT3-fs (mmcblk0p2): recovery required on readonly filesystem > [ 3.916320] EXT3-fs (mmcblk0p2): write access will be enabled during > recovery > [ 4.325744] kjournald starting. Commit interval 5 seconds > [ 4.336456] EXT3-fs (mmcblk0p2): recovery complete > [ 4.341613] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data > mode > [ 4.349151] VFS: Mounted root (ext3 filesystem) readonly on device 179:2. > [ 4.360687] devtmpfs: mounted > [ 4.364501] Freeing init memory: 224K > INIT: version 2.88 booting > Starting udev > [ 5.420043] udevd[72]: starting version 182 > Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file > or directory > bootlogd. > [ 10.349182] EXT3-fs (mmcblk0p2): using internal journal > ALSA: Restoring mixer settings... > Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device > Starting rpcbind daemon...[ 12.370544] NET: Registered protocol family 10 > done. > INIT: Entering runlevel: 5 > Starting system message bus: dbus. > Starting OpenBSD Secure Shell server: sshd > done. > Starting Distributed Compiler Daemon: distcc. > Starting syslogd/klogd: done > * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ > ok ] > Starting Telephony daemon > Starting Linux NFC daemon > Starting OProfileUI server > Stopping Bootlog daemon: bootlogd. > > > > > > > On Mon, Jan 6, 2014 at 12:20 PM, Philip Balister <philip@opensdr.com> wrote: > >> On 01/06/2014 10:06 AM, Taylor Centers wrote: >>> I get an error running uhd_usrp_probe and can't figure out why, I >>> would definitely appreciate any insight into this error and how to >>> resolve it. Thanks! >> >> Do you have a monitor attached? >> >> Can you try this without a monitor by logging in over the serial port? >> >> I'd like to see the messages from u-boot at the start of the boot process. >> >> Thanks, >> >> Philip >> >>> >>> >>> root@ettus-e1xx:/apps# uhd_usrp_probe >>> linux; GNU C++ version 4.7.2; Boost_105300; UHD_003.005.002-0-unknown >>> >>> -- Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga_v2.bin... >> done = 1 >>> >>> -- 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 >>> >>> >>> >>> _______________________________________________ >>> USRP-users mailing list >>> USRP-users@lists.ettus.com >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> >> >> >

Interesting. I have the original SD card from the E100 that I've tried and it works fine, the uhd_usrp_probe command works as expected as well. So I don't think it is a hardware problem. I created the SD card with the error through OpenEmbedded; the uImage and the rootfs. The MLO and u-boot.image I took from the original. On Mon, Jan 6, 2014 at 1:46 PM, Philip Balister <philip@opensdr.com> wrote: > On 01/06/2014 01:37 PM, Taylor Centers wrote: > > I'm using the screen command to connect via serial through the console > > port. I can't scroll up to copy the whole boot message, but pasted below > > are the very beginning and very end that I had time to grab and copy. > I'll > > try and figure out how to get the whole picture for you, but hopefully > you > > can deduce something from this. > > > > U-Boot 2011.12-00010-ga3eb89c (Jan 29 2012 - 14:53:43) > > > > OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz > > OMAP3 Beagle board + LPDDR/NAND > > I2C: ready > > DRAM: 256 MiB > > NAND: 0 MiB > > MMC: OMAP SD/MMC: 0 > > *** Warning - readenv() failed, using default environment > > > > In: serial > > Out: serial > > Err: serial > > Beagle Rev Ax/Bx > > timed out in wait_for_pin: I2C_STAT=0 > > I2C read: I/O error > > Unrecognized expansion board: 0 > > timed out in wait_for_pin: I2C_STAT=0 > > I2C read: I/O error > > Unrecognized expansion board: 0 > > OK, this stuff is bad. It means the Overo can't read some data from the > onboard i2c EEPROM. The first thing to try is re-seating the Overo on > the motherboard. > > Philip > > > > Die ID #0a300004000000000403730510014003 > > Net: Net Initialization Skipped > > No ethernet found. > > Hit any key to stop autoboot: > > > > > > ////////////////////////////////////////////MISSING STUFF > > HERE///////////////////////////////////////////////// > > > > > > [ 3.762786] Key type dns_resolver registered > > [ 3.767822] VFP support v0.3: implementor 41 architecture 3 part 30 > > variant c rev 1 > > [ 3.783386] ThumbEE CPU extension supported. > > [ 3.787994] sr_init: No PMIC hook to init smartreflex > > [ 3.793762] smartreflex smartreflex.0: omap_sr_probe: SmartReflex > driver > > initialized > > [ 3.802276] mmc0: new SDHC card at address e624 > > [ 3.807495] smartreflex smartreflex.1: omap_sr_probe: SmartReflex > driver > > initialized > > [ 3.816528] mmcblk0: mmc0:e624 SU08G 7.40 GiB > > [ 3.831420] mmcblk0: p1 p2 > > [ 3.836425] clock: disabling unused clocks to save power > > [ 3.844238] registered taskstats version 1 > > [ 3.850128] fbcvt: 640x480@60: CVT Name - .307M3-R > > [ 3.865692] Console: switching to colour frame buffer device 80x30 > > [ 3.881072] VDAC: incomplete constraints, leaving on > > [ 3.888549] twl_rtc twl_rtc: setting system clock to 2013-12-19 > 02:27:37 > > UTC (1387420057) > > [ 3.897399] ALSA device list: > > [ 3.900665] #0: omap3beagle > > [ 3.909027] EXT3-fs (mmcblk0p2): recovery required on readonly > filesystem > > [ 3.916320] EXT3-fs (mmcblk0p2): write access will be enabled during > > recovery > > [ 4.325744] kjournald starting. Commit interval 5 seconds > > [ 4.336456] EXT3-fs (mmcblk0p2): recovery complete > > [ 4.341613] EXT3-fs (mmcblk0p2): mounted filesystem with writeback > data > > mode > > [ 4.349151] VFS: Mounted root (ext3 filesystem) readonly on device > 179:2. > > [ 4.360687] devtmpfs: mounted > > [ 4.364501] Freeing init memory: 224K > > INIT: version 2.88 booting > > Starting udev > > [ 5.420043] udevd[72]: starting version 182 > > Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such > file > > or directory > > bootlogd. > > [ 10.349182] EXT3-fs (mmcblk0p2): using internal journal > > ALSA: Restoring mixer settings... > > Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device > > Starting rpcbind daemon...[ 12.370544] NET: Registered protocol family > 10 > > done. > > INIT: Entering runlevel: 5 > > Starting system message bus: dbus. > > Starting OpenBSD Secure Shell server: sshd > > done. > > Starting Distributed Compiler Daemon: distcc. > > Starting syslogd/klogd: done > > * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon > [ > > ok ] > > Starting Telephony daemon > > Starting Linux NFC daemon > > Starting OProfileUI server > > Stopping Bootlog daemon: bootlogd. > > > > > > > > > > > > > > On Mon, Jan 6, 2014 at 12:20 PM, Philip Balister <philip@opensdr.com> > wrote: > > > >> On 01/06/2014 10:06 AM, Taylor Centers wrote: > >>> I get an error running uhd_usrp_probe and can't figure out why, I > >>> would definitely appreciate any insight into this error and how to > >>> resolve it. Thanks! > >> > >> Do you have a monitor attached? > >> > >> Can you try this without a monitor by logging in over the serial port? > >> > >> I'd like to see the messages from u-boot at the start of the boot > process. > >> > >> Thanks, > >> > >> Philip > >> > >>> > >>> > >>> root@ettus-e1xx:/apps# uhd_usrp_probe > >>> linux; GNU C++ version 4.7.2; Boost_105300; UHD_003.005.002-0-unknown > >>> > >>> -- Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga_v2.bin... > >> done = 1 > >>> > >>> -- 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 > >>> > >>> > >>> > >>> _______________________________________________ > >>> USRP-users mailing list > >>> USRP-users@lists.ettus.com > >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >>> > >> > >> > > > >

On 01/06/2014 02:43 PM, Taylor Centers wrote: > Interesting. I have the original SD card from the E100 that I've tried and > it works fine, the uhd_usrp_probe command works as expected as well. So I > don't think it is a hardware problem. > > I created the SD card with the error through OpenEmbedded; the uImage and > the rootfs. The MLO and u-boot.image I took from the original. I will now go insane. So MLO reads the u-boot file from the sd card. U-boot reads the eeprom and prints those messages. So you are using the original files and getting a different result. Let me think about this some. Philip > > > On Mon, Jan 6, 2014 at 1:46 PM, Philip Balister <philip@opensdr.com> wrote: > >> On 01/06/2014 01:37 PM, Taylor Centers wrote: >>> I'm using the screen command to connect via serial through the console >>> port. I can't scroll up to copy the whole boot message, but pasted below >>> are the very beginning and very end that I had time to grab and copy. >> I'll >>> try and figure out how to get the whole picture for you, but hopefully >> you >>> can deduce something from this. >>> >>> U-Boot 2011.12-00010-ga3eb89c (Jan 29 2012 - 14:53:43) >>> >>> OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz >>> OMAP3 Beagle board + LPDDR/NAND >>> I2C: ready >>> DRAM: 256 MiB >>> NAND: 0 MiB >>> MMC: OMAP SD/MMC: 0 >>> *** Warning - readenv() failed, using default environment >>> >>> In: serial >>> Out: serial >>> Err: serial >>> Beagle Rev Ax/Bx >>> timed out in wait_for_pin: I2C_STAT=0 >>> I2C read: I/O error >>> Unrecognized expansion board: 0 >>> timed out in wait_for_pin: I2C_STAT=0 >>> I2C read: I/O error >>> Unrecognized expansion board: 0 >> >> OK, this stuff is bad. It means the Overo can't read some data from the >> onboard i2c EEPROM. The first thing to try is re-seating the Overo on >> the motherboard. >> >> Philip >> >> >>> Die ID #0a300004000000000403730510014003 >>> Net: Net Initialization Skipped >>> No ethernet found. >>> Hit any key to stop autoboot: >>> >>> >>> ////////////////////////////////////////////MISSING STUFF >>> HERE///////////////////////////////////////////////// >>> >>> >>> [ 3.762786] Key type dns_resolver registered >>> [ 3.767822] VFP support v0.3: implementor 41 architecture 3 part 30 >>> variant c rev 1 >>> [ 3.783386] ThumbEE CPU extension supported. >>> [ 3.787994] sr_init: No PMIC hook to init smartreflex >>> [ 3.793762] smartreflex smartreflex.0: omap_sr_probe: SmartReflex >> driver >>> initialized >>> [ 3.802276] mmc0: new SDHC card at address e624 >>> [ 3.807495] smartreflex smartreflex.1: omap_sr_probe: SmartReflex >> driver >>> initialized >>> [ 3.816528] mmcblk0: mmc0:e624 SU08G 7.40 GiB >>> [ 3.831420] mmcblk0: p1 p2 >>> [ 3.836425] clock: disabling unused clocks to save power >>> [ 3.844238] registered taskstats version 1 >>> [ 3.850128] fbcvt: 640x480@60: CVT Name - .307M3-R >>> [ 3.865692] Console: switching to colour frame buffer device 80x30 >>> [ 3.881072] VDAC: incomplete constraints, leaving on >>> [ 3.888549] twl_rtc twl_rtc: setting system clock to 2013-12-19 >> 02:27:37 >>> UTC (1387420057) >>> [ 3.897399] ALSA device list: >>> [ 3.900665] #0: omap3beagle >>> [ 3.909027] EXT3-fs (mmcblk0p2): recovery required on readonly >> filesystem >>> [ 3.916320] EXT3-fs (mmcblk0p2): write access will be enabled during >>> recovery >>> [ 4.325744] kjournald starting. Commit interval 5 seconds >>> [ 4.336456] EXT3-fs (mmcblk0p2): recovery complete >>> [ 4.341613] EXT3-fs (mmcblk0p2): mounted filesystem with writeback >> data >>> mode >>> [ 4.349151] VFS: Mounted root (ext3 filesystem) readonly on device >> 179:2. >>> [ 4.360687] devtmpfs: mounted >>> [ 4.364501] Freeing init memory: 224K >>> INIT: version 2.88 booting >>> Starting udev >>> [ 5.420043] udevd[72]: starting version 182 >>> Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such >> file >>> or directory >>> bootlogd. >>> [ 10.349182] EXT3-fs (mmcblk0p2): using internal journal >>> ALSA: Restoring mixer settings... >>> Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device >>> Starting rpcbind daemon...[ 12.370544] NET: Registered protocol family >> 10 >>> done. >>> INIT: Entering runlevel: 5 >>> Starting system message bus: dbus. >>> Starting OpenBSD Secure Shell server: sshd >>> done. >>> Starting Distributed Compiler Daemon: distcc. >>> Starting syslogd/klogd: done >>> * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon >> [ >>> ok ] >>> Starting Telephony daemon >>> Starting Linux NFC daemon >>> Starting OProfileUI server >>> Stopping Bootlog daemon: bootlogd. >>> >>> >>> >>> >>> >>> >>> On Mon, Jan 6, 2014 at 12:20 PM, Philip Balister <philip@opensdr.com> >> wrote: >>> >>>> On 01/06/2014 10:06 AM, Taylor Centers wrote: >>>>> I get an error running uhd_usrp_probe and can't figure out why, I >>>>> would definitely appreciate any insight into this error and how to >>>>> resolve it. Thanks! >>>> >>>> Do you have a monitor attached? >>>> >>>> Can you try this without a monitor by logging in over the serial port? >>>> >>>> I'd like to see the messages from u-boot at the start of the boot >> process. >>>> >>>> Thanks, >>>> >>>> Philip >>>> >>>>> >>>>> >>>>> root@ettus-e1xx:/apps# uhd_usrp_probe >>>>> linux; GNU C++ version 4.7.2; Boost_105300; UHD_003.005.002-0-unknown >>>>> >>>>> -- Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga_v2.bin... >>>> done = 1 >>>>> >>>>> -- 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 >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> USRP-users mailing list >>>>> USRP-users@lists.ettus.com >>>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>>>> >>>> >>>> >>> >> >> >