[Ovmsdev] Transition to new esp-idf

Tue Jan 16 08:23:35 HKT 2018

Sorry, no idea. So much has changed in IDF 2.x -> 3.x, and the matching compiler toolchain.

Regards, Mark.

> On 16 Jan 2018, at 2:10 AM, Greg D. <gregd2350 at gmail.com> wrote:
> 
> Hi Mark,
> 
> Before I do the upgrade...  Do you know if the new ESP code base changes the operation of the interrupt service, or provides any new capabilities in that regard?  I'm still working on the CAN 2/3 bus hang, and don't want to shift things, timing wise, making the issue "go away" without actually being solved.  On the other hand, perhaps they've accidentally fixed whatever is we're having trouble with, or perhaps have the ability to do things differently with the chip.
> 
> Thanks,
> 
> Greg
> 
> 
> 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 <mailto: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 <mailto: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 <mailto: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 <mailto: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 <mailto:OvmsDev at lists.teslaclub.hk>
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
>> 
>> 
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

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