unable to load images onto imx8mm-evk

cancel
Showing results for 
Search instead for 
Did you mean: 

unable to load images onto imx8mm-evk

Jump to solution
3,446 Views
Contributor I

I am following instructions in Sect 3.3.1 of Android™ Quick Start Guide, Rev. P9.0.0_1.0.0-ga, 01/2019 and running

the following uuu in Windows10.  I am using the images from : android_p9.0.0_1.0.0-ga_image_8mmevk.tar.gz

On Windows Host side the console shows ...

uuu.exe c:\android_p9.0.0_1.0.0-ga_image_8mmevk\uuu-android-mx8mm-evk-emmc.lst

uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.2.91-0-g3799f4d

Your console don't support VT mode, fail back to verbose mode
Build in config:
        Pctl     Chip            Vid     Pid     BcdVersion
        ==================================================
        SDPS:    MX8QXP          0x1fc9  0x012f  [0x0002..0xffff]
        SDPS:    MX8QM           0x1fc9  0x0129  [0x0002..0xffff]
        SDP:     MX7D            0x15a2  0x0076
        SDP:     MX6Q            0x15a2  0x0054
        SDP:     MX6D            0x15a2  0x0061
        SDP:     MX6SL           0x15a2  0x0063
        SDP:     MX6SX           0x15a2  0x0071
        SDP:     MX6UL           0x15a2  0x007d
        SDP:     MX6ULL          0x15a2  0x0080
        SDP:     MX6SLL          0x1fc9  0x0128
        SDP:     MX7ULP          0x1fc9  0x0126
        SDP:     MXRT106X        0x1fc9  0x0135
        SDP:     MX8MM           0x1fc9  0x0134
        SDP:     MX8MQ           0x1fc9  0x012b
        SDPU:    SPL             0x0525  0xb4a4  [0x0000..0x04ff]
        SDPV:    SPL1            0x0525  0xb4a4  [0x0500..0x9998]
        SDPU:    SPL             0x0525  0xb4a4  [0x9999..0x9999]
        FBK:                     0x066f  0x9afe
        FBK:                     0x066f  0x9bff
        FB:                      0x0525  0xa4a5
        FB:                      0x18d1  0x0d02

Wait for Known USB Device Appear...
New USB Device Attached at 2:6
2:6>Start Cmd:SDP: boot -f u-boot-imx8mm-evk-uuu.imx
6400%2:6>Okay
New USB Device Attached at 2:6
2:6>Start Cmd:SDPU: delay 1000
2:6>Okay
2:6>Start Cmd:SDPU: write -f u-boot-imx8mm-evk-uuu.imx -offset 0x57c00
100%2:6>Okay
2:6>Start Cmd:SDPU: jump
6400%2:6>Okay

When the first FB command in the lst file is executed (FB: ucmd setenv fastboot_dev mmc) the host uuu program just hangs.  It appears that the generic bulk io interface on the mx8mm-evk was not inited as the eval's usb iface on windows host side does not enumerate.

On mx8mm-evk side the debug console shows:

U-Boot SPL 2018.03 (Dec 19 2018 - 17:40:19 +0800)
power_bd71837_init
DDRINFO: start lpddr4 ddr init
DRAM PHY training for 3000MTS
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 3000MTS
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 400MTS
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 100MTS
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 720872 to 0x40400000... done
Jumping to header at 0x40400000
Header Tag is not an IMX image


U-Boot 2018.03 (Dec 19 2018 - 17:40:19 +0800)

CPU:   Freescale i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 41C
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM:  2 GiB
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
Power supply on USB2
TCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
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)
In:    serial
Out:   serial
Err:   serial

 BuildInfo:
  - ATF d6451cc
  - U-Boot 2018.03

Detect USB boot. Will enter fastboot mode!
Net:
Warning: ethernet@30be0000 using MAC address from ROM
eth0: ethernet@30be0000
Card did not respond to voltage select!
Block device mmc 0 not supported
bcb_rw_block, get_block_size return 0
read_bootctl, bcb_rw_block read failed
read command failed
Fastboot: Normal
Boot from USB for uuu
Hit any key to stop autoboot:  0
g_dnl_register: failed!, error: -19
u-boot=>

I have same result if I attempt to use Linux as host.  I also note that if I boot the eval into the u-boot in eMMC that the eval came with and enter:  "fastboot 1" that the usb iface on windows host side does not enumerate. 

0 Kudos
1 Solution
579 Views
NXP TechSupport
NXP TechSupport

Hello John,

      since downloading android and linux images are the same result, I feel the issue should be caused by windows configurations, I have ever tested android 9.0 BSP (including fastboot) on windows 7 64bit and windows 10 64bit for several times. A the beginning, we need to do some necessary configrations for usb driver, like android ADB driver etc.

      I have written for it, recording the full operations for downloading images onto board. see the link, please!

https://community.nxp.com/docs/DOC-342719 

Hope it can help you!

Have a nice day!

Best Regards,

NXP TIC Weidong

View solution in original post

0 Kudos
6 Replies
580 Views
NXP TechSupport
NXP TechSupport

Hello John,

      since downloading android and linux images are the same result, I feel the issue should be caused by windows configurations, I have ever tested android 9.0 BSP (including fastboot) on windows 7 64bit and windows 10 64bit for several times. A the beginning, we need to do some necessary configrations for usb driver, like android ADB driver etc.

      I have written for it, recording the full operations for downloading images onto board. see the link, please!

https://community.nxp.com/docs/DOC-342719 

Hope it can help you!

Have a nice day!

Best Regards,

NXP TIC Weidong

View solution in original post

0 Kudos
579 Views
Contributor I

Thanks Wigros...I can load the board now.

0 Kudos
579 Views
Contributor II

Hello John:

   I have the same issue if I try to use Linux as host to download image. How did you solve it?

U-Boot SPL 2018.03-imx-linux-sumo-ritu+g72bb67f (May 16 2019 - 07:01:38 +0000)
power_bd71837_init
DDRINFO: start lpddr4 ddr init
DRAM PHY training for 3000MTS
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 3000MTS
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 400MTS
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 100MTS
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 1042456 to 0x40400000... done
Jumping to header at 0x40400000
Header Tag is not an IMX image


U-Boot 2018.03-imx-linux-sumo-ritu+g72bb67f (May 16 2019 - 07:01:38 +0000)

CPU: Freescale i.MX8MMQL rev1.0 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 51C
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM: 2 GiB
tcpc_init: Can't find device id=0x52
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-linux-sumo-ritu+g72bb67f

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 0x96000004
elr: 0000000040230944 lr : 0000000040230938 (reloc)
elr: 00000000bdf61944 lr : 00000000bdf61938
x0 : 0000000014000280 x1 : 00000000308900b4
x2 : 00000000bdf52460 x3 : 0000000000000001
x4 : 00000000ffffffff x5 : 0000000000000000
x6 : 00000000bc929220 x7 : 00000000ffffffd0
x8 : 0000000000000000 x9 : 0000000000000008
x10: 0060009000000200 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 ...

U-Boot SPL 2018.03-imx-linux-sumo-ritu+g72bb67f (May 16 2019 - 07:01:38 +0000)

Thanks

0 Kudos
579 Views
Contributor I

Hi Nick,

For me the real issue was not that my windows config was not setup properly but that I was not using the usb3 debug cable that came with the kit between PORT1 on the eval (DEBUG port) and my PC .... it went missing on me for a while and I so tried using two usb cables connected together which prevented the usb on the eval from working properly.  Once I relocated and used the single usb3 debug cable that came with the kit itself then I was able to follow the instructions in Sect 3.3.1 of Android™ Quick Start Guide, Rev. P9.0.0_1.0.0-ga, 01/2019 to get the eval loaded.

-jd  

0 Kudos
579 Views
Contributor III

Can you see this post please? https://community.nxp.com/message/1265552  

0 Kudos
579 Views
NXP TechSupport
NXP TechSupport

OK,Welcome!

0 Kudos