Raspberry Pi 5 - Lite 64bit - Stuck on default utronics screen

[arnstarn]

Using a Raspberry Pi 5 and the official 500gb NVME ssd drive along with the following Uctronics components

• UCTRONICS PoE Hat for Raspberry Pi 5, Power Over Ethernet HAT for Raspberry Pi 4B/3B+, Support 802.3af PoE Network Standard with Heatsinks and Onboard Cooling Fan

Useing the 19" 1U Rack Pro for RPi 5 - SKU:RM0013 - https://core-electronics.com.au/attachments/localcontent/RM0013-Assembly-Guide_280483831c7.pdf

Installed Raspbian Lite - 64bit (Also updated all apt components)
Ensured ARM I2C is enabled in raspi-config.

git clone https://github.com/UCTRONICS/SKU_RM0004.git
cd SKU_RM0004 make
./deployment_service.sh
sudo reboot

I get no errors, but the default "UCTRONICS" display stays frozen. Toggling power button does start/shutdown the PI and the display but the screen does not change beyodn the default screen.

Contents of /boot/firmware/config.txt

# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on,i2c_arm_baudrate=400000
#dtparam=i2s=on
#dtparam=spi=on

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Additional overlays and parameters are documented
# /boot/firmware/overlays/README

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Automatically load initramfs files, if found
auto_initramfs=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Run in 64-bit mode
arm_64bit=1

# Disable compensation for displays with overscan
disable_overscan=1

# Run as fast as firmware / board allows
arm_boost=1

[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1

[cm5]
dtoverlay=dwc2,dr_mode=host

[all]
dtoverlay=gpio-shutdown,gpio_pin=4,active_low=1,gpio_pull=up,debounce=1000
dtparam=pciex1_gen=3

[Yabbo]

same issue.

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org

[BerserkeR-Git]

Try to add these to /etc/modules

i2c-dev
i2c-bcm2835
spi-bcm2835
snd-bcm2835

and reboot the Pi and give it a moment.

I also included all of these in my /boot/firmware/config.txt

dtparam=i2c_arm=on,i2c_arm_baudrate=400000
dtparam=i2s=on
dtparam=spi=on

@arnstarn @Yabbo

[Yabbo]

turns out its an under power issue. once i removed the power button it works fine. I do get messages for under power voltage if i have the power and display plugged in.

[BerserkeR-Git]

No issues here with that with a Waveshare PoE HAT (F) and this line in /boot/firmware/config.txt
psu_max_current=5000

[BerserkeR-Git]

I'm getting no display now, just looks like the ''backlight'' is on but I had display before. What a wonderful product and support from these guys.

[BerserkeR-Git]

I cloned my NVMe SSD with dd from my first Pi to another NVMe SSD and put it in my second Pi, so exact same data as the first drive, and that display just lights up right away. So this whole issue is very inconsistent, people warned me this would be a low quality product for the amount of money paid and then we don't even get shit like this fixed. $300 for thin stamped metal.

[Yabbo]

Given there are no other products on the market like this Im not upset about the price or the quality. I think there needs to be some revision done to the board in some way. Even with psu_max_current=5000 if i have both the LCD and Power button plugged in i get notices of under power in my cli. I think something is just drawing more power then it needs. have 4 Pi5 16Gb models running in this rack with a POE+ Hat on them. they all run fine if i unplug the power button. Im happy with how this functions as i would never use the power button in my scenario.

[BerserkeR-Git]

So, my secondary Pi has a working display – it lights up quickly, you get the little initialization flicker, and then the UCTRONICS logo pops up as expected. Interestingly, this secondary Pi is running off a byte-for-byte cloned NVMe drive from the primary Pi, so the software is identical.

I tried a few things:

First, I swapped the Waveshare PoE HATs between the two Pis. The second Pi still worked fine, still nothing on the primary Pi so it’s not a PoE HAT issue, for me.

Then I took the M.2 drive and moved it to a completely different NVMe board, and right away, the screen came right to life. It instantly went through the usual initialization and showed the UCTRONICS logo without any hesitation.

Meanwhile, the original setup – even when I swap parts around – just gives me a faint backlight, no logo, no initialization, nothing. At this point, it really seems like that NVMe board or the screen itself is just defective.

Hopefully, UCTRONICS can send a couple of replacement parts rather than making me send the whole thing back, but we’ll see how that goes.

Edit; obviously after the UCTRONICS logo I'd get the pages it cycles through, let that be clear. I have two working displays now and at least 1 seems to be defective.

[piwi1263]

Also my RM0013 is displaying ONLY the UCTRONICS @ startup and stays. No cycling thru anything as with my RM0004.

Added the above lines to /etc/modules but no changes yet.

What wonders me is the emptiness of sudo i2cdetect -y 1 resulting in the following:

Any idea, tip or trick.

TIA.

[ingo916]

Same issue here with a clean install of Raspberry pi OS on rpi5 with intel nvme and no poe

[piwi1263]

Does anyone have the wiring of the 6-wired display connector ?

I take it that red could be VCC and black could be GND, but the does anybody know about the yellow, green, blue and white?

TIA.

[StriteskyPetr]

I am sorry for what may be a bit of offtopic, but since we are speaking about the default UCTRONICS screen:

Is there a way of re-programming the boot logo? It seems to be pre-loaded in the LCD unit itself.

[Pentacle-dev]

The LCD driver IC (ST773) is driven by an MCU (STM8S003F3) on the baseboard (UC-906). The MCU is effectively acting as a proxy between the RPI and LCD driver's SPI & I2C interfaces. The MCU is running something... Only Uctronics knows exactly what the software is doing...

Have been probing the OLED connector and pinout is as follows:
R(1) = RPI's GND
BLK(2) = STM8's VDD
Y(3) = STM8's SPI CLK
G(4) = STM8's SPI MOSI
B(5) = STM8's PD2
W(6) = STM8's PD3

Note the power wire colors, really inspires confidence in the quality of Uctronic's products...
I suspect that one of the PDx lines is an enable, and the other possibly being a reset.

Given that it was previously working for me with a RPI 4B, and the issues seem to be exclusively with RPI5, it would suggest that there is a difference in the I2C interaction between the RPI & STM8 MCU.

Can't debug further at this stage as I've not got a logic analyzer, or a RPI 4B to compare.

[Pentacle-dev]

I am sorry for what may be a bit of offtopic, but since we are speaking about the default UCTRONICS screen:

Is there a way of re-programming the boot logo? It seems to be pre-loaded in the LCD unit itself.

The ST773 driver has onboard EEPROM which can be used to store a default screen/state, however, we have no idea what the proxy MCU is doing at boot. It could potentially be writing it's own Uctronic default screen to EEPROM at boot, in which case you would have to wait until the RPI has booted to run your own application which replaces the default Uctronic logo.

[Pentacle-dev]

Also my RM0013 is displaying ONLY the UCTRONICS @ startup and stays. No cycling thru anything as with my RM0004.

Added the above lines to /etc/modules but no changes yet.

What wonders me is the emptiness of sudo i2cdetect -y 1 resulting in the following:

Any idea, tip or trick.

TIA.

Has anyone got it working on another device? If so are they able to run the i2cdetect command above to confirm if the STM8 MCU even shows up when the LCD is working?