app_main not starting

gouragoura
Posts: 3
Joined: Fri Mar 31, 2017 3:51 am

app_main not starting

Postby gouragoura » Sun Apr 09, 2017 6:43 am

I'm having trouble with esp-idf.

After I updated esp-idf, possibly that caused my esp32 not to enter app_main, and it's now in a reboot loop.
  • First I thought it's my app's problem, so I tried flashing https://github.com/espressif/esp-idf-template, as well as trying other projects, but it was the same.
  • Next I thought it's my board or power source problem, so I tried with another devboard, which is powered by a different power source, but it was the same.
  • Then I thought maybe my esp-idf is corrupted, so I deleted the esp-idf and started over with a fresh esp-idf, by git cloning esp-idf (with --recursive), but it didn't solve the problem.
  • Since I've been developing an OTA app, I thought the partition table might be the problem, so I tried erase_flash, re-flashing the partition table, but haven't found any cure yet.
My bad, I'm not sure when and what caused this problem. I was regularly developing and flashing my firm at last until few days ago.
I'm developing on Mac OS X and flashing with make flash (esptool.py).

Is there anyone facing this problem, or is it just me? I appreciate your help.

Thank you.

Code: Select all

rst:0x10 (RTCWDT_RTC_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:2488
load:0x40078000,len:7128
load:0x40080000,len:252
0x40080000: _iram_start at ??:?

entry 0x40080034
0x40080034: _iram_start at ??:?

I (804) cpu_start: Pro cpu up.
I (804) cpu_start: Single core mode
I (805) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (817) heap_alloc_caps: At 3FFAE2A0 len 00001D60 (7 KiB): DRAM
I (838) heap_alloc_caps: At 3FFB6CD8 len 00029328 (164 KiB): DRAM
I (859) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (880) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (901) heap_alloc_caps: At 4009A2A8 len 00005D58 (23 KiB): IRAM
I (922) cpu_start: Pro cpu start user code
I (982) cpu_start: Starting scheduler on PRO CPU.
Guru Meditation Error: Core  0 panic'ed (Interrupt wdt timeout on CPU0)
Register dump:
PC      : 0x40080bc4  PS      : 0x00060034  A0      : 0x800843ff  A1      : 0x3ffaea40  
0x40080bc4: ipc_task at /Users/mydir/esp/esp-idf/components/esp32/./ipc.c:106

A2      : 0x3ffae5e0  A3      : 0x3ffaeb74  A4      : 0x00060020  A5      : 0x3ffe3b30  
A6      : 0x00000000  A7      : 0x00000000  A8      : 0x3ffaeb74  A9      : 0x3ffaeb74  
A10     : 0x00000001  A11     : 0x00000001  A12     : 0x00060020  A13     : 0x3ffe3b10  
A14     : 0x3ffb13dc  A15     : 0x00000000  SAR     : 0x00000000  EXCCAUSE: 0x00000005  
EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  

Backtrace: 0x40080bc4:0x3ffaea40 0x400843ff:0x3ffaea60 0x40083397:0x3ffaea80 0x40080bf3:0x3ffaeac0
0x40080bc4: ipc_task at /Users/mydir/esp/esp-idf/components/esp32/./ipc.c:106

0x400843ff: xPortGetCoreID at /Users/mydir/esp/esp-idf/components/freertos/./tasks.c:4415
 (inlined by) vTaskPlaceOnEventList at /Users/mydir/esp/esp-idf/components/freertos/./tasks.c:2852

0x40083397: xQueueGenericReceive at /Users/mydir/esp/esp-idf/components/freertos/./queue.c:2034

0x40080bf3: ipc_task at /Users/mydir/esp/esp-idf/components/esp32/./ipc.c:106


Rebooting...

ESP_igrr
Posts: 2072
Joined: Tue Dec 01, 2015 8:37 am

Re: app_main not starting

Postby ESP_igrr » Sun Apr 09, 2017 8:33 am

Do you have single core mode enabled in menuconfig? If so, this looks like this issue:
https://github.com/espressif/esp-idf/issues/496

gouragoura
Posts: 3
Joined: Fri Mar 31, 2017 3:51 am

Re: app_main not starting

Postby gouragoura » Sun Apr 09, 2017 8:58 am

Thanks ESP_igrr, will check it out :)

gouragoura
Posts: 3
Joined: Fri Mar 31, 2017 3:51 am

Re: app_main not starting

Postby gouragoura » Sun Apr 09, 2017 9:38 am

I was having the single core enabled, and I confirmed that the patch solves the problem.
Thanks ESP_igrr :)

Who is online

Users browsing this forum: Google [Bot] and 90 guests