And yes, there is. You need to find some way to call deepSleepFunction 20 seconds after power up. You can either do that manually, by making sure the code path before the call to that function lasts 20 seconds (inserting delays strategically would indeed help there) or you could schedule a timer cal...

manoj.balakrishnan wrote: ↑

Tue Apr 16, 2024 6:46 am

Hi Experts ,

You are posting on a wrong subforum, as a reply under an unrelated post, on a question that the community here is unlikely to be able to help you with. Suggest you send an email to sales@espressif.com instead

Ah, never mind, I initially read over your deepSleepFunction code. What do you mean with 'it doesn't even execute the code and stays in a stagnant "on" state.'?

Yes I found these (and some others). Interesting option, but not very much I/O pins (may or may not suffice for a particular task, although I also use I2C and SPI I/O extenders quite often). Also I don't think any of them have SPI RAM, do they? I'd like to have SPI RAM for receiving and buffering i...

That is very odd. Just to check it's not a hardware issue: can you reproduce it on other supermini boards as well?

Your image is unreadable potato quality; suggest you share it as a PDF rather than an image. Aside from that, please check the basics: are your voltage rails okay? Do you see 40MHz on the main crystal? Do you get any output on the serial port on power-on or reset?

#incluir "BluetoothSerial.h" #si !definido(CONFIG_BT_ENABLED) || !definido(CONFIG_BLUEDROID_ENABLED) #error ¡Bluetooth no está habilitado! Ejecute make menuconfig y habilítelo. #terminara si ...the only reason I can explain this is that English is your native language, but you chucked this in an au...

USB-C specs say you should connect the receptacle to ground ( here , page 135) so you can get rid of C1/R3. I'd personally add an 10uF on VCC as well, but that's more intuition than grounded in theory. Wrt adding resistors/inductors, please follow the hardware reference guide , for instance the C3 d...

You're probably running out of interrupts, and the encryption mqtt wants to do indirectly initializes the hardware RSA peripheral, which needs an interrupt to work. You can free up interrupts by marking them as shared (use the correct flag when initializing peripherals for that) or you can disable h...

'delay' doesn't do anything wrt sleep modes. You probably want to read up on deep sleep a bit and retry writing your code.