Posts by Konzept

Konzept · Nov 21st 2023

Sorry for the corrupt image. Something went wrong during the creation of the post.
It should be visible now.

Konzept · Nov 20th 2023

Hello,

we're using a PicoCore MX8MP-V2-LIN HW-Rev. 1.0 which works with our software + hardware.

We replaced it with Rev. 1.1 and use the same Hardware + Software. Now the LVDS-Display isn't working anymore.

Old U-Boot output:

U-Boot SPL 2020.04 (Jul 20 2021 - 08:40:33 +0000)

DDRInfo: RAM initialization success.

Using fixed config: 0x3b

Normal Boot

Trying to boot from BOOTROM

image offset 0x0, pagesize 0x200, ivt offset 0x0

NOTICE: BL31: v2.2(release):rel_imx_5.4.70_2.3.2_rc1-0-g2a2678646-dirty

NOTICE: BL31: Built : 18:46:16, Jul 19 2021

U-Boot 2020.04 (Jul 20 2021 - 08:40:33 +0000) for F&S

CPU: i.MX8MP[8] rev1.0 1800 MHz (running at 1200 MHz)

CPU: Commercial temperature grade (0C to 95C) at 39C

Reset cause: POR

Model: F&S PicoCoreMX8MP

Board: PicoCoreMX8MP Rev 1.00 (2x LAN, eMMC, 1x DRAM)

DRAM: 1 GiB

tcpc_init: Can't find device id=0x52

setup_typec: tcpc port init failed, err=-19

MMC: FSL_SDHC: 0, FSL_SDHC: 2

Loading Environment from MMC... OK

In: serial

Out: serial

Err: serial

BuildInfo:

- ATF 2a26786

- U-Boot 2020.04

flash target is MMC:2

Net: eth0: ethernet@30be0000 [PRIME], eth1: ethernet@30bf0000

Fastboot: Normal

Normal Boot

New output on Rev 1.1 looks like this:

The CPU-Name changed.

Probably because of the updated U-Boot version?

The error we get in the systemlog with Rev 1.1 are:

Mar 21 17:02:43 fsimx8mp kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

Mar 21 17:02:43 fsimx8mp kernel: [drm] No driver support for vblank timestamp query.

Mar 21 17:02:43 fsimx8mp kernel: imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)

Mar 21 17:02:43 fsimx8mp kernel: imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200

Mar 21 17:02:43 fsimx8mp kernel: imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi

Mar 21 17:02:43 fsimx8mp kernel: imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19

Mar 21 17:02:43 fsimx8mp kernel: imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops)

Mar 21 17:02:43 fsimx8mp kernel: [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0

...

Mar 21 17:02:44 fsimx8mp systemd[1]: Started Start Psplash Boot Screen.

Mar 21 17:02:44 fsimx8mp psplash[288]: Error opening /dev/fb0

Mar 21 17:02:44 fsimx8mp systemd[1]: Started Load/Save Random Seed.

Mar 21 17:02:44 fsimx8mp systemd[1]: psplash-start.service: Main process exited, code=exited, status=255/EXCEPTION

Mar 21 17:02:44 fsimx8mp systemd[1]: psplash-start.service: Failed with result 'exit-code'.

...

Mar 21 17:02:44 fsimx8mp systemd[1]: Started Start Psplash Boot Screen.

Mar 21 17:02:44 fsimx8mp psplash[323]: Error opening /dev/fb0

Mar 21 17:02:44 fsimx8mp systemd[1]: psplash-start.service: Main process exited, code=exited, status=255/EXCEPTION

Mar 21 17:02:44 fsimx8mp systemd[1]: psplash-start.service: Failed with result 'exit-code'.

...

Mar 21 17:02:45 fsimx8mp kernel[329]: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

Mar 21 17:02:45 fsimx8mp kernel[329]: [drm] No driver support for vblank timestamp query.

Mar 21 17:02:45 fsimx8mp kernel[329]: imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)

Mar 21 17:02:45 fsimx8mp kernel[329]: imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200

Mar 21 17:02:45 fsimx8mp kernel[329]: imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi

Mar 21 17:02:45 fsimx8mp kernel[329]: imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19

Mar 21 17:02:45 fsimx8mp kernel[329]: imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops)

