[TW#27580] strange behavior on reset #2731
Comments
Alvin1Zhang
changed the title
|
Hi @chegewara. This behavior is not right. I can assume that this is happening due to some kind of settings in sdkconfig.
Also, I have some question:
|
if i remember hello-world was compiled with release/v3.1 branch with default config https://gist.github.com/chegewara/9fed4a6fdc2678c4cd3f6a0bfba10093 |
|
Thank @chegewara for your report. I was able to reproduce your error. I will try to find a solution. The reason is different CPU frequency in two configurations.
It reproduced on master branch as well. |
|
Good catch, i wouldnt find it myself. |
igrr
added a commit
that referenced
this issue
Feb 28, 2019
In the situation when bootloader was compiled for 240MHz, and app was compiled for 160MHz, and the chip is a revision 0 chip, the bootloader will assume that the application has also been running at 240MHz. This will cause the chip to lock up later. Modify this to use a run time check of DPORT_CPUPERIOD_SEL, which indicates which of the PLL frequencies was used. Closes #2731.
igrr
added a commit
that referenced
this issue
Mar 1, 2019
In the situation when bootloader was compiled for 240MHz, and app was compiled for 160MHz, and the chip is a revision 0 chip, the bootloader will assume that the application has also been running at 240MHz. This will cause the chip to lock up later. Modify this to use a run time check of DPORT_CPUPERIOD_SEL, which indicates which of the PLL frequencies was used. Closes #2731.
catalinio
pushed a commit
to catalinio/pycom-esp-idf
that referenced
this issue
Jun 28, 2019
In the situation when bootloader was compiled for 240MHz, and app was compiled for 160MHz, and the chip is a revision 0 chip, the bootloader will assume that the application has also been running at 240MHz. This will cause the chip to lock up later. Modify this to use a run time check of DPORT_CPUPERIOD_SEL, which indicates which of the PLL frequencies was used. Closes espressif/esp-idf#2731.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just end with OTA over BLE example and it is running fine, but after ota flashing i have very strange behavior. As first app to ota flash i have hello-world from esp-idf examples. No modifications at all. After updating esp32 code is running fine and after 10 seconds loop esp32 restart but not always is starting again. Here is log:
Usually its only one "empty" restart and next time is running fine (no interaction from my side). In this log we can see 2 "empty"restarts, First
SW_CPU_RESETand thenRTCWDT_RTC_RESET.my esp32 is devKitC v2
The text was updated successfully, but these errors were encountered: