[Ovmsdev] PSRAM fix in esp-idf release v3.3

Mark Webb-Johnson mark at webb-johnson.net
Wed Jul 15 10:13:02 HKT 2020

Finally… Crazy that this took so long.

We have a GetOVMSHardware() in ovms_version.cpp that picks up the esp_chip_info_t structure and has chip.revision (documented as "chip revision number”). That is stored in metric m.hardware. My bench unit is showing rev=ESP32/1. I checked a bunch of recent cars connected to api.openvehicles.com <http://api.openvehicles.com/>, but all showed the same. So not sure if the v3 silicon is not reported in that chip.revision, if we are just using existing stocks, or an IDF update is required to pickup the new silicon version number. The v3 seems fairly recent (March 2020?) and I don’t see a v2 listed. Anyway, I’ve just yesterday received a new batch of modules so will check those to see if it shows up.

What do we need to do to switch to this? Presumably I turn off auto-build of the firmware on api.openvehicles.com <http://api.openvehicles.com/>, you merge your SPIRAM branch to master, we tell everyone to download the new toolchain, then we switch both our edge builds back to master branch with new toolchain?

Apart from the CONFIG_SPIRAM_SUPPORT 2MB workaround, I can’t see any significant differences between remotes/origin/spiram-fix-test and master? Is the only difference the ovms_websockethandler.cpp change to std::string (vs extram::string)?

Regards, Mark.

> On 15 Jul 2020, at 2:11 AM, Michael Balzer <dexter at expeedo.de> wrote:
> Mark,
> it seems the fix has finally arrived in the official release 3.3 branch:
> https://github.com/espressif/esp-idf/issues/2892#issuecomment-658327913 <https://github.com/espressif/esp-idf/issues/2892#issuecomment-658327913>
> https://github.com/espressif/esp-idf/commit/f4333c8e3a554e8bb4210d825cbdf4bcaa1fc1b8 <https://github.com/espressif/esp-idf/commit/f4333c8e3a554e8bb4210d825cbdf4bcaa1fc1b8>
> Btw:
>> In the v3 silicon, the issue has been fixed, and the workaround is no longer required.
> I guess that means from some manufacturing point on we should provide two builds, one for the older hardware and one for the modules with v3 chips, as the fix definitely has a performance impact.
> Regards,
> Michael
> -- 
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200715/c1b012df/attachment.htm>

More information about the OvmsDev mailing list