You can try this documentation page, it explains more about various exceptions. Perhaps you can use the backtrace and core dump features to find the place in the code where error happens.
https://docs.espressif.com/projects/esp ... rrors.html
Search found 2067 matches
- Fri Dec 07, 2018 12:10 am
- Forum: ESP32 Arduino
- Topic: My ESP32 issues.
- Replies: 10
- Views: 14770
- Thu Dec 06, 2018 3:28 pm
- Forum: General Discussion
- Topic: How to obtain documented assembly listing ?
- Replies: 4
- Views: 6858
Re: How to obtain documented assembly listing ?
One option is to start xtensa-esp32-elf-gdb <elf file> and then execute "disassemble /m <function name>".
You don't need to connect to the target to do this.
You don't need to connect to the target to do this.
- Wed Dec 05, 2018 3:04 pm
- Forum: ESP-IDF
- Topic: [question] wifi radio sleep
- Replies: 1
- Views: 2316
Re: [question] wifi radio sleep
It says "total sleep time: 0 us" (out of xxxxx us of connection time), so this part looks correct.
- Wed Dec 05, 2018 12:45 pm
- Forum: Hardware
- Topic: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
- Replies: 22
- Views: 24417
Re: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
Okay, if it does not enter user application then it means that it still locks up when switching the frequency, just in a different place. This makes more sense. Indeed a power supply instability or other noise can prevent the PLL from locking. You can contact Espressif support via sales at Espressif...
- Wed Dec 05, 2018 11:22 am
- Forum: Sample Code
- Topic: ulp simple counter
- Replies: 1
- Views: 4178
Re: ulp simple counter
The mistake is in
I_ADDR(R2, R2, 1)
This should be
I_ADDI(R2, R2, 1)
Otherwise you are calculating R2=R2+R1 (1 is treated as register index), and R1 is 0.
I_ADDR(R2, R2, 1)
This should be
I_ADDI(R2, R2, 1)
Otherwise you are calculating R2=R2+R1 (1 is treated as register index), and R1 is 0.
- Wed Dec 05, 2018 11:18 am
- Forum: General Discussion
- Topic: Is it possible to force using the internal oscillator instead of the external 32kHz crystal
- Replies: 6
- Views: 8604
Re: Is it possible to force using the internal oscillator instead of the external 32kHz crystal
Zingemneire: at the moment copying that bit of code is probably the easiest way to achieve what you need. I have added this as a feature request ("allow selecting RTC slow clock source at run time") for the next IDF version.
- Wed Dec 05, 2018 11:15 am
- Forum: Hardware
- Topic: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
- Replies: 22
- Views: 24417
Re: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
Just to clarify, with the 40MHz change applied, does it boot all the way to your application, or it stops at "pro CPU start user code"? I don't have any good explanation for this behavior, as I don't know of any reasons why clock switching might not succeed at first, but succeed later (2nd clock swi...
- Wed Dec 05, 2018 4:22 am
- Forum: Hardware
- Topic: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
- Replies: 22
- Views: 24417
Re: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
Okay, can you try changing "int cpu_freq_mhz = 80;" to "int cpu_freq_mhz = 40;" in bootloader_clock.c, and see if that allows the 2nd stage bootloader to proceed past "bootloader_clock_configure()"?
- Wed Dec 05, 2018 3:12 am
- Forum: ESP-IDF
- Topic: how to debug rst:0x8 (TG1WDT_SYS_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT) an arduino-esp32
- Replies: 3
- Views: 17564
Re: how to debug rst:0x8 (TG1WDT_SYS_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT) an arduino-esp32
I don't know how to do this in Arduino, but if you build with Arduino as IDF component, you can increase bootloader log verbosity. This will print PC (program counter) values of both CPUs, after reboot. Often this can give a hint about the location of the issue.
- Wed Dec 05, 2018 1:40 am
- Forum: Hardware
- Topic: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
- Replies: 22
- Views: 24417
Re: Help needed - New ESP32 PICO D4.1 design continously looping with RTCWDT_RTC_RESET
Upon further thought, RTC WDT might be happening because the bootloader eventually disables the TG WDT, and keeps only RTC WDT running. So might not be related to bootloader_clock_configure.