Angus, attached is full console log where heap corruption starts. This code was working fine before recent update to espidf, toolchain with a few exceptions - I've seen it a couple of times in the past but ignored it. Now it happens every time I go through this cycle. This is the code that is failin...

I just updated to latest version espidf + toolchain and am now crashing with what seems like the same or related error. The first log message prints the expected json object data. The next 2 log messages print fine. I crash every time before getting to last log message. config::network.hubIP is a st...

I am saving wifi configuration data in nvs. After I updated the code and re-flashed, the program retrieves stored ssid/password. The parameters are stored in std::string. There are no errors on retrieval, the strings retrieved are the proper lengths but they contain all null characters. I've done th...

I saw that example and my assumption was that all of the code in the ulp folder was sensor-specific. It may be that I could tweak for my specific requirements but if I need code that is significantly different, I'm afraid I'd be lost

I've been planning to migrate i2c processes over to the ulp but just realized that assembly-level programming is required. This is beyond my capabilities and I don't have the time (or desire I guess) to try coming up to speed for anything complex. Is there any plan/schedule to be able to program the...

not quite sure what you mean by 'the application'. I've got putty monitoring the esp32 (espidf) so this has to be an esp32 message, correct?

correction. now I get what you're meaning. Just did a global search on the message and found it in the paho mqtt library. thanks for the boost Neil

Trying to debug some very intermittent issues and I got the following on my log monitor. After these messages printed, the app picked back up and ran normally: closing session 4 closing session cleaning session Does anyone have any idea what these messages refer to so that I can try and troubleshoot?

So there is no way to figure out what the back trace is pointing to?

With the debugging suggestions here, I now know the task causing WDT - its a pretty simple task so not obvious why the WDT would be called. Trying to understand how to trace error based on what the monitor is showing me but not having much luck. Could someone explain (or point to a link) if/how I ca...

in general, there are no long running tasks so don't think JTAG would help with this issue although I have been considering it for other debugging. I'm guessing my issue is related to wifi communications getting hung somewhere so I'll take a look at the panic config to see if that can provide more i...