Bookworm 6.12.y for the uConsole and DevTerm

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/

Hello, I’ve been running the uConsole with this image, with a CM5, and the AIO board for some time, very successfully. I even upgraded to Trixie.

One of the last remaining issues is audio crackling when the voltage dips, even slightly. Seems it only doesn’t crackle when 100% or plugged in.

My guess is the CM5 is more power hungry, and a voltage drop somewhere is causing distortion.

Any clues or fixes found since last brought up? Even if hardware or power regulation improvements?

it usually cracks when charge below ~50%. could be you have weak batteries?

there is no other real solution than charge, insert headphone’s jack or CM5 speaker static got you down?

running the Trixie image on a DevTerm with CM5. Anyone have advice or a guide to get the printer working?

you should be able to do sudo apt install devterm-thermal-printer* and then add the printer in the gui printer software.

1 Like

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ā€.

I only see the axp221-adc under the iio tree.

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 ..

Yes and no. You can get the packages to upgrade to the version trixie runs but you won’t have any packages that were added or and tweaks to trixie.

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?

yes, it’s somehow uconsole motherboard’s power delivery fail.

now you can buy IO board and use CM5 as full size raspberry!

I don’t think you remember my issue.

I was using the Waveshare mini base board to flash emmc CM5. I was getting 4 blinking green lights on the base board.

Then I just bought a CM5 lite,

1 Like

Can someone please confirm if I can install this right now or do I need a new adapter board?

That CM will not work with this image. You’ll need the one compatible with the Radxa CM5.

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.

  1. Used rpiboot and the IO board to connect to CM5 as mass storage device.
  2. Used Raspberry Pi Imager to restore the Bootloader for Pi5 family
  3. Flashed @Rex image to the CM5
  4. 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.

thanks.

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.

1 Like

@chokereflex I was sort of in the same boat. You can fix it with rpiboot

  1. git clone --recurse-submodules --shallow-submodules --depth=1 https://github.com/raspberrypi/usbboot

  2. cd usbboot

  3. make INSTALL_PREFIX=/usr/local

  4. cd recovery

  5. ./update-pieeprom.sh

  6. cd..
    sudo rpiboot -d recovery

Now you should have a fixed EEPROM.

2 Likes

@Chad_Vavra Thanks, that helped!

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)

2 Likes

Any chance CM4104016 will work with this, too?