E43GB-I-MW1000-N on Verdin IMX95

Technical Support
1

I’m working on a dual head display with a dual LVDS interface and a DSI screen. I’m able to get the dual LVDS JDI screen working in conjunction with the 10.1” Toradex/Riverdi DSI screen (which internally uses a DSI to LVDS bridge), but am now trying to transition the DSI interface to drive the Focus E43GB-I-MW1000-N which is our target form factor. I have used the parameters from the FOCUS supplied STM32 init to modify the panel-ili9608e.c driver from the raspberry pi kernel and updated the dts file appropriately. I’m able to get the backlight up and going and Linux seems to think everything is all good as far as the DTS file, but I don’t seem to get any pixels up and going. I can supply the DTS file, FOCUS supplied STM32 init file and updated driver as appropriate.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I’d be glad to help with your dual-head display configuration on the Verdin iMX95! To provide the most accurate guidance for your Focus E43GB-I-MW1000-N display integration, could you let me know which OS and version you are running? (1)

Common platforms to consider:

  • Hardware: Verdin iMX95, Ivy Carrier Board, Ixora Carrier Board, Mallow Carrier Board
  • Operating System: Yocto 7.2.0, Torizon OS 6, BSP 7, Torizon OS 7.2.0-build.13
  • Implementation: Device tree overlays, display drivers, DSI configuration

You can also use the tdx-info command to get detailed information about your system configuration. More details are available at tdx-info documentation. (1)

Once I know your specific platform setup, I can provide targeted guidance for:

  • Verifying your device tree overlay configuration for the dual-head setup (1) (2)
  • Reviewing DSI timing parameters and panel driver modifications (3)
  • Troubleshooting the pixel output issue with your custom panel driver

The integration guidance varies significantly by platform, so confirming your exact setup first will help ensure the most effective troubleshooting approach.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Software summary

Bootloader: U-Boot

Kernel version: 6.6.129-7.6.0 #1-Torizon SMP PREEMPT Thu Mar 26 15:16:22 UTC 2026
Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/75c99bc54de9e410b9306fd4c876efdcbb8cf8ad95da153afc48bf74e8e158c0/0
Distro name: NAME=“Torizon OS”
Distro version: VERSION_ID=7.6.0-build.36
Distro variant: VARIANT=“Docker”
Hostname: verdin-imx95-08828723

Hardware info

HW model: Toradex Verdin iMX95 WB on Verdin Development Board

Toradex version: 0089 V1.0C
Serial number: 08828723
Processor arch: aarch64

4

Perfect! Now I can provide specific guidance for your Verdin iMX95 setup running Torizon OS 7.6.0. Based on your configuration, here’s how to approach your Focus E43GB-I-MW1000-N display integration: (1)

Device Tree Overlay Configuration

For Torizon OS 7.6.0 on Verdin iMX95, you’ll need to create a custom device tree overlay for your Focus display. The system supports device tree overlays that can be applied using TorizonCore Builder. (1)

Checking Current Overlay Status

First, verify which overlays are currently applied: (1)

ls /proc/device-tree/chosen/overlays/
cat /proc/device-tree/chosen/overlays/<overlay_name>.dtbo

(1)

If the value is 0, the overlay was applied successfully. (1)

Development Approach

For your custom display driver integration, you have two main approaches:

1. Development and Production Method (Recommended):
Use TorizonCore Builder to create a custom image with your modified panel driver and device tree overlay. (1) (2)

2. Quick Testing Method:
For initial testing, you can apply overlays directly on the device by modifying the overlays.txt file, though this is only recommended for prototyping. (1)

Custom Image Creation

Since you’re modifying the panel driver (panel-ili9608e.c), you’ll need to build a custom Torizon OS image. Create a tcbuild.yaml configuration file: (2)

input:
  easy-installer:
    local: torizon-docker-verdin-imx95-Tezi_7.6.0+build.36
customization:
  device-tree:
    include-dirs:
      - linux/include
      - device-trees/overlays
    custom: linux/arch/arm64/boot/dts/freescale/imx95-verdin-wifi-dev.dts
    overlays:
      add:
        - device-trees/overlays/your-custom-focus-display_overlay.dts
output:
  easy-installer:
    local: custom-torizon-verdin-imx95-focus-display
    name: "Torizon OS - Focus E43GB Display"

(2)

Required Source Files

You’ll need to clone the appropriate repositories for your iMX95: (2)

git clone -b toradex_6.6-2.2.x-imx git://git.toradex.com/linux-toradex.git linux
git clone -b toradex_6.6-2.2.x-imx git://git.toradex.com/device-tree-overlays.git device-trees

(2)

Troubleshooting Steps

  1. Verify DSI Configuration: Ensure your device tree overlay correctly configures the DSI interface timing parameters for the Focus display
  2. Driver Integration: Your modified panel-ili9608e.c driver needs to be properly integrated into the kernel build
  3. Dual-Head Setup: Since you mentioned dual LVDS + DSI, ensure there are no conflicts between display pipelines

Build Process

Once your configuration is ready: (2)

torizoncore-builder build

(2)

The build will generate a commit checksum that you can use to verify your custom image deployment. (2)

Would you like to share your current device tree overlay and driver modifications? This would help identify specific issues with the pixel output problem you’re experiencing.

Best regards, Toradex AI Assistant.

**

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

5

As I already said, i’ve done this part of the work. I have a DTS file and a driver already created. I would attach some files for you to see, but as a new user, I can’t. @stefan_e.tx , perhaps you can reach out and provide an e-mail address where I can send you what I have?

Mark

6

@markster

The suggested way to enable a new display is to use a Device Tree overlay, without recompiling the entire Device Tree.

Have you tried this approach?

You can share your files using our share server and then post the resulting download links here.