OTA updates causes RESET_PANIC above 7.1.1

[StarkJohan]

When updating OTA the percentage halts around 10% and causes a RESET_PANIC. This is consistent on release 7.3.0 and above but works as intended on 7.1.1. When uploading by wire everything works as intended.

Using Stark CMR v1 as it's a two can-bus setup so I can't test the exact settings on the lilygo.

volatile CAN_Configuration can_config = {
.battery = CAN_NATIVE, // Which CAN is your battery connected to?
.inverter = CANFD_NATIVE // Which CAN is your inverter connected to? (No need to configure incase you use RS485)
//.battery_double = CAN_ADDON_MCP2515, // (OPTIONAL) Which CAN is your second battery connected to?
//.charger = CAN_NATIVE // (OPTIONAL) Which CAN is your charger connected to?
};

#define NISSAN_LEAF_BATTERY
#define BYD_CAN
#define HW_STARK
#define CONTACTOR_CONTROL
#define CAN_FD
#define USE_CANFD_INTERFACE_AS_CLASSIC_CAN

#define WIFI
#define WEBSERVER
#define WEBSERVER_AUTH_REQUIRED false

#define LOAD_SAVED_SETTINGS_ON_BOOT
#define HA_AUTODISCOVERY (to avoid the ifdef bug in this version, not using MQTT)
#define DUMMY_EVENT_ENABLED false

#define BATTERY_WH_MAX 58000
#define BATTERY_USE_SCALED_SOC true
#define BATTERY_MAXPERCENTAGE 8000
#define BATTERY_MINPERCENTAGE 2000
#define BATTERY_MAX_CHARGE_AMP 750
#define BATTERY_MAX_DISCHARGE_AMP 750

[PaulV71]

We have the same, using 7.3.0

[StarkJohan]

We have the same, using 7.3.0

What hardware and software version? What setup?

[PaulV71]

Lilygo Tcan connected to the LEAF battery. The other one to the inverter has no issues so far.

[dalathegreat]

@amarofarinha could this be related to the OTA library update? #454

[amarofarinha]

@amarofarinha could this be related to the OTA library update? #454

it could be, but after some testing and investigation we found it has to do with pause functionality and changes on the preOta handler.

it is fixed and was tested on the system that experience the error. on #499

[amarofarinha]

We have the same, using 7.3.0

@PaulV71 can you try #499 ?

[StarkJohan]

@amarofarinha solved this and I have confirmed that his solution works.

[amarofarinha]

closing this as it resolved original issue and the fix is already merged on main. @PaulV71 , pease test latest main version to check if you problem is also solved.

[PaulV71]

problem solved. Thanks