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.
