Luckfox Omni3576 Boot Failure and Touchscreen Malfunction with Waveshare 70H-1024600

2026-03-25 9:09

Hi everyone,

I am working with the Luckfox Omni3576 and trying to integrate the Waveshare 70H-1024600 (7-inch HDMI/DSI, 1024x600) display. I am encountering two specific issues that I hope the community can help with:

1. Boot Failure (Cold Boot)
When the Waveshare 70H-1024600 is connected during power-on, the Luckfox Omni3576 fails to boot. The system hangs before reaching the OS.

Observation: If I boot the device with a different monitor and then hot-plug the Waveshare screen, the display works, but this is not a viable solution for my application.

Question: Is there a known timing issue or power draw spike during the handshake that might be causing the bootloader (U-Boot) to hang?

2. Touchscreen Not Working
Even when I manage to get the display working (via the hot-plug method mentioned above), the touch functionality is completely unresponsive.

The screen is connected via HDMI and USB-TYPE-C cable for touch.

The system does not seem to initialize the HID-multitouch driver or the specific I2C driver required for this panel.

Hardware/Software Environment:
SBC: Luckfox Omni3576

Display: Waveshare 70H-1024600 (Resolution: 1024x600)

OS/Image: Debian 12 builded from sdk

Power Supply: 5V/3A

What I’ve Tried:
Tested with other HDMI/DSI monitors: Boots successfully.

Power cycling the display separately from the SBC.

Checking dmesg logs (though difficult when the boot hangs).

Has anyone successfully configured the device tree (.dts) or modified the boot configuration for this specific Luckfox/Waveshare combination? Any guidance on getting the touch drivers recognized would be greatly appreciated.

Thanks in advance!

2026-03-28 3:36

Due to the wide variety of HDMI display devices, 1024×600 is not a standard HDMI resolution (i.e., it is not defined in CEA/VESA standard timings). Therefore, this resolution is not included by default in the Rockchip SDK, and the system cannot automatically recognize or configure it during boot.

Based on test results, the display works correctly after manual configuration, which indicates that the hardware link is functioning properly. The issue mainly lies in the fact that the system does not include this resolution as a built-in default display mode.

We have reported this issue to the engineering team for evaluation and potential optimization (such as adding default timing support or improving compatibility). However, since this involves low-level driver modifications, the fix may take some time.

Temporary Solution

At this stage, it is recommended to dynamically add the resolution during system startup using xrandr:

export DISPLAY=:0
xrandr --newmode "1024x600_test" 49.00 1024 1072 1168 1312 600 603 613 624 -hsync +vsync
xrandr --addmode HDMI-1 "1024x600_test"
xrandr --output HDMI-1 --mode "1024x600_test"

This method has been verified to provide stable display output and is recommended as a temporary workaround at the current stage.

Additional Note

If touch functionality is required, please ensure that DSI is disabled; otherwise, touch input may not function properly.