It *is* worth trying, Espressif just forgot to mention a necessary build config change. Details: https://github.com/espressif/esp-idf/issues/2892#issuecomment-499184318 I've created a test branch for this: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commits/spi... I'm now running the new version on both my modules, and they seem to be very stable up to now. Not a single websocket data corruption yet. I'll publish the build to my "edge" users now. Regards, Michael Am 05.06.19 um 19:01 schrieb Michael Balzer:
Not worth trying yet.
It seems the toolchain libstdc++ hasn't been built with workaround, std::string is still broken.
Regards, Michael
Am 05.06.19 um 09:19 schrieb Mark Webb-Johnson:
FYI: Espressif have (finally) released a test toolchain for our PSRAM issue:
https://github.com/espressif/esp-idf/issues/2892
Linux <https://dl.espressif.com/dl/xtensa-esp32-elf-linux64-1.22.0-90-g26d9621-5.2.0-psramfix-20190605.tar.gz> Windows <https://dl.espressif.com/dl/xtensa-esp32-elf-win32-1.22.0-90-g26d9621-5.2.0-psramfix-20190605.tar.gz> OSX <https://dl.espressif.com/dl/xtensa-esp32-elf-macos-1.22.0-90-g26d9621-5.2.0-psramfix-20190605.tar.gz>
Apparently, we need to include the following flags:
|CFLAGS+=-mfix-esp32-psram-cache-dupldst CXXFLAGS+=-mfix-esp32-psram-cache-dupldst|
This is a preliminary test fix only, so not for general release, but worth trying.
Regards, Mark
_______________________________________________ OvmsDev mailing list OvmsDev@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@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