Hi all, So I just started playing with a new E100 with an SBX daughterboard and SD card dated around Sep. 29, 2011. I tried to do something simple like rx_samples_to_file or rx_ascii_art_dft, but they error out when they check the lo_locked sensor. From the LEDs, I can see that RX_LD is off and TX_LD is on. I've tried many different frequencies as well with same results. Am I missing something? I wonder if this is a hardware or software issue. Thanks, ~Jahshan root@usrp-e1xx:/usr/share/uhd/examples# ./rx_ascii_art_dft --rate=1e6 --freq=xxxe6 linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500; UHD_003.003.000-e0a7b8a Creating the usrp device with: ... -- Opening device node /dev/usrp_e0... -- Initializing FPGA clock to 64.000000MHz... -- USRP-E100 clock control: 6 -- r_counter: 1 -- a_counter: 0 -- b_counter: 12 -- prescaler: 8 -- vco_divider: 2 -- chan_divider: 15 -- vco_rate: 1920.000000MHz -- chan_rate: 960.000000MHz -- out_rate: 64.000000MHz -- -- Performing wishbone readback test... pass Using Device: Single USRP: Device: E-Series Device Mboard 0: E100 (xxxxxxxx) RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX (0x0054) TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX (0x0055) Setting RX Rate: 1.000000 Msps... Actual RX Rate: 1.000000 Msps... Setting RX Freq: xxx.000000 MHz... Actual RX Freq: xxx.000000 MHz... Checking RX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int _main(int, char**) at /home/balister/src/git/oe/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/uhd-git-r6.7/git/host/examples/rx_ascii_art_dft.cpp:136

On 10/08/2011 05:32 PM, Jahshan Bhatti wrote: > Hi all, > > So I just started playing with a new E100 with an SBX daughterboard > and SD card dated around Sep. 29, 2011. I tried to do something simple > like rx_samples_to_file or rx_ascii_art_dft, but they error out when > they check the lo_locked sensor. From the LEDs, I can see that RX_LD > is off and TX_LD is on. I've tried many different frequencies as well > with same results. Am I missing something? I wonder if this is a > hardware or software issue. I don't know if this will solve your problem, but you should go ahead and update your sd card to this version: http://dl.dropbox.com/u/14618236/E100-sd-07OCT2011-1.bin.gz Philip > > Thanks, > ~Jahshan > > > root@usrp-e1xx:/usr/share/uhd/examples# ./rx_ascii_art_dft --rate=1e6 > --freq=xxxe6 > linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500; > UHD_003.003.000-e0a7b8a > > > Creating the usrp device with: ... > -- Opening device node /dev/usrp_e0... > -- Initializing FPGA clock to 64.000000MHz... > -- USRP-E100 clock control: 6 > -- r_counter: 1 > -- a_counter: 0 > -- b_counter: 12 > -- prescaler: 8 > -- vco_divider: 2 > -- chan_divider: 15 > -- vco_rate: 1920.000000MHz > -- chan_rate: 960.000000MHz > -- out_rate: 64.000000MHz

No change. ~Jahshan On Sat, Oct 8, 2011 at 4:40 PM, Philip Balister <philip@balister.org> wrote: > On 10/08/2011 05:32 PM, Jahshan Bhatti wrote: >> Hi all, >> >> So I just started playing with a new E100 with an SBX daughterboard >> and SD card dated around Sep. 29, 2011. I tried to do something simple >> like rx_samples_to_file or rx_ascii_art_dft, but they error out when >> they check the lo_locked sensor. From the LEDs, I can see that RX_LD >> is off and TX_LD is on. I've tried many different frequencies as well >> with same results. Am I missing something? I wonder if this is a >> hardware or software issue. > > I don't know if this will solve your problem, but you should go ahead > and update your sd card to this version: > > http://dl.dropbox.com/u/14618236/E100-sd-07OCT2011-1.bin.gz > > Philip > >> >> Thanks, >> ~Jahshan >> >> >> root@usrp-e1xx:/usr/share/uhd/examples# ./rx_ascii_art_dft --rate=1e6 >> --freq=xxxe6 >> linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500; >> UHD_003.003.000-e0a7b8a >> >> >> Creating the usrp device with: ... >> -- Opening device node /dev/usrp_e0... >> -- Initializing FPGA clock to 64.000000MHz... >> -- USRP-E100 clock control: 6 >> --   r_counter: 1 >> --   a_counter: 0 >> --   b_counter: 12 >> --   prescaler: 8 >> --   vco_divider: 2 >> --   chan_divider: 15 >> --   vco_rate: 1920.000000MHz >> --   chan_rate: 960.000000MHz >> --   out_rate: 64.000000MHz >

On 10/08/2011 02:32 PM, Jahshan Bhatti wrote: > Hi all, > > So I just started playing with a new E100 with an SBX daughterboard > and SD card dated around Sep. 29, 2011. I tried to do something simple > like rx_samples_to_file or rx_ascii_art_dft, but they error out when > they check the lo_locked sensor. From the LEDs, I can see that RX_LD > is off and TX_LD is on. I've tried many different frequencies as well > with same results. Am I missing something? I wonder if this is a > hardware or software issue. > Sounds like something is not clocked or not powered correctly. I would check to make sure that the daugtercard is correctly seated and screwed in. If this is not the case, our daughterboard guy can give you some more helpful tips on monday. -Josh

After further investigation, it seems like pin 11 and 13 on the RX daughterboard interface does not have a clock signal. The TX side (pin 12 and 14) does have a valid 64 MHz clock signal. I had a DBSRX2 card as well, and it did not lock on this E100. ~Jahshan On Sun, Oct 9, 2011 at 10:48 AM, Josh Blum <josh@ettus.com> wrote: > > > On 10/08/2011 02:32 PM, Jahshan Bhatti wrote: >> Hi all, >> >> So I just started playing with a new E100 with an SBX daughterboard >> and SD card dated around Sep. 29, 2011. I tried to do something simple >> like rx_samples_to_file or rx_ascii_art_dft, but they error out when >> they check the lo_locked sensor. From the LEDs, I can see that RX_LD >> is off and TX_LD is on. I've tried many different frequencies as well >> with same results. Am I missing something? I wonder if this is a >> hardware or software issue. >> > > Sounds like something is not clocked or not powered correctly. I would > check to make sure that the daugtercard is correctly seated and screwed > in. If this is not the case, our daughterboard guy can give you some > more helpful tips on monday. > > -Josh > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >

After even further investigation, assuming that the TX and RX clock circuit are supposed to be identical, then the board (U1E Board Rev. 4.0) is missing L205 (near U8). I couldn't find these components on the posted schematic though. ~Jahshan On Mon, Oct 10, 2011 at 10:57 AM, Jahshan Bhatti <jabhatti91@gmail.com> wrote: > After further investigation, it seems like pin 11 and 13 on the RX > daughterboard interface does not have a clock signal. The TX side (pin > 12 and 14) does have a valid 64 MHz clock signal. I had a DBSRX2 card > as well, and it did not lock on this E100. > > ~Jahshan > > On Sun, Oct 9, 2011 at 10:48 AM, Josh Blum <josh@ettus.com> wrote: >> >> >> On 10/08/2011 02:32 PM, Jahshan Bhatti wrote: >>> Hi all, >>> >>> So I just started playing with a new E100 with an SBX daughterboard >>> and SD card dated around Sep. 29, 2011. I tried to do something simple >>> like rx_samples_to_file or rx_ascii_art_dft, but they error out when >>> they check the lo_locked sensor. From the LEDs, I can see that RX_LD >>> is off and TX_LD is on. I've tried many different frequencies as well >>> with same results. Am I missing something? I wonder if this is a >>> hardware or software issue. >>> >> >> Sounds like something is not clocked or not powered correctly. I would >> check to make sure that the daugtercard is correctly seated and screwed >> in. If this is not the case, our daughterboard guy can give you some >> more helpful tips on monday. >> >> -Josh >> >> _______________________________________________ >> USRP-users mailing list >> USRP-users@lists.ettus.com >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >> >

Hi all, I'm not sure if I've identified the problem.. can someone confirm? If so, what action should be taken here (find the inductor (size?, inductance?) and solder it on, send the E100 back in, etc.)? ~Jahshan On Mon, Oct 10, 2011 at 11:46 AM, Jahshan Bhatti <jabhatti91@gmail.com> wrote: > After even further investigation, assuming that the TX and RX clock > circuit are supposed to be identical, then the board (U1E Board Rev. > 4.0) is missing L205 (near U8). I couldn't find these components on > the posted schematic though. > > ~Jahshan > > On Mon, Oct 10, 2011 at 10:57 AM, Jahshan Bhatti <jabhatti91@gmail.com> wrote: >> After further investigation, it seems like pin 11 and 13 on the RX >> daughterboard interface does not have a clock signal. The TX side (pin >> 12 and 14) does have a valid 64 MHz clock signal. I had a DBSRX2 card >> as well, and it did not lock on this E100. >> >> ~Jahshan >> >> On Sun, Oct 9, 2011 at 10:48 AM, Josh Blum <josh@ettus.com> wrote: >>> >>> >>> On 10/08/2011 02:32 PM, Jahshan Bhatti wrote: >>>> Hi all, >>>> >>>> So I just started playing with a new E100 with an SBX daughterboard >>>> and SD card dated around Sep. 29, 2011. I tried to do something simple >>>> like rx_samples_to_file or rx_ascii_art_dft, but they error out when >>>> they check the lo_locked sensor. From the LEDs, I can see that RX_LD >>>> is off and TX_LD is on. I've tried many different frequencies as well >>>> with same results. Am I missing something? I wonder if this is a >>>> hardware or software issue. >>>> >>> >>> Sounds like something is not clocked or not powered correctly. I would >>> check to make sure that the daugtercard is correctly seated and screwed >>> in. If this is not the case, our daughterboard guy can give you some >>> more helpful tips on monday. >>> >>> -Josh >>> >>> _______________________________________________ >>> USRP-users mailing list >>> USRP-users@lists.ettus.com >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> >> >

On 10/10/2011 12:48 PM, Jahshan Bhatti wrote: > Hi all, > > I'm not sure if I've identified the problem.. can someone confirm? If > so, what action should be taken here (find the inductor (size?, > inductance?) and solder it on, send the E100 back in, etc.)? > Yes definitely. For the record, the missing part is not missing from the other boards in that batch. So it seems to be a freak occurrence. Anyway congrats on finding and debugging that. And expect an email off-list from my co-worker. Thanks, -josh > ~Jahshan > > On Mon, Oct 10, 2011 at 11:46 AM, Jahshan Bhatti <jabhatti91@gmail.com> wrote: >> After even further investigation, assuming that the TX and RX clock >> circuit are supposed to be identical, then the board (U1E Board Rev. >> 4.0) is missing L205 (near U8). I couldn't find these components on >> the posted schematic though. >> >> ~Jahshan >> >> On Mon, Oct 10, 2011 at 10:57 AM, Jahshan Bhatti <jabhatti91@gmail.com> wrote: >>> After further investigation, it seems like pin 11 and 13 on the RX >>> daughterboard interface does not have a clock signal. The TX side (pin >>> 12 and 14) does have a valid 64 MHz clock signal. I had a DBSRX2 card >>> as well, and it did not lock on this E100. >>> >>> ~Jahshan >>> >>> On Sun, Oct 9, 2011 at 10:48 AM, Josh Blum <josh@ettus.com> wrote: >>>> >>>> >>>> On 10/08/2011 02:32 PM, Jahshan Bhatti wrote: >>>>> Hi all, >>>>> >>>>> So I just started playing with a new E100 with an SBX daughterboard >>>>> and SD card dated around Sep. 29, 2011. I tried to do something simple >>>>> like rx_samples_to_file or rx_ascii_art_dft, but they error out when >>>>> they check the lo_locked sensor. From the LEDs, I can see that RX_LD >>>>> is off and TX_LD is on. I've tried many different frequencies as well >>>>> with same results. Am I missing something? I wonder if this is a >>>>> hardware or software issue. >>>>> >>>> >>>> Sounds like something is not clocked or not powered correctly. I would >>>> check to make sure that the daugtercard is correctly seated and screwed >>>> in. If this is not the case, our daughterboard guy can give you some >>>> more helpful tips on monday. >>>> >>>> -Josh >>>> >>>> _______________________________________________ >>>> USRP-users mailing list >>>> USRP-users@lists.ettus.com >>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>>> >>> >> > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com