Repository navigation
2.3.3 - #373
2.3.3#373
Conversation
✅ Unit tests passed8 passed, 0 failed/error, 0 skipped — view workflow run
Download the |
Compiler warningsThe extended-warning build completed successfully. Application compiler warningsShow warnings |
|
Build output available: |
CodeChecker static analysis✅ No non-style issues found. 14 known nRF5340 hardware-register accesses are reviewed as intentional using exact checker/path/hash rules in |
Merge #276 and #371 into the release branch, preserving current main. Select battery profiles from the powered IMU probe before charging setup; use a 4.2 V fallback on failed detection and share charging safety checks. Validated with clean SDK 3.4.1 FOTA/regular builds and nine host battery-policy tests.
|
Build output available: |
Bound gauge configuration transitions and propagate I2C errors. Keep charging inhibited on missing/failed gauge setup, report the fault through the shell, and stop periodic readers before manual gauge configuration.
|
Build output available: |
Use 80 mA for Grepow and unidentified cells, retaining 100 mA for VARTA. Enable the CD input buffer so diagnostics and fault-injection validation can read the actual charging-inhibit gate. Update profile regression expectations.
|
Build output available: |
|
Build output available: |
Keep the BQ27220 66 us command gap and timestamp update inside the I2C mutex so concurrent telemetry and policy reads cannot bypass the required wait.
|
Build output available: |
Follow BQ27220 TRM section 5.3 at 400 kHz: split multi-byte commands into individual byte writes with a locked 66 us gap between every packet.
|
Build output available: |
Use the supported step below the requested 95 mA. Keep the unidentified fallback at 80 mA and VARTA at 100 mA; round temperature-derated current down to a representable charger step.
|
Build output available: |
Verify charger profile/current readback before enabling CD; latch I2C or setpoint failures off until restart. Serialize manual gauge setup, charging work and diagnostics with the recursive bus mutex, releasing it before publication/reboot. Wait for sensor POR before each detection. Add production-driver fault/concurrency regressions to CI.
|
Build output available: |
|
Build output available: |
|
Build output available: |
|
Build output available: |
Firmware 2.3.3 combines hardware 2.1.0 support (#276) and the encrypted bond-clear/shutdown service (#371). Both source PRs are merged into this branch. Current
main(0d0b5d82) is included, and the release merges into it without conflicts.Latest CodeChecker fixes (
e0280085):bt_id_get, check its returned count and bound the logging loop by the array itself.2.3.3. Physical boards retain their last flashedae29902fimage until updated.Battery profiles are selected by a powered, validated IMU probe before charger/gauge configuration, including charging-only boots:
0x680x69Grepow uses the supported step below 95 mA; the charger uses 10 mA steps in this range. Grepow temperature derating requests 40 mA. Profiles prohibit charging outside 0–45 °C or with invalid readings; Grepow/fallback do not automatically recover below 3.0 V. Existing 10 mA termination is retained. UICR metadata cannot enable 4.3 V. Learned FCC is excluded from design-setting mismatch checks.
Review fixes retained in this release:
The BQ27220 driver also serializes its 66 µs command gap and timestamp under the bus mutex and uses byte writes at 400 kHz, per TI TRM section 5.3. Both firmware variants default to Balanced auto-off after 15 minutes; saved preferences take precedence. The device-control service preserves existing identity handling and requires encryption for bond-clear/shutdown operations.
The release reports exactly
2.3.3over BLE, using the release number fromVERSION. Git/development metadata remains available in internal build diagnostics. MCUboot version remains2.3.3+0.The pair flasher adds
--hw auto: it retains each device's existing UICR revision before erasing, supports mixed 2.0.1/2.1.0 pairs, and uses the established 2.0.1 station default for blank boards. Invalid hardware metadata stops both devices before either is erased. Explicit hardware selection keeps its previous behavior.Validation:
ae29902fon HW 2.0.1 (823008641) and HW 2.1.0 (823009485), preserving UICR and MCUboot trailers.26298fd9; that control path is unchanged by the latest update.All four latest-head workflows pass: firmware build, native and sanitizer tests, compiler-warning report and CodeChecker. CodeChecker now reports no outstanding findings; reviewed hardware accesses remain disclosed and retained in the artifact.
Grepow capacity learning did not complete: the previous discharge test ended at 3.30 V with VDQ = 1, EDV2 = 0 and FCC unchanged at 111 mAh. The supplied datasheet/user do not provide Grepow CEDV coefficients, so accurate state-of-charge characterization remains open. The 123.1 mAh gross experiment log excludes a pause/recharge and is not net usable capacity. No independent meter calibration, full temperature/rate characterization, end-to-end acoustic measurement or full OTA transfer is claimed.
Other open PRs #111, #220, #267 and #311 remain targeted to
2.3.3. This PR targetsmainand is ready for review. No stable release/tag is published.