Greg,
1. See https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/111
-- TL;DR: you should update to an "edge" build or build
yourself.
2. You need to format the SD card with FAT32, also users
reported the MacOS FAT32 format would not be accepted by the
module (I can't test that, all Linux formatted cards work).
There are some issues with the FAT implementation in
esp-idf, i.e. with reading damaged partitions.
Regards,
Michael
Am 17.05.2018 um 22:49 schrieb
Greg D.:
Greg D. wrote:
I'll
pick up the logging tomorrow, and provide that
{sigh}
I went to the car to grab a verbose log, and started
poking around for the commands, etc. Looked at the
network status, and see that ppp has an IP address!
What? Boot status showed:
OVMS# boot status
Last boot was 249 second(s) ago
This is reset #15 since last power cycle
Detected boot reason: FirmwareUpdate
Crash counters: 0 total, 0 early
CPU#0 boot reason was 12
CPU#1 boot reason was 12
OVMS#
OVMS# metric list m.version
m.version
3.1.005/ota_1/main (build idf v3.1-dev-454-gdaef4b5c
May 1 2018 21:38:50)
OVMS#
...which is bogus, since if it really upgraded the
firmware it should be on .006. Also, the OTA time is set
to the default 2am, which is clearly not the current time
in any relevant timezone.
I had tried to insert an SD card for easier log
portability, but for some reason it wasn't seen. 'sd
status' says no SD card has been inserted, and sd mount
fails. There IS an active USB connection (being used for
a serial console monitor), so our friendly cp2102 issue
shouldn't be at play, and there is no firmware file
present on the SD either, but the timing of the reboot is
about right for when the SD was inserted. It's a SanDisk
16gb Ultra Plus microsd... No luck with it either on my
3.0 proto module, but it reads fine on my PC. This is my
first time trying to use a microSD card with the OVMS
module, so I don't know what to expect. Could be user
error on my part?
Did the act of jiggling the module and inserting the SD
card cause a reboot, the reason for which was not logged
(i.e. is the 'firmware upgrade' status leftover from the
.004 -> .005 upgrade some weeks ago)?
{shrug}
Anyway, bottom line are three issues:
1. What caused my module to reboot with an apparently
bogus "upgrade"?
2. Why can't either of my modules see this SD card?
3. I will need to wait for the loss of modem
connectivity to reproduce, since the reboot "fixed" it...
Sorry.
Greg
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev
--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev