AnsweredAssumed Answered

Booting always from the secondary image with eMMC v5.0 and imx6 Quad Plus 

Question asked by Corentin Morisse on Apr 11, 2017
Latest reply on May 12, 2017 by Corentin Morisse

Hi Community,

 

 

We have a custom board designed for a imx6DL using a design imx6qsabresd, booting from a eMMC v4.41, which is working fine.

 

We replaced the processor with a imx6 Quad Plus and use a eMMC v5.0

We use Linux 4.1.15 and u-boot 2016.03-r0.

 

But now, when we boot, the board boot from the secondary image almost all the time.

We created a secondary image (the same as the first) and booting from the second IVT table is always successful, so the u-boot and kernel seem correct.

Using Boot_Tester.exe, it show that when it boot from the secondary image the PERSIST_SECONDARY_BOOT is set (src_gpr10 = 0x40000000), but no software code seem to write it :

 

 

 

 

*********************************************

Boot Debug (106.1) for MX6DQ or MX6DQplus

Build: Nov 10 2015, 21:43:53

Freescale Semiconductor, Inc.

*********************************************

 

WDOG Fuse Disabled

 

Boot_cfg_1 = 0x6a

Boot_cfg_2 = 0x50

Boot_cfg_3 = 0x00

Boot_cfg_4 = 0x4b

 

SBMR2 = 0x0a000001

BMOD = 10 Boot from GPIO/Fuses

BT_FUSE_SEL = 0

DIR_BT_DIS = 0

SEC_CONFIG = 01

 

Persistent Reg Value: 0x40000000

 

iROM Version = 0x20

 

USB_ANALOG_DIGPROG = 0x00630100

Device = MX6 Dual/Quad Plus

Si Revision = 2.0

 

Log Entry #0 (0x00010002) BOOTMODE - Internal/Override

Log Entry #1 (0x000200f0) Security Mode - Open

Log Entry #2 (0x00030000) DIR_BT_DIS = 0

Log Entry #3 (0x00040000) BT_FUSE_SEL = 0

Log Entry #4 (0x00050001) Secondary Image Selected

Log Entry #5 (0x00060001) USDHC Boot

Log Entry #6 (0x00070000) Device INIT Call

Log Entry #7 (0x000700f0) Device INIT Pass

Log Entry #8 (0x00080000) Device READ Data Call Address: 0x00000000

Log Entry #10 (0x000800f0) Device READ Data Pass

Log Entry #11 (0x00080000) Device READ Data Call Address: 0x00000320

 

Log Entry #13 (0x000800f0) Device READ Data Pass

Log Entry #14 (0x00090000) HAB Authentication Status Code:

(0x000a0533) Invalid IVT

Log Entry #16 (0x00061004) Recovery Mode ECSPI

Log Entry #17 (0x00080000) Device READ Data Call Address: 0x00000000

Log Entry #19 (0x000800f0) Device READ Data Pass

Log Entry #20 (0x00090000) HAB Authentication Status Code:

(0x000a0533) Invalid IVT

Log Entry #22 (0x000c0000) Serial Downloader Entry

Log Entry #23 (0x00090000) HAB Authentication Status Code:

(0x000a0533) Invalid IVT

Log Entry #25 (0x000d0000) Serial Downloader Call

(0x0091712c) Address: 0x0091712c

 

 

 

 

Anybody have the same behavior and how to manage that ?

Outcomes