# uConsole died after a few hours **URL:** \ **Category:** uConsole\ **Tags:** help\ **Created:** [July 17, 2024, 8:23pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985 "2024-07-17T20:23:03Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Tylerb](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/tylerb/32/9955_2.png) [@Tylerb](https://forum.clockworkpi.com/u/Tylerb)\ **Post date:** [July 17, 2024, 8:23pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/1 "2024-07-17T20:23:03Z")
So I just got my uConsole and I’m struggling to get it to boot properly. I’m using a CM4 with EMMC which I flashed using a different carrier board via USB. This worked great for a few hours and a few reboots until I tried to power up this morning. Right after boot, the speakers let out a short low beep and the screen froze with a lot tearing and glitching. When this fault occurred, it was on battery and usb c power. I shut it down again and tried to reboot but the screen only flashed for a second and then nothing. I’ve tried reimaging the pi, reseating every connector and booting without battery. Every time I try, I just get a brief screen flash. Any ideas? Right now I’m thinking it may be a hardware failure, but I’m going to try to redownload the image in case it was corrupted somehow. Thanks! ---
**Author:** ![Tylerb](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/tylerb/32/9955_2.png) [@Tylerb](https://forum.clockworkpi.com/u/Tylerb)\ **Post date:** [July 17, 2024, 10:47pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/2 "2024-07-17T22:47:31Z")
Just to add, I tried redownloading the image as well as the lite/xfce version and still just getting a screen flash and no boot. I’m starting to think either my pi or the uconsole main board is dead. ---
**Author:** ![mterencelao](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mterencelao/32/9066_2.png) [@mterencelao](https://forum.clockworkpi.com/u/mterencelao)\ **Post date:** [July 18, 2024, 2:55am UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/3 "2024-07-18T02:55:59Z")
You do know that this forum warns you if your topic is related to one posted earlier? You’re not helping this forum by making your question stand out. **This isn’t Reddit.** Anyway, based on the details you provided, I’m starting to think your main board is at fault. Why will the CM4 allow you to flash an image to its eMMC if it is compromised? There should be a green LED next to the power button. If it doesn’t stay on, it’s gotta be a problem with the main board. Check for loose or missing parts. E-mail [help@clockworkpi.com](mailto:help@clockworkpi.com) right away. ---
**Author:** ![Tylerb](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/tylerb/32/9955_2.png) [@Tylerb](https://forum.clockworkpi.com/u/Tylerb)\ **Post date:** [July 19, 2024, 8:49pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/4 "2024-07-19T20:49:35Z")
> [@mterencelao](#): > > You do know that this forum warns you if your topic is related to one posted earlier? You’re not helping this forum by making your question stand out. **This isn’t Reddit.** Sorry about the topic, my intention wasn’t to click bait. When posting, I didn’t see any topic that related to others. Lots of “unable to boot” but no “booted fine a few times then stopped working”. I’ll be sure to be mindful of this in the future. > [@mterencelao](#): > > Anyway, based on the details you provided, I’m starting to think your main board is at fault. Why will the CM4 allow you to flash an image to its eMMC if it is compromised? I won’t pretend to understand the USB EMMC flashing mechanism on the CM4. However I anticipate it could be possible that the firmware responsible for this may be functional while something else is compromised that prevents the pi from completely booting. I have attempted to boot on a carrier board with standard pi images with no luck. I did only try this briefly so I’ll have to look further into it. > [@mterencelao](#): > > There should be a green LED next to the power button. If it doesn’t stay on, it’s gotta be a problem with the main board. The power led stays on without issue. I’ve reached out to the help email and am awaiting response. Any idea what the process is if the main board is at fault? ---
**Author:** ![mterencelao](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mterencelao/32/9066_2.png) [@mterencelao](https://forum.clockworkpi.com/u/mterencelao)\ **Post date:** [July 20, 2024, 2:32am UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/5 "2024-07-20T02:32:57Z")
> [@Tylerb](#): > > The power led stays on without issue. I’ve reached out to the help email and am awaiting response. > Any idea what the process is if the main board is at fault? This is a game changer. Perhaps there’s something wrong with the eMMC. You’ve also mentioned your uConsole was fine for a couple runs before the incident. How old is your CM4? Has it been used for disk I/O intensive workloads? You may need to plug in your uConsole to an external monitor to see what’s wrong. It would also be great if you have a spare CM4 to test if the mainboard really is at fault. > [@Tylerb](#): > > I have attempted to boot on a carrier board with standard pi images with no luck. I did only try this briefly so I’ll have to look further into it. OK, now that sounds like a problem with the CM4. ---
**Author:** ![Tylerb](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/tylerb/32/9955_2.png) [@Tylerb](https://forum.clockworkpi.com/u/Tylerb)\ **Post date:** [July 20, 2024, 5:38pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/6 "2024-07-20T17:38:16Z")
The CM4 I was using was used for a few other projects and had a good amount of read and write cycles on the emmc. I ordered a CM4 lite and sd card to test with. After some discussion with support, they suspect it’s the main board. They’re sending me a replacement so later this week I should have a better idea of what went wrong. ---
**Author:** ![Tylerb](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/tylerb/32/9955_2.png) [@Tylerb](https://forum.clockworkpi.com/u/Tylerb)\ **Post date:** [July 24, 2024, 2:17am UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/7 "2024-07-24T02:17:53Z")
Turns out the CM4 died. Got a replacement CM4 lite today and it booted no problem with an SD card. Thanks for the help! ---
**Author:** ![mterencelao](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mterencelao/32/9066_2.png) [@mterencelao](https://forum.clockworkpi.com/u/mterencelao)\ **Post date:** [July 24, 2024, 5:29am UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/8 "2024-07-24T05:29:32Z")
And now I know why a CM4 with built-in storage can become a disaster. Thanks for the tip. ---
**Author:** ![d0ktamo](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@d0ktamo](https://forum.clockworkpi.com/u/d0ktamo)\ **Post date:** [September 13, 2025, 3:04am UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/9 "2025-09-13T03:04:14Z")
Reviving this conversation because I’m having a similar issue… Today, I assembled a new uConsole with a CM5-108000 (RK3588S) compute module. On the very first power-on, the system booted immediately from the microSD card and appeared to operate normally. I then performed a clean shutdown. When I attempted to restart the device, however, it failed to boot. The power LED glows steady green and the SoC becomes moderately warm, which indicates that it is drawing power and showing some partial activity. The LCD remains completely dark, with no backlight at any point, and the system does not respond to a USB keyboard test. Even after waiting more than a minute, the Caps Lock LED never toggles. To troubleshoot, I first confirmed that power is not the issue. The battery is around fifty percent charged and I also tested with a reliable 5V/3A USB-C supply. I forced a complete shutdown by holding the power button for twenty seconds, disconnected power, and then reconnected everything, but this made no difference. I then turned to the microSD card. I replaced the original card with a brand-new Samsung card, reflashed it with a fresh copy of the stock image, and tested again. The problem persisted. I next checked connections. I reseated the LCD ribbon cable several times, making sure it was firmly locked, and I also removed the CM5 module, inspected the contacts for damage or debris, and reseated it carefully. Nothing changed. I tried booting both with the LCD connected and disconnected, but in either case the system behavior was identical. With no mini-HDMI cable available I have not yet been able to test external video, but attaching a USB keyboard produces no activity, suggesting the device is not reaching an operating system. The SoC does warm up slightly, though not as much as it did when Linux was actually running, which suggests it is powering but hanging before it can initialize the display or load the operating system. Because the CM5 does not rely on an external EEPROM, this seems to indicate that the boot ROM inside the SoC is failing to load properly from the microSD. I am interested to know if others have seen a similar failure mode with the CM5, where the unit boots successfully once and then will not boot again. Could this be explained by a fault in the carrier board’s SD interface, or does it point more likely to an early failure in the CM5 module itself? Also, should the CM5 at least power the LCD backlight even without a valid operating system present? I’m feeling stuck on this one… ---
**Author:** ![Rex](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/rex/32/16852_2.png) [@Rex](https://forum.clockworkpi.com/u/Rex)\ **Post date:** [September 13, 2025, 3:16am UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/10 "2025-09-13T03:16:05Z")
First are you using a RPi CM5-2712 or a Radxa CM5-RK3588S big difference on what it could be. If it’s the RPi CM5 then when you had it booted the first time you needed to edit the EEPROM to the settings outlined here. It’s the first thing you should do next time you get it booted. > [@EEPROM config and the CM5 lite](https://forum.clockworkpi.com/t/eeprom-config-and-cm5-lite/19649): > > With the upcoming release of NVME capable adapter boards from @vileer & @lululvlv I have changed up the EEPROM config to be able to use them. If you have a CM5 lite and are having problems with the sd card booting or have already updated the config but plan on getting a NVMe board. You need to edit your EEPROM and your CM5 lite has to have updated firmware that was released after 2025-01-06. Check using vcgencmd version to update sudo rpi-eeprom-update sudo rpi-eeprom-config -e To edit the eep… To try and get it working again, remove the batteries it makes shutting down a failed boot easier. You cannot shut the device down by the power button on a failed boot. You need to just pull power. Try smaller SD cards and a few different ones. Once you apply the EEPROM settings change then any SD card will work. ---
**Author:** ![sharpwizard](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@sharpwizard](https://forum.clockworkpi.com/u/sharpwizard)\ **Post date:** [September 13, 2025, 6:41pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/11 "2025-09-13T18:41:12Z")
I started with a stock CM4 running Bookwork and it was very stable. I replaced with CM5 and latest Bookworm (as of 2 weeks ago) and even with the recommended config fixes, it was ultra unstable. Even with low temps, it would boot but within a minute or two, just hard crash / power off. I then tried it all with Trixie and it is much more stable - as long as I don’t push it very hard. 34C idle and it’s fine. 40-45C doing moderate things, its probably stable for hours but may hard crash in a day. If I use Handbrake to convert a video and temps go up to 45-50C, it will probably hard crash. When replacing the CM5 I followed another thread here’s advice and have a thermal pad and heat sink. But that said, shouldn’t the CM5 just throttle down and not just crash constantly when any kind of non trivial use is going on? ---
**Author:** ![Rex](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/rex/32/16852_2.png) [@Rex](https://forum.clockworkpi.com/u/Rex)\ **Post date:** [September 13, 2025, 6:49pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/12 "2025-09-13T18:49:04Z")
are you on battery or mains power when this happens? i can push the cm5 hard and get it upto 62c with a m.2 heatsink on the back but it won’t crash or power off as long as my battery isn’t low. it won’t even thermal throttle. ---
**Author:** ![d0ktamo](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@d0ktamo](https://forum.clockworkpi.com/u/d0ktamo)\ **Post date:** [September 13, 2025, 7:58pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/13 "2025-09-13T19:58:37Z")
After battling this all night long, with at least 5 complete tear down and rebuilds, the CM5 snapped into the carrier board a bit more snugly. _Et voila_. It works. What amazing side adventures I took to fix a bad connection. The misadventure, illustrated: [xkcd: Repairs](https://xkcd.com/1994/) ---
**Author:** ![sharpwizard](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@sharpwizard](https://forum.clockworkpi.com/u/sharpwizard)\ **Post date:** [September 13, 2025, 10:15pm UTC](https://forum.clockworkpi.com/t/uconsole-died-after-a-few-hours/13985/14 "2025-09-13T22:15:47Z")
Mains most all the time, though the hard crashes don’t seem to correlate to main or battery. It happens on both.