IMX8QXP u-boot failed (VService: Connection is failed)

beratovic — Tue, 25 Jan 2022 08:59:04 GMT

Hi everyone,

I'm currently working with the IMX8QXP MEK board. I'm using the file flash.bin from https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX8-Boot-process-and-creating-a-bootable-image/ta-p/1101253 .

When I loaded this image file to the board, this is what I'm faced with:

CPU: Freescale i.MX8QXP revB A35 at 1200 MHz at 18C
Model: Freescale i.MX8QXP MEK
Board: iMX8QXP MEK
Boot: USB
DRAM: 2.8 GiB
imx_vservice_connect: Timeout to connect peer, -110
VService: Connection is failed, ret -110
virt_i2c: Faild to setup vservice
imx_vservice_connect: Timeout to connect peer, -110
VService: Connection is failed, ret -110
virt_i2c: Faild to setup vservice
imx_vservice_connect: Timeout to connect peer, -110
VService: Connection is failed, ret -110
virt_i2c: Faild to setup vservice
setup_typec lookup gpio@1a_7 failed ret = -19
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... MMC: no card present
*** Warning - No block device, using default environment

Failed (-5)
[pcie_ctrlb_sata_phy_init_rc] LNK DOWN 8600000
In: serial
Out: serial
Err: serial

BuildInfo:
- SCFW f83a2bed, SECO-FW 92ef1143, IMX-MKIMAGE dd023400, ATF 1cb68fa
- U-Boot 2018.03

MMC: no card present
Detect USB boot. Will enter fastboot mode!
Net:
Warning: ethernet@5b040000 using MAC address from ROM
eth0: ethernet@5b040000 [PRIME]
Warning: ethernet@5b050000 (eth1) using random MAC address - c2:c6:3a:cc:7a:c5
, eth1: ethernet@5b050000
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;
Hit any key to stop autoboot: 0

## Checking Image at 83100000 ...
Legacy image found
Image Name: fsl-image-mfgtool-initramfs-imx8
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 10798591 Bytes = 10.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Run fastboot ...
dev_get_parent_platdata: null device
"Synchronous Abort" handler, esr 0x96000007
elr: 0000000080045720 lr : 0000000080052358 (reloc)
elr: 0000000087e9b720 lr : 0000000087ea8358
x0 : 0000000000000000 x1 : 0000000000000000
x2 : 000000000000000a x3 : 000000005a060014
x4 : 00000000ffffffff x5 : 0000000000000000
x6 : 0000000000000000 x7 : 0000000000000003
x8 : 0000000000001fc0 x9 : 0000000000000008
x10: 00000000ffffffd0 x11: 0000000085668208
x12: 0000000000001fbe x13: 0000000000000011
x14: 0000000000000001 x15: 0000000000000008
x16: 0000000000002080 x17: 0000000000000000
x18: 0000000085673da8 x19: 0000000000000000
x20: 0000000000000001 x21: 0000000085667dcf
x22: 0000000000000000 x23: 000000000000001d
x24: 0000000000000002 x25: 0000000000000001
x26: 0000000000000000 x27: 0000000000000000
x28: 00000000856b9150 x29: 0000000085667d00

Resetting CPU ...

resetting ...

Any help?

Thanks.

Re: IMX8QXP u-boot failed (VService: Connection is failed)

AldoG — Fri, 28 Jan 2022 00:43:56 GMT

Hello,

This may be caused because the flash.bin may have a hello world example which does not have RPMSG enabled.

In default partitioning I2C1 owner is the M4, so when A35 tries to access through virtual channel fails.

You may refer to the following document which does explain it:

https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/Understand-iMX8QX-Hardware-Partitioning-By-Making-M4-Hello-world/ta-p/1112326?attachment-id=81800

Best regards,
Aldo.

Re: IMX8QXP u-boot failed (VService: Connection is failed)

beratovic — Fri, 28 Jan 2022 13:19:26 GMT

Thanks for your answer, I got the point !

topic Re: IMX8QXP u-boot failed (VService: Connection is failed) in i.MX Processors

IMX8QXP u-boot failed (VService: Connection is failed)

Re: IMX8QXP u-boot failed (VService: Connection is failed)

Re: IMX8QXP u-boot failed (VService: Connection is failed)