Doesn't look like it. I'll file an internal issue.

Yep. Some fly-by-night (no proper user agent) crawler decided to hit our forum from like 30 different IPs. They're blocked now.

atique wrote: ↑

Fri Sep 06, 2024 8:16 am

while my partition size is just 0x1000.

That may be your problem: NVS needs at least 3 sectors and you're only giving it one.

Vaibhav02 wrote: ↑

Fri Sep 06, 2024 6:04 am

If I run my Node.js server on the ESP32,

Node.js cannot (meaningfully) run on an ESP32.

You could select the menuconfig option to make the task wdt panic; that should give you a backtrace that may give us more info.

Not sure what's wrong, but the canonical way to do this is to use the esp-idf build system to generate the partition so you're sure you have an entirely clean one. Perhaps try that?

Thank you for your patience , understood ! Then the only way to it is : - flashing myself with encryption on This is correct - ask the manufacturer to do it (giving him the key) What would usually happen is that you give the manufacturer a bootloader, partition table and 'factory' app. If you compi...

You're welcome. Yeah, variable lifetime (and ownership) suddenly gets a lot more important as you're passing pointers between tasks.

Also that terminal screenshot looks like the ESP is getting too little power... perhaps your power supply lines are too thin/long? Adding a large cap (100u electrolytic or something, whatever you have in your parts bin) to the 3.3v power supply close to the pads of the module might help then.

Change it to The compiler likely gave you a warning about this.