Apparently I'm still having issues with capture.
I'm trying to make short trace (~5 mins). I start with:
can log start vfs crtd /sd/ct5-02.crtd 034 03f 04b-04c 063 073-0cc
147-1be 225-297 2a9-2c9 2ce-2d1 2d4-2d7 2da 2dc 2e0 2e2-382 3a2-3a8 3aa-3ba 3d0-3d5 41b 42b 442-458 462 467-469 46d 478-483 489-48d 494 499-49d 49f-4a0 4a2 4a4-4cc 4ce-4d0 4d7-4da 4dc 4df 4e3 4e6-4f8 4fa-580 582-588 58d-58f 591-594 596-597 5a4-5b8 5ba 5bd-5be 5c1 5c3 5c5-5c6 5c8-5e1 5e4-5e5 5eb 5ef 5f1-5f2 5f4 5f6-5fe 701-702 707-714 717 71d 71f-721 724-728 72e-752 754-757 759-764 767 769 771-772 774 779-784 786-78a 78e 791-7a6 7a8-7ab 7ae-7b9 7bb 7bd 7bf 7d0-7d4 7df-14daf380
and everything looks good. A couple of minutes later when I check, the module has rebooted. When I tried this earlier today I didn't think there was a stack trace. But I got one a few minutes ago:
OVMS# boot
Last boot was 423 second(s) ago
Time at boot: 2026-07-01 21:15:10 PDT
This is reset #2 since last power cycle
Detected boot reason: Crash (12/12)
Reset reason: Task watchdog (6)
Crash counters: 2 total, 0 early
Auto init level: Full
Last crash: abort() was called on core 0
Current task on core 0: IDLE0, 512 stack bytes free
Current task on core 1: OVMS CanLog, 2232 stack bytes free
Backtrace:
0x40089137 0x400893d1 0x4010a354 0x40083df2
Event: vehicle.aux.12v.dip@ovms-server-v3 36 secs
WDT tasks: IDLE1
Version: 3.3.006-67-gd4d8b577/ota_0/main (build idf
v3.3.4-854-g9063c8662 Jun 3 2026 15:19:31, product v3.3-5)
Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/3; MODEM SIM7600
Which works out to:
sea 3 % ./backtrace.sh 0x40089137 0x400893d1 0x4010a354 0x40083df2
+ xtensa-esp32-elf-addr2line -e build/ovms3.elf 0x40089137
0x400893d1 0x4010a354 0x40083df2
/home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/esp32/panic.c:736
/home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/esp32/panic.c:736
/home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/esp32/task_wdt.c:274
/home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/freertos/xtensa_vectors.S:1154
So a watchdog timer?
I've also notice it's not unusual when this car+module is on the home wifi (and the car idle for hours) that I can ping it but not ssh/http do not respond and I cannot send commands via the ios app.
I just updated to 3.3.006-120-g465b5249. I guess tomorrow I'll try creating a crtd without any filter terms. If that doesn't work I'll try changing the vehicle to obdii. Other ideas?
Craig
P.S. I was too impatient when 3.3.006-120-g465b5249 was booting and got a stack trace when trying to ssh in during the first ~30 seconds of uptime. Looks like I'm hitting the abort() at the end of esp_sha_read_digest_state():
abort(); // SHA peripheral returned all zero state, probably due to
fault injection
I sure wish the we wouldn't accept a tcp connection until the crypto is all done initializing... (Is this difficult to fix?)
sea 3 % ./backtrace.sh 0x40089137 0x400893d1 0x4028b989 0x4026bef2 0x40265c9a 0x4026768f 0x40276ac3 0x4026795e 0x40267989 0x40156720 0x40157db0 0x40159501 0x40159a23 0x40155f32 0x4015b78e 0x40145470 0x40145599
- xtensa-esp32-elf-addr2line -e build/ovms3.elf 0x40089137 0x400893d1 0x4028b989 0x4026bef2 0x40265c9a 0x4026768f 0x40276ac3 0x4026795e 0x40267989 0x40156720 0x40157db0 0x40159501 0x40159a23 0x40155f32 0x4015b78e 0x40145470 0x40145599 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/esp32/panic.c:736 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/esp32/panic.c:736 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/esp32/hwcrypto/sha.c:272 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/mbedtls/port/esp_sha256.c:349 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_cli.c:3894 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 /home/sea/u0/leres/esp/openvehicles-xtensa-esp32-elf/components/mbedtls/mbedtls/library/ssl_tls.c:7649 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/mongoose/mongoose/mongoose.c:1701 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/mongoose/mongoose/mongoose.c:1701 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/mongoose/mongoose/mongoose.c:1701 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/mongoose/mongoose/mongoose.c:1701 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/mongoose/mongoose/mongoose.c:1701 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/mongoose/src/mongoose_client.cpp:52 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_netmanager.cpp:1000 /home/sea/u0/leres/src/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_netmanager.cpp:980