Thanks for confirming @Xornix and @corty. I usually limit the changelog items between the stable versions. E.g. if an issue was introduced by a test-version, which is fixed by the next test-version then I do not include this.
Just to summarize what I did between test.1 and test.2:
- I changed the Linux boot command to not attach the console to the serial output of the Raspberry Pi (it would feed console output / boot logs into the GNSS module, and GNSS output back into the console) (see: https://github.com/chirpstack/chirpstack-gateway-os/blob/master/conf/base_raspberrypi_bcm27xx_bcm2709/patches/no-uart-console.patch)
- There was a link issue between the Semtech HAL and the Concentratord. Iām using Rust
bindgen
for automatically generating the Rust to C interface. This code was generated against the host toolchain, it should have been against the target toolchain (see: https://github.com/chirpstack/chirpstack-openwrt-feed/blob/master/chirpstack/chirpstack-concentratord/Makefile#L21). While it compiled fine, I noticed that (at least with the GNSS) it would cause unexpected behavior as there was some memory misalignment between the Rust to C mappings. - I improved the initial boot. Previously on first boot it would update the
config.txt
in the boot partition. Now these changes are included already in the image and no reboot after the first boot is required (see: https://github.com/chirpstack/chirpstack-gateway-os/blob/master/conf/base_raspberrypi_bcm27xx_bcm2709/patches/boot-config.patch). - I added part of the ethernet / wlan mac to the AP name (ChirpStackAP-XXXXXX) and hostname (with all the different Pis in my office, it is much easier to have unique hostnames I think this helps others too).
- For SX1301 config, the GatewayID is again based on ethernet / wlan MAC (this was still missing).