I think the last device we sold was in 2011 and I am not aware
if anyone has used it for the last couple of years. Remove it
to lower the complexity of the builds.
In yocto versions before dizzy/master the build was done
in the source directory and when configure was executed
twice in the same directory we would have a build failure
due the symlink already existing. Simply assume that if
the ln fails the link is already there.
Out of disk space situations are handled more early by
OE and missing files will be found by configure.
In dizzy/master OE will clean the build directory before
calling configure so the issue does not apply there.
Fixes: SYS#1170
The name of the config file was changed and so far
I was hesitant to upgrade the MLO. I think the change
in EEPROM applies to the MLO as well so we should
upgrade it. It has neither been build tested nor tested
on a device.
Now reading the command it should probably be add.nwp or
rem.wp but so is life. We can add an alias for add.nwp in a
future version. The boot, recovery and fwup command have been
changed to issue nand rem.nwp before touching the flash.
The sysmobts-mgr is now linking to libgps. This means we need to
DEPEND on gpsd to have this library available. The tracking build
for both dora and master is broken due this.
One might need to erase the environment but with a default
environment barebox will now send a LLDP during boot up. This
way we can see if a device is on a local link or not.
Fixes: SYS#488
Without inheriting pkgconfig the PKG_CHECK_MODULES macro can not
be expanded in dizzy. Fix it. While being there use "autotools"
for the pcu and not autotools_stage.
Add post install script that will mangle the config to be the
right one for the given machine. This will be executed once
after the post installation. In case of the getty change the
system must re-start once to be fully usable. E.g. for the
sysmoBTS2050 the PA might not be powered up on first boot.
Having:
osmo-bts requires sysmobts-firmware > 3.11
sysmobts-firmware requires osmo-bts > 0.4.2
is something opkg can't resolve in one go. One needs two calls to
the opkg command to end up with a fully upgraded version. Make sure
that we require/pull newer firmware when installing a new version
of osmo-bts.
* Add sysmobts-firmware 3.11. The firmware will work with the
previous osmo-bts software and this one (as we don't use the
new primitives)
* Build newer version of osmo-bts with support for online
calibration and CMR fixes.
Build a version of barebox that has support for NAND flash and
ubifs. Load the kernel from the device. One needs to flash the
*mlo*.img into the xloader partitions and the other image into
the barebox partition.
erase /dev/nand0.xload.bb
erase /dev/nand0.xload_backup1.bb
erase /dev/nand0.xload_backup2.bb
erase /dev/nand0.xload_backup3.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup1.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup2.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup3.bb
This doesn't work like this. We need to know the _exact_ PV/PR
of the package and we don't. Specially with the PR server in dora
and later we can not know the version.
This reverts commit 767d7b6939.
This upgrades the firmware from 3.6 to 3.10. This is a significant
firmware upgrade and it changed ABIs too. Try hard to fix the
dependencies as much as possible. This requires the DSP headers
files to be of version 3.10 as well but we can not have versioned
DEPENDS.
The code has not been finished and doesn't meet the quality
standards we have for a product. Comment the sysmobts-mgr
related files that will be back soon.
Let's flash multiple copies of UBL and U-Boot to cope better with
NAND bits flipping in these sectors. To fit multiple copies of
U-Boot into the flash we had to move the rootfs a bit to the end.
Daniel noticed that on upgrade his /etc/osmocom/osmo-bts.cfg
was overwritten. This was due the addition of the sysmobts-mgr
config file and using an assignment instead of an append.
We do not intend to use u-boot right now but at least this
version will build. In the first version we will use the
barebox images provided to us by the producer of the SoM.
This is fixing max_power_reduction for revC hardware and applies
a new max_power_reduction when it arrives through OML and the
system is already initialized.
We had an upgrade issue where using newer firmware with older
osmo-bts binaries didn't work. Make sure that the shiny new 0.4.0
binaries are used with firmware starting from 3.2.
Addresses: #158
Use the native systemd service file to avoid running a shell script
that is ran from within the screen. This code expects the pcu to have
a .service file itself.
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.
Holger Hans Peter Freyther
Jan Luebbe
Harald Welte
Henning Heinold
Holger Hans Peter Freyther