IMX8MP Problem with FPD Link III

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMX8MP Problem with FPD Link III

634 Views
csander
Contributor I

Hi there,

 

i have a problem regarding the connection between the IMX8MPLUS , the DS90UB947/8 SerDes and a 10 inch panel

My device tree is based off of a functioning variant, in which we didn't use the FPD Link and connected our panel directly to the LVDS signal from the IMX8MP.

I have explored almost every possible option there is and i really don't know any further.

The FPD Link is set up correctly: Single Link, OpenLDI Mapping, Single Pixel Input, Single Link Transport to Deserializer, Single Link JEIDA Output. Everything is 24 bit Video, I2C Passthrough is activated, the cable is set to STP on both devices, Port0 is selected on both devices, DE_GATE_RGB is activated.

The FPD Link is stable: Deserializer 0x1C[0,1] = 1, Serializer 0x0c[0,1,2] = 1

Looking at the 0x20 Register on the Serializer the functions of the Deserializer are correctly identified. 0x5A also shows that everything is supposed to be working fine [0,2,4,6,7] = 1, 0x5F also shows the correct pixelclock of 74,25MHz.


i am currently using this dts. 
Things i have tried: swapped data mapping of the lvds-channel and panel between jeida and spwg (all kinds of combinations), the timings are from another working dts, regarding the ldb i have tried adding either phys = <&ldb_phy> phy-names = "ldb_phy" as well as directly using ldb_phy1 neither worked, i have tried both lvds-channels either single or dual link.
 
I really dont know any further and would appreciate any kind of ideas you guys have.
0 Kudos
Reply
3 Replies

601 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hi @csander 

Could you describe the current issue you meet in more detail? From your description, I can understand what you did, but I can't grasp the problem.

Best Regards,
Zhiming

0 Kudos
Reply

594 Views
csander
Contributor I

Ah yes of course, I wanted to edit the message afterwards to ad my actual problem but realised i couldn't edit it anymore.

First of all thank your for your fast reply.

My exact problem is the following:

I want to extend my video signaling via the FPD3Link and everything is wired up correctly but i can't get any image or video on my display.

When booting up my SoM and powering the display i can see that the backlight turns on but thats it.

And no matter what I do I can't get the lcd controller to connect with the ldb and I checked the manual to confirm that lcdif2 is for LVDS and at the address 32e9000

root@imx8mp-display:~# dmesg | grep -iE "lvds|ldb|lcdif|drm"
[ 0.051459] platform panel: Fixed dependency cycle(s) with /ldb-display-controller/lvds-channel@0
[ 1.422143] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 0
[ 1.724239] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
[ 1.732467] imx-drm display-subsystem: bound ldb-display-controller (ops imx8mp_ldb_ops)
[ 1.741177] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1
[ 1.815820] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device
[ 1.823574] imx8mp-ldb ldb-display-controller: Failed to create device link (0x180) with 32e90000.lcd-controller
[ 4.082340] systemd[1]: Starting Load Kernel Module drm...

I have also tried watched the framebuffer change between values of 37 an 40
viawatch -n 0.5 "grep -nE 'plane\\[|fb=|crtc\\[33\\]|connector\\[35\\]' $STATE | head -n 60"
which indicates that some kind of visual is supposed to be seen.

I also edited the weston.ini to just show a one coloured background which did not do anything.

Killing weston and writing directly into the framebuffer also did not work.

 

 

 

0 Kudos
Reply

560 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hi @csander 

If the hardware design is sound (this is crucial), the only remaining aspect to check at the software level is Pixel Polarity in static const struct display_timing-->flags and bus_flags.


Best Regards,
Zhiming

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2302317%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EIMX8MP%20Problem%20with%20FPD%20Link%20III%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302317%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3Ei%20have%20a%20problem%20regarding%20the%20connection%20between%20the%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fc-pwmxy87654%2FIMX8MPLUS%2Fpd-p%2FIMX8MPLUS%22%20class%3D%22lia-product-mention%22%20data-product%3D%2221-1%22%20target%3D%22_blank%22%3EIMX8MPLUS%3C%2FA%3E%26nbsp%3B%2C%20the%20DS90UB947%2F8%20SerDes%20and%20a%2010%20inch%20panel%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EMy%20device%20tree%20is%20based%20off%20of%20a%20functioning%20variant%2C%20in%20which%20we%20didn't%20use%20the%20FPD%20Link%20and%20connected%20our%20panel%20directly%20to%20the%20LVDS%20signal%20from%20the%20IMX8MP.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EI%20have%20explored%20almost%20every%20possible%20option%20there%20is%20and%20i%20really%20don't%20know%20any%20further.%3C%2FP%3E%0A%3CP%3EThe%20FPD%20Link%20is%20set%20up%20correctly%3A%20Single%20Link%2C%20OpenLDI%20Mapping%2C%20Single%20Pixel%20Input%2C%20Single%20Link%20Transport%20to%20Deserializer%2C%20Single%20Link%20JEIDA%20Output.%20Everything%20is%2024%20bit%20Video%2C%20I2C%20Passthrough%20is%20activated%2C%20the%20cable%20is%20set%20to%20STP%20on%20both%20devices%2C%20Port0%20is%20selected%20on%20both%20devices%2C%20DE_GATE_RGB%20is%20activated.%3C%2FP%3E%0A%3CP%3EThe%20FPD%20Link%20is%20stable%3A%20Deserializer%200x1C%5B0%2C1%5D%20%3D%201%2C%20Serializer%200x0c%5B0%2C1%2C2%5D%20%3D%201%3C%2FP%3E%0A%3CP%3ELooking%20at%20the%200x20%20Register%20on%20the%20Serializer%20the%20functions%20of%20the%20Deserializer%20are%20correctly%20identified.%200x5A%20also%20shows%20that%20everything%20is%20supposed%20to%20be%20working%20fine%20%5B0%2C2%2C4%2C6%2C7%5D%20%3D%201%2C%200x5F%20also%20shows%20the%20correct%20pixelclock%20of%2074%2C25MHz.%3C%2FP%3E%0A%3CDIV%3E%0A%3CDIV%3E%3CSPAN%3E%3CBR%20%2F%3E%3C%2FSPAN%3Ei%20am%20currently%20using%20this%20dts.%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EThings%20i%20have%20tried%3A%20swapped%20data%20mapping%20of%20the%20lvds-channel%20and%20panel%20between%20jeida%20and%20spwg%20(all%20kinds%20of%20combinations)%2C%20the%20timings%20are%20from%20another%20working%20dts%2C%20regarding%20the%20ldb%20i%20have%20tried%20adding%20either%26nbsp%3B%3CSPAN%3Ephys%20%3D%20%26lt%3B%3C%2FSPAN%3E%3CSPAN%3E%26amp%3Bldb_phy%3C%2FSPAN%3E%3CSPAN%3E%26gt%3B%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3Bphy-names%20%3D%20%3C%2FSPAN%3E%3CSPAN%3E%22ldb_phy%22%20as%20well%20as%20directly%20using%20ldb_phy1%20neither%20worked%2C%20i%20have%20tried%26nbsp%3B%3C%2FSPAN%3Eboth%20lvds-channels%20either%20single%20or%20dual%20link.%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EI%20really%20dont%20know%20any%20further%20and%20would%20appreciate%20any%20kind%20of%20ideas%20you%20guys%20have.%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2302317%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3EGraphics%20%26amp%3B%20Display%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ei.MX%208%20Family%20%7C%20i.MX%208QuadMax%20(8QM)%20%7C%208QuadPlus%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ei.MX%208M%20%7C%20i.MX%208M%20Mini%20%7C%20i.MX%208M%20Nano%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2302627%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20IMX8MP%20Problem%20with%20FPD%20Link%20III%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302627%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EAh%20yes%20of%20course%2C%20I%20wanted%20to%20edit%20the%20message%20afterwards%20to%20ad%20my%20actual%20problem%20but%20realised%20i%20couldn't%20edit%20it%20anymore.%3C%2FP%3E%3CP%3EFirst%20of%20all%20thank%20your%20for%20your%20fast%20reply.%3C%2FP%3E%3CP%3EMy%20exact%20problem%20is%20the%20following%3A%3C%2FP%3E%3CP%3EI%20want%20to%20extend%20my%20video%20signaling%20via%20the%20FPD3Link%20and%20everything%20is%20wired%20up%20correctly%20but%20i%20can't%20get%20any%20image%20or%20video%20on%20my%20display.%3C%2FP%3E%3CP%3EWhen%20booting%20up%20my%20SoM%20and%20powering%20the%20display%20i%20can%20see%20that%20the%20backlight%20turns%20on%20but%20thats%20it.%3C%2FP%3E%3CP%3EAnd%20no%20matter%20what%20I%20do%20I%20can't%20get%20the%20lcd%20controller%20to%20connect%20with%20the%20ldb%20and%20I%20checked%20the%20manual%20to%20confirm%20that%20lcdif2%20is%20for%20LVDS%20and%20at%20the%20address%2032e9000%3C%2FP%3E%3CP%3Eroot%40imx8mp-display%3A~%23%20dmesg%20%7C%20grep%20-iE%20%22lvds%7Cldb%7Clcdif%7Cdrm%22%3CBR%20%2F%3E%5B%200.051459%5D%20platform%20panel%3A%20Fixed%20dependency%20cycle(s)%20with%20%2Fldb-display-controller%2Flvds-channel%400%3CBR%20%2F%3E%5B%201.422143%5D%20%5Bdrm%5D%20Initialized%20vivante%201.0.0%2020170808%20for%2040000000.mix_gpu_ml%20on%20minor%200%3CBR%20%2F%3E%5B%201.724239%5D%20imx-drm%20display-subsystem%3A%20bound%20imx-lcdifv3-crtc.0%20(ops%20lcdifv3_crtc_ops)%3CBR%20%2F%3E%5B%201.732467%5D%20imx-drm%20display-subsystem%3A%20bound%20ldb-display-controller%20(ops%20imx8mp_ldb_ops)%3CBR%20%2F%3E%5B%201.741177%5D%20%5Bdrm%5D%20Initialized%20imx-drm%201.0.0%2020120507%20for%20display-subsystem%20on%20minor%201%3CBR%20%2F%3E%5B%201.815820%5D%20imx-drm%20display-subsystem%3A%20%5Bdrm%5D%20fb0%3A%20imx-drmdrmfb%20frame%20buffer%20device%3CBR%20%2F%3E%5B%201.823574%5D%20imx8mp-ldb%20ldb-display-controller%3A%20Failed%20to%20create%20device%20link%20(0x180)%20with%2032e90000.lcd-controller%3CBR%20%2F%3E%5B%204.082340%5D%20systemd%5B1%5D%3A%20Starting%20Load%20Kernel%20Module%20drm...%3C%2FP%3E%3CP%3EI%20have%20also%20tried%20watched%20the%20framebuffer%20change%20between%20values%20of%2037%20an%2040%3CBR%20%2F%3E%3CSPAN%3Eviawatch%20-n%200.5%20%22grep%20-nE%20'plane%5C%5C%5B%7Cfb%3D%7Ccrtc%5C%5C%5B33%5C%5C%5D%7Cconnector%5C%5C%5B35%5C%5C%5D'%20%24STATE%20%7C%20head%20-n%2060%22%3CBR%20%2F%3Ewhich%20indicates%20that%20some%20kind%20of%20visual%20is%20supposed%20to%20be%20seen.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20also%20edited%20the%20weston.ini%20to%20just%20show%20a%20one%20coloured%20background%20which%20did%20not%20do%20anything.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EKilling%20weston%20and%20writing%20directly%20into%20the%20framebuffer%20also%20did%20not%20work.%3C%2FP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2302551%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20IMX8MP%20Problem%20with%20FPD%20Link%20III%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302551%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F259307%22%20target%3D%22_blank%22%3E%40csander%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ECould%20you%20describe%20the%20current%20issue%20you%20meet%20in%20more%20detail%3F%20From%20your%20description%2C%20I%20can%20understand%20what%20you%20did%2C%20but%20I%20can't%20grasp%20the%20problem.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20Regards%2C%3CBR%20%2F%3EZhiming%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2304342%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20IMX8MP%20Problem%20with%20FPD%20Link%20III%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2304342%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F259307%22%20target%3D%22_blank%22%3E%40csander%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20the%20hardware%20design%20is%20sound%20(this%20is%20crucial)%2C%20the%20only%20remaining%20aspect%20to%20check%20at%20the%20software%20level%20is%20Pixel%20Polarity%20in%26nbsp%3B%3CSTRONG%3E%3CSPAN%3Estatic%3C%2FSPAN%3E%20%3CSPAN%3Econst%3C%2FSPAN%3E%20%3CSPAN%3Estruct%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSTRONG%20style%3D%22font-family%3A%20inherit%3B%22%3E%3CSPAN%3Edisplay_timing--%26gt%3Bflags%20%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3Eand%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%20style%3D%22font-family%3A%20inherit%3B%22%3E%3CSPAN%3Ebus_flags%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CSPAN%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EBest%20Regards%2C%3CBR%20%2F%3EZhiming%3C%2FP%3E%3C%2FLINGO-BODY%3E