I am using a Verdin imx8mp on a custom carrier board and trying to get the display working. Currently I cannot see anything on the display and weston fails to launch. I managed to get the backlight working by customizing my devictree .dtsi like in this thread Imx8mm: mipi-dsi display with 1920x1200 .
The panel I’m using is Ortustech COM43H4N10ULC , for which I have a driver and which is working properly on a Colibri imx8qxp custom carrier board. The BSP version used is 6.3.0 Kirkstone.
The panel I’m using is Ortustech COM43H4N10ULC , for which I have a driver and which is working properly on a Colibri imx8qxp custom carrier board. The BSP version used is 6.3.0 Kirkstone.
Is the device tree used for the Colibri iMX8X similar to what you used for the Verdin iMX8M Mini?
Where exactly did you get the driver for your display? In the Downstream kernel used on BSP 6 I can’t find any references to its compatible field in the kernel devicetree documentation, only for other displays of the same manufacturer:
[linux/Documentation/devicetree/bindings]$ git status
On branch toradex_5.15-2.2.x-imx
Your branch is up to date with 'origin/toradex_5.15-2.2.x-imx'.
nothing to commit, working tree clean
[linux/Documentation/devicetree/bindings]$ grep -R ortustech,com43h4n10ulc
[linux/Documentation/devicetree/bindings]$ grep -R ortustech
display/panel/panel-simple.yaml: - ortustech,com37h3m05dtc
display/panel/panel-simple.yaml: - ortustech,com37h3m99dtc
display/panel/panel-simple.yaml: - ortustech,com43h4m85ulc
vendor-prefixes.yaml: "^ortustech,.*":
The driver is self written and based on Raydium rm67191 driver. Also, it is enabled in kernel config and loaded at the boot. I tried patching these files accordingly like you suggested, and actually Weston starts but there is still no image.
The driver is self written and based on Raydium rm67191 driver.
Given that you wrote the driver, it’s hard for us to tell exactly about the device tree bindings for it, as this depends on how your driver interprets it. If you based it on the Raydium rm67191 driver then its DT binding documentation in the kernel is probably the best resource you can look to make sure the bindings are correct.
Apologies for not answering, I’ve been off for a while.
Here is the driver file, panel-simple.c patch and panel definitions (as a collective .txt file for the purpose of this post). As for now, the com43h4n10ulc driver wont load, only imx_sec_dsim (dmesg | grep -i ortus returns nothing). If I comment out panel_desc_dsi com43h4n10ulc etc then the ortustech driver will load, although then also these imx_sec_dsim timeout errors pop up along with com43h4n10ulc backlight enable/disable failure messages (dmesg | grep -i ortus will return succeeded in all the other each steps). Regardless of what’s in panel-simple.c, only backlight is working but still no image even with Weston running.
