Bookworm 6.12.y for the uConsole and DevTerm

you could find some small working card.

Raspberry released cm5 in quite strange state: buggy firmware and without audio drivers, they added drivers like 1-2 months after release

Many thanks. It’s all beginning to come back to me :slight_smile: Including Vi (scary). Anyway, the config.txt section for the CM4 didn’t turn rtc on, so added that line. Also removed the line turning it off in the CM5 section so when I swap between my CM4 and CM5, that should now work.

Have checked sudo hwclock -r after reoot and it’s now showing correct time.

Thanks again everyone :slight_smile:

Did you restart after you installed the package and before you tried writing to the hardware clock?

The package sets everything up the way it should. RTC off in the config.txt under the cm5 is because the cm5 has a built-in RTC that you just need to apply battery voltage too. So RTC off turns off that one so you can use the one on the AIO card.

Anything you changed in the config.txt could have the pi reading the fake hardware clock when you boot that’s why you’re seeing something now.

I flashed the firmware using the waveshare mini base board and raspberry pi imager.

I get a green light for a few seconds and the screen flashes but then it cuts out and the light goes red every time I press the power button.

Can the CM5 boot up like this or do I need to wait for the UConsole?

If you’re using one of my images on a regular pi or in your case an IO board. Then you just need to comment out the one line in the pi5 section in the config.txt that says uConsole. TTY will be rotated 90° though unless you remove fbcon=rotate:1 from the cmdline.txt. just make sure you uncomment that line in the config.txt and redo that line in cmdline.txt before you put it in your uConsole.

Yes I’m using your image - 6.12.

I don’t really want to mess around with it; I’ll wait for the UConsole.

To be honest, I’ve also got the CM5 lite. I’m going to flash a card tomorrow and do the edits you’ve mentioned and see if it works.

Thanks.

1 Like

If I use the eMMC version, can I still use an sd card in the UConsole for storage?

Ideally, I want the OS and other software on the eMMC and data on an sd card.

Nope that lanes for the SD card are used by the EMMC. It’s one or the other.

1 Like

I hope you will wait less than 5 months!

2 Likes

I just realised I received the wrong order for the CM5 - with no wireless.

Is this going to be a problem?

The lite has wireless but I really want to use the eMMC version.

it’s no problem if you don’t need wireless or have a supported dongle. me personally like the lite better, you don’t need to pull to CM out if you need to reflash or try something. I use mine for work and keep a already setup image on a spare sd in case something happens while i’m in the field.

I see the UConsole’s little board on the side has a connector to plug in the WiFi antenna and the community has been using this instead of plugging the antenna into the CM5 itself for better results. Could I use this if I used the eMMC version?

I’m now leaning towards using the lite to be honest. At least this way, I can use different OSs like Kali and have storage up to 256GB. Am I on the right path?

The wifi on the main board is for the CM3 or the Clockwork CMs. The CM4&5 physically don’t connect to it so it can’t be used. Like I said I’d personally go for the lite, it makes life a lot easier in the long run.

3 Likes

I’m going to use the lite. I’m going to flash a card right now, do the edits to config.txt you mentioned before and see if it boots up using the waveshare mini base board.

Will update in a little while.

Thank you.

1 Like

you can glue all it inside of a shoe box and named it ā€˜deci-Console’

1 Like

It just will not boot.

I flashed the card using Raspberry Pi Imager - ClockworkPi-Bookworm-6.12.40.img

I changed cmdline.txt to:
console=serial0,115200 console=tty1 root=PARTUUID=545e8bc9-02 rootfstype=ext4 fsck.repair=yes rootwait quiet psi=1 splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=GB systemd.run=/boot/firstrun.sh systemd.run_success_action=reboot systemd.unit=kernel-command-line.target

I think the cmdline.txt file has changed after trying to tboot up

I changed the config.txt file Pi5 section to:
[pi5]
#dtoverlay=clockworkpi-devterm-cm5
#dtoverlay=clockworkpi-uconsole-cm5
dtoverlay=vc4-kms-v3d-pi5,cma-384
dtparam=pciex1=off
dtparam=uart0

I pressed the power button on the waveshare base board a few times but it cuts out and goes red after 3/4 seconds.

I don’t know what else to do.

no offense, but is there any particular reason why you want to use uconsole image?

why not to flash regular raspberry pi debian and use till you wait for your uconsole (3+ months)

the only negative side that you’ll have to flash a fresh image later, but you wiull be able to copy your user files.

otherwise debian is a debian.

1 Like

I’m only doing this to ensure the image is working and the card is done right ready for the UConsole.

I’m flashing the official Raspberry Pi OS image to the card right now to check if it boots up correctly.

Will update shortly.

Official OS is working totally fine with saved settings for WiFi. It connected to the internet instantly.

What am I doing wrong with Rex’s image? Should I not save personal settings such as host name and WiFi settings?