<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Greg,<br>
<br>
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.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 18.05.2018 um 09:24 schrieb Greg D.:<br>
</div>
<blockquote type="cite"
cite="mid:990ca371-3ad5-6ddd-7542-9f7a545fe43e@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi Michael,<br>
<br>
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.<br>
<br>
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.<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Michael Balzer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:bc8a8abd-f284-8d2e-03b8-9c9c9d0f16d6@expeedo.de">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Greg,<br>
<br>
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.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 18.05.2018 um 01:56 schrieb Greg
D.:<br>
</div>
<blockquote type="cite"
cite="mid:20ad8005-2d08-7215-ceae-5b725a71e586@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Thanks, Michael, I'd missed that. So, that explains the
reboot status, but not why the SD card isn't seen.<br>
<br>
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). <br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Michael Balzer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f9ed196e-43ac-49f3-7986-52dccb27555d@expeedo.de">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Greg,<br>
<br>
1. See <a class="moz-txt-link-freetext"
href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/111"
moz-do-not-send="true">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/111</a>
-- TL;DR: you should update to an "edge" build or build
yourself.<br>
<br>
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.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 17.05.2018 um 22:49 schrieb
Greg D.:<br>
</div>
<blockquote type="cite"
cite="mid:51269aa9-0806-3d0d-d10b-8f44ba09d5e3@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Greg D. wrote:<br>
<blockquote type="cite"
cite="mid:5d427bac-f864-2913-98d3-229cdf1dbb48@gmail.com">I'll
pick up the logging tomorrow, and provide that</blockquote>
<br>
{sigh}<br>
<br>
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:<br>
<blockquote><tt>OVMS# boot status</tt><tt><br>
</tt><tt> Last boot was 249 second(s) ago</tt><tt><br>
</tt><tt> This is reset #15 since last power cycle</tt><tt><br>
</tt><tt> Detected boot reason: FirmwareUpdate</tt><tt><br>
</tt><tt> Crash counters: 0 total, 0 early</tt><tt><br>
</tt><tt> CPU#0 boot reason was 12</tt><tt><br>
</tt><tt> CPU#1 boot reason was 12</tt><tt><br>
</tt><tt> OVMS# </tt><tt><br>
</tt><tt> OVMS# metric list m.version</tt><tt><br>
</tt><tt> m.version
3.1.005/ota_1/main (build idf v3.1-dev-454-gdaef4b5c
May 1 2018 21:38:50)</tt><tt><br>
</tt><tt> OVMS# </tt><br>
</blockquote>
...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.<br>
<br>
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?<br>
<br>
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)?<br>
<br>
{shrug}<br>
<br>
Anyway, bottom line are three issues:<br>
<br>
1. What caused my module to reboot with an apparently
bogus "upgrade"?<br>
2. Why can't either of my modules see this SD card?<br>
3. I will need to wait for the loss of modem
connectivity to reproduce, since the reboot "fixed" it...
Sorry.<br>
<br>
Greg<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>