Did you try other pins? There's nothing locking I2C to 21/22, but maybe there's a problem with those connections on the board.

I did months ago, and confirmed the code worked as the changed pins worked on a diff board. Just didn't work on these two.

Just to "update". Still no luck, didn't touch it for months (sitting on my desk the whole time lol) and tried today with a fresh mindset, no change. My only thought left is maybe the charging circuit on the board is screwing with the I2C. But I have no interest in looking into that. Need to find a ...

Hey there, thanks for the reply. I've ran a few versions of a scanner now, including yours. Still can't read the I2C on the Lolin, but my other ESP32 works fine.

If I set the pins 21/22 to low/high every other second in their own code, they do correctly change, so it's not a misconfiguration of ...

Hello! Been a while. I'm currently working on an alarm clock, and I'm at my wits' end now.

Originally I was using a board that registered as Node32s in Arduino IDE. Like this one
https://www.aliexpress.com/item/1005005393681904.html?spm=a2g0o.order_list.order_list_main.17.347d1802p25W0k

Everything ...

Thanks for the spaghetti-code warning. I've seen people post worse while not seeing any problem with it...

My guess would be that the TFT code is not re-entrant, that is, you cannot have two tasks call something that writes to the TFT at the same time as the two calls will interfere.


I think ...

Alright. I'll start off by saying I'm sorry for the pain I will cause some of you. I know my code is gonna be painful for some of you, and there's a few incomplete parts, but what matters is it works... but now it doesn't, which is why I'm here.

I started off with an Arduino Mega and an TFT 9486 ...