Colibri iMX8DX 1GB V1.0D continuous booting

Technical Support
1

Stuck with below text and could not able to resolve.
Please find the below error attached text and request your support!

U-Boot 2020.04-5.5.0-devel+git.81bc8894031d (Nov 30 2021 - 11:36:12 +0000)

CPU: NXP i.MX8QXP RevC A35 at 1200 MHz at 44C

DRAM: 1022 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC… OK
In: serial
Out: serial
Err: serial
Model: Toradex Colibri iMX8 DualX 1GB V1.0D, Serial# 14714799

BuildInfo:

  • SCFW 778670e2, SECO-FW 7aeb8423, IMX-MKIMAGE 8947fea3, ATF 835a8f6
  • U-Boot 2020.04-5.5.0-devel+git.81bc8894031d

flash target is MMC:0
Net: eth0: ethernet@5b040000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1…
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1…
Found U-Boot script /boot.scr
5752 bytes read in 27 ms (208 KiB/s)

Executing script at 83200000

Loading DeviceTree: imx8dx-colibri-eval-v3.dtb
126687 bytes read in 17 ms (7.1 MiB/s)
620 bytes read in 19 ms (31.3 KiB/s)
Applying Overlay: colibri-imx8x_parallel-rgb_overlay.dtbo
1498 bytes read in 20 ms (72.3 KiB/s)
Applying Overlay: colibri-imx8x_atmel-mxt-connector_overlay.dtbo
523 bytes read in 17 ms (29.3 KiB/s)
Applying Overlay: display-lt161010_overlay.dtbo
863 bytes read in 13 ms (64.5 KiB/s)
10446704 bytes read in 343 ms (29 MiB/s)
Uncompressed size: 25086464 = 0x17ECA00
Bootargs: root=PARTUUID=19aa7b3f-02 ro rootwait video=imxdpufb5:off video=imxdpufb6:off video=imxdpufb7:off console=null quiet

Flattened Device Tree blob at 83100000

Booting using the fdt blob at 0x83100000
Loading Device Tree to 00000000bd629000, end 00000000bd66afff … OK

Starting kernel …

[ 0.121971] No BMan portals available!
[ 0.123414] No QMan portals available!
[ 0.256299] imx8qxp-lpcg-clk 37620000.clock-controller: failed to get clock parent names
[ 0.433658] mxsfb 5a180000.lcdif: Failed to create outputs
[ 0.815382] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid
[ 0.943503] debugfs: Directory ‘59040000.sai’ with parent ‘imx8qxp-sgtl5000’ already present!
[ 1.170503] imx6q-pcie 5f010000.pcie: ERROR PM_REQ_CORE_RST is still set.
[ 1.198387] imx6q-pcie 5f010000.pcie: PCIe PLL lock timeout
[ 3.749212] atmel_mxt_ts 17-004a: __mxt_read_reg: i2c transfer failed (-5)
[ 3.773533] atmel_mxt_ts 17-004a: mxt_bootloader_read: i2c recv failed (-5)
[ 3.791644] atmel_mxt_ts 17-004a: mxt_bootloader_read: i2c recv failed (-5)
[ OK ] Stopped Hardware RNG Entropy Gatherer Daemon.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
[ OK ] Started Reboot.
[ OK ] Reached target Reboot.
[ 13.516169] reboot: Restarting system

Also, for reference, attaching the working text content!

U-Boot 2020.04-5.5.0-devel+git.81bc8894031d (Nov 30 2021 - 11:36:12 +0000)

CPU: NXP i.MX8QXP RevC A35 at 1200 MHz at 36C

DRAM: 1022 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC… OK
In: serial
Out: serial
Err: serial
Model: Toradex Colibri iMX8 DualX 1GB V1.0D, Serial# 14755421

BuildInfo:

  • SCFW 778670e2, SECO-FW 7aeb8423, IMX-MKIMAGE 8947fea3, ATF 835a8f6
  • U-Boot 2020.04-5.5.0-devel+git.81bc8894031d

flash target is MMC:0
Net: eth0: ethernet@5b040000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1…
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1…
Found U-Boot script /boot.scr
5752 bytes read in 26 ms (215.8 KiB/s)

Executing script at 83200000

Loading DeviceTree: imx8dx-colibri-eval-v3.dtb
126687 bytes read in 18 ms (6.7 MiB/s)
620 bytes read in 19 ms (31.3 KiB/s)
Applying Overlay: colibri-imx8x_parallel-rgb_overlay.dtbo
1498 bytes read in 20 ms (72.3 KiB/s)
Applying Overlay: colibri-imx8x_atmel-mxt-connector_overlay.dtbo
523 bytes read in 17 ms (29.3 KiB/s)
Applying Overlay: display-lt161010_overlay.dtbo
863 bytes read in 13 ms (64.5 KiB/s)
10446704 bytes read in 344 ms (29 MiB/s)
Uncompressed size: 25086464 = 0x17ECA00
Bootargs: root=PARTUUID=9d049b21-02 ro rootwait video=imxdpufb5:off video=imxdpu fb6:off video=imxdpufb7:off console=null quiet

Flattened Device Tree blob at 83100000

Booting using the fdt blob at 0x83100000
Loading Device Tree to 00000000bd629000, end 00000000bd66afff … OK

Starting kernel …

[ 0.121637] No BMan portals available!
[ 0.122818] No QMan portals available!
[ 0.256592] imx8qxp-lpcg-clk 37620000.clock-controller: failed to get clock p arent names
[ 0.434133] mxsfb 5a180000.lcdif: Failed to create outputs
[ 0.814767] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invali d
[ 0.930660] debugfs: Directory ‘59040000.sai’ with parent ‘imx8qxp-sgtl5000’ already present!
[ 1.157778] imx6q-pcie 5f010000.pcie: ERROR PM_REQ_CORE_RST is still set.
[ 1.185648] imx6q-pcie 5f010000.pcie: PCIe PLL lock timeout
[ 3.696595] atmel_mxt_ts 17-004a: __mxt_read_reg: i2c transfer failed (-5)
[ 3.713318] atmel_mxt_ts 17-004a: mxt_bootloader_read: i2c recv failed (-5)
[ 3.752441] atmel_mxt_ts 17-004a: mxt_bootloader_read: i2c recv failed (-5)
[FAILED] Failed to start Start a wayland application.
See ‘systemctl status wayland-app-launch.service’ for details.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes…
[ OK ] Started Update UTMP about System Runlevel Changes.

TDX Wayland with XWayland 5.5.0-devel-20220218133815+build.0 (dunfell) colibri-imx8x-14755421 ttyLP3
Colibri-iMX8X_Reference-Multimedia-Image

2

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hand-shake,

The issue you’re experiencing with the Colibri iMX8 DualX 1GB V1.0D appears to be related to several hardware and software components not functioning as expected during the boot process. The error messages indicate problems with clock sources, PCIe communication, and I2C transfer failures, among others. Here are some steps and considerations to help you troubleshoot and potentially resolve the issue:

  1. Check Power Supply: Ensure that the power supply is stable and meets the module’s requirements. Insufficient power can cause various components to malfunction.

  2. Verify Hardware Connections: Loose or incorrect connections can lead to I2C transfer failures and other communication issues. Double-check all connections, especially those related to the display and any PCIe devices.

  3. Review Device Tree Overlays: The error messages suggest issues when applying device tree overlays. Verify that the overlays applied are compatible with your hardware setup. Incorrect or conflicting overlays can cause the issues you’re seeing.

  4. Update Firmware and Software: Ensure that the U-Boot, Linux kernel, and device tree binaries are up to date. Sometimes, bugs affecting hardware initialization are fixed in newer versions.

  5. PCIe Clock Source: The error imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid suggests a problem with the PCIe clock source configuration. Review the device tree settings related to PCIe to ensure they are correctly configured for your hardware.

  6. I2C Transfer Failures: The I2C transfer failures (atmel_mxt_ts 17-004a: __mxt_read_reg: i2c transfer failed (-5)) might indicate a problem with the touchscreen controller communication. Verify the I2C bus configuration and ensure that the touchscreen controller is correctly initialized.

  7. Kernel Configuration: Some of the errors, like No BMan portals available! and No QMan portals available!, might be related to the kernel configuration, especially for the networking and buffer management features. Review the kernel configuration to ensure that all required drivers and subsystems are enabled.

  8. Debugging and Logs: Enable additional kernel debugging options to gather more detailed logs. This can provide further insights into where the boot process is failing.

  9. Compare Working vs. Non-Working Setups: Since you have provided a working text content for reference, compare the boot process, applied device tree overlays, and kernel command line between the working and non-working setups. Look for

Please, also check if these links can help you solve your problem:

SBOM | Toradex Developer Center.

3

Hi @Jagruthi ,

Please try to re-flash the module using Toradex Easy Installer

4

Re-flashed the module and it is working fine now.Thanks Sahil!

Could you please elaborate what could be the root cause for such text?

Initially, the module worked fine and later started rebooting.
This shows that there might be no issue with the Hardware components and is related to Software.

5

Hi @Jagruthi ,

There is no known issue which ends the module in continuous rebooting condition. So, commenting on the exact reason is not possible at the moment.