imx8mmevk android flashing

cancel
Showing results for 
Search instead for 
Did you mean: 

imx8mmevk android flashing

265 Views
Contributor I

Hi Team

I am trying to flash android on already loaded yocto linux imx8mmevk.

When I try to run the command ./uuu_imx_android_flash.sh -f imx8mm, it repeatedly loops in flashing u-boot.imx

and on the debug console I am getting this error:

U-Boot 2018.03 (Nov 29 2019 - 14:44:32 +0530)

CPU: Freescale i.MX8MM rev1.0 1500 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 54C
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM: 2 GiB
wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x52 retry=0
wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x52 retry=1
wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x52 retry=2
i2c_init_transfer: give up i2c_regs=0x30a30000
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)
In: serial
Out: serial
Err: serial

BuildInfo:
- ATF 84a79ee
- U-Boot 2018.03

Detect USB boot. Will enter fastboot mode!
Net:
Error: ethernet@30be0000 address not set.
No ethernet found.
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
dev_get_parent_platdata: null device
"Synchronous Abort" handler, esr 0x8a000000
elr: ffffffff802cefff lr : 000000004022dda4 (reloc)
elr: ffffffffffffffff lr : 00000000bff5eda4
x0 : 0000000000000000 x1 : 00000000b9f29330
x2 : 0000000000000001 x3 : ffffffffffffffff
x4 : aaaaaaaaaaaaaaaa x5 : 0000000000000010
x6 : 00000000bff5b100 x7 : 00000000bffa17e0
x8 : 00000000ffffffd0 x9 : 0000000000000008
x10: 00000000000000cd x11: 000000000000000d
x12: 0000000000000006 x13: 0000000000000000
x14: 0000000000000000 x15: 00000000bff32388
x16: 0000000000000000 x17: 0000000000000000
x18: 00000000b9f30da8 x19: 00000000b9f29330
x20: 0000000000000001 x21: 00000000b9f2939f
x22: 0000000000000000 x23: 000000000000001d
x24: 0000000000000000 x25: 0000000080000000
x26: 0000000000000000 x27: 00000000b9f35640
x28: 0000000000000000 x29: 00000000b9f292d0

Resetting CPU ...

resetting ...

Requesting help on this! Thanks in advance.

0 Kudos
1 Reply

55 Views
NXP TechSupport
NXP TechSupport

Hello,


It seems that uboot is failing to initialize the type-C in the board,  you can try removing from the defconfig and from the dts file those dependencies:

 

From defconfig:

CONFIG_USB_TCPC = n

 

fsl-imx8mm-evk.dts:

&usbotg1

      {

---       drm_mode= "otg";

---       extcon = <0>, <&typec1_ptn5110>;

---       picophy,pre-emp-curr-control = <3>;

---       picophy,dc-vol-level-adjust = <7>;

          status = "okay";

      };

&usbotg2

      {

---       drm_mode= "otg";

---       extcon = <0>, <&typec2_ptn5110>;

---       picophy,pre-emp-curr-control = <3>;

---       picophy,dc-vol-level-adjust = <7>;    

          status = "okay";

      };

 

Hope this helps,

Regards,

Aldo.

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos