[Ovmsdev] 3.1.006

[Stephen Casner]

Michael,

Can you clarify regarding the IRAM space issues.  Was there an error
at build time?  If so, that's a surprise because I don't think our
code does anything with preallocation of IRAM so that means everyone
who uses a similar set of system functions would hit this.

My memory diagnostic code allocates from IRAM if available, but only
if the memory commands are issued, so any system allocations in IRAM
should come first.

                                                        -- Steve

On Tue, 22 May 2018, Michael Balzer wrote:

> I've pushed the updated esp-idf status to our clone now, so we can start using that for release 007.
>
> I've also checked the upstream master status again, which is already quite some commits ahead, including lots of wifi and bluetooth updates.
>
> Unfortunately I got IRAM space issues and had to disable bluetooth to be able to build at all. The resulting firmware crashed immediately on wifi power up with
> error code 0x102 and a message that we should use WIFI_INIT_CONFIG_DEFAULT. Which we do, I don't see anything wrong in our init code. So I switched back to the
> working version for now.
>
> To use the new esp-idf version all you need to do is a pull from our repository and a git submodule update. The xtensa tools are still the same.
>
> Regards,
> Michael
>
>
> Am 17.05.2018 um 10:41 schrieb Michael Balzer:
> > Regarding the esp-idf update: it works without (new) issues and seems to improve stability a bit, but not as much as I was hoping.
> >
> > So it's an option, but not a priority for 006.
> >
> > Regards,
> > Michael
> >
> >
> > Am 17.05.2018 um 05:06 schrieb Mark Webb-Johnson:
> >> Deadline for the factory firmware is this weekend. The modules have all been built and are waiting sim cards, firmware flash, then final QC.
> >>
> >> So, I suggest we freeze things as they are. I will double-check the wifi setup tonight (it seemed ok last time I checked, so hopefully good now). Build will not include the bluetooth code I am working on (that is disabled in our default sdkconfig anyway).
> >>
> >> Is there anything else holding this up? Or anything anybody wants to rush in?
> >>
> >> Regards, Mark.
> >>
> >> _______________________________________________
> >> OvmsDev mailing list
> >> OvmsDev at lists.openvehicles.com
> >> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
> --
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>