iMX8MQ custom board flashing issue using UUU utility

[nirmalluhana]

Hello,

Release: Yocto-Sumo (4.14.78_1.0.0_GA)

Board: i.MX8MQ based custom board

We are working on iMX8MQ based custom board and facing issue while flashing image into eMMC using UUU utility on Linux 16.04.

We have followed all the steps as mentioned in this link: Home · NXPmicro/mfgtools Wiki · GitHub to flash the board and logs are attached as below.

U-Boot SPL 2018.03-master_v2018.03+g2b92a49 (Jul 15 2019 - 10:52:27 +0000)
PMIC:  PFUZE100 ID=0x10
DDRINFO: start lpddr4 ddr init
DRAM PHY training for 3200MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 667MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 3200MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from USB SDP
SDP: initialize...
SDP: handle requests...
Downloading file of size 757384 to 0x40400000... done
Jumping to header at 0x40400000
Header Tag is not an IMX image

U-Boot 2018.03-master_v2018.03+g2b92a49 (Jul 15 2019 - 10:52:27 +0000)

CPU:   Freescale i.MX8MQ rev2.0 1300 MHz (running at 800 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 33C
Reset cause: POR
Model: Winsystem i.MX8MQ PICOITX
DRAM:  4 GiB
tcpc_init: Can't find device id=0x50
setup_typec: tcpc init failed, err=-19
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment

Failed (-5)
No panel detected: default to HDMI
Display: HDMI (1280x720)
cdn_api_checkalive: keep-alive counter did not increment for 10us...
HDMI enable failed!
In:    serial
Out:   serial
Err:   serial

 BuildInfo:
  - ATF d6451cc
  - U-Boot 2018.03-master_v2018.03+g2b92a49

Card did not respond to voltage select!
Detect USB boot. Will enter fastboot mode!
Net:   No ethernet found.
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} ${initr;
Hit any key to stop autoboot:  0

## Checking Image at 43800000 ...
Unknown image format!
Run fastboot ...
dev_get_parent_platdata: null device
"Synchronous Abort" handler, esr 0x96000004
elr: 0000000040233d70 lr : 0000000040233d6c (reloc)
elr: 00000000fff5bd70 lr : 00000000fff5bd6c
x0 : d503201fd503201f x1 : 00000000308600b4
x2 : 00000000fff49b8c x3 : 0000000000000001
x4 : 00000000ffffffff x5 : 0000000000000000
x6 : 00000000fe9201c0 x7 : 00000000ffffffd0
x8 : d503201fd503201f x9 : 0000000000000002
x10: 00000000fff9ebc0 x11: 00000000fecb53e0
x12: 0000000000000002 x13: 0000000000000004
x14: 00000000fe9205ac x15: 0000000000000008
x16: 0000000000001080 x17: 0000000000000000
x18: 00000000fe927da0 x19: 0000000000000000
x20: 0000000000000001 x21: 00000000fe92029f
x22: 0000000000000000 x23: 000000000000001d
x24: 0000000000000002 x25: 0000000000000001
x26: 0000000000000000 x27: 0000000000000000
x28: 00000000fecb5500 x29: 00000000fe9201d0

Resetting CPU ...

resetting ...

After getting above logs boards getting reset and again do the same in a continuous loop.

(NOTE: The same image I tried to flash on iMX8MQ EVK board and flashing done successfully on Linux 16.04)

I have followed below link but found nothing important.

Can UUU be used only on hardware with type C co... | NXP Community - 亚博yobo体育 

As mentioned in the above link is there any type C connector dependency to flash using UUU utility?

Best regards,

Nirmal

[nirmalluhana]

Hello,

Any update on this issue?

Best regards,

Nirmal

[diegoadrian]

Hello,

I apologize for the delay.

The logs are from UUU, or during the booting process?

Regarding the USB, I do not think that there is a problem with the type C connector since UUU make use of USB 2.0.

Furthermore, are you using the same memory devices as our board use? Probably UUU could not find the drivers to download the Linux image.

Best regards,

Diego.

[nirmalluhana]

Hello Diego Adrian Cuevas,

Thanks for your response.

The logs are from UUU utility while board flashing.

This issue is produced on our custom-designed board which has USB 3.0 type A connector.

I am able to flash my custom image on the EVK board but failed on custom-designed board. That's why I have doubt on "type C" connector.

We used a different memory device. But, I was able to flash image before using Mfg tool for L4.9.51 kernel version.

We facing issue on L4.14.78 kernel version using UUU utility.

Best regards,

Nirmal

[nirmalluhana]

Hello Diego Adrian Cuevas,

Any update on this?

Best regards,

Nirmal

[diegoadrian · Accepted solution]

Hello,

I apologize for the delay.

Apparently, there is a dependency for UUU for the USB type C IC. This is because the UUU script, search for the type C controller IC. Did you remove the type C controller from your custom design?

Best regards,

Diego.

[eric_kang]

Dear Diego Adrian Cuevas,
I have the same problem with Nimal, but I can't add the type C controller IC like as Nimal.

So I have to find the method to solve this issue without type C controller IC.

I saw your comments for this problem like as below.
- There is a dependency for UUU for the USB type C IC.
- This is because the UUU script, search for the type C controller IC.

Please let me know how to solve this problem.

Best Regards,
Eric.

[wanpengfu]

Hello Eric,

Do you get the solution that without TYPC-C controller IC?  I have the problem too.

Can you share me the solution if you have ?

Thanks!

BR

Wanpeng

[eric_kang]

Hi Wanpeng,

I didn't find the solution, but I could find the work-around.
When I applied the work-around, the board was booted normally.

Plesae refer to the attached file as reference ONLY.

We have to find the root cause.

I think the problem is relative to the UUU.

Best Regards,

Eric.

[wanpengfu]

Thanks, Eric.

I will try you way and as you said: "find the root cause",  I will do some reaserch about it later. 

BR 

Wanpeng

[nirmalluhana]

Hello Wanpeng Fu & Eric Kang,

This Type C check is mentioned in the imx8mq U-boot source code. So, if we are not using the type C controller then we need to disable this check by changing CONFIG_USB_TCPC macro status to no in imx8mq evk defconfig file. This will resolve the issue of UUU flashing.

 CONFIG_SPL_LOAD_FIT=y
-CONFIG_USB_TCPC=y
+# CONFIG_USB_TCPC is not set
 CONFIG_USB=y

BR

Nirmal

[nirmalluhana]

Hello Diego Adrian Cuevas,

Thanks for your response.

This issue is resolved now and I am able to flash the board using UUU utility.

Best regards,

Nirmal

[eric_kang]

Dear Nirmal,

I have the same problem in i.MX8MM based board.

Could you share your solution if you solve the problem?

I removed the USB PD TCPC PHY IC / PTN5110NHQZ in i.MX8MM-EVK.

The problem was occurred like as you.

tcpc_init: Can't find device id=0x52

Header 1

U-Boot 2018.03-imx_v2018.03_4.14.78_1.0.0_ga+g654088c (Nov 28 2018 - 19:15:55 +0000) CPU:   Freescale i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz) CPU:   Commercial temperature grade (0C to 95C) at 52C Reset cause: POR Model: FSL i.MX8MM EVK board DRAM:  2 GiB tcpc_init: Can't find device id=0x52     // Eric setup_typec: tcpc port2 init failed, err=-19 tcpc_init: Can't find device id=0x50 setup_typec: tcpc port1 init failed, err=-19 MMC:   FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from MMC... Card did not respond to voltage select! *** Warning - No block device, using default environment Failed (-5) No panel detected: default to MIPI2HDMI adv7535_init: Can't find device id=0x3d, on bus 1 Display: MIPI2HDMI (1920x1080) Video: 1920x1080x24 In:    serial Out:   serial Err:   serial  BuildInfo:   - ATF d6451cc   - U-Boot 2018.03-imx_v2018.03_4.14.78_1.0.0_ga+g654088c Card did not respond to voltage select! Detect USB boot. Will enter fastboot mode! Net:   No ethernet found. 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 43800000 ... Unknown image format! Run fastboot ... dev_get_parent_platdata: null device "Synchronous Abort" handler, esr 0x8600000e elr: ffffffff962cf280 lr : 00000000402309e4 (reloc) elr: 0000000014000280 lr : 00000000bdf619e4 x0 : 0000000000000000 x1 : 00000000bc929290 x2 : 0000000000000001 x3 : 0000000014000280 x4 : 0000000000000000 x5 : 0000000000000000 x6 : 00000000bc929220 x7 : 00000000bc929290 x8 : 0000000000000000 x9 : 0000000000000008 x10: 0000000000000000 x11: 00000000bd1225e0 x12: 0000000000000002 x13: 0000000000000004 x14: 00000000bc92960c x15: 0000000000000008 x16: 0000000000001080 x17: 0000000000000000 x18: 00000000bc930da0 x19: 0000000000000000 x20: 0000000000000001 x21: 00000000bc9292ff x22: 0000000000000000 x23: 000000000000001d x24: 0000000000000002 x25: 0000000000000001 x26: 0000000000000000 x27: 0000000000000000 x28: 00000000bd122700 x29: 00000000bc929230 Resetting CPU ... resetting ...      // Eric

[nirmalluhana]

Hello Eric Kang,

This issue is generated due to there is a dependency for UUU for the USB type C IC.

Our hardware team is added type C controller IC on hardware and we are able to flash the board using UUU utility.

Best regards,

Nirmal

[eric_kang]

Hi Nirmal,

Thanks for your rapid response.

I can't add the type C controller IC, so I have to solve this problem by removing the dependency between UUU and USB type C IC.

For this, I'll discuss with Diego Adrian Cuevas.

Anyway thanks for your response.

Best Regards,

Eric.