<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Michael,<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="content-isolator__container"><div class="protected-part"><div class="protected-content"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class=""><blockquote type="cite" class=""><div class="content-isolator__container"><div class="protected-part"><div class="protected-content"><div class="">3. Will v3.3 automatically be built using the latest ESP32 WROVER, i.e. with the revision 3 ESP32 including the hardware SPIRAM fix?</div></div></div></div></blockquote></div><div class=""><br class=""></div><div class="">They normally build each batch with the latest. I haven’t checked for a while, so will check one from the last batch I received, and let you know. We can request this, but it will depend on stock.</div></div></div></div></div></blockquote><br class=""></div><div class="">Down the rabbit hole of detecting chip revision…</div><div class=""><br class=""></div><div class="">I checked a sample from the latest batch, and get:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">OVMS:</span></font></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">OVMS WIFI BLE BT cores=2 rev=ESP32/1</span></font></div></blockquote></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class=""><br class=""></span></font></div><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Esptool flash_id:</span></font></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Detecting chip type... ESP32</span></font></div></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Chip is ESP32D0WDQ5 (revision 1)</span></font></div></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None</span></font></div></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Crystal is 40MHz</span></font></div></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Device: 4018</span></font></div></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Detected flash size: 16MB</span></font></div></div></blockquote></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class=""><br class=""></span></font></div><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">Boot log:</span></font></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">I (925) psram: This chip is ESP32-D0WD</span></font></div><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">I (925) spiram: Found 64MBit SPI RAM device</span></font></div><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">I (925) spiram: SPI RAM mode: flash 40m sram 40m</span></font></div><div class=""><font face="Andale Mono" class=""><span style="font-style: normal;" class="">I (928) spiram: PSRAM initialized, cache is in low/high (2-core) mode.</span></font></div></div></blockquote></blockquote><div class=""><br class=""></div><div class="">I suspect that our old IDF is not detecting the latest revision (because it was released after our firmware).</div><div class=""><br class=""></div><div class="">The raw espfuse command on an old module shows:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_VER_REV1 Silicon Revision 1 = 1 R/W (0x1)</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_VER_REV2 Silicon Revision 2 = 0 R/W (0x0)</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_VERSION Reserved for future chip versions = 0 R/W (0x0)</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_PACKAGE Chip package identifier = 0 R/W (0x0)</span></div></blockquote><div class=""><br class=""></div><div class="">Running against the sample from the latest batch shows:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_VER_REV1 Silicon Revision 1 = 1 R/W (0x1)</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_VER_REV2 Silicon Revision 2 = 0 R/W (0x0)</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_VERSION Reserved for future chip versions = 2 R/W (0x2)</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class="">CHIP_PACKAGE Chip package identifier = 1 R/W (0x1)</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: "Andale Mono";" class=""><br class=""></span></div><div class=""><font color="#000000" face="Andale Mono" class=""><span style="caret-color: rgb(0, 0, 0);" class="">BLK0: 00000000 2a6cbad0 0074a803 0000a200 00001231 00000000 00000004</span></font></div></blockquote><div class=""><div><br class=""></div><div>Using the latest IDF espefuse v3.1, against the sample from the latest batch shows:</div><div><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div><div><font face="Andale Mono" class=""><span style="font-style: normal;" class="">CHIP_VER_REV1 (BLOCK0): Silicon Revision 1 = True R/W (0b1)</span></font></div><div><font face="Andale Mono" class=""><span style="font-style: normal;" class="">CHIP_VER_REV2 (BLOCK0): Silicon Revision 2 = False R/W (0b0)</span></font></div><div><font face="Andale Mono" class=""><span style="font-style: normal;" class="">CHIP_VERSION (BLOCK0): Reserved for future chip versions = 2 R/W (0b10)</span></font></div><div><font face="Andale Mono" class=""><span style="font-style: normal;" class="">CHIP_PACKAGE (BLOCK0): Chip package identifier = 1 R/W (0b001)</span></font></div><div><font face="Andale Mono" class=""><span style="font-style: normal;" class="">MAC_VERSION (BLOCK3): Version of the MAC field = 0 R/W (0x00)</span></font></div><div><font face="Andale Mono" class=""><span style="font-style: normal;" class=""><br class=""></span></font></div><div><font face="Andale Mono" class="">BLOCK0 ( ) [0 ] read_regs: 00000000 2a6cbad0 0074a803 0000a200 00001231 00000000 00000004</font></div></div></div></blockquote><div class=""><div><br class=""></div><div>So, I guess it is still rev 1, but it seems a different rev 1 than the older modules? I’m confused….</div><div><br class=""></div><div>I’ll check with the supplier and ask for him to try to source rev 3 in future. However, it seems we are going to have to bite the bullet at some point and undertake the massive task of moving to the latest IDF to take advantage of everything they’ve improved in the past couple of years.</div><div><br class=""></div><div>Regards, Mark.</div><div><br class=""><blockquote type="cite" class=""><div class="">On 17 Aug 2021, at 3:55 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="content-isolator__container"><div class="protected-part"><div class="protected-title">Signed PGP part</div><div class="protected-content"><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Michael,<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="content-isolator__container"><div class="protected-part"><div class="protected-content"><div class="">1. I had the impression we've had more than expected "modem not/stopped working" issues. Is that impression wrong, or didn't those cases share a hardware cause? I was wondering if that could be related to a voltage regulator issue (e.g. <a class="moz-txt-link-freetext" href="https://www.openvehicles.com/node/2855">https://www.openvehicles.com/node/2855</a>).<br class=""></div></div></div></div></blockquote><div class=""><br class=""></div>I have had just three reports of modem module not working at 12V, but working at 5V. On two, the issue was the power regulator chip blown on the modem board. I don’t think there is anything inherently wrong there - probably just a faulty component or power surge.</div><div class=""><br class=""></div><div class=""><br class=""><blockquote type="cite" class=""><div class="content-isolator__container"><div class="protected-part"><div class="protected-content"><div class="">2. Any chance to fix the missing HW flow control on the modem UART connection?<br class=""></div></div></div></div></blockquote><div class=""><br class=""></div>I don’t think we have enough GPIOs. Perhaps later when/if ESP32 S3 becomes suitable?</div><div class=""><br class=""><blockquote type="cite" class=""><div class="content-isolator__container"><div class="protected-part"><div class="protected-content"><div class="">3. Will v3.3 automatically be built using the latest ESP32 WROVER, i.e. with the revision 3 ESP32 including the hardware SPIRAM fix?</div></div></div></div></blockquote></div><div class=""><br class=""></div><div class="">They normally build each batch with the latest. I haven’t checked for a while, so will check one from the last batch I received, and let you know. We can request this, but it will depend on stock.</div><div class=""><br class=""></div><div class="">Regards, Mark.<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 17 Aug 2021, at 3:31 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="content-isolator__container"><div class="protected-part"><div class="protected-title">Signed PGP part</div><div class="protected-content">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div class="">
Mark,<br class="">
<br class="">
1. I had the impression we've had more than expected "modem
not/stopped working" issues. Is that impression wrong, or didn't
those cases share a hardware cause? I was wondering if that could be
related to a voltage regulator issue (e.g.
<a class="moz-txt-link-freetext" href="https://www.openvehicles.com/node/2855">https://www.openvehicles.com/node/2855</a>).<br class="">
<br class="">
2. Any chance to fix the missing HW flow control on the modem UART
connection?<br class="">
<br class="">
3. Will v3.3 automatically be built using the latest ESP32 WROVER,
i.e. with the revision 3 ESP32 including the hardware SPIRAM fix?<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Am 17.08.21 um 07:30 schrieb Mark
Webb-Johnson:<br class="">
</div>
<blockquote type="cite" cite="mid:2500E21B-0833-402F-99D5-A88C6A52DCF9@webb-johnson.net" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
For the 4G modem options we need to go through FCC, CE, and ROHS
certification. Minimising/eliminating the changes to the main
board simplifies this (and brings down the exorbitant costs) but
if there is anything urgent / necessary, now is the time to do it.
<div class=""><br class="">
</div>
<div class="">
<div style="caret-color: rgb(0, 0, 0);" class="">The goal here is to maintain 100% compatibility with
existing OVMS main boards, to keep this is a simple and
relatively cheap upgrade of the modem board.</div>
</div>
<div class=""><br class="">
</div>
<div class="">So far, I have come up with this minimal list:</div>
<div class=""><br class="">
</div>
<div class="">
<ol class="MailOutline">
<li class="">Main board v3.3: Improve soldering of micro USB
port. Bigger solder pads, and more solder to secure it
better.<br class="">
<br class="">
</li>
<li class="">Modem board v1.3: Add support for SIM7600 module.<br class="">
<br class="">
</li>
<li class="">Modem board v1.3: Fix support for DTR sleep/awake
support.</li>
</ol>
</div>
<div class=""><br class="">
</div>
<div class="">Is there anything else required for this update?</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</div>
</div></div><br class=""><iframe class="content-isolator__isolated-content" sandbox="allow-scripts" scrolling="auto" width="200" height="10" style="border:none;display:block;overflow:auto;" data-src="data:text/html;charset=UTF-8;base64,PGlmcmFtZS1jb250ZW50IGRhdGEtaWZyYW1lLWhlaWdodD0idHJ1ZSI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+T3Ztc0RldiBtYWlsaW5nIGxpc3Q8QlI+T3Ztc0RldkBsaXN0cy5vcGVudmVoaWNsZXMuY29tPEJSPmh0dHA6Ly9saXN0cy5vcGVudmVoaWNsZXMuY29tL21haWxtYW4vbGlzdGluZm8vb3Ztc2RldjxCUj48L2lmcmFtZS1jb250ZW50Pg=="></iframe></div></div></blockquote></div><br class=""></div></div></div></div><br class=""><iframe class="content-isolator__isolated-content" sandbox="allow-scripts" scrolling="auto" width="200" height="10" style="border:none;display:block;overflow:auto;" data-src="data:text/html;charset=UTF-8;base64,PGlmcmFtZS1jb250ZW50IGRhdGEtaWZyYW1lLWhlaWdodD0idHJ1ZSI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+T3Ztc0RldiBtYWlsaW5nIGxpc3Q8QlI+T3Ztc0RldkBsaXN0cy5vcGVudmVoaWNsZXMuY29tPEJSPmh0dHA6Ly9saXN0cy5vcGVudmVoaWNsZXMuY29tL21haWxtYW4vbGlzdGluZm8vb3Ztc2RldjxCUj48L2lmcmFtZS1jb250ZW50Pg=="></iframe></div></div></blockquote></div><br class=""></div></body></html>