Messages

1

Yate users hangout place / Re: Bladerf, is it working yet?

« on: August 16, 2014, 09:33:06 PM »

just set it with "transceiver-bladerf", there are files fit for BladeRF

2

YateBTS / Re: I have problem with starting Yate with my BladeRF, please help

« on: August 07, 2014, 08:16:39 PM »

In my experience such problems are caused by hardware issues on the USB 3.0 bus - the host controller, the cable or even noise propagated through the cable.

To get a better view of the problems:

• Stop yate
• killall transceiver
• run: yate -Df -vvvv -l /var/log/yate.log

This way you will get a more detailed log. Look in it and see:

• How the bladeRF is initialized (high speed / super speed)
• Which is the first sign of trouble

Another place where it's good to look is the system log. Depending on distribution you may try dmesg | less or less /var/log/messages or journalctl

Consider testing with other cable. If possible power the bladeRF through the external connector (you'll have to change some jumpers on the board).

When I look into the system log I find :
[   17.298542] usb 4-1: New USB device found, idVendor=1d50, idProduct=6066
[   17.298552] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.298557] usb 4-1: Product: bladeRF
[   17.298562] usb 4-1: Manufacturer: Nuand
[   17.298575] usb 4-1: SerialNumber: a9086af51d724f1d800853e50c769922

It is surely superspeed USB

When I start OpenBTS， it's also work well and quit ：
TRXManager.cpp:107:clockHandler: TRX clock interface timed out, assuming TRX is dead.

3

YateBTS / I have problem with starting Yate with my BladeRF, please help

« on: August 07, 2014, 09:53:04 AM »

When I run:
 yate -l /var/log/yate.log
My balderf is well started， but such warn appears time and again：
 
Release 3.1.3 formal build date Jul 14 2014 rev334
Starting MBTS...
MBTS ready
ALERT 140595077220096 13:38:14.9 TRXManager.cpp:460:setPower: SETPOWER failed with status -1
<mbts:WARN> TRXManager.cpp:460:setPower: SETPOWER failed with status -1
Starting MBTS...
ALERT 140210232137600 13:39:17.0 TRXManager.cpp:472:setTSC: SETTSC failed with status 1
<mbts:WARN> TRXManager.cpp:472:setTSC: SETTSC failed with status 1
MBTS ready
CRIT 140209724012288 13:39:18.2 RadioResource.cpp:211:AccessGrantResponder: LUR congestion, RA=11 T3122=2
<mbts:WARN> RadioResource.cpp:211:AccessGrantResponder: LUR congestion, RA=11 T3122=2
EMERG 140210231252736 13:39:41.1 TRXManager.cpp:96:clockHandler: TRX clock interface timed out, assuming TRX is dead.
<mbts:GOON> TRXManager.cpp:96:clockHandler: TRX clock interface timed out, assuming TRX is dead.
MBTS connected to YBTS
 
When it display 'MBTS ready', my mobilephone can search the carrier 'PLMN test 1-1'
But the problem still exists.
I don't konw what's the problem, please help me, thanks