[Ovmsdev] Flash memory and developement setup
Mark Webb-Johnson
mark at webb-johnson.net
Wed Apr 8 10:05:16 HKT 2020
> Am I correct to assume that the 16Mb of memory is on the module now?
The ESP32 chip uses an external flash chip. The WROOM/WROVER modules include a flash chip in the modules.
In the very early days of development prototypes for OVMS v3, we used an external 16MB flash chip (as only 4MB WROOM modules were available at the time).
For production, we switched to 16MB WROVER modules, so don’t require any external flash chip any more.
> How are the core developers dealing with this slowness?
I don’t find it slow at all (but I use MAC and LINUX for development). Most of the time, it is an incremental build (only building changes code, and then a linking step) - it normally takes longer to flash the chip than build the code. I timed a full ‘make clean; make -j 4’ to see what it is for me:
$ time make -j 4
...
real 2m53.557s
user 5m55.978s
sys 1m40.391s
Just under 3 minutes real time. Perhaps you can check in windows to see how much worse it is?
> Is it at all possible, if i could force platformio to use the correct the idf-esp libraries, to compile the OVMS code in a more recent environment that uses cmake and ninja?
I haven’t tried it myself. We do have some make scripts in various components that may rely on the existing build system. Things like the versioning.
OVMS was written when ESP-IDF was quite new, and unpolished. At some point, we will most likely migrate to a newer build system, as ESP-IDF matures.
Regards, Mark.
> On 8 Apr 2020, at 8:37 AM, Eddy Vromen <eddy_vromen at hotmail.com> wrote:
>
>
>
>
> HI All,
>
> I have a question about the flash memory of the ESP32.
> I read that the ESP32 uses 16Mb of external flash memory and in the schematics on page 27 there is a flash memory chip. However, in the latest v3.2 schematics there is no external flash chip.
> Am I correct to assume that the 16Mb of memory is on the module now?
> How does this impact the e-fuse settings?
>
>
>
> Another question that came up while setting up a development environment:
> The version of esp-idf thats used by the OVSM project uses the Mingw32 environment. Based on my limited exposure to using this environment, its very slow compared to compiling esp-idf code under e.g. platformio under VSCode.
> How are the core developers dealing with this slowness?
> Is it at all possible, if i could force platformio to use the correct the idf-esp libraries, to compile the OVMS code in a more recent environment that uses cmake and ninja?
>
>
>
> Thanks,
> Eddy
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200408/1cfd0fb0/attachment.htm>
More information about the OvmsDev
mailing list