QUERY · ISSUE

ESP32-D2WD

openby tcpipchipopened 2019-09-10updated 2019-09-11

port-esp32

This new patch is making my NINA W102 reset

Some partition problem!

When i followed your step...
https://user-images.githubusercontent.com/428908/62618040-1feb6000-b8c8-11e9-990b-c3843319f524.png
Had worked very fine :)

Now crash!

CANDIDATE · ISSUE

ESP32: add support for 160MHz rated CPUs

closedby fgiavaopened 2019-10-01updated 2019-10-18

port-esp32

Some recent ESP32 chips are rated only to 160MHz: ESP32-D2WD or ESP32-S0WD.

Flashing this kind of ESP32 board with the current mPython version 1.11 we have a continuous reset loop with primary bootloader activation.

The same problem has been reported in the Arduino environment “Espressif ESP32 board support” and solved in the last release 1.03.
Here some relevant link:

https://forum.micropython.org/viewtopic.php?f=18&t=6980&p=39922&hilit=240#p39922

https://esp32.com/viewtopic.php?f=12&t=11439&start=10

Assessment

S Sonnet · medium

Both issues report the same chip (ESP32-D2WD) entering a reset/crash loop when running MicroPython. Issue #5089 attributes the problem to partition configuration, but the symptom — continuous reset on ESP32-D2WD — is almost certainly the same root cause identified in #5169: the chip is rated only to 160MHz but MicroPython configures it to run at 240MHz, causing bootloader-level failures that could manifest as both reset loops and partition errors. The NINA W102 module used in #5089 is based on the ESP32-D2WD, making it the exact same hardware class. #5169 provides the correct diagnosis and links to corroborating reports, while #5089 misdiagnoses the symptom as a partition issue. The confidence is medium rather than high because the partition angle in #5089 could theoretically be a separate regression, but the chip, symptom, and timing all align.

Suggested action

Close #5089 as a duplicate of #5169. The newer issue (#5169) has substantially better diagnostic detail — it correctly identifies the 160MHz CPU frequency limitation as the root cause and references external corroboration — so the older issue should be closed in favour of it. Suggested close comment: "This appears to be the same issue as #5169 — the ESP32-D2WD is rated to 160MHz maximum and MicroPython was configuring it at 240MHz, causing the reset loop. Closing in favour of the better-documented report."

ESP32-D2WD

ESP32: add support for 160MHz rated CPUs

Keyboard