We are still experiencing different issues with the ESP32 on the Pycom devices, see also
Thomas Rogg of Neonius seems to have found a glitch related to PSRAM and dual core mode.
While we are not into the details of this yet, you might enjoy diving into it. It looks like Espressif is working on a workaround solution shipped through ESP-IDF to mitigate the issues for all the silicon which is already out there.
Andreas
September 18, 2019, 8:44pm
2
Besides
there are also some other recent reports which indicate something might be fishy here.
Andreas
October 31, 2019, 12:53pm
3
Falling back to unicore mode
lowjs
Thomas Rogg of Neonius says:
so they switched back to single-core mode:
committed 11:12PM - 22 Feb 19 UTC
OVMS
Others seem to be doing similar things for now:
committed 01:49PM - 29 Oct 19 UTC
Reason: https://github.com/espressif/esp-idf/issues/2892
TL;DR: SPIRAM still wo… rks reliably only in unicore mode
See also:
opened 11:17AM - 04 Oct 19 UTC
closed 01:26AM - 10 Oct 19 UTC
I'm trying to set up to ESP toolchain to be able to compile OVMS V3. I followed … the [Espressif Setup Guide](https://docs.espressif.com/projects/esp-idf/en/stable/get-started/) to install the latest tool chain and have been able to successfully compile the 'hello-word' example.
I'm aware I now need to switch to the [OVMS specific older version of esp-idf](https://github.com/openvehicles/esp-idf) in order to compile OVMS V3. I've tried changing the `$IDF_PATH` to the OVMS esp-idf but I get a `Toolchain version is not supported` warning and some errors (see below). Any trips on how to make this work, I've been trying to follow the guide in the old OVMS developers gdoc. Once I get this working would you like me to write a guide for the new docs page?
```
WARNING: Toolchain version is not supported: esp32-2019r1
Expected to see version: crosstool-ng-1.22.0-80-g6c4433a
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.
WARNING: Compiler version is not supported: 8.2.0
Expected to see version(s): 5.2.0
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.
WARNING: Toolchain version is not supported: esp32-2019r1
Expected to see version: crosstool-ng-1.22.0-80-g6c4433a
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.
WARNING: Compiler version is not supported: 8.2.0
Expected to see version(s): 5.2.0
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.
WARNING: Missing submodule components/bootloader/subproject/components/micro-ecc/micro-ecc...
Attempting 'git submodule update --init components/bootloader/subproject/components/micro-ecc/micro-ecc' in esp-idf root directory...
error: pathspec 'components/bootloader/subproject/components/micro-ecc/micro-ecc' did not match any file(s) known to git.
/home/bailey/Downloads/dev/esp-idf/make/project.mk:611: recipe for target '/home/bailey/Downloads/dev/esp-idf/components/bootloader/subproject/components/micro-ecc/micro-ecc/.git' failed
make[1]: *** [/home/bailey/Downloads/dev/esp-idf/components/bootloader/subproject/components/micro-ecc/micro-ecc/.git] Error 1
/home/bailey/Downloads/dev/esp-idf/components/bootloader/Makefile.projbuild:41: recipe for target '/home/bailey/Downloads/dev/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/build/bootloader/bootloader.bin' failed
make: *** [/home/bailey/Downloads/dev/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/build/bootloader/bootloader.bin] Error 2
```
Andreas
November 1, 2019, 11:53pm
5
Damien George also confirms there are hardware bugs with and compiler workarounds against issues with the SPIRAM on ESP32.
opened 12:14PM - 23 Aug 19 UTC
closed 10:19AM - 24 Aug 19 UTC
Mp version: 4d94fae
esp-idf version: 6b3da6b1882f3b72e904cc90be67e9c4e3f369a9
Hardware:4M SPIRAM + 4M flash
Hi,
I found micropython starts slower when dual core is enabled. No matter which...
port-esp32
Andreas
February 4, 2020, 10:13pm
7
There have been some updates on the core issue within the Espressif issue tracker. Enjoy.
opened 04:42PM - 27 Dec 18 UTC
We stumbled upon the fact that cache issue with PSRAM still exist, even in the newest development environment. This can produce...