TRX clock interface timed out, assuming TRX is dead

[habib]

hi everyone.
i am using bladerf x115 with ubuntu 14.04. i am trying to run YateBts. when i use this command .sudo yate -sd -vvvvv -l /var/yate.log. my radio device response and the output of log file is

Code: Select all

Primitive: RadioReady
Info: 0
-----
2014-12-22_23:18:19.818500 <ybts:NOTE> State changed Running -> RadioUp
ALERT 140558074234624 23:18:23.0 TRXManager.cpp:500:setSlot: SETSLOT failed with status -1
2014-12-22_23:18:23.060594 <mbts:WARN> TRXManager.cpp:500:setSlot: SETSLOT failed with status -1
ALERT 140558074234624 23:18:23.0 TRXManager.cpp:500:setSlot: SETSLOT failed with status -1
2014-12-22_23:18:23.061568 <mbts:WARN> TRXManager.cpp:500:setSlot: SETSLOT failed with status -1
ALERT 140558075676416 23:18:25.0 TRXManager.cpp:460:setPower: SETPOWER failed with status -1
2014-12-22_23:18:25.065011 <mbts:WARN> TRXManager.cpp:460:setPower: SETPOWER failed with status -1
ALERT 140558075676416 23:18:31.0 TRXManager.cpp:460:setPower: SETPOWER failed with status -1
2014-12-22_23:18:31.065464 <mbts:WARN> TRXManager.cpp:460:setPower: SETPOWER failed with status -1
EMERG 140558112577280 23:18:44.2 TRXManager.cpp:96:clockHandler: TRX clock interface timed out, assuming TRX is dead.
2014-12-22_23:18:44.228273 <mbts:GOON> TRXManager.cpp:96:clockHandler: TRX clock interface timed out, assuming TRX is dead.

thus may be my problem is TRX clock interface timed out, assuming TRX is dead. i don,t know whay this problem is arrised.Thanks

[habib]

Ya problem is solved.the problem was in my firmware. if you faced this problem ,you may follow this link (http://forum.yate.ro/index.php?topic=37 ... 98#msg1098). this instruction was great at site of me.thanks everyone for helping.special thanks to my twitter friend Jean-Michel Picod. After setting NIB i am playing with YatesBts and 6 cell phone.

[jynik]

Nice work habib - thanks for following up!

I commented on that Yate forum thread and just wanted to echo here the note here that moving forward, we'll look to keep our top-level CHANGELOG updated with a list of compatible versions. However, using the compatible versions recommended by the Yate team is probably the best idea, given that they would have tested and verified things on their end.

I hope you'll stick around the bladeRF and Yate forums to help assits folks running into similar issues!