Mar 21 17:02:45 fsimx8mp kernel[329]: [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0

...

Mar 21 17:02:47 fsimx8mp startApplication.sh[418]: Failed to create wl_display (No such file or directory)

Mar 21 17:02:47 fsimx8mp startApplication.sh[418]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.

Mar 21 17:02:47 fsimx8mp startApplication.sh[418]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Mar 21 17:02:47 fsimx8mp startApplication.sh[418]: Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland.

Mar 21 17:02:47 fsimx8mp audit[422]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=422 comm="APP" exe="/opt/APP" sig=6 res=1

Mar 21 17:02:47 fsimx8mp startApplication.sh[418]: /opt/startApplication.sh: line 15: 422 Aborted /opt/APP

Mar 21 17:02:47 fsimx8mp systemd[1]: app.service: Main process exited, code=exited, status=134/n/a

Mar 21 17:02:47 fsimx8mp systemd[1]: app.service: Failed with result 'exit-code'.

Mar 21 17:02:47 fsimx8mp kernel: audit: type=1701 audit(1679414567.020:5): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=422 comm="APP" exe=/opt/APP" sig=6 res=1

Mar 21 17:02:47 fsimx8mp kernel[329]: audit: type=1701 audit(1679414567.020:5): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=422 comm="APP" exe="/opt/APP" sig=6 res=1

For the old Version we get this additional log and have a working frame buffer:
Nov 20 11:21:20 fsimx8mp kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

Nov 20 11:21:20 fsimx8mp kernel: [drm] No driver support for vblank timestamp query.

Nov 20 11:21:20 fsimx8mp kernel: imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)

Nov 20 11:21:20 fsimx8mp kernel: imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops)

Nov 20 11:21:20 fsimx8mp kernel: imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200

Nov 20 11:21:20 fsimx8mp kernel: imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi

Nov 20 11:21:20 fsimx8mp kernel: imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19

Nov 20 11:21:20 fsimx8mp kernel: imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops)

Nov 20 11:21:20 fsimx8mp kernel: imx-drm display-subsystem: bound 32c00000.bus:ldb@32ec005c (ops imx8mp_ldb_ops)

Nov 20 11:21:20 fsimx8mp kernel: [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1

Nov 20 11:21:20 fsimx8mp kernel: Console: switching to colour frame buffer device 160x50

Konzept · Nov 14th 2023

Hello,

is there any updated HW-Documentation available?

I can only find an old Version

"for HW Revision 1.00

Preliminary

Version 004

(2021-11-02)"

Konzept · Jul 26th 2022

Hello,

thank you for updating the manual.

The commands that are mentioned on page 7
"...<build-directory>]$ source ./..sources/poky/oe-init-build-env
...<build-directory>]$ bitbake meta-toolchain"

didn't work for me.
QT wasn't compiled with that.

With the configured Yocto i used the command
"bitbake meta-toolchain-qt5"

Best regards

Benni

Konzept · Jul 19th 2022

Hello,

i'm looking for the Crosscompile QT-Version(qmake) path in the Yocto Build.

The "F&S Introduction to QT5 Debugging an Application Version 1.4" document describes everything for Buildroot. But the "F&S i.MX8M-Plus Linux First Steps Version 1.0" document states that "Buildroot Release is not yet available."

So the Yocto-Build is a "fus-image-qt5"(fus-imx-wayland).

Thank you.

With best regards
Benni

Konzept · Jul 12th 2022

Hello,

thank you for your answer.

It's a PicocoreMX8MP-V2.

The activation of channel 0 was tried before and it didn't work.

The problem was probably, that LVDS Channel1 was not fully deactivated and there was a conflict.

Now it works.

Best regards,
Benni

Konzept · Jul 11th 2022

Guten Tag,

bei der Inbetriebnahme eines LVDS-Displays am PicoCoreMX8MP wird leider kein Bild angezeigt. Das Regeln der Hintergrundbeleuchtung funktioniert.
Das Display ist an die LVDS0 Schnittstelle angeschlossen (BL_ON, BL_PWM, VLCD_ON, LVDS0_CLK_P, LVDS0_CLKN, LVDS0_D[0-4]_[P/N]).

Der Devicetree basiert auf picocoremx8mp-lcdif-j070wvtc0211.dts und sieht folgendermaßen aus:

C

#define CONFIG_PICOCOREMX8MP_MIPI_DSI_LVDS
#include "picocoremx8mp.dts"
/ {
lvds0_panel {
compatible = "panel-lvds";
power-supply = <&reg_vlcd>;
backlight = <&backlight_ldb>;
data-mapping = "vesa-24";
label = "j070wvtc0211";
width-mm = <216>;
height-mm = <135>;
status = "okay";
panel-timing {
clock-frequency = <72400000>;
hactive = <1280>;
vactive = <800>;
hback-porch = <88>;
hfront-porch = <72>;
hsync-len = <20>;
vback-porch = <23>;
vfront-porch = <15>;
vsync-len = <10>;
de-active = <0>;
vsync-active = <0>;
hsync-active = <0>;
};
port {
panel_lvds0_in: endpoint {
remote-endpoint = <&lvds0_out>;
};
};
};
lvds1_panel {
compatible = "panel-lvds";
power-supply = <&reg_vlcd>;
backlight = <&backlight_ldb>;
data-mapping = "vesa-24";
label = "j070wvtc0211";
width-mm = <216>;
height-mm = <135>;
status = "okay";
panel-timing {
clock-frequency = <72400000>;
hactive = <1280>;
vactive = <800>;
hback-porch = <88>;
hfront-porch = <72>;
hsync-len = <20>;
vback-porch = <23>;
vfront-porch = <15>;
vsync-len = <10>;
de-active = <0>;
vsync-active = <0>;
hsync-active = <0>;
};
port {
panel_lvds1_in: endpoint {
remote-endpoint = <&lvds1_out>;
};
};
};
};
&backlight_ldb {
pwms = <&pwm2 0 250000 0>;
brightness-levels = <0 155 159 174 176 177 179 180 182 183
184 186 187 189 190 191 192 193 194 196
198 199 200 202 203 204 206 207 208 209
210 212 213 214 215 217 218 219 220 221
223 224 225 226 227 228 230 231 232 233
234 235 236 238 239 240 241 242 243 244
245 246 248 249 250 251 252 253 254 255>;
default-brightness-level = <35>;
status = "okay";
};
/* MIPI-DSI */
&lcdif1 {
status = "okay";
};
/* LVDS */
&lcdif2 {
status = "okay";
};
/* HDMI */
&lcdif3 {
status = "disbled";
};
&ldb_phy {
status = "okay";
};
&ldb {
status = "okay";
/* DSI_A */
lvds-channel@0 {
fsl,data-mapping = "spwg";
fsl,data-width = <24>;
status = "disabled";
port@1 {
reg = <1>;
lvds0_out: endpoint {
remote-endpoint = <&panel_lvds0_in>;
};
};
};
/* DSI_B */
lvds-channel@1 {
fsl,data-mapping = "spwg";
fsl,data-width = <24>;
status = "okay";
port@1 {
reg = <1>;
lvds1_out: endpoint {
remote-endpoint = <&panel_lvds1_in>;
};
};
};
};
&mipi_dsi {
status = "okay";
};

Display More

Beim Erstellen treten folgende Warnungen auf:

Code

[developer@f-s-development-machine F+S]$ dtc -O dtb -b 0 -o $DST $TMP
picocoremx8mp-Single.dtb: Warning (unit_address_vs_reg): Node /power-domains/power-domain@14 has a unit name, but no reg property
picocoremx8mp-Single.dtb: Warning (unit_address_vs_reg): Node /soc@0/bus@32c00000/mipi_dsi@32e60000/port@0 has a unit name, but no reg property
picocoremx8mp-Single.dtb: Warning (unit_address_vs_reg): Node /soc@0/bus@32c00000/ldb@32ec005c has a unit name, but no reg property
picocoremx8mp-Single.dtb: Warning (unit_address_vs_reg): Node /soc@0/bus@32c00000/hdmi@32fd8000/port@0 has a unit name, but no reg property
picocoremx8mp-Single.dtb: Warning (unit_address_vs_reg): Node /soc@0/bus@32c00000/phy@32ec0128 has a unit name, but no reg property
picocoremx8mp-Single.dtb: Warning (unit_address_vs_reg): Node /mix_gpu_ml has a reg or ranges property, but no unit name
picocoremx8mp-Single.dtb: Warning (unit_address_format): Node /reserved-memory/rpmsg@0x55800000 unit name should not have leading "0x"
picocoremx8mp-Single.dtb: Warning (avoid_unnecessary_addr_size): unnecessary #address-cells/#size-cells without "ranges" or child "reg" property in /regulators
picocoremx8mp-Single.dtb: Warning (alias_paths): aliases property name 'mipi_dsi' is not valid
picocoremx8mp-Single.dtb: Warning (alias_paths): aliases property name 'ldb_phy' is not valid
picocoremx8mp-Single.dtb: Warning (alias_paths): aliases property name 'snvs_rtc' is not valid

Display More

DMESG gekürzt:

Code

Linux version 5.4.70 (oe-user@oe-host) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Mon Jun 20 13:12:51 UTC 2022
Machine model: F&S PicoCoreMX8MP
imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
mc: Linux media interface: v0.10
videodev: Linux video capture interface: v2.00
imx8-pcie-phy 32f00000.pcie-phy: failed to get imx pcie phy clock
i2c /dev entries driver
ledtrig-cpu: registered to indicate activity on CPUs
EINJ: ACPI disabled.
i.MX8MP clock driver probe done
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.
imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops)
imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200
imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19
imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops)
libphy: stmmac: probed
[drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 0
i2c i2c-0: IMX I2C adapter registered
i2c i2c-1: IMX I2C adapter registered
i2c i2c-2: IMX I2C adapter registered
i2c i2c-3: IMX I2C adapter registered
pca9450 4-0025: Device ID=0x30
pca9450 4-0025: gpio_intr = 115
pca9450 4-0025: chip_irq=189
...
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.
imx6q-pcie 33800000.pcie: PLL REF_CLK is used!.
imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
imx6q-pcie 33800000.pcie: PCIe PHY PLL clock is locked.
imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops)
imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200
imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19
imx6q-pcie 33800000.pcie: PCIe PLL locked after 0 us.
imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops)
...
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.
imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops)
imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops)
imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200
imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19
imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops)
imx-drm display-subsystem: bound 32c00000.bus:ldb@32ec005c (ops imx8mp_ldb_ops)
[drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1
Console: switching to colour frame buffer device 160x50
imx-drm display-subsystem: fb0: imx-drmdrmfb frame buffer device

Display More

Es taucht ein Framebuffer auf mit den korrekten Parametern:

Code

root@fsimx8mp:~# fbset
mode "1280x800"
geometry 1280 800 1280 800 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode

Bild wird aber keines ausgegeben.
Weder mit cat /dev/urandom > /dev/fb0 noch wenn ein QT Beispiel wie z.B. /usr/share/examples/gui/analogclock gestartet wird.

qtdiag liefert folgendes:

Code

root@fsimx8mp:~# qtdiag
QOpenGLFramebufferObject: Framebuffer incomplete attachment.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
Failed to create Vulkan instance: -9
Failed to create platform Vulkan instance
Failed to create Vulkan instance: -9
Failed to create platform Vulkan instance
Vulkan instance is not valid
Qt 5.15.0 (arm64-little_endian-lp64 shared (dynamic) release build; by GCC 9.2.0) on "wayland"
OS: F&S i.MX Release Distro 5.4-zeus (zeus) [linux version 5.4.70]
Architecture: arm64; features: Neon
Environment:
QT_QPA_PLATFORM="wayland"
Features: QT_NO_EXCEPTIONS QT_NO_SESSIONMANAGER
File selectors (increasing order of precedence):
C unix linux fus-imx-wayland
Platform capabilities: ThreadedPixmaps OpenGL ThreadedOpenGL BufferQueueingOpenGL MultipleWindows NonFullScreenWindows NativeWidgets WindowManagement RasterGLSurface
...
Screens: 1, High DPI scaling: inactive
# 0 "LVDS-1" Depth: 32 Primary: yes
Manufacturer: unknown
Model: unknown
Serial number:
Geometry: 1280x800+0+0 Available: 1280x800+0+0
Physical size: 216x135 mm Refresh: 58.478 Hz Power state: 0
Physical DPI: 150.519,150.519 Logical DPI: 96,96 Subpixel_None
DevicePixelRatio: 1 Pixel density: 1
Primary orientation: 2 Orientation: 2 Native orientation: 0 OrientationUpdateMask: 0
LibGLES Vendor: Vivante Corporation
Renderer: Vivante GC7000UL
Version: OpenGL ES 3.1 V6.4.3.p1.305572
Shading language: OpenGL ES GLSL ES 3.10
Format: Version: 3.1 Profile: 0 Swap behavior: 0 Buffer size (RGBA): 8,8,8,8
Unable to create a Vulkan instance, error code is-9

Display More

Ist das ein Problem mit dem Devicetree oder müssen spezielle Treiber aktiviert werden?

Vielen Dank,

Benni.

Posts by Konzept

LVDS-Display PicoCore MX8MP-V2-LIN HW-Rev. 1.0 vs Rev 1.1

LVDS-Display PicoCore MX8MP-V2-LIN HW-Rev. 1.0 vs Rev 1.1

Hardware Documentation PicoCore™MX8MP for HW Revision 1.1

QT5 Crosscompile MX8MP Yocto

QT5 Crosscompile MX8MP Yocto

PicoCoreMX8MP - LVDS Display

PicoCoreMX8MP - LVDS Display