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, 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, 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)?
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev