Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

if CPU freq clock > 80MHz, then 2'nd bootloader hangs up after restarting from panic error #223

Closed
amuzyka27 opened this issue Jan 12, 2017 · 1 comment
Closed

if CPU freq clock > 80MHz, then 2'nd bootloader hangs up after restarting from panic error #223

amuzyka27 opened this issue Jan 12, 2017 · 1 comment
Labels
Resolution: Done Issue is done internally Status: Resolved Issue is done internally
Milestone
v2.0

Comments

@amuzyka27
Copy link

amuzyka27 commented Jan 12, 2017 •
edited
Loading

Reproducible on board: ESP-Wroom-32

After commit 2e3ca1c2f7f35775010cd7637bd85fac0ef6dbef when CPU freq is configured to 240 or 160 MHz and restart form panic error occurs, sometimes (5/10) 2'nd stage bootloader is hanging up. Only by unpowering the restart is possible. Some logs (panic error source doesn't matter):

Guru Meditation Error of type InstrFetchProhibited occurred on core  0. Exception was unhandled.
Register dump:
PC      : 0xf7ffffff  PS      : 0x00060730  A0      : 0x8008bd35  A1      : 0x3ffe3b20  
A2      : 0xf7ffffff  A3      : 0x3ffc98a6  A4      : 0x00000025  A5      : 0x00000032  
A6      : 0x000000ff  A7      : 0x00000000  A8      : 0x3f400124  A9      : 0x0000000c  
A10     : 0x00000000  A11     : 0x00000002  A12     : 0x5fff0007  A13     : 0x00000000  
A14     : 0x00000000  A15     : 0x00000000  SAR     : 0x00000000  EXCCAUSE: 0x00000014  
EXCVADDR: 0xf7fffffc  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0x00000000  

Backtrace: 0x77ffffff:0x3ffe3b20 0x4008bd35:0x3ffe3b40 0x40088d79:0x3ffe3b80 0x40089e51:0x3ffe3bb0 0x4008a635:0x3ffe3bd0 0x400d275b:0x3ffe3bf0 0x400d2103:0x3ffe3c10 0x40080b4e:0x3ffe3c30 0x40080caf:0x3ffe3c60 0x4007841d:0x3ffe3ca0 0x40078634:0x3ffe3cd0 0x40078ba4:0x3ffe3d50 0x40080101:0x3ffe3e70 0x40007c34:0x3ffe3eb0 0x40000740:0x3ffe3f20

Rebooting...
ets Jun  8 2016 00:22:57

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:3384
load:0x40078000,len:7524
load:0x40080000,len:260
entry 0x40080034

And after that nothing happens.

Br,
Adrian
@projectgus
Copy link
Contributor

Thanks for reporting this Adrian. I was able to reproduce and we have a fix here, should appear in esp-idf master branch shortly.

@igrr igrr added the Status: In Progress Work is in progress label Jan 15, 2017
@igrr igrr closed this as completed in e53d307 Jan 16, 2017
igrr added a commit that referenced this issue Jan 16, 2017
@igrr
Merge branch 'bugfix/panic_reset_hangs' into 'master'
6538252 
Panic handler: Use same reset path as esp_restart(), disabling hardware

Closes #223 #223

See merge request !417
@igrr igrr removed Status: In Progress Work is in progress labels Jan 16, 2017
@igrr igrr modified the milestone: v2.0 Jan 20, 2017
@espressif-bot espressif-bot added Status: Opened Issue is new Status: In Progress Work is in progress Status: Reviewing Issue is being reviewed and removed Status: Opened Issue is new Status: In Progress Work is in progress labels May 12, 2022
@espressif-bot espressif-bot added Resolution: Done Issue is done internally Status: Resolved Issue is done internally and removed Status: Reviewing Issue is being reviewed labels Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution: Done Issue is done internally Status: Resolved Issue is done internally
Projects
None yet
Milestone
v2.0
Development

No branches or pull requests
4 participants
@projectgus @igrr @amuzyka27 @espressif-bot