gregbreen/uncannier-thunderboard-sense2

Thunderboard Sense 2 made better

uncannier-thunderboard-sense2's Issues

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.

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).

Support WSTK VAEM as a valid supply

I have an EFR32 Blue Gecko Bluetooth Start Kit. AKA a WSTK (Wireless Starter Kit).

Model: SLWSTK6020B

https://www.silabs.com/products/development-tools/wireless/bluetooth/blue-gecko-bluetooth-low-energy-soc-starter-kit

This supports AEM (Advanced Energy Monitoring). The VAEM can power the Sense 2, and then the WSTK can be used to measure current draw using the Simplicity Studio Energy Profiler.

At boot, the Sense 2 probes its power supply to categorize it as:

• UNKNOWN
• AAA
• CR2032
• USB

This is done in the UTIL_supplyProbe() function of hardware/kit/common/bsp/thunderboard/util_supply.c

The UTIL_isLowPower() function of the same file returns true only if the supply type is categorized as CR2032 or UNKNOWN. This return value determines whether deep sleep is enabled in main.c

The WSTK is wrongly categorized as an AAA battery. The consequence being that deep sleep is not enabled, and so I can't profile the energy consumption that would occur when a CR2032 is fitted (main use case). I need WSTK/VAEM to select low power mode.

(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.

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.

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.

image docker

hi
thanks for your work
i have a problem with image docker :

docker pull gregbreen/uncannier-thunderboard
Using default tag: latest
Error response from daemon: manifest for gregbreen/uncannier-thunderboard:latest not found

thanks

Automated software versioning

The firmware version is hard-coded in the Sense 2 firmware in the appl_ver.h file. It seems this file is designed to be overwritten by a CI build. The Firmware Version characteristic of the Device Information service reports this firmware version (and do some printf() calls on the serial port). 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). Probably get rid of appl_ver.h
• 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.

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

Setup vanilla Thunderboard Sense 2 (SDK 2.10.0) as a baseline

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

Setup continuous integration on CircleCI

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.

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/

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.