topic Re: U boot error In IMX8M MINI EVK for Android 10 OS in i.MX Processors

U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Fri, 09 Jul 2021 10:15:38 GMT

U boot error In IMX8M MINI EVK for Android 10 OS

I have attached my log below . I have connected LVDS converter of SN65DSI83

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Juan-Rodarte — Tue, 20 Jul 2021 17:09:03 GMT

Hello,

I noticed that you have opened two threads that are related to the same problem, if possible I would like to keep communication in one thread so we can avoid any misunderstanding.
This are the other 2 threads you have:

https://community.nxp.com/t5/i-MX-Processors/Error-in-uboot/td-p/1308862
https://community.nxp.com/t5/i-MX-Processors/How-to-support-LVDS-in-Uboot-for-imx8mm-in-Android-OS/td-p/1308170

Moving to the issue, It seems that you made some modification to the I2C configuration, I would like to see what changes you made, did you try with a precompiled image?

Regards
Diego.

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Wed, 21 Jul 2021 04:32:56 GMT

I am trying to Add mipi to LVDS using sn65dsi83.

i am disabling adv7535 which is HDMI bridge .

i Have added sn65dsi83 bridge .I have attached the folder below.

And i am Adding dts file below you can go throught it.

I have attached changes made in Kernel imx8mm-evk.dts file path /android_build/vendor/nxp-opensource/kernel_imx/arch/arm64/boot/dts/freescale/

and in uboot imx8mm-evk.dts file path /android_build/vendor/nxp-opensource/uboot-imx/arch/arm/dts/

Kindly provide solution for upbring of LVDS display

https://www.digi.com/resources/documentation/digidocs/embedded/dey/3.0/cc8mmini/bsp_r_video-lvds_8m

The above link was provided by Ur colleague. For integrating LVDS bridge

Thanks and regards

Ruban

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Fri, 23 Jul 2021 05:42:09 GMT

Any solution

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Juan-Rodarte — Fri, 23 Jul 2021 18:41:55 GMT

Hello,

The I2C2 uses pads GPIO5-16 and GPIO5-17 which you have commented and put GPIO5-18 and GPIO5-19 for SDA and SCL, even you have the same pads for the I2C3, you must undo this change.
You need to remove the part of "adv_bridge: adv7535" and move to the I2C2 block the "dsi_lvds_bridge: sn65dsi84" since it will be connected to the same MIPI-DSI port
Also, you may disable the CONFIG_VIDEO_ADV7535, located here:
https://source.codeaurora.org/external/imx/uboot-imx/tree/configs/imx8mm_evk_defconfig?h=imx_v2020.04_5.4.24_2.1.0#n140

Regards.
Diego.

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Mon, 26 Jul 2021 04:30:44 GMT

Thanks for the Support Juan Rodarte

I have a doubt. I have a LVDS bridge is it enough only to change in U-boot-imx file or should i even add in Kernel-imx file .

And should i even change in panel folder or its enough only in u-boot to detect the driver .

If i have to add in panel folder like how they have done for rm67191. setting everything of display with timing diagram.

According to the changes you told clock frequency of i2c2 is 400000 and for i2c3 its 100000. For LVDS it mentions 100000 will it run in 400000 also.

-> enable-gpios = <&gpio3 0 GPIO_ACTIVE_HIGH>;

should i use gpio3 or gpio2

-> interrupt-parent = <&gpio3>;

should i use gpio3 or gpio2

-> pinctrl_lvds: lvdsgrp { fsl,pins = < /* SN65DSI83 enable */ MX8MM_IOMUXC_NAND_ALE_GPIO3_IO0 0x19 /* SN65DSI83 interrupt */ MX8MM_IOMUXC_NAND_DATA00_GPIO3_IO6 0x19 >; };
In the above function should i use gpio3 or gpio2
if gpio2 which iomux should i use to enable and interrupt

-> port@1 {
dsim_to_adv7535: endpoint {
remote-endpoint = <&adv7535_from_dsim>;
};
};

port@2 {
dsim_to_rm67191: endpoint {
remote-endpoint = <&rm67191_from_dsim>;
};
};
for LVDS should i use port 1 or 2

i have attached the latest editted file

Thanks and Regards

Ruban

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Juan-Rodarte — Tue, 27 Jul 2021 19:25:50 GMT

Hello Ruban,

You must do the modification in the kernel as well.
For the driver you must follow the indications that are in the link that you attached.
For the I2C configurations and what the document mentioned you can use them for reference only, since the board is not ours.

Regards,
Diego.

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Wed, 28 Jul 2021 04:22:07 GMT

Hi Juan Rodarte,

You must do the modification in the kernel as well.

-> Can you provide the snippet to add in Kernel

since the board is not ours.

-> Can you provide link or details for our nxp imx8mm evk board

Thanks and reagrds

Ruban

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Juan-Rodarte — Wed, 28 Jul 2021 19:42:36 GMT

Hello Ruban,

To modify the kernel you can refer to the document you attached.
About the board, the changes mentioned you must be adapted to our board, since this document is for a different board.

Regards,
Diego.

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Fri, 30 Jul 2021 06:39:06 GMT

Hi Juan Rodarte,

What all changes should be made according to our board

Thanks and reagrds

Ruban

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Juan-Rodarte — Tue, 03 Aug 2021 16:53:22 GMT

Hi Ruban,

The changes that I mentioned in previous comments.

Best regards
Diego.

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Wed, 04 Aug 2021 04:42:15 GMT

Hi Juan Rodarte,

In my boot log

Error in uboot

cant find probe panel device adv@7535@3d

-> how to change fron adv@7535 to sn65dsi83

failed to gett any video link display timings

-> where should i add the display timing

probe video device failed, ret -22

-> what does the above error means

pinctrl-0 = <&pinctrl_i2c3>;

pinctrl-1 = <&pinctrl_i2c3_gpio>;

scl-gpios = <&gpio5 18 GPIO_ACTIVE_HIGH>;

sda-gpios = <&gpio5 19 GPIO_ACTIVE_HIGH>;

These above lines are found in uboot dts file but in kernel file its not found

-> can you suggest me which pins i have to use for scl and sda in kernel

/* SN65DSI83 enable */

MX8MM_IOMUXC_NAND_ALE_GPIO3_IO0 0x19

/* SN65DSI83 interrupt */

MX8MM_IOMUXC_NAND_DATA00_GPIO3_IO6 0x19

According to our nxp data sheet has the same pin can you tell me to which pin i have to configure

In the below function can you tell which all i have to change according to our board can you tel the pin number along with it

&i2c3 { clock-frequency = <100000>;

pinctrl-names = "default", "gpio";

pinctrl-0 = <&pinctrl_i2c3>;

pinctrl-1 = <&pinctrl_i2c3_gpio>;

scl-gpios = <&gpio5 18 GPIO_ACTIVE_HIGH>;

sda-gpios = <&gpio5 19 GPIO_ACTIVE_HIGH>;

status = "okay";

dsi_lvds_bridge: sn65dsi84@2c { compatible = "ti,sn65dsi83"; reg = <0x2c>;

ti,dsi-lanes = <4>;

ti,lvds-format = <1>;

ti,lvds-bpp = <24>;

ti,width-mm = <217>;

ti,height-mm = <136>;

enable-gpios = <&gpio3 0 GPIO_ACTIVE_HIGH>;

interrupt-parent = <&gpio3>;

interrupts = <6 IRQ_TYPE_LEVEL_HIGH>;

pinctrl-names = "default"; pinctrl-0 = <&pinctrl_lvds>;

status = "disabled";

display-timings { native-mode = <&lvds0_g101evn010>;

/* AUO G101EVN01.0 */ l

vds0_g101evn010:

timing@0 { clock-frequency = <69000000>;

hactive = <1280>;

vactive = <800>;

hfront-porch = <120>;

hback-porch = <1>;

hsync-len = <8>;

vback-porch = <10>;

vfront-porch = <1>;

vsync-len = <6>;

hsync-active = <1>;

vsync-active = <1>;

de-active = <1>;

pixelclk-active = <0>;

};

/* Fusion 10" F10A-0102 */

lvds0_hsd101pfw2: timing@1 { clock-frequency = <45000000>;

hactive = <1024>;

vactive = <600>;

hfront-porch = <120>;

hback-porch = <1>;

hsync-len = <8>;

vback-porch = <10>;

vfront-porch = <1>;

vsync-len = <6>;

hsync-active = <1>;

vsync-active = <1>;

de-active = <1>;

pixelclk-active = <0>;

};

port {

dsi_lvds_bridge_in: endpoint { remote-endpoint = <&mipi_dsi_lvds_out>;

};

...

};

...

&mipi_dsi {

status = "okay";

...

port@2 {

mipi_dsi_lvds_out: endpoint {

remote-endpoint = <&dsi_lvds_bridge_in>;

};

pinctrl_lvds: lvdsgrp {

fsl,pins = <

/* SN65DSI83 enable */

MX8MM_IOMUXC_NAND_ALE_GPIO3_IO0 0x19

/* SN65DSI83 interrupt */

MX8MM_IOMUXC_NAND_DATA00_GPIO3_IO6 0x19 >;

};

Below i have attached the files which i have included in drivers

Should i configure anything in that

Should i edit these above function in I2C3 or such as adv should i place it in i2c2

In log aftr uboot it enteires to kernel i found error

[ 1.448505] imx-drm soc@0:bus@32c00000:display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)
[ 1.458432] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[ 1.465986] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[ 1.474264] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -517
[ 1.482050] imx-drm soc@0:bus@32c00000:display-subsystem: failed to bind 32e10000.mipi_dsi (ops imx_sec_dsim_ops): -517
[ 1.492924] imx-drm soc@0:bus@32c00000:display-subsystem: master bind failed: -517

[ 2.724268] i2c i2c-0: IMX I2C adapter registered
[ 2.729439] gpio-146 (scl): enforced open drain please flag it properly in DT/ACPI DSDT/board file
[ 2.739252] imx8mm-pinctrl 30330000.pinctrl: pin MX8MM_IOMUXC_NAND_ALE already requested by 30bb0000.spi; cannot claim for 1-002c
[ 2.750922] imx8mm-pinctrl 30330000.pinctrl: pin-61 (1-002c) status -22
[ 2.757549] imx8mm-pinctrl 30330000.pinctrl: could not request pin 61 (MX8MM_IOMUXC_NAND_ALE) from group lvdsgrp on device 30330000.pinctrl
[ 2.770164] sn65dsi83 1-002c: Error applying setting, reverse things back
[ 2.776973] sn65dsi83: probe of 1-002c failed with error -22

I have sents everything i have got Kindly help me to solve the issuse

Thanks and regards

Ruban

Re: U boot error In IMX8M MINI EVK for Android 10 OS

Ruban1 — Fri, 06 Aug 2021 03:46:50 GMT

Hi Juan Rodarte,

Any solution or updates

Re: U boot error In IMX8M MINI EVK for Android 10 OS

dipak290485 — Thu, 25 Nov 2021 06:30:36 GMT

Hi Ruben1,

Your problem was solved for sn65dsi83 lvds bridge ? Is it working on hardware ?

If yes, Can you send me the corrected device tree file of added this bridge into it ?