March 2026 - OvmsDev - Open Vehicles

Firmware size approaching 4 MB limit
by Michael Balzer 07 Apr '26

07 Apr '26

Everyone, with the latest vehicle additions, the firmware size has now grown to 4,015,328 bytes in build 3.3.005-485-gc4664881. Our flash partitioning scheme is currently designed to provide three firmware partitions (factory, ota_0 & ota_1) of 4MB = 4,194,304 bytes each. So we've now got 178,976 bytes = ~4% left. Options beyond the 4 MB limit: a) split features, e.g. vehicle support, into two or more builds b) repartition into two firmware partitions of 6 MB each, reusing the factory partition for OTA c) switch to an ESP32 WROOM module with 32 MB flash (possible?) We've got some time left, new vehicles normally don't need that much space, I just wanted to raise awareness. Regards, Michael -- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926

5 33

Firmware release 3.3.006
by Michael Balzer 18 Mar '26

18 Mar '26

Everyone, I suggest making the OTA repartitioning the closing feature for the 3.3.006 release (to be accompanied by Android App release 5.2.4). Feature development has settled a bit lately, and crashes are mostly eliminated. I especially haven't seen a single heap corruption in the last weeks. The remaining crash reports still hint at a possible common issue with transitions from mobile to wifi, but otherwise seem to be more caused by individual misconfigurations like bad event script behaviour now. Release 3.3.005 was on 2025-07-18. We've got three new vehicles since 3.3.005 (Maxus T90, Fiat e-Doblo & VW e-Golf), and a lot of improvements especially on the Smart vehicle support, so I'd say 3.3.006 is due. If you've got anything important in the making that should be included, please reply. Regards, Michael -- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926

3 3

Draft P/R - Retrying starting of ECU Can
by Michael Geddes 12 Mar '26

12 Mar '26

I have a draft for a little issue I was encountering where the ECU CAN was not starting. It was possibly happening in a hot car? It was compounded by the state going to ON despite it not actually starting. I have moved the map loading into the ECU Task, and I retry turing the CAN on in the task until it starts or is killed. I've also put some mutexes around the value map access. I was contemplating just moving the map reload into the thread, but then the dump still should be mutexed. https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/1350 It still needs some more testing, but feedback wouldbe welcome. //.

1 0