SMARC i.MX8MP + Verdin DSI Display Adapter + Riverdi RVT101HVDNWC00-B – Backlight On but No Display Output

Hi,

I am working with the Toradex SMARC i.MX8M Plus SoM and the Toradex SMARC Carrier Board. The display interface is through the Verdin DSI Display Adapter.

The LCD touch display I am using is:

Model: Riverdi RVT101HVDNWC00-B

Resolution: 1280×800 (Touch is supported in this module)

What I Have Done.

I followed the Toradex documentation which mentions that the panel DT configuration is already included inside the display overlays. I applied the overlay:

toradex-smarc-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
The overlay was added successfully, and after reboot:
Backlight turns ON,
However, the display does not show any image (black screen)
dmesg does not show obvious panel or SN65DSI83 initialization failure

I am unable to locate the corresponding .dts/.dtso source for the loaded .dtbo overlay to confirm the panel timing and LVDS mapping

My Questions

1.Whether the Verdin DSI Display Adapter is compatible with the Toradex SMARC i.MX8M Plus SoM and the Toradex SMARC Carrier Board?

2.Where can I obtain the exact .dts / .dtso source file used to build:

toradex-smarc-imx8mp_panel-cap-touch-10inch-dsi_overlay. dtbo, so I can verify the panel timing block?

3.Since this panel is RVT101HVDNWC00-B (with touch), can you confirm whether the default overlay includes:

The correct LVDS mapping (VESA-24 vs JEIDA-24)
The proper pixel clock and hsync/vsync porch timing for this Riverdi model?

Also, I have attached the dmesg failure logs

Hi, I’m the Toradex AI Assistant.

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


SMARC iMX8M Plus Display Integration

I understand you’re working with the SMARC iMX8M Plus SoM and experiencing display issues. Let me address your questions based on the available documentation.

1. Compatibility Assessment

Based on the available overlay information, the Verdin DSI Display Adapter appears to be designed specifically for the Verdin family modules (1). For SMARC modules, the documentation shows different overlay naming conventions.

For SMARC iMX8M Plus, the available DSI display overlays are (2):

  • toradex-smarc-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
  • toradex-smarc-imx8mp_panel-cap-touch-7inch-dsi_overlay.dtbo

2. Device Tree Source Location

The device tree overlay sources are available in the Toradex Device Tree Overlays repository on GitHub (1). You can find the source files there to examine the exact timing parameters and configurations.

3. Custom Display Configuration

Since you’re using a Riverdi RVT101HVDNWC00-B display, which is not the standard Toradex display, you’ll likely need to create a custom overlay. The pre-built overlays are designed for specific Toradex displays (1).

Recommended Approach

Create Custom Overlay

For your Riverdi display, you’ll need to modify the device tree overlay with the correct timing parameters. Here’s the general structure you’ll need (3):

&ldb {
    status = "okay";
    lvds-channel@0 {
        fsl,data-mapping = "spwg";
        fsl,data-width = <18>;
        panel@0 {
            compatible = "panel-lvds";
            label = "riverdi_rvt101hvdnwc00";
            data-mapping = "jeida-18";
            panel-timing {
                clock-frequency = <65000000>;
                hactive = <1280>;
                vactive = <800>;
                hsync-len = <136>;
                hfront-porch = <24>;
                hback-porch = <160>;
                vsync-len = <6>;
                vfront-porch = <3>;
                vback-porch = <29>;
            };
        };
    };
};

Key Configuration Points

  1. Data Mapping: Set fsl,data-mapping and fsl,data-width properties according to your panel specifications (4)
  2. Timing Parameters: The horizontal period must equal hback_porch + hactive + hfront_porch + hsync-len and vertical period must equal vback_porch + vactive + vfront_porch + vsync-len (1)
  3. Panel Compatibility: Use the panel-lvds driver for defining timing details directly in the device tree (4)

Debugging Steps

  1. Check Display Detection: Use modetest -M imx-drm to verify display detection (4)
  2. Verify Overlay Loading: Ensure your custom overlay is properly loaded and applied
  3. Review Timing Parameters: Compare your display datasheet specifications with the device tree timing values

The backlight turning on indicates power is reaching the display, but the black screen suggests timing or data mapping issues. You’ll need to consult your Riverdi display datasheet for the exact timing parameters and LVDS mapping requirements.

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.

Hi @Sreehari,
This query is already answered on the emails.
Please update us in case yo are still facing the issue.

Hey,
Just wanted to update you—I actually figured out the issue! Turns out it was hardware related. I needed to remove the jumper from the J95 connector, and after that, everything started working as expected.
Also, I realized that the link I shared earlier pointed to a different branch (device-tree-overlays.git - Sources for Device Tree Overlays), which caused some confusion.