[Ovmsdev] Modem fails to connect
Michael Balzer
dexter at expeedo.de
Sat May 19 01:51:59 HKT 2018
Greg,
no idea on the reboot, possibly coincidence. We've got many strange bugs remaining, e.g.
Last crash: IllegalInstruction exception on core 0
Registers:
PC : 0x00000000 PS : 0x00000000 A0 : 0x00000000 A1 : 0x00000000
A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000
A6 : 0x00000000 A7 : 0x00000000 A8 : 0x00000000 A9 : 0x00000000
A10 : 0x00000000 A11 : 0x00000000 A12 : 0x00000000 A13 : 0x00000000
A14 : 0x00000000 A15 : 0x00000000 SAR : 0x00000000 EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000
Backtrace:
…out of nowhere.
Regards,
Michael
Am 18.05.2018 um 19:13 schrieb Greg D.:
> Hi Michael,
>
> Well, never underestimate what one can do when they don't know what they're doing. I assumed as you stated, that it could only go in one way, and since it
> did, I didn't try the other orientation.
>
> But, that did it! SD is mounted, no reboot this time. Now, to wait for the modem to fail again...
>
> Thanks,
>
> Greg
>
> p.s. Any idea what caused the reboot earlier, given the SD was not even making electrical contact? (Queue theme to Twilight Zone here...)
>
>
> Michael Balzer wrote:
>> Greg,
>>
>> not sure how you can insert an SD in the wrong orientation, they normally are mechanically protected against that, but it seems you did: the contacts need to
>> face the upper side of the case, towards the USB connector.
>>
>> Regards,
>> Michael
>>
>>
>> Am 18.05.2018 um 09:24 schrieb Greg D.:
>>> Hi Michael,
>>>
>>> Fair question. Pretty sure I got it right. The proto box was a lot trickier, but on both units I engaged the SD with the spring and pushed it into
>>> position where it clicked into place. Another push and it unlatched and came out. Certainly felt right.
>>>
>>> Presume the contacts side of the SD face the bottom of the case, away from the USB connector, right? I didn't try it upside down.
>>>
>>> Greg
>>>
>>>
>>> Michael Balzer wrote:
>>>> Greg,
>>>>
>>>> as that's the first time, are you sure you inserted the SD correctly? With a closed case you need a screw driver or similar to get it in. The slot has a
>>>> spring latch you can feel and hear.
>>>>
>>>> Regards,
>>>> Michael
>>>>
>>>>
>>>> Am 18.05.2018 um 01:56 schrieb Greg D.:
>>>>> Thanks, Michael, I'd missed that. So, that explains the reboot status, but not why the SD card isn't seen.
>>>>>
>>>>> fdisk -l on my Linux system claims that the SD card is formatted FAT32, and it mounts / umounts just fine there. The SD card is basically new / empty,
>>>>> other than a few directories auto-created when it was once inserted into a cell phone. fsck.fat -v is clean. So, I'm puzzled what's preventing it from
>>>>> being seen. A fresh build from this morning on my v3.0 proto module acts the same (minus the reboot).
>>>>>
>>>>> Greg
>>>>>
>>>>>
>>>>> Michael Balzer wrote:
>>>>>> 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 at 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 at lists.openvehicles.com
>>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at 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 at lists.openvehicles.com
>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>>
>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at 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 at lists.openvehicles.com
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180518/f76defa1/attachment-0001.html>
More information about the OvmsDev
mailing list