[Ovmsdev] Transition to new esp-idf

Michael Balzer dexter at expeedo.de
Tue Jan 16 02:21:33 HKT 2018

Transition went fine. "make flash" didn't even erase "/store", I had expected that to happen, good to know.


OVMS > sd status
SD CARD is inserted
Name: SL32G
Speed: default speed
Size: 30436MB
CSD: ver=1, sector_size=512, capacity=62333952 read_bl_len=9
SCR: sd_spec=2, bus_width=5

→ me too (the minion) :)

BUT… after reconfiguration to the same components as before, I'm now missing about 30-40 KB of free RAM.

After loading just the Twizy module & the v2 server, I'm now again down to…

OVMS > module memory
Free 8-bit 2632/286352, 32-bit 17972/45144, SPIRAM 0/0

…so it crashes as soon as it needs to actually do anything, like sending a notification.

This is without any of the new CAN logging stuff yet, that's stashed away for the transition.

I'll now check the config again for any more options to save RAM…


Am 15.01.2018 um 06:48 schrieb Stephen Casner:
> In order for the the "module memory" and "module tasks" commands to
> work, the configuration needs to be changed from the sdk.default.hw30
> that Mark just provided. CONFIG_FREERTOS_USE_TRACE_FACILITY needs to
> be enabled, CONFIG_HEAP_POISONING must be enabled (LIGHT or
> COMPREHENSIVE), and CONFIG_HEAP_TASK_TRACKING must be enabled.  I have
> attached a diff for the sdkconfig.  That diff also includes a section
> for enabling telnet, which some of you may be using.
> Please also note that in this revised implementation of "module
> memory" the block address is now the address that is returned from
> malloc, not the address of the header that precedes it, and the length
> of the block is now exclusive of the debugging overhead.
>                                                         -- Steve
> On Mon, 15 Jan 2018, Mark Webb-Johnson wrote:
>> All committed and pushed now.
>> Developers MUST now update their ESP IDF and XTENSA build tools to use this new build. They should also compare sdkconfig and sdkconfig.defaults.hw30 to verify differences. I also suggest you do a ‘make flash’ (rather than ‘make app-flash’) at least once, to update the bootloader to the latest (as bootloaders before v2.1 are no longer supported).
>> Check
>> https://esp-idf.readthedocs.io/en/latest/get-started/index.html#setup-toolchain <https://esp-idf.readthedocs.io/en/latest/get-started/index.html#setup-toolchain>
>> to see the version of XTENSA toolchain required for latest Espressif IDF ‘master’ builds. As of this writing, it is 1.22.0-80-g6c4433a-5.2.0.
>> I hope this goes smoothly for you.
>> Regards, Mark.
>> commit dfcc658557fc480bcccb09b23bc24399bb6e7497 (HEAD -> master, origin/master, origin/HEAD)
>> Author: Mark Webb-Johnson <mark at webb-johnson.net>
>> Date:   Mon Jan 15 07:56:45 2018 +0800
>>     Provide a sdkconfig.default.hw31 for OVMS v3.1 hardware
>> commit 003592d553c881f735fb228b08836a13c306cec3
>> Merge: e58c5b6 b28db5e
>> Author: Mark Webb-Johnson <mark at webb-johnson.net>
>> Date:   Mon Jan 15 07:49:13 2018 +0800
>>     Merge branch 'for-master'. This requires ESP-IDF v3.0 support:
>>     OVMS developers should now:
>>     1] Pull the latest OpenVehicles IDF, and checkout MASTER branch.
>>     2] Update XTENSA tools to match version required by Espressif for MASTER branch.
>>     3] For ovms hardware v3.0, a sdkconfig default file sdkconfig.default.hw30 has
>>        been provided. That can be merged/copied to sdkconfig as appropriate.
>>     4] For ovms hardware v3.1, a sdkconfig default file sdkconfig.default.hw31 will
>>        been provided in the next update.
>>     5] It is recommended that developers perform at least one full 'make flash'
>>        with this version, to update the bootloader to latest. Note that the
>>        sdkconfig.default.* files are now set to require bootloader at least v2.1
>>        (or later), and bootloader v2.0 is no longer supported.
>>     Enjoy.
>>> On 15 Jan 2018, at 7:25 AM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
>>> Merge is ok, but triple checking a couple of things. Should be committed and pushed within the next half hour.
>>> Regards, Mark
>>>> On 15 Jan 2018, at 1:09 AM, Stephen Casner <casner at acm.org> wrote:
>>>> Mark,
>>>> It looks like you were not able to do the sdkconfig.default and merge
>>>> as you planned?
>>>>                                                       -- Steve
>>>>> On Fri, 12 Jan 2018, Stephen Casner wrote:
>>>>>> On Sat, 13 Jan 2018, Mark Webb-Johnson wrote:
>>>>>> @Steve can you update our master clone to latest from Espressif and
>>>>>> make sure your stuff is still ok?
>>>>> I have just now done this.  I had already done a rebase a few days ago
>>>>> before committing the improved version of the OS changes so I could
>>>>> issue a pull request.  There were a few commits since then, which I
>>>>> have now merged.  My code still runs correctly.
>>>>>> I guess steps for developers will be:
>>>>>> 1) pull the openvehicles IDF and switch to master branch. Sub module update.
>>>>>> 2) download and install xtensa build chain to match.
>>>>>> 3) update OVMS master, make clean, check menu config, then build and play.
>>>>> Sounds right.
>>>>>> I can get my part done by Sunday 14th night (HKT), so suggest to do
>>>>>> the Merge of the OVMS firmware master branch then.
>>>>> I'll be sleeping then, so you can go ahead and do the merge.
>>>>>                                                       -- Steve
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> >
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

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

More information about the OvmsDev mailing list