Search found 107 matches
- Wed Mar 03, 2021 2:00 am
- Forum: General Discussion
- Topic: ESP32-S2 abort() in locks.c with no reference to my code in backtrace [WIFI-3462][WIFI-3463]
- Replies: 13
- Views: 13120
Re: ESP32-S2 abort() in locks.c with no reference to my code in backtrace
Thanks ESP-Marius. Changing ESP_LOGI to ESP_EARLY_LOGI in lib_printf did indeed stop the aborts. But there seems to be some other problem with the wifi module. In an earlier version of 4.3 it worked fine, but now it takes 10 seconds after boot before the wifi manages to start up then it looks like i...
- Tue Mar 02, 2021 12:16 pm
- Forum: General Discussion
- Topic: ESP32-S2 abort() in locks.c with no reference to my code in backtrace [WIFI-3462][WIFI-3463]
- Replies: 13
- Views: 13120
Re: ESP32-S2 abort() in locks.c with no reference to my code in backtrace
And where do I find these 2 files, since those paths don't refer to anything on my Windows machine. 0x4010bd0a: _vfprintf_r at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp32s2-elf/src/newlib/newlib/libc/stdio/vfprintf.c:853 (discriminator 2) 0x4010ed69: vprintf at /builds/idf/c...
- Tue Mar 02, 2021 11:57 am
- Forum: General Discussion
- Topic: ESP32-S2 abort() in locks.c with no reference to my code in backtrace [WIFI-3462][WIFI-3463]
- Replies: 13
- Views: 13120
ESP32-S2 abort() in locks.c with no reference to my code in backtrace [WIFI-3462][WIFI-3463]
On an ESP32-S2 using ESP-IDF v4.3-beta1-25-g603db1828 I'm getting a deterministic abort about 1400ms after boot. The backtrace doesn't reference any of my code. abort() was called at PC 0x40026786 on core 0 0x40026786: lock_acquire_generic at E:/Dev/Espressif/esp-idf/components/newlib/locks.c:138 Ba...
- Sun Feb 28, 2021 4:05 am
- Forum: General Discussion
- Topic: Debugging LoadProhibited from Windows 10
- Replies: 3
- Views: 3631
- Fri Feb 26, 2021 4:07 am
- Forum: General Discussion
- Topic: Debugging LoadProhibited from Windows 10
- Replies: 3
- Views: 3631
Debugging LoadProhibited from Windows 10
I'm getting a LoadProhibited out of a library that I have been happily using for several years. Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled. Core 0 register dump: PC : 0x400dc335 PS : 0x00060e30 A0 : 0x800e620c A1 : 0x3ffda3e0 0x400dc335: ArduinoJson::Internals::...
- Fri Jan 15, 2021 3:47 am
- Forum: General Discussion
- Topic: WDT timeout in bootloader for ESP32s2
- Replies: 22
- Views: 16386
Re: WDT timeout in bootloader for ESP32s2
OK, much thanks to Angus for help on this one.
Turns out it was a conflict between flash and PSRAM brought on by our erroneous use of GPIO26 on the ESP32S2 Wrover.
William
Turns out it was a conflict between flash and PSRAM brought on by our erroneous use of GPIO26 on the ESP32S2 Wrover.
William
- Fri Jan 08, 2021 5:42 am
- Forum: General Discussion
- Topic: WDT timeout in bootloader for ESP32s2
- Replies: 22
- Views: 16386
Re: WDT timeout in bootloader for ESP32s2
Angus, none of those Saved PC addresses look valid: E:\Source\wylas\beamatouch>xtensa-esp32s2-elf-addr2line -pfiaC -e build/beamatouch.elf 0x40334a6f 0x40334a6f: ?? ??:0 E:\Source\wylas\beamatouch>xtensa-esp32s2-elf-addr2line -pfiaC -e build/beamatouch.elf 0x40334a71 0x40334a71: ?? ??:0 E:\Source\wy...
- Fri Jan 08, 2021 4:27 am
- Forum: General Discussion
- Topic: WDT timeout in bootloader for ESP32s2
- Replies: 22
- Views: 16386
Re: WDT timeout in bootloader for ESP32s2
@ESP_Angus we realise this might be intractable without the source code.
How can we share that with you privately?
How can we share that with you privately?
- Fri Jan 08, 2021 4:24 am
- Forum: General Discussion
- Topic: WDT timeout in bootloader for ESP32s2
- Replies: 22
- Views: 16386
Re: WDT timeout in bootloader for ESP32s2
To put this in context. This code works // All My setup code is above here. ESP_LOGI(TAG, "Finished setup"); // NB this line was added just to stop the app from aborting during startup. It is a hack. // See https://www.esp32.com/viewtopic.php?f=2&t=18842 ESP_LOGI(TAG, "Finished setup2"); // while (t...
- Fri Jan 08, 2021 4:19 am
- Forum: General Discussion
- Topic: WDT timeout in bootloader for ESP32s2
- Replies: 22
- Views: 16386
Re: WDT timeout in bootloader for ESP32s2
Hi Angus. Some answers. Yes the apps is definitely running for 1.2 seconds. There is app log showing. Yes, the log output indicates that it is past the bootloader and into the app. I assumed it had to be to do with the bootloader because the address given only appears to be valid for the bootloader,...