[Ovmsdev] Transition to new esp-idf

Mark Webb-Johnson mark at webb-johnson.net
Sat Jan 13 11:25:28 HKT 2018

I think we are pretty much ready to go. I just need to make the sdkconfig.default for v3.0 and v3.1. So long as it works for v3.0 developer hardware, that is fine.

@Steve can you update our master clone to latest from Espressif and make sure your stuff is still ok?

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.

I can get my part done by Sunday 14th night (HKT), so suggest to do the Merge of the OVMS firmware master branch then.

Regards, Mark

> On 13 Jan 2018, at 4:44 AM, Stephen Casner <casner at acm.org> wrote:
> We expect production OVMS to be based on release/v3.1 of esp-idf in
> order to incorporate the support for SPIRAM (PSRAM).
> I'd like to set a target for all develpers to move to the master
> branch of openvehicles/esp-idf that contains the finished version of
> my modifications to support the "module memory" command.  At the same
> time I need to then merge the corresponding changes from my temporary
> branch in openvehicles/Open-Vehicle-Monitoring-System-3 to the master
> branch there since the API between the two has changed.
> In other words, we need a flag day.
>                                                        -- Steve
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

More information about the OvmsDev mailing list