-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
Here I have a module which:
- Can get its flash programmed incorrectly (completely different data on read-back, no easily discernible patterns)
- After some boots may get stuck at early stages of bootloader, no reaction to reset or esptool.py. Pressing reset leads to just:
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
(each message is printed on each reset).
Only power-off (disconnect from USB) is what helps.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels