Posts by deltasjimmy

Quote from Da Flex

I've never seen a DSI driver developer on this forum. So I think you're searching at the wrong place.

Usually it goes like this: Find an open source driver, and adapt it for your needs.

I found this thread on the RPi forums, which is a good starting point: Click!

Da Flex, no need to develop new driver since in the 5.15 kernel it already exists. See here:.

Also, there is a documentation how to use it here.

My problem is that I so newbie to linux that I cannot write the working overlay file.

When it is written then I can compile it an run from config.txt.

In this overlay file I would ask anybody's help.

Thanks in advance guys.

Hello guys,

I have a deep knowledge of PCB hardware so I have designed an adapter board for CM4IO to "tdo,tl070wsh30" DSI display.

On the otherside I am really a noobie on linux, so I would ask your help how to enable this display to work.

What I had already done:

- latest 5.15.13 LE is built with this display enabled in the *.conf file

- I have CM4IO with this adapter board where LCD_RESET is connected to GPIO6.

- backlight is alwyas enabled by hardware

- display is connected to CM4IO DISP1 port

I would need a working DToverlay file.

Thanks for your great support guys in advance.

jimmy

Hi again,

Correction:

Those *.ko files are exist here:

./run/kernel-overlays/modules/5.15.0/kernel/drivers/gpu/drm/panel/panel-ronbo-rb070d30.ko

./usr/lib/kernel-overlays/base/lib/modules/5.15.0/kernel/drivers/gpu/drm/panel/panel-ronbo-rb070d30.ko

But still the display is dark.

See pastekodi HERE

These are added to config.txt:

ignore_lcd=1

dtoverlay=lcd_ronbo

Here is my "lcd_ronbo.dtbo" file content, :

/dts-v1/;
/plugin/;

/ {
    compatible = "brcm,bcm2711";

    fragment@0 {
        target = <&dsi1>;
        __overlay__{
            status = "okay";
            #address-cells = <1>;
            #size-cells = <0>;
            port {
                dsi_out_port:endpoint {
                    remote-endpoint = <&panel_dsi_port>;
                };
            };

            rb070d30:rb070d30@0 {
                compatible    = "ronbo,rb070d30";
                status        = "okay";
                reg           = <0>;
                power-gpios   = <&gpio 4 1>;   // ENABLE
                reset-gpios   = <&gpio 17 1>;   // RESET
                shlr-gpios    = <&gpio 27 1>;    // SHLDR
                updn-gpios    = <&gpio 22 1>;    // UPDN
                vcc-lcd-supply= <&reg_display>;
                port {
                    panel_dsi_port: endpoint {
                        remote-endpoint = <&dsi_out_port>;
                    };
                };
            };
        };
    };

    fragment@1 {
        target = <&gpio>;
        __overlay__ {
            rb070d30_pins: rb070d30_pins {
                brcm,pins = <4 17 27 22>;
                brcm,function = <1 1 1 1>; // out
                brcm,pull = <0 0 0 0>; // off
            };
        };

    };

    __overrides__ {
        power = <&rb070d30_pins>,"brcm,pins:4",
            <&rb070d30>,"power-gpios:4";

        reset = <&rb070d30_pins>,"brcm,pins:17",
            <&rb070d30>,"reset-gpios:17";

        shlr = <&rb070d30_pins>,"brcm,pins:27",
            <&rb070d30>,"shlr-gpios:27";
            
        updn = <&rb070d30_pins>,"brcm,pins:22",
            <&rb070d30>,"updn-gpios:22";
    };
};

Hello guys,

The meanwhile I have switched to a landscape mode display that is Ronbo, RB070D30.

(Parallelly, switched to CM4IO board.)

It has an existing Linux driver HERE.

Unfortunately, when I activate this drivre within "/projects/RPi/devices/RPi4/linux/linux.aarch64.conf" then building the system image then

.ko is not generated so I cannot use the display with my own dt overlay.

Can you please help what did I wrong?

The difference between the two display from RPi point of view is:

LT070ME05000 driver exists in the RPi OS by default but RB070D30 not.

Thanks for your great support again.

HiassofT, Da Flex.

I have started a new topic at the RPi forum here:

CM3+ screen rotation for LT070ME05000 with LibreELEC

There, I have referred to our discussion here on the LE forum.

Please support me guys on that forum if you have capacity to do.

Thanks a lot again.

That's a great idea.

Today I have tried it out, but it not works. There are three problems with it:

- 18.7 Leia is installed (I don't know how to install 19.1 Matrix)

- KODI hangs at KODI "18.7 Leia" screen

- RPiOS is well rotated but KODI is still at the original orientation.

Additionally, I can also confirm that next to LE, also RPiOS hangs without HDMI connected on kernel 5.10.48.

It sounds that this won't be solved soon.

Does anybody work on this feature or is it planned from kodi side?

I have tried this line with different parameters today in cmdline.txt:

1) video=DSI-1:1200x1920@60,panel_orientation=left_side_up >>> nothing rotated

2) video=DSI-1:1200x1920@60,panel_orientation=right_side_up >>> nothing rotated

Then just for playing around:

3) video=DSI-1:1200x1920@60,panel_orientation=upside_down >>> LE logo is upside down, but GUI reversed back to original orientation

4) video=DSI-1:1200x1920@60,reflect_x=y >>> LE logo is mirrored on x axis, but GUI reversed back to original orientation

5) video=DSI-1:1200x1920@60,rotate=270 >>> nothing rotated

Also tried to use 'lcd_rotate' and'display_rotate' additionally in config.txt but nothing help.

Good point HiassofT.

Suggested changes are made then image is re-compiled.

Then I could reproduce the behaviour.

1) When the board starts up with HDMI connected then the board boots up with LE GUI on the HDMI display.

2) When the board starts up with no HDMI connected then the LCD remains dark.

3) When HDMI is connected and the board is powered; after like 4-5 seconds the HDMI cable is removed then the board starts with LE GUI on the LCD.

So it looks that you and RPi devs can solve this issue next week. Good to hear

The next question is, how can I rotate the screen?

By the way the touch screen also works, but that one is oriented right.

(touchscreen-inverted-x and touchscreen-swapped-x-y in it's dtoverlay.)

Thanks guys this great job.

Quote from HiassofT

deltasjimmy can you test if the display is working on RPi OS with the latest rpi-update kernel (currently 5.10.46-v7+)?

I built an LE image with the missing drivers included, but it just locks up on my RPi3B+ when I add the vc4-kms-dsi-lt070me05000 dtoverlay - and the same happens on RPiOS with latest kernel as well. I don't have any DSI displays here so not sure if that's the cause - the DSI driver is still under heavy development so it could be an issue in latest kernel, too.

so long,

Hias

Hi HiassofT,

As you can read my first post, the display already tested out with the latest RPi OS (kernel 5.10.46-v7+) using these additions in the config.txt:

ignore_lcd=1

dtoverlay=vc4-kms-v3d

dtoverlay=vc4-kms-dsi-lt070me05000,reset=39,enable=38,dcdc-en=41

This way the display works fine.

LibreELEC:

Yesterday, I have also compiled the latest nightly build with the next modifications in the "http://LibreELEC.tv/projects/RPi/devices/RPi2/linux/linux.arm.conf":

CONFIG_TOUCHSCREEN_GOODIX=m

CONFIG_DRM_PANEL_JDI_LT070ME05000=m

(I don't know if anything else is needed or not, please let me know if something more are required)

This way I have the same experiences as you have, the board does not boot, no logs within KODI or LE files.

For me , it means that the kernel can handle the display, so the problem is within KODI or LE.

To help you to figure out the problem, maybe I should activate the kernel UART debug feature then using a FTDI-FT232 cable I can log everything using my notebook.

If it helps then please let me know how can I activate this feature.

Here can see two photos of the board if interested.

Thanks for your great support, please keep on.

Thanks guys,

Good to hear that you found my issue this quickly.

Please also help with the Goodix GT911 touchscreen attached.

CONFIG_TOUCHSCREEN_GOODIX

Should I use the procedure to add modules as it is readable on RPi website or is it different for LE?

Quote from Da Flex

Thanks!

Code

Jul 05 18:40:00.805362 LibreELEC systemd[1]: Condition check resulted in Kodi user autostart script being skipped.

Please post the content of your autostart.sh.

"/storage/.config/autostart.sh" file does not exist.

Quote from Da Flex

You're still at log level 0, so we are missing some info. Activate debug logging at GUI (HUD will appear), and do it again.

PS: Reboot before running pastekodi.

OK, so I commented out "dtoverlay=vc4-kms-dsi-lt070me05000,reset=39,enable=38,dcdc-en=41" in config.txt to be able to log in using HDMI.

Then log level set for debug >>> HUD appeared >>> power off >>> revert config.txt changes >>> power up >>> log in SSH >>> run pastekodi

Here are the results: LINK

Thanks Da Flex, HiassofT.

Quote from HiassofT

Please test with the latest nightly (currently 20210704). If that doesn't work please provide a full "pastekodi" log - ssh in, run "pastekodi" and post the URL

so long,

Hias

Thanks for your quick response HiassofT.

Here is the link from pastekodi: LINK

Hello Guys,

I would like to support you with testing on a custom hardware.

I have my own designed hardware basing on CM3+ and LT070ME05000 DSI display and of course a lot of additional perpherals.

Now the system already works close to fine using Raspberry OS with the latest firmware. (kernel 5.10.46).

Today, I have dowloaded the latest nightly build from here (LibreELEC-RPi2.arm-10.0-nightly-20210628-f904c2e.img.gz).

Added the same lines in my config.txt:

ignore_lcd=1

dtoverlay=vc4-kms-v3d

dtoverlay=vc4-kms-dsi-lt070me05000,reset=39,enable=38,dcdc-en=41

Unfortunately, my LCD remains dark wathever I do, although I have tried many parameter changes.

Using HDMI everythig works fine, but the final target would be this huge LCD screen.

Please let me help to give life to this screen with your nice LibreELEC.

In hardware staff I have a lot of experiences as an electrical development engineer, but to be honest, for Linux, KODI, LE, RPi software staff I am really newbie.

dmesg says this:

[ 3.167778] [drm:vc4_dsi_bind] *ERROR* Failed to get DMA channel: -19

[ 3.167819] vc4-drm soc:gpu: failed to bind 3f700000.dsi (ops 0x80c5eb40): -19

Which is from here: "ret = PTR_ERR(dsi->reg_dma_chan);" from "vc4_dsi.c" line 1514.

So please handle me as a 5-year-old kid

Thanks for your great help and keep on!