« previous next »
Pages: [1]

Author Topic: BladeRF issues - UPDATED  (Read 10257 times)

cmurmann

  • Newbie
  • *
  • Posts: 2
    • View Profile
BladeRF issues - UPDATED
« on: June 12, 2015, 11:09:41 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.


----------------------------------------

After talking with L-FY on IRC channel yate / freenode. It came to an issue with new libraries, as to our conversation he explained they are working on a new release for next week that shouldnt rely anymore on the old libraries. Looking forward!

Thanks for the hardwork
« Last Edit: June 15, 2015, 06:29:41 PM by cmurmann »
Logged

noob

  • Newbie
  • *
  • Posts: 1
    • View Profile
Re: BladeRF issues - UPDATED
« Reply #1 on: July 06, 2015, 10:23:04 PM »
Hi,

Does anyone have an update to this?

Ive been trying for 3 days to get this to work... killing me...

Logged

Diana Cionoiu

  • Administrator
  • Jr. Member
  • *****
  • Posts: 71
    • View Profile
Re: BladeRF issues - UPDATED
« Reply #2 on: July 20, 2015, 07:54:52 AM »
Use the latest YateBTS SVN with the latest Yate SVN.
Logged

Ioana Stanciu

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
Re: BladeRF issues - UPDATED
« Reply #3 on: July 21, 2015, 01:31:14 AM »
Hi,
 
If you're using a SVN revision prior to rev. 504, this should give you a clue:

Quote
2015-06-03_23:15:07.890780 <mbts:GOON> OpenBTS.cpp:151:startTransceiver: cannot find ./transceiver-bladerf


Possible causes for this:
* you don't have the development version of bladerf or libusb1, so the transceiver was not compiled. Check where you compiled YateBTS that you have the compiled transceiver-bladerf (it should be in mbts/TransceiverRAD1). If you don't have it, run the configure script again and look for the lines that say if it detected support for it or not.
* you didn't configure the correct path to the transceiver-bladerf. Check again the path to the installed transceiver-bladerf and make sure you have configured it correctly in ybts.conf.


If you're using SVN revision 504 or upwards, you don't need bladerf-devel anymore. Just make sure that you use the latest Yate also and that you have libusb1-devel.
Logged
Pages: [1]
« previous next »