Re: [Openbts-discuss] Connected, but all USB communication to USRP fails

[Dirk K. <Dir...@un...>]

I now further looked into this issue, together with people from our electronics department. So, at is turns out, we are having a nice 52Mhz signal both at CLOCK_OUT and C1016. So I guess it is not a clocking issue? What else could it be?
We speculated if it could be something with the USB, so just the controller works, but no actual data is transmitted although the USRP works fine. Could this be possible? If so, how could we check this?

I would really appreciate your help. Thanks.

On Monday, January 24, 2011 19:45 CET, Alexander Chemeris <ale...@gm...> wrote: 
 
> Dirk,
> 
> This usually means that USRP don't have clock signal at FPGA. USB
> controller has independent clock source and thus your USRP is
> recognized even if you completely remove FPGA clock.So, check your
> FA-SY 1 output.
> 
> On Mon, Jan 24, 2011 at 20:18, Dirk Kirsten
> <Dir...@un...> wrote:
> > Hi,
> >
> > First one side remark regarding my last mail to this list and in case anyone else ever has the same problem: The FA-SY1 needs to be connected to USB, the external power source is just for the heating... Remember this, otherwise you will keep wondering three days, why nothing happens.
> >
> > Unfortunately, I still have connection problems with the USRP1. Using lsusrp I can see the USRP:
> > USRP 0 serial number 4cccbd63
> >  RX d'board A: Flex 1800 Rx MIMO B
> >  RX d'board B: Flex 1800 Rx MIMO B
> >  TX d'board A: Flex 1800 Tx MIMO B
> >  TX d'board B: Flex 1800 Tx MIMO B
> >
> > However, all related test fail to communicate with the USRP. Using usrp_benchmark_usb.py just prints "Testing 2MB/sec..." and then fails. I sniffed the USB communication, this is what happens
> >
> > f691e380 425562708 S Ci:001:00 s a3 00 0000 0001 0004 4 <
> > f691e380 425562726 C Ci:001:00 0 4 = 00010000
> > f691e380 425562732 S Ci:001:00 s a3 00 0000 0002 0004 4 <
> > f691e380 425562740 C Ci:001:00 0 4 = 00010000
> > f7066700 425562745 S Ii:001:01 -115 2 <
> > f7066700 427871024 C Ii:001:01 -2 0
> >
> > I used wireshark to decode it a little, so there are just two control messages passed and two usb interrupts - This seems a bit to less communication for me.
> >
> > Also using usrp_fft or similar has no output at all.
> > Using kalibrator (v0.3) prints the error message "error: usrp_source::tune"
> >
> > I am using Ubuntu 10.10. For me it seems like the USRP is recognized by the bus, but does not answer anything (exept some control messages). Is this correct and more important, what could cause this problem and how could I fix it?
> >
> > Thanks for your replies,
> > Dirk
> >
> > ------------------------------------------------------------------------------
> > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> > Finally, a world-class log management solution at an even better price-free!
> > Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> > February 28th, so secure your free ArcSight Logger TODAY!
> > http://p.sf.net/sfu/arcsight-sfd2d
> > _______________________________________________
> > Openbts-discuss mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/openbts-discuss
> >
> 
> 
> 
> -- 
> Regards,
> Alexander Chemeris.
> http://www.fairwaves.ru