sbts2050-util is a small binary-only userspace program used to
interface with the sysmoBTS 2050 board management controller,
i.e. to enable/disable PA power, read power consumption/temperature
and the like.
This tool is going to disappear once the respective features have been
included in the (open source) sysmobts-util / sysmobts-mgr. Please be
patient meanwhile.
The build differs in that it doesn't use a getty on ttyS0. In the fuutre,
a modified kernel serial driver as well as a 2050-specific utility
for managing the supervisor processor will follow.
This is a osmo-bts that will use libosmo-abis for OML and RSL and
is based on master. In one way it should improve quality in another
it is also testing.
This is a bigger update and brings the SAPI queue, readv/writev
and realtime scheduling to the sysmobts software. This will greatly
improve the stability of the software under load.
Install the sysmobts firmware headers on top of the Osmocom toolchain.
This way the SDK can be used to re-compile both the OpenBSC and the
osmo-bts software.
Make sure the -dev package of the femtobts-api has not runtime
dependencies to a library that does not exist.
The name will be resolved to the hash during parse time. This will
not work when not having access to the internet. Use the sha1 sum
to make offline builds work.
* Fix the link timeout handling as found in post-review.
* Fix the set bts attr parsing due a funny parsing error.
* Sleep 10 seconds after the execution, reload DSP and FPGA firmware
This will include
* Fix of CHAN_NR IEI in common channel RSL messages generated by BTS
* zecke/request_queueing
* Improve shutdown of DSP on exit
* various calib updates
* GSMTAP: use RxLevel and RxQual
* DSP power control bypass on ul_power_target==0
* Add radio link timeout procedure
The latest release currently does not support the RevC hardware. Install
both 3.0.1pre and 3.1 (luckily ubifs compresses them) and set a symlink.
Use the EEPROM size as an indicator if we are on revD or revC hardware
and then set the symlink. It has been tested for revC and needs to be tested
on revD hardware.
Re-work the way we distribute the header and firmware files. The header
files may be accessed by everyone but the firmware may only be used by
owners of our device. Create a header only repository with all the header
versions of the firmware and create tarballs for specific releases that
will be provided to our customers. Use COMPATIBLE_MACHINE to pick the right
firmware and API version depending on sysmoBTSv1 and sysmoBTSv2.