After struggling with building openLTE for Raspberry Pi 3 Model B running
Raspbian 8 Lite and repeated failure due to mismatched dependency hell. I
attempted to try ArchLinux-ARM (I'm more comfortable with ArchLinux's build
and packaging process) successfully installed some pre-build bleeding edge
packages like gnuradio, GrOsmoSDR, rtl-sdr, UHD, HackRF, bladeRF and
iptables, but I had to build/pachage the requisite polarssl 1.3.9 (latest)
locally and finally build/packaged and installed openLTE v00-20-04 for this
platform.
At the moment, I only have bladeRF X40, which LTE_fdd_enodeb recognized;
though the process is still under testing, but I could not resist sharing
this experience with the creators and users of this wonderful software.
The original/current 'enodeb_nat_script.sh' did not work for me, because of
incompatibility and portability issues; I'm working on it and shall soon
share and, or post the updates ASAP.
I once again am heartily thankful to original developers and contributors
of this project, indeed.
Thank you,
Regards,
--
Balwinder S "bdheeman" Dheeman (http://bdheeman.BlogSpot.in/)
"Working together, works! The proof is GNU/Linux and F/LOSS Projects;
Do you too voluntarily work on or contribute to making any difference?"
Hey there, congratulations on getting this to work!
Can you get an eNB from this OpenLTE to show up on a test device? I've got mine running, but a whole heap of error messages regarding RX timestamps (bandwidth related?)
Last edit: hyerisf 2017-03-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everybody,
After struggling with building openLTE for Raspberry Pi 3 Model B running
Raspbian 8 Lite and repeated failure due to mismatched dependency hell. I
attempted to try ArchLinux-ARM (I'm more comfortable with ArchLinux's build
and packaging process) successfully installed some pre-build bleeding edge
packages like gnuradio, GrOsmoSDR, rtl-sdr, UHD, HackRF, bladeRF and
iptables, but I had to build/pachage the requisite polarssl 1.3.9 (latest)
locally and finally build/packaged and installed openLTE v00-20-04 for this
platform.
At the moment, I only have bladeRF X40, which LTE_fdd_enodeb recognized;
though the process is still under testing, but I could not resist sharing
this experience with the creators and users of this wonderful software.
The original/current 'enodeb_nat_script.sh' did not work for me, because of
incompatibility and portability issues; I'm working on it and shall soon
share and, or post the updates ASAP.
I once again am heartily thankful to original developers and contributors
of this project, indeed.
Thank you,
Regards,
--
Balwinder S "bdheeman" Dheeman (http://bdheeman.BlogSpot.in/)
"Working together, works! The proof is GNU/Linux and F/LOSS Projects;
Do you too voluntarily work on or contribute to making any difference?"
Hey there, congratulations on getting this to work!
Can you get an eNB from this OpenLTE to show up on a test device? I've got mine running, but a whole heap of error messages regarding RX timestamps (bandwidth related?)
Last edit: hyerisf 2017-03-11
Same here, I saw a lot of errors like this, "error radio LTE_fdd_enb_radio.cc 996 RX failed: Requested timestamp is in the past".
And don't know, why I'm getting these all my machines are time synced to ntp time servers.