imx8qmmek: Run Sumo image after Zeus mmc update

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

imx8qmmek: Run Sumo image after Zeus mmc update

Jump to solution
578 Views
fabatera
Contributor II

Hi!
After flashing imx8qmmek board with Zeus image built from manifest imx-5.4.70-2.3.1.xml:

 

uuu -b emmc_all imx-boot core-image-minimal-imx8qmmek.wic.bz2

 

Loading a Zeus image, through tftpboot (kernel and dtb), works fine.


But loading a Sumo image, through tftpboot (kernel and dtb), leads to :

 

mmc0: Timeout waiting for hardware interrupt.
[   44.267871] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[   44.274315] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00000002
[   44.280761] mmc0: sdhci: Blk size:  0x00000200 | Blk cnt:  0x00000001
[   44.287206] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000013
[   44.293644] mmc0: sdhci: Present:   0x01fd8a0a | Host ctl: 0x00000011
[   44.300083] mmc0: sdhci: Power:     0x00000002 | Blk gap:  0x00000080
[   44.306518] mmc0: sdhci: Wake-up:   0x00000008 | Clock:    0x000080ff
[   44.312956] mmc0: sdhci: Timeout:   0x0000008f | Int stat: 0x00000000
[   44.319393] mmc0: sdhci: Int enab:  0x107f100b | Sig enab: 0x107f100b
[   44.325831] mmc0: sdhci: AC12 err:  0x00000000 | Slot int: 0x00000502
[   44.332271] mmc0: sdhci: Caps:      0x07eb0000 | Caps_1:   0x8000b407
[   44.338714] mmc0: sdhci: Cmd:       0x0000083a | Max curr: 0x00ffffff
[   44.345152] mmc0: sdhci: Resp[0]:   0x00000900 | Resp[1]:  0xffffffff
[   44.351589] mmc0: sdhci: Resp[2]:   0x320f5903 | Resp[3]:  0x00d07f01
[   44.358026] mmc0: sdhci: Host ctl2: 0x00000000
[   44.362466] mmc0: sdhci: ADMA Err:  0x00000009 | ADMA Ptr: 0xfffff200
[   44.368902] mmc0: sdhci: ============================================
[   44.375451] mmc0: error -110 whilst initialising MMC card

 

The same procedure, but on a board flashed with Sumo image, used to work fine.

Could it be a uboot/kernel Zeus/Sumo incompatibility?

Thanks!

0 Kudos
1 Solution
571 Views
igorpadykov
NXP Employee
NXP Employee

Hi fabatera

 

>Could it be a uboot/kernel Zeus/Sumo incompatibility?

 

in general yes, as each uboot/linux versions should be formally aligned as

described in Release Notes document on linux documentation link

https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

Also it is necessary to follow sect.1.2 System Controller Firmware (SCFW) Requirements

i.MX 8QuadMax Automotive and Infotainment Applications Processors

 

Best regards
igor

View solution in original post

0 Kudos
1 Reply
572 Views
igorpadykov
NXP Employee
NXP Employee

Hi fabatera

 

>Could it be a uboot/kernel Zeus/Sumo incompatibility?

 

in general yes, as each uboot/linux versions should be formally aligned as

described in Release Notes document on linux documentation link

https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

Also it is necessary to follow sect.1.2 System Controller Firmware (SCFW) Requirements

i.MX 8QuadMax Automotive and Infotainment Applications Processors

 

Best regards
igor

0 Kudos