Sometimes I don't see the "BTDM_INIT: 32.768kHz XTAL not detected" message, but the 32.768k clock is unstable and causes the board to usually crash when entering light sleep. I can confirm the exact same findings. I was not the one who tested the 10M resistor, a colleague did, but reported no chang...

"me too" May be relevant: https://github.com/espressif/esp-idf/issues/6621 Altough I've tried commits all the way back to August of last year, and I can't get it to work. We've got a batch of 5 custom boards, on 3 the crystal works, on 2 the crystal doesn't. It also doesn't work on the ESP32-WROVER...

If anyone is ever interested in this... for some reason ...here is the macro I've wrote for it. It's huge and totally impractical, as it is so large, that if you use 2 of them like this: A -> ioset -> ioset -> B, you will not be able to call a jump from A to B, because of Error: relocation out of ra...

That's quite unfortunate.. My first thought was the same as your proposal, but just thinking about it makes me nauseous - even though I'll probably have to go down that route (except that I'll hide it in a macro). I'll pass on your variable register writes, because that does indeed look quite dodgy ...

I've just now realized, that the C macros used in the ULP programs, like WRITE_RTC_REG, do not accept register values (r0, r1, etc). Is there a way around that? I've got a register that contains the RTCIO pin number of the pin I'd like to control, but I've got no way to use that value to actually wr...

For future reference, I've fixed this by rewriting my wifi lib to be completely synchronous. That way, the esp_wifi_start() is not being called inside of the event callbacks, but in a separate synchronous task - this resolved the issue, or, at least I cannot reproduce it anymore. What I mean by that...

Well, that's a bit unfortunate, but it's fine as I've had some other ideas to mitigate the issues I'm encountering from this drift (in the future, I could store the current RTC time along with the data the ULP is generating, to take the cycle duration out of the equation). Also, remember that RTC sl...

From my testing it seems that when you setup the ULP via ulp_set_wakeup_period , and run the ULPs program, it essentially works like a loop with a delay with the length being the period you set. This means that if you, for example, set a period of 100ms, the actual execution time for each loop will ...

You could try some special passive IR sensors from Kemet. I haven't tried them yet, but from what I've seen , if they offer the claimed range and focal length (60°) then It might be just perfect (and assuming animals can trigger them). I've got a few, just forgot to buy the tiny pitch JST connectors...

I was making a follow-up to this post, describing log output, commit number, etc.. and then it hit me. This is totally not a thing, just a nasty chain of event handlers that got fired in my own code - leading to esp_restart -> which in turn caused the ulp to get reinitialized due to the wakeup reaso...