gregbreen/uncannier-thunderboard-react

Thunderboard React made better

uncannier-thunderboard-react's Issues

(Insecure) Over The Air (OTA) Device Firmware Upgrade (DFU) Using Gecko Bootloader

Support Over The Air (OTA) Device Firmware Upgrade (DFU) using Gecko Bootloader.

Use Gecko Bootloader because:

1. It's easy
2. OTA DFU will work using the stock Blue Gecko phone app

Don't bother with security initially. Insecure updates for now.

Using the stock TB React project, it's not possible to generate a Hex or binary image that can be flashed into an erased flash memory. We also need to add the Gecko Bootloader to the project, to generate the first and second stage bootloaders, and then use Simplicity Commander to merge the bootloader and application Hex files. Thus producing a single Hex file that can be flashed into an erased part.

Deep sleep is broken since upgrading to BT SDK 2.11.0

BT SDK 2.11.0 modified the React example app by adding the following FEATURE_LFXO conditional compilation around the sleep flags in main.c:

#if defined(FEATURE_LFXO)
  .sleep.flags = SLEEP_FLAGS_DEEP_SLEEP_ENABLE,
#else
  .sleep.flags = 0,
#endif // LFXO

FEATURE_LXFO is not set by default in the example app. Pretty sure that's a SiLabs' bug.

Anyway, I brought this change in, and thus broke deep sleep. This was the offending PR: #17

Everything works in a functional sense, but the current draw is much too high. Need to fix it.

Setup vanilla Thunderboard React (SDK 2.10.0) as a baseline

Need a starting point. Vanilla TR app, generated from latest Blue Gecko SDK (2.10.0).

Raise the compilation warning level and rename the default build configuration

By default, the warning level is low. Turn it up, fix easy warnings, disable a handful that are too hard to fix in SiLabs' code.

I also don't lile the default build configuration name of "GNU ARM v7.2.1 - Default". I understand where it comes from, but I prefer the decades old tried and true Debug and Release.

Create a Debug build configuration, with optimization O0. Also define DEBUG macro constant for that build configuration.

Battery level measurement is erratic

The battery level reported by the Thunderboard is noisy and highly inaccurate. It fails to account for how the battery voltage varies greatly with the load current. This changes the voltage much more than the loss of charge.

It also samples at very high frequency given that, in reality, takes about 20 minutes to dissipate 1% of charge (when maximally loaded at ~4mA, streaming IMU data over BLE).

Upgrade to Bluetooth SDK 2.11.0 and Gecko SDK 2.5

Upgrade both the app and the bootloader to latest SDKs.

This will upgrade Gecko Bootloader to 1.8.0.

Ensure to bring forward any updates to the example source code.

Unit testing and code coverage on CircleCI

Get the Test configuration building on CircleCI. Generate xUnit output, and save the test results on each build. Save the code coverage as an artifact too.

Automated software versioning

The firmware version is hard-coded in the Firmware Version characteristic of the Device Information service. Instead:

• add the Software Version characteristic to DIS
• generate the Software Version from each CI build (build number and GIT commit hash in the version)
• use Firmware Version field to report the Gecko Bootloader version and the Bluetooth SDK stack version (these are reported to the application in the boot-up event)
• consider to add support in the CircleCI build plan for major.minor.patch release generation when a tag is created in GitHub.

Setup CppUTest unit test harness

Add the CppUTest harness to the project. Create a new Test build configuration that makes an x86 build of the Thunderboard application, to allow on-host unit testing of components.

Although I only want to unit test Uncannier components, take the time to get the entire Thunderboard application into the harness. This means making a fairly extensive test seam.

https://uncannier.com/unit-testing-of-embedded-software-cpputest-simplicity-studio-thunderboard-part-1/

Secure OTA DFU - Gecko Bootloader authentication and encryption

https://www.silabs.com/documents/public/user-guides/ug266-gecko-bootloader-user-guide.pdf
https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2017/06/22/secure_ota_dfu-Wb22

Unit test coverage reports with LCOV & GCOV

Add GCOV profiling to the Test build configuration. Use LCOV to generate an HTML coverage report every time the unit tests are executed.

Upgrade to Bluetooth SDK 2.11.5 and Gecko SDK 2.5.5

Upgrade both the app and the bootloader to latest SDKs.

This will upgrade Gecko Bootloader to 1.8.4.

Ensure to bring forward any updates to the example source code.

Setup continuous integration on CircleCI