this is my output after editing the Makefile:
https://pastebin.com/3mhwccp2
BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
-
- Posts: 9
- Joined: Fri Dec 07, 2018 12:10 am
-
- Posts: 156
- Joined: Thu Feb 28, 2013 11:14 pm
Re: BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
You should run `make' in the upper directory. So cd .. down from modules. If you run make in yate/ it will invoke yate/modules's Make as well.
The output looks good though, there were no errors. I would suggest running a make clean in yate/modules now to ensure no stale files.
.
The output looks good though, there were no errors. I would suggest running a make clean in yate/modules now to ensure no stale files.
.
-
- Posts: 9
- Joined: Fri Dec 07, 2018 12:10 am
Re: BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
Yate and YateBTS successfully installed.
Here is output of when I try to run yate -s
https://pastebin.com/2b3ZX2ec
have a couple of errors - definitely made progress today though
output from: sudo yate -sd -vvvvv -l /var/yate.log
https://pastebin.com/28tmGphv
Here is output of when I try to run yate -s
https://pastebin.com/2b3ZX2ec
have a couple of errors - definitely made progress today though
output from: sudo yate -sd -vvvvv -l /var/yate.log
https://pastebin.com/28tmGphv
-
- Posts: 8
- Joined: Fri Oct 26, 2018 2:54 am
Re: BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
Hi, Robert;
BladeRF with YateBTS has worked successfully, but it gives the following errors and turns off the device. Why do you think it would be?
2018-12-08_13:29:48.666724 <gsmtrx:NOTE> ARFCN[0]: Duplicate burst received at 448 56/0 [0x7f4fd4033bb0]
EMERG 140214413788928 13:29:52.4 proc 14278 TRXManager.cpp:266:clockHandler: thread 140214413788928: TRX clock interface timed out, assuming TRX is dead.
2018-12-08_13:29:52.429785 <mbts:CRIT> proc 14278 TRXManager.cpp:266:clockHandler: thread 140214413788928: TRX clock interface timed out, assuming TRX is dead.
2018-12-08_13:29:52.429988 <ybts-signalling:NOTE> Peer stop notification 'RadioLost' [0x1e12fa0]
2018-12-08_13:29:53.002847 <mbts:NOTE> proc 14278 TRXManager.cpp:127:sendCommandPacket: thread 140214414673728: this:0x865cc0 command CMD STOP
2018-12-08_13:29:53.004092 <gsmtrx:NOTE> Stopping transceiver: received STOP command
BladeRF with YateBTS has worked successfully, but it gives the following errors and turns off the device. Why do you think it would be?
2018-12-08_13:29:48.666724 <gsmtrx:NOTE> ARFCN[0]: Duplicate burst received at 448 56/0 [0x7f4fd4033bb0]
EMERG 140214413788928 13:29:52.4 proc 14278 TRXManager.cpp:266:clockHandler: thread 140214413788928: TRX clock interface timed out, assuming TRX is dead.
2018-12-08_13:29:52.429785 <mbts:CRIT> proc 14278 TRXManager.cpp:266:clockHandler: thread 140214413788928: TRX clock interface timed out, assuming TRX is dead.
2018-12-08_13:29:52.429988 <ybts-signalling:NOTE> Peer stop notification 'RadioLost' [0x1e12fa0]
2018-12-08_13:29:53.002847 <mbts:NOTE> proc 14278 TRXManager.cpp:127:sendCommandPacket: thread 140214414673728: this:0x865cc0 command CMD STOP
2018-12-08_13:29:53.004092 <gsmtrx:NOTE> Stopping transceiver: received STOP command
-
- Posts: 9
- Joined: Fri Dec 07, 2018 12:10 am
Re: BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
Did a fresh install of ubuntu 18.10 and used these steps:
was able to console into the bladeRF-cli and check basic commands.
Now onto Yate:
Next onto the yate tar:
edited the lines of Makefile according:
so far so good...
the make install fails erroring on line 259 of Makefile.
To fix this:
Try again:
everything installs.
go on to build and install yateBTS:
start apache and create the link to nipc:
I was getting an error saying it couldnt find the .RBF file in " /home/x1y/ ..."
To fix this:
led to this:
used vim to staticly add my username (me) to make it the proper path..created the proper path and then moved the xA4.RBF to the /Nuand/
Complete output of:
https://pastebin.com/63fZZAfF
TLDR:
Hope this is useful...
Code: Select all
$ sudo add-apt-repository ppa:bladerf/bladerf
$ sudo apt-get update
$ sudo apt-get install bladerf
$ sudo apt-get install libbladerf-dev
$ sudo apt-get install bladerf-fpga-hostedxa4
Now onto Yate:
Code: Select all
sudo addgroup yate
sudo usermod -a -G yate me
Code: Select all
dos2unix *
./autogen.sh
./configure --prefix=/usr/local
Code: Select all
LDFLAGS:= -lbladeRF -g3
YATELIBS:= -L.. -lyate -lbladeRF -g3
Code: Select all
make
sudo make install
To fix this:
Code: Select all
sudo make install-noapi
Try again:
Code: Select all
sudo make install
sudo ldconfig
go on to build and install yateBTS:
Code: Select all
./autogen.sh
./configure --prefix=/usr/local
make
sudo make install
sudo ldconfig
Code: Select all
sudo touch /usr/local/etc/yate/snmp_data.conf /usr/local/etc/yate/tmsidata.conf
sudo chown root:yate /usr/local/etc/yate/*.conf
sudo chmod g+w /usr/local/etc/yate/*.conf
start apache and create the link to nipc:
Code: Select all
sudo ln -s /usr/local/share/yate/nipc_web/ nipc
Code: Select all
sudo yate -vvvvvv -CDoa
To fix this:
Code: Select all
sudo find / -xdev -type f -print0 | xargs -0 grep -H "/home/x1y/"
Code: Select all
/home/me/Downloads/yate/yate/modules/radio/ybladerf.cpp: bladerf_load_fpga((struct bladerf *)lb_dev, "/home/x1y/.config/Nuand/hostedxA4.rbf");
Complete output of:
Code: Select all
sudo yate -vvvvvv -CDoa
TLDR:
Code: Select all
EMERG 140035957196544 13:32:06.7 proc 16019 TRXManager.cpp:266:clockHandler: thread 140035957196544: TRX clock interface timed out, assuming TRX is dead.
2018-12-09_13:32:06.714768 <ybts-signalling:INFO> Received [0x55beb4ff1780]
-----
Primitive: Stop
Info: 1
-----
2018-12-09_13:32:06.714782 <ybts-signalling:NOTE> Peer stop notification 'RadioLost' [0x55beb4ff1780]
2018-12-09_13:32:06.714788 <ybts:ALL> Restart scheduled in 1ms [0x7fa7686f5500]
2018-12-09_13:32:06.714794 <ybts:ALL> Scheduled stop in 0ms
2018-12-09_13:32:06.714798 <ybts-signalling:ALL> Worker thread terminated [0x55beb4ff1780]
2018-12-09_13:32:06.714805 <mbts:CRIT> proc 16019 TRXManager.cpp:266:clockHandler: thread 140035957196544: TRX clock interface timed out, assuming TRX is dead.
2018-12-09_13:32:07.003701 <mbts:NOTE> proc 16019 TRXManager.cpp:127:sendCommandPacket: thread 140035958077248: this:0x55abba24d5c0 command CMD STOP
2018-12-09_13:32:07.004788 <gsmtrx:INFO> Module state changed Running -> Waiting
2018-12-09_13:32:07.004798 <gsmtrx:NOTE> Stopping transceiver: received STOP command
2018-12-09_13:32:07.004848 <gsmtrx:ALL> Radio device read thread (0x7fa73c002470) terminated [0x7fa73c01ac60]
2018-12-09_13:32:07.004868 <gsmtrx:ALL> Radio device send thread (0x7fa73c028c70) terminated [0x7fa73c01ac60]
2018-12-09_13:32:07.004920 <gsmtrx:ALL> Stopping [0x7fa73c01ac60]
2018-12-09_13:32:07.004943 <gsmtrx:ALL> Sending 'EXITING' on clock interface [0x7fa73c01ac60]
-
- Posts: 8
- Joined: Fri Oct 26, 2018 2:54 am
Re: BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
Exactly the same problem I've experienced.
-
- Posts: 156
- Joined: Thu Feb 28, 2013 11:14 pm
Re: BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
Let me try things out on a few other machines, and I'll provide some updated documentation on this.
-
- Posts: 9
- Joined: Fri Dec 07, 2018 12:10 am
Re: BladeRF 2.0 openLTE, srsLTE and YateBTS Problem
thanks robert
-
- Posts: 156
- Joined: Thu Feb 28, 2013 11:14 pm