Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESP32-C6-LCD-1.47 LDO overheat #10042

Open
peterzhenghj opened this issue Feb 8, 2025 · 3 comments
Open

ESP32-C6-LCD-1.47 LDO overheat #10042

peterzhenghj opened this issue Feb 8, 2025 · 3 comments
Labels

Comments

@peterzhenghj
Copy link

CircuitPython version and board name

Adafruit CircuitPython 9.2.4 on 2025-01-29; Waveshare ESP32-C6 LCD 1.47 with ESP32-C6FH4

Code/REPL

# NO code to run

Behavior

After the flash restart, I noticed that the area of the low dropout regulator (LDO) feels overheated when touched.
However, I only have one unit available, so I am not sure if this issue is unique to my device.
Interestingly, when I flash the factory images, there is no overheating situation.

Description

No response

Additional information

Waveshare product wiki

@kylefmohr
Copy link

I was able to recreate this (any excuse to use my thermal camera!) but I question whether this is specifically a CircuitPython issue, or if this more relates to the fact that Python is an interpreted language. I would theorize that you would see the same amount of heat if you created a program in C/C++/Arduino's language which was always running at 100%.

Nevertheless, here are the temps I found.

First with the factory image loaded, I saw it max out at about 107°F (~42°C), and the LCD capped out around 92°F (~33°C).

Image Image

Then once I flashed CircuitPython onto the device, it quickly climbed to 140°F (~60°C), as did the LCD screen.

Image Image

and after leaving it idle for a few hours (Just waiting at the REPL prompt for CircuitPython), the device was at about 160 F (71 C)

Image

Here's a video of the temperature climbing as the device is plugged into power

20250209-075540.mp4

But I will just say one more time, I don't think CircuitPython is to blame for this.

@tannewt
Copy link
Member

tannewt commented Feb 10, 2025

Please talk to Waveshare about this. Maybe there is some pin state that needs to be set in CircuitPython.

@peterzhenghj
Copy link
Author

Please talk to Waveshare about this. Maybe there is some pin state that needs to be set in CircuitPython.

Yes I will, thank you sir.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants