[Ovmsdev] Repeated WDT crashes after upgrade to 3.3 with 4G

[Stephen Casner]

Mark,

Before installing the 4G modem onto my v3.1 main board I just switched
the version tag from main to edge (because I thought that was what was
needed to get the new 3.3 code) and then did "Flash from web".  That
resulted in the the 3.3.001-285.

I have now flashed with the URL you suggested:

http://api.openvehicles.com/firmware/ota/v3.2/edge/3.3.001.ovms3.bin

The result was still the same crash:

OVMS# boot
Last boot was 56 second(s) ago
Time at boot: 2022-03-03 22:10:40 PST
  This is reset #39 since last power cycle
  Detected boot reason: Crash (12/12)
  Reset reason: Task watchdog (6)
  Crash counters: 1 total, 0 early

Last crash: abort() was called on core 0
  Backtrace:
  0x4008e676 0x4008e911 0x400e938c 0x40084152
  Event: ticker.1 at esp32wifi 0 secs
  WDT tasks: IDLE0
  Version: 3.3.001/ota_0/edge (build idf v3.3.4-848-g1ff5e24b1 Nov 22 2021 09:58:29)

                                                        -- Steve

On Fri, 4 Mar 2022, Mark Webb-Johnson wrote:

> Steve, Jeff,
>
> I have noticed you running '3.3.001-285'. Can you try with the standard '3.3.001' that was released a while ago? You can get it from:
>
> http://api.openvehicles.com/firmware/ota/v3.3/main/ovms3.bin <http://api.openvehicles.com/firmware/ota/v3.3/main/ovms3.bin>
>
> or
>
> http://api.openvehicles.com/firmware/ota/v3.2/edge/3.3.001.ovms3.bin <http://api.openvehicles.com/firmware/ota/v3.2/edge/3.3.001.ovms3.bin>
>
> I wonder if something is broken in the latest edge?
>
> P.S. I think that in general we may be confusing people here. The firmware/ota/<X> directory is for those version <X> mainboards. So /v3.1/, /v3.2/ or /v3.3/. The idea is that we can then have different build settings (sdkconfig) for different base hardware (in particular esp32 revision) and make improvements. At the moment v3.1 and v3.2 are symlinked together (on api.openvehicles.com <http://api.openvehicles.com/>) as ESP32 is the same.
>
> Regards, Mark
>
> > On 4 Mar 2022, at 9:17 AM, Stephen Casner <casner at acm.org> wrote:
> >
> > On Thu, 3 Mar 2022, Mark Webb-Johnson wrote:
> >
> >> Can you try to get a debug log for the cellular system?
> >
> > Inline below.  This is with cellular, gsm-mux and SIM7600 set to
> > debug.  Any other useful tags?  Looks like it dies not long after
> > entering NetStart state.
> >
> >                                                        -- Steve