Boot loops on Wemos Lolin S3 Mini

[sartyx]

Hi, just tried IRRemote with a S3 Mini... not so successfull though.

I know there are bootloops documented at the esp8266 fork https://github.com/crankyoldgit/IRremoteESP8266/
but I tried different pins 5 and 8 with same result :(

TinyReceiver.ino:

16:10:09.432 -> START C:\Users\A1\OneDrive\Dokumente\Arduino\IR_TinyReceiver\IR_TinyReceiver.ino from Feb 26 2024
16:10:09.432 -> Using library version 2.0.0
16:10:09.432 -> Ready to receive Fast IR signals at pin 8
16:10:10.407 -> 
16:10:10.407 -> abort() was called at PC 0x40378e87 on core 1
16:10:10.407 -> 
16:10:10.407 -> 
16:10:10.407 -> Backtrace: 0x40377a8e:0x3fc93940 0x4037b2bd:0x3fc93960 0x40380ad1:0x3fc93980 0x40378e87:0x3fc93a00 0x40378f99:0x3fc93a30 0x40379068:0x3fc93a50 0x42016f32:0x3fc93a80 0x42019f59:0x3fc93d90 0x42021e91:0x3fc93dc0 0x4200cf96:0x3fc93df0 0x4200d02b:0x3fc93e20 0x42003a45:0x3fc93ea0 0x42003b3a:0x3fc93ed0 0x42001d2d:0x3fc93f40 0x42001ab3:0x3fc93fa0 0x42001847:0x3fc94030 0x40375309:0x3fc94050 0x4202050d:0x3fc94070 0x40375459:0x3fc94090 0x4037547e:0x3fc940b0 0x40378bf5:0x3fc940d0 0x420017a1:0x3fcebd80 0x420026ed:0x3fcebda0
16:10:10.407 -> 
16:10:10.407 -> 
16:10:10.407 -> 
16:10:10.407 -> 
16:10:10.407 -> ELF file SHA256: f0bf9890c310594c
16:10:10.407 -> 
16:10:10.407 -> Rebooting...
16:10:10.407 -> ESP-ROM:esp32s3-20210327
16:10:10.407 -> Build:Mar 27 2021
16:10:10.407 -> rst:0xc (RTC_SW_CPU_RST),boot:0x2b (SPI_FAST_FLASH_BOOT)
16:10:10.407 -> Saved PC:0x42020b5e
16:10:10.407 -> SPIWP:0xee
16:10:10.407 -> mode:DIO, clock div:1
16:10:10.407 -> load:0x3fce3808,len:0x44c
16:10:10.407 -> load:0x403c9700,len:0xbd8
16:10:10.407 -> load:0x403cc700,len:0x2a80
16:10:10.407 -> entry 0x403c98d0

SimpleReceiver.ino:

16:26:47.020 -> START C:\Users\A1\AppData\Local\Temp\arduino_modified_sketch_26321\SimpleReceiver.ino from Feb 26 2024
16:26:47.020 -> Using library version
16:26:47.020 -> abort() was called at PC 0x40378f7f on core 1
16:26:47.020 -> 
16:26:47.020 -> 
16:26:47.020 -> Backtrace: 0x40377b86:0x3fc93c50 0x4037b3fd:0x3fc93c70 0x40380d75:0x3fc93c90 0x40378f7f:0x3fc93d10 0x40379091:0x3fc93d40 0x40379160:0x3fc93d60 0x420194fe:0x3fc93d90 0x4201c525:0x3fc940a0 0x420244ad:0x3fc940d0 0x4200f562:0x3fc94100 0x4200f5f7:0x3fc94130 0x4200574d:0x3fc941b0 0x42005842:0x3fc941e0 0x42002921:0x3fc94250 0x420026a7:0x3fc942b0 0x420023ff:0x3fc94340 0x40375317:0x3fc94360 0x40375422:0x3fc94380 0x4037941f:0x3fc943a0 0x40375c2c:0x3fc943c0 0x40378ced:0x3fc943e0 0x400559dd:0x3fcebca0 |<-CORRUPTED
16:26:47.020 -> 
16:26:47.020 -> 
16:26:47.020 -> 
16:26:47.020 -> 
16:26:47.020 -> ELF file SHA256: 7f6af9ffed98f408
16:26:47.020 -> 
16:26:47.020 -> Rebooting...
16:26:47.020 -> ESP-ROM:esp32s3-20210327
16:26:47.020 -> Build:Mar 27 2021
16:26:47.020 -> rst:0xc (RTC_SW_CPU_RST),boot:0x2b (SPI_FAST_FLASH_BOOT)
16:26:47.020 -> Saved PC:0x4202317a
16:26:47.020 -> SPIWP:0xee
16:26:47.020 -> mode:DIO, clock div:1
16:26:47.020 -> load:0x3fce3808,len:0x44c
16:26:47.020 -> load:0x403c9700,len:0xbd8
16:26:47.020 -> load:0x403cc700,len:0x2a80
16:26:47.020 -> entry 0x403c98d0
16:26:47.627 -> 
16:26:47.627 -> abort() was called at PC 0x40378f7f on core 1
16:26:47.627 -> 

[ArminJo]

Sorry I cant reproduce it, I have no S3.
And BTW. ESP su...
More than 90 % of mysterious errors are on ESP platforms.

[sartyx]

Well yeah, that is also a way to solve issues. Nevermind I used a different lib already.