Just had this problem. The default config.txt is configured for the uconsole and not the devterm. If you modify the config.txt to comment out the uconsole line and uncomment the devterm line for your pi model (pi5 for my cm5), it will boot in the correct orientation.
I was using the full trixie image and had already gone through the initial setup upside down. When I rebooted after making the changes to config.txt, the bootloader and kernel where in the correct orientation but the desktop was sideways. I had to go to menuāpreferencesā control centre ā screens ā right click on dsi-2 ā orientation ā right ā apply to get it properly oriented. I used the keyboard and tab to āguessā where apply was as it was offscreen/
Thanks Rex, thatās what I thought but I just canāt get it working. I had it working with the A06 and the stock OS. Iāve installed both packages. The -cups package adds the device to the command centre gui, the -cm4 package installs but fails to start the devterm-socat service. Looking at the /usr/local/bin/devgterm-socat.sh launched by the service, it seems the service is looking for an adc101c device in /sys/bus/iio/devices/iio:device* and fails when none is found with āadc node errā.
hi Rex, is there an easy way to upgrade to trixie from your bookworm image, without losing stuff ?
got a bunch of installations and configuration on my uconsole, wouldnt want tot start over ..
My solution was just to buy another CM5 along with the correct power supply from RPI. I thought I had fried the other boards by using other power supplies. Does this now mean those boards are still working fine?
Hey @Rex and @backer954 . Could use some help with my CM5 build.
I picked up a CM5 and IO board yesterday to upgrade my Uconsole and Iāve tried numerous times, including following @backer954ās post with no luck. Here is where Iām at.
Used rpiboot and the IO board to connect to CM5 as mass storage device.
Used Raspberry Pi Imager to restore the Bootloader for Pi5 family
Removed eMMC jumper from IO board and powered on with external screen on HDMI0. (No Signal)
I also flashed the same image from Rex to a SD card and installed both the SD card and CM5 in my console. Green light, no screen, no backlight.
Iām certain Iām missing a simple step to update the EEPROM or Firmware or SD card issue - but canāt for the life of me figure it out. Any suggestions would be greatly appreciated.
edit: I did just notice that the CM5 is not āliteā. it has 32G of eMMC.
I think I broke my EEPROM. Did this on a CM4 and broke it; now I get āFailed to open partitionā errors. Any ideas if I can still fix this?
I ran this
Check using vcgencmd version to update sudo rpi-eeprom-update sudo rpi-eeprom-config -e To edit the eeprom.
backup current config, then replace with:
[all]
BOOT_UART=1
# Switch off PMIC outputs on HALT
POWER_OFF_ON_HALT=1
# Default BOOT_ORDER for provisioning
# SD -> NVMe -> USB -> Network
BOOT_ORDER=0xf461
# Try boot on SDCard repeatly
SD_BOOT_MAX_RETRIES=2
# Slow down SDCard SDR Mode on bootloader
SD_QUIRKS=1
Those instructions were for the CM5 lite only. Thereās nothing you need to do to the eeprom with the CM4. You can hopefully reflash the bootloader to fix it. You can make a SD to reflash the bootloader and eeprom from within raspberry pi imager.
FIXED!
For those that may have a similar issue. It was a corrupted EEPROM. The step that seems to be skipped in all the online answers is running ./update-pieeprom.sh in the recovery5 folder before sudo rpiboot -d recovery.
Once youāve had success with that itās smooth sailing - and Iāve even upgraded to Dragon OS and have it working on my uConsole / CM5 4G/32G. (not lite)