[PATCH V2 1/2] imx: imx8mp_evk: fix boot issue

[Peng Fan]

> Subject: Re: [PATCH V2 1/2] imx: imx8mp_evk: fix boot issue
> 
> Hi Peng,
> 
> On Mon, May 11, 2020 at 3:55 AM Peng Fan <peng.fan at nxp.com> wrote:
> >
> > The u-boot-spl.bin pad with ddr firmware conflicts with the
> > CONFIG_MALLOC_F_ADDR area, the ddr firmware will be overwritten by
> > malloc in SPL stage and cause ddr initialization not able to finish.
> > So update the related addresses to fix the issue.
> >
> > Reported-by: Fabio Estevam <festevam at gmail.com>
> > Signed-off-by: Peng Fan <peng.fan at nxp.com>
> 
> It does allow to boot U-Boot, but 'reset' is broken:
> 
> U-Boot 2020.07-rc1-00001-gaedb60e072-dirty (May 11 2020 - 09:01:16
> -0300)
> 
> CPU:   Freescale i.MX8MP rev1.0 at 1000 MHz
> Reset cause: POR
> Model: NXP i.MX8MPlus EVK board
> DRAM:  6 GiB
> WDT:   Started with servicing (60s timeout)
> MMC:   FSL_SDHC: 1, FSL_SDHC: 2
> Loading Environment from MMC... OK
> In:    serial
> Out:   serial
> Err:   serial
> Net:   No ethernet found.
> Hit any key to stop autoboot:  0
> u-boot=> reset
> resetting ...
> "Synchronous Abort" handler, esr 0x5e000000
> elr: 000000004020011c lr : 00000000402001a8 (reloc)
> elr: 00000000fff6311c lr : 00000000fff631a8
> x0 : 0000000084000009 x1 : 0000000000000000
> x2 : 0000000000000000 x3 : 0000000000000000
> x4 : 0000000000000000 x5 : 0000000000000000
> x6 : 0000000000000000 x7 : 0000000000000000
> x8 : 00000000fdf5e0b0 x9 : 000000000000000c
> x10: 00000000000008d4 x11: 00000000fdf5dbfc
> x12: 00000000000008b5 x13: 0000000000003908
> x14: 00000000fdf5dfa8 x15: 0000000000000002
> x16: 0000000000001080 x17: 0000000000004190
> x18: 00000000fdf62dd0 x19: 00000000ffffffda
> x20: 0000000000000001 x21: 0000000000000000
> x22: 00000000fdf71680 x23: 0000000000000001
> x24: 00000000fffdf924 x25: 0000000000000000
> x26: 0000000000000000 x27: 0000000000000000
> x28: 00000000fdf716c0 x29: 00000000fdf5dd90
> 
> Code: d65f03c0 17ffffc7 ffffffff d4000003 (f94003e4) Resetting CPU ...

U-Boot proper should use ATF to reset. I think it might be
using wdog here.

> 
> Also, could you please make sure it can boot a NXP 5.4.3_2.0.0 kernel?

ok, will give a try.

Thanks,
Peng.

> 
> Thanks