Hello,
Is it possible to send this privately in chat or email? the entire log has company sensitive information.
Both cores run freertos, core 1 has some of the tasks pinned to it including LWIP.
Search found 57 matches
- Tue Sep 05, 2023 8:47 pm
- Forum: General Discussion
- Topic: Watchdog Reset By handle_livelock_int
- Replies: 5
- Views: 4877
- Tue Sep 05, 2023 4:05 am
- Forum: General Discussion
- Topic: Watchdog Reset By handle_livelock_int
- Replies: 5
- Views: 4877
Re: Watchdog Reset By handle_livelock_int
Hello,
interesting thing is when this happens I get no trace of any shape since CPU locks up, it just reboots and on the next boot it prints the PC mentioned above. Is there any other method to get more info from it to send you?
interesting thing is when this happens I get no trace of any shape since CPU locks up, it just reboots and on the next boot it prints the PC mentioned above. Is there any other method to get more info from it to send you?
- Sun Sep 03, 2023 7:21 am
- Forum: General Discussion
- Topic: Watchdog Reset By handle_livelock_int
- Replies: 5
- Views: 4877
Watchdog Reset By handle_livelock_int
Hello, We have built a product using ESP32-PICO-V3-MINI module. We do use the 2MB PSRAM mostly for a large queue and also Task stacks. We get lots of watch dog resets related to live lock(Using IDF V5.1 stable release): 0x40081c84: .handle_livelock_int at C:/Espressif/frameworks/esp-idf-v5.1/compone...
- Sat Jan 25, 2020 9:19 pm
- Forum: Hardware
- Topic: PSRAM/SD card/PICO D4
- Replies: 11
- Views: 20702
Re: PSRAM/SD card/PICO D4
I have been successfully using my PICO-D4 with PSRAM for 2 years on hundreds of boards now, however once I updated IDF to master branch (v4.1-dev-1891-g3634192de-dirty) which is supposed to have PSRAM support for PICO-D4, my code broke and is crashing with this error on boot: E (1220) memory_layout:...
- Wed Aug 07, 2019 3:29 am
- Forum: ESP-IDF
- Topic: Modbus on UART0
- Replies: 1
- Views: 3308
Modbus on UART0
Hello ESP experts. I have tested the modbus slave example with Uart2 and everything works fine. However I need to use Uart0 instead. I have changed the console port to uart1 and changed modbus port to uart0. Even though the console is now successfully moved to uart1, but modbus doesn't work on uart0...
- Sun Jun 23, 2019 8:13 pm
- Forum: Report Bugs
- Topic: WiFi cannot allocate memory in SPIRAM when ISRAM is full
- Replies: 3
- Views: 5723
Re: WiFi cannot allocate memory in SPIRAM when ISRAM is full
I have the same issue. As soon as I enable the option for Wifi and LWIP stack to allocate from PSRAM, weird things such as WiFi not connecting starts happening. Were you ever able to figure this out?
- Wed Jun 19, 2019 4:18 am
- Forum: ESP-IDF
- Topic: ESP_ping issue in v3.3-beta3
- Replies: 14
- Views: 16472
Re: ESP_ping issue in v3.3-beta3
Yes, I have a better idea of where the issue is now. Like @ESP_Sprite mentioned, I knew that disabling the workaround will most likely cause unrecoverable issues in the future, and since my device is in the field, it will be hard to deal with. I dug a bit deeper, just messing around with sdkconfig p...
- Sun Jun 16, 2019 5:39 pm
- Forum: ESP-IDF
- Topic: ESP_ping issue in v3.3-beta3
- Replies: 14
- Views: 16472
Re: ESP_ping issue in v3.3-beta3
I found the issue ! Under menu config, if I enable any or both of the following two options, weird things such as the one I explained starts happening: -- CONFIG_SPIRAM_CACHE_WORKAROUND As soon as I turn it off, things start working again!! So between idf 3.1 and 3.3 someone has changed something in...
- Mon Jun 10, 2019 3:56 am
- Forum: ESP-IDF
- Topic: ESP_ping issue in v3.3-beta3
- Replies: 14
- Views: 16472
Re: ESP_ping issue in v3.3-beta3
Still looking. I think I will have to dig deeper into the API source, but I have to narrow it down first. I'm thinking it is most likely in WiFi, LWIP modules.
- Wed Jun 05, 2019 5:15 am
- Forum: ESP-IDF
- Topic: ESP_ping issue in v3.3-beta3
- Replies: 14
- Views: 16472
Re: ESP_ping issue in v3.3-beta3
I Upgraded from 3.1, master is doing the same thing. Actually my previous thought was wrong, the issue had nothing to do with the interface call. The issue is ping process starting before wifi stack (I use ethernet interface as well). So what I did is put a flag so it waits for wifi to initialize a...