Author Topic: Running YateBTS on BladeRF (Video)  (Read 5172 times)

habibur333

  • Newbie
  • *
  • Posts: 17
    • View Profile
Running YateBTS on BladeRF (Video)
« on: January 16, 2015, 02:04:25 AM »
I have installed YateBTS sucessfully on my bladerf x115 device. You may see the video from this link.(http://youtu.be/3iirE8xuji4). if u have any question ,Please ask me without any hesitation in Twitter.(https://twitter.com/Habibur18495307). Thanks

Diana Cionoiu

  • Administrator
  • Jr. Member
  • *****
  • Posts: 71
    • View Profile
Re: Running YateBTS on BladeRF (Video)
« Reply #1 on: March 31, 2015, 02:14:36 AM »
Really really cool.

cagriaksu

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Running YateBTS on BladeRF (Video)
« Reply #2 on: April 03, 2015, 09:32:33 AM »
This is really cool, can you please share your guide on how to prepare this system?

andrew77

  • Newbie
  • *
  • Posts: 30
    • View Profile
Re: Running YateBTS on BladeRF (Video)
« Reply #3 on: April 11, 2015, 11:16:26 AM »
Hello guys,
I have a problem when running yate with bladeRF:
I have USB2.0
the installation of yate and yate BTS all gone OK via SVN

this is the output when i run:
 yate -Df -vvvv -l /var/log/yate.log

20150411113607.759068 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
20150411113607.763468 <nib:CONF> Please configure country code. See subscribers.conf or use the NIB web interface
20150411113607.765483 <NOTE> Failed to open config file '/usr/local/etc/yate/tmsidata.conf', using defaults (2: No such file or directory)
20150411113607.766009 <nib:INFO> Finished reading saved registered subscribers. Found 0 registered_subscribers.
20150411113607.766748 <nib:INFO> Checked that only NIB is enabled.
Yate engine is initialized and starting up on and-HP-Compaq-2510p-Notebook-PC
20150411113607.767043 <INFO> Creating first message dispatching thread
20150411113608.279609 <cpuload:NOTE> Updating CPU core number from 1 to 2
20150411113608.486824 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
20150411113609.487476 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
20150411113610.488483 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
20150411113611.489554 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
20150411113612.490525 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 5
20150411113612.490618 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver
ALERT 3075032832 13:36:12.4 TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150411113612.491006 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
20150411113612.595984 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver w/ 1 ARFCNs and Args:
EMERG 3074321216 13:36:12.5 OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver
20150411113612.596437 <mbts:GOON> OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver
EMERG 3074321216 13:36:12.5 OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting.
20150411113612.597726 <mbts:GOON> OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting

ybts.conf doesn't show transceiver-bladerf:

Path: string: Path to the transceiver relative to where the MBTS is started.
; Should be one of: ./transceiver-rad1 ./transceiver-usrp1 ./transceiver-uhd
; Defaults to ./transceiver.
;Path=./transceiver

but config.log produced by Yatebts's ./configure seems ok:

checking for bladeRF support using pkg-config
configure:4448: result: 1.2.1-2015.02-1-ppatrusty
configure:4483: checking libusb-1.0/libusb.h usability
configure:4483: gcc -c  -O2 -DLITTLE_ENDIAN  conftest.c >&5
configure:4483: $? = 0
configure:4483: result: yes
configure:4483: checking libusb-1.0/libusb.h presence
configure:4483: gcc -E  conftest.c
configure:4483: $? = 0
configure:4483: result: yes
configure:4483: checking for libusb-1.0/libusb.h
configure:4483: result: yes
configure:4749: creating ./config.status

I don't know how to solve this issue

cagriaksu

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Running YateBTS on BladeRF (Video)
« Reply #4 on: April 12, 2015, 10:46:42 AM »
Just select the correct transceiver from the NIB web panel. If the problem persists, please feed more info here.

andrew77

  • Newbie
  • *
  • Posts: 30
    • View Profile
Re: Running YateBTS on BladeRF (Video)
« Reply #5 on: April 19, 2015, 12:32:28 PM »
Solved!
Thanks

cmurmann

  • Newbie
  • *
  • Posts: 2
    • View Profile
Running YateBTS on BladeRF
« Reply #6 on: June 03, 2015, 09:18:56 PM »
Hello,

I set up the transceiver in the nib and also tried manually in the ybts.conf , when I probe bladerf or info everything seems properly working (FPGA loaded and all).

bladeRF> info

  Serial #:                 2c77309e4cf55388978bd44e5ac352b9
  VCTCXO DAC calibration:   0x9650
  FPGA size:                115 KLE
  FPGA loaded:              yes
  USB bus:                  2
  USB address:              2
  USB speed:                SuperSpeed
  Backend:                  libusb
  Instance:                 0



Logs :

2015-06-03_23:15:02.808998 <ybts:NOTE> State changed WaitHandshake -> Running
2015-06-03_23:15:02.809022 <ybts-signalling:INFO> Sending [0x253d330]
-----
Primitive: Handshake
Info: 0
-----
2015-06-03_23:15:02.829508 <javascript:INFO> Parsed 'nib' script: /usr/local/share/yate/scripts/nib.js
2015-06-03_23:15:02.831382 <nib:CONF> Please configure country code. See subscribers.conf or use the NIB web interface
2015-06-03_23:15:02.832212 <NOTE> Failed to open config file '/usr/local/etc/yate/tmsidata.conf', using defaults (2: No such file or directory)
2015-06-03_23:15:02.832411 <nib:INFO> Finished reading saved registered subscribers. Found 0 registered_subscribers.
2015-06-03_23:15:02.832774 <nib:INFO> Checked that only NIB is enabled.
2015-06-03_23:15:02.832831 <ALL> Rescanning handler list for 'engine.start' [0x7ffcaa0fd020] at priority 100
Yate engine is initialized and starting up on lpt
2015-06-03_23:15:02.832922 <INFO> Creating first message dispatching thread
2015-06-03_23:15:03.725090 <cpuload:NOTE> Updating CPU core number from 1 to 4
2015-06-03_23:15:03.809995 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 1
2015-06-03_23:15:04.810642 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 2
2015-06-03_23:15:05.811791 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 3
2015-06-03_23:15:06.812588 <mbts:MILD> TRXManager.cpp:283:sendCommandPacket: TRX link timeout on attempt 4
ALERT 140467719026496 23:15:07.8 TRXManager.cpp:432:powerOff: POWEROFF failed with status -12015-06-03_23:15:07.813478 <mbts:MILD> TRXManager.c$

2015-06-03_23:15:07.813518 <mbts:NOTE> TRXManager.cpp:293:sendCommandPacket: lost control link to transceiver
2015-06-03_23:15:07.813530 <mbts:WARN> TRXManager.cpp:432:powerOff: POWEROFF failed with status -1
2015-06-03_23:15:07.890610 <mbts:NOTE> OpenBTS.cpp:145:startTransceiver: starting transceiver ./transceiver-bladerf w/ 1 ARFCNs and Args:
EMERG 140467718141696 23:15:07.8 OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver-bladerf
2015-06-03_23:15:07.890780 <mbts:GOON> OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver-bladerf
EMERG 140467718141696 23:15:07.8 OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting.
2015-06-03_23:15:07.890868 <mbts:GOON> OpenBTS.cpp:159:startTransceiver: Transceiver quit with status 256. Exiting.
2015-06-03_23:15:11.013331 <ybts:NOTE> Peer pid 24186 vanished
2015-06-03_23:15:11.013373 <ybts:ALL> Restart scheduled in 1ms [0x7ff8cf6b6580]
2015-06-03_23:15:11.013383 <ybts:ALL> Scheduled stop in 0ms
2015-06-03_23:15:12.012003 <ybts:NOTE> 'shutdown' command failed

I dont know what I'm doing wrong.
« Last Edit: June 03, 2015, 09:29:25 PM by cmurmann »