Which firmware are you using (the URL you download from).

Best approach is to use Michael’s a2l script, give it the backtrace addresses, and the .elf file for firmware, and it will output an annotated backtrace that we can see where the crash occurred.

Regards, Mark.

On 12 Apr 2020, at 10:49 PM, Tamás Kovács <kommykt@gmail.com> wrote:

More info from crash. I see the following errors before crash (picture attached). Now i disable vfs logging, and run a can loggint to savyyCAN, this is the fastest mode to crash the module. i receive ~700k can messages. 

Tamás Kovács <kommykt@gmail.com> ezt írta (időpont: 2020. ápr. 12., V, 9:14):
Car Peugeot iOn used TRIO vehicle type.

Last crash: abort() was called on core 0 Backtrace: 0x4008b03f 0x4008b2d5 0x400e709c 0x40083d96 Version: 3.2.011-172-g51b71688/ota_1/eap (build idf v3.3-beta3-776-g3d198cd50 Apr 11 2020 11:57:14)

Crash at 2020.04.11 18:59 and 20:59, 04.12 09:06
Created a log file the first 2 time only info level, but last with debug level. And another on OVMS SHELL is see many dropped ticker event before crash, but not show in log file.



--
Üdvözlettel:
Kovács Tamás

<Screenshot 2020-04-12 at 16.42.20.png>_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev