MIPI Display Support

Sure @le51. May be there is simpler way of doing that, if yes I would like to know.
I am also thinking about releasing prebuilt image with these changes. Here is what I did and the reasoning behind it.

  1. kernel should have needed drivers/modules to run the hardware.
    I am building armbian image using their builder. There I enable few modules.
    CONFIG_DRM_PANEL_RADXA_DISPLAY_8HD=y
    CONFIG_DRM_PANEL_JADARD_JD9365DA_H3=y
    Why these modules? These where enabled in debian/ubuntu from Radxa where display is working. I have additional modules added but these two I added for monitor. After armbian builds image. If the default modules are enough please somebody fix my mistake.

  2. you need to tell the system that it has this hardware (screen/ may be camera) attached.
    For attachable detachable hardware like screen, camera ,… dtoverlay (device tree overlay) is used.

  • For radxa debian you add into /boot/config.txt the line dtoverlay=rock-5b-radxa-display-10hd as you can check from https://wiki.radxa.com/Rock5/accessories/radxa-display-10hd
  • For armbian you add into /boot/armbianEnv.txt the line overlays=radxa-display-10hd. Note in the current distro another value is wrong and you need to change it, that shoul be overlay_prefix=rock-5b , by default the value was different and it was wrong. The reasoning here is like this. System joins values of these fields to generate a file name.
    overlay_prefix+overlays => "rock-5b" + "radxa-display-10hd" => "rock-5b-radxa-display-10hd"
    and tries to find that file inside directory /boot/dtb-5.10 bla bla/rockchip/overlay/ . You can navigate there and check yourself. After restart it should ideally work. Be careful it may not boot if something is wrong. In that case put your sd card into another computer, open the armbianEnv.txt and remove the overlays= line. I used this page as source https://docs.armbian.com/User-Guide_Allwinner_overlays/

If you want just the image that works for me I can upload it. Then you download and write it to sdcard.

3 Likes

Did you manage to use that display? Is its connector compatible?

You like a knowledgable fellow. Can you please help me out. Boot Screen Orientation - ROCK 5 Series - Radxa Forum

Thank you very much @tsadigov
I will give it a try next week, because I’m on vacation right now.

Cheers

Enjoy vacation. If you try it please let me know your results. If you need the image I have built I can upload. If you can map these steps to an easier way of achieveing the same thing, I would be happy to learn from you.

@jack I see the developments in repo
Will they be released on soon? Or should I try building to try it?

I did rebuild the image and I have visuals for Android on the 10 inch screen, currently the orientation is wrong for me, trying to find the right knob

Update:

Everything worked at last. Here is a video.
MIPI 10" screen with Android - ROCK 5 Series - Radxa Forum

1 Like

I’m wondering if the PI TFT70 will work too. AFAIK this works with the ROCK 4 SE but is there anyone who can confirm that it’s been ported to the ROCK 5 series too? It uses the basic same drivers as the Raspberry Pi 7 inch touchscreen

I wonder if that worked for you

1 Like

Hi
using apt install -y linux-5.10-rock-5-latest to upgrade de kernel to version 5.10.110-30-rockchip
is say that the kernel is already the newest version (5.10.66.-27-rockchip)
is there any way to force upgrade to version 5.10.110-30-rockchip?
regards

Try this

$ sudo apt update -y
$ sudo apt install -y linux-5.10-rock-5-latest

I have a similar issue. I ordered the Radxa Display 8HD (Rock 5B Model) but the mounting holes don’t match the 5B Board and having updated the kernel and /boot/config.txt and used the update script I still get nothing displayed.

I suspect I was sent the wrong Model but I cannot find out how to tell the difference. The screen I got won’t work with the driver setup as I suspect the MIPI interface is different on the 5A model.

I’ve vlogged the problems on youtube: https://youtu.be/vgrrnY77juM

Please help. I think there’s a screenshot of the product code in the video and I suspect that the ‘A’ at the end of it means that it’s the Rock 5A variant.

Hi mate, on most of the current oses available, by enabling the overlays, I am able to get display outputs(by editing the env.txt file), but no touch in all of the oses except for radxa official builds, how do I enable touch for the other OS?

did you manage to get the touch working?

I am currently consentrated on something else so cant provide you details, but I am sure I was using touch out of the box

Has anyone made the Radxa HD 10 touch screen work on Rock5B with Joshua Riek’s Ubuntu Rockchip images? Ubuntu Rockchip (joshua-riek.github.io)

Specifically I tried with Ubuntu 22.04.3 Desktop image from that page. When I have the display connected to the Rock5B via the MIPI cable and power the Rock5B on I get nothing. No light on the display, no image, nothing.

Hey,i just got the 8 HD display,with rock 5 under android,the display Shows nothing!How can i fix this?

What kernel driver does the touch functionality on the Display 10 FHD use? Does it use the gt9xx driver and is support for that device yet added to the 5.10 or 6.1 kernels?


Joshua Riek has managed to get the Display 8 HD working, with touch support, on his Ubuntu Rock5B images. I have verified that the display portion of the Display 10 FHD also works in his Ubuntu images.

However we’re having trouble getting touch to work on the Display 10 FHD and are wondering if it has even been supported in the Radxa kernels yet.

Trying to get this to work on Armbian:

editing /boot/armbianEnv.txt
I addded overlays=rock-5b-radxa-display-10hd

The screen does not turn on.
running
dmesg | grep -i "mipi\|dsi\|display" |grep ERROR
I get

[    5.467757] dw-mipi-dsi2 fde30000.dsi: [drm:dw_mipi_dsi2_bind] *ERROR* Failed to find panel or bridge: -517
[    5.473341] jadard-jd9365da fde30000.dsi.0: [drm:jadard_dsi_probe] *ERROR* failed to get vccio regulator
[    7.257058] dw-mipi-dsi2 fde30000.dsi: [drm:dw_mipi_dsi2_bind] *ERROR* Failed to find panel or bridge: -517 ```

Any idea how to solve this? no idea where to start?