[U-Boot] ls1021a: problem with errata A009007
Ran Wang
ran.wang_1 at nxp.com
Thu Jul 12 08:04:51 UTC 2018
Hi Heiko,
> -----Original Message-----
> From: Heiko Schocher [mailto:hs at denx.de]
> Sent: Thursday, July 12, 2018 13:44
> To: Ran Wang <ran.wang_1 at nxp.com>
> Cc: Sriram Dash <sriram.dash at nxp.com>; Rajesh Bhagat
> <rajesh.bhagat at nxp.com>; Suresh Gupta <suresh.bhagat at nxp.com>; u-
> boot at lists.denx.de
> Subject: ls1021a: problem with errata A009007
>
> Hello Ran Wang,
>
> I have ported successfully U-Boot to an ls1021a based board and works nice
> for the HW I have access to.
>
> Now the customer reports problems on his HW with
> SYS_FSL_ERRATUM_A009007
> which is always activated.
>
> Board does not boot, and crashes in erratum_a009007()
>
> (Sorry I have no logs ... nor access to this HW)
>
> Disabling this function, and U-Boot boots ...
>
> Customer states/confirmed me, that he has the same HW ...
>
> On the board USB is not used.
>
> Any ideas hints what can be wrong here?
>
I just re-reverified on latest upstream U-Boot with LS1021ATWR board. It worked fine.
You might need to know what kind of crash they encountered:
1. That erratum workaround programming will happen before the UART print activated, that means
no log will show when writing those register, how does then know the crash?
2. Except erratum programming, USB controller (xHCI) will NOT be initialized untill U-Boot command 'usb start'
is executed. That means if user didn't type 'usb start', USB IP will not begin to work at all.
3. Anyway, this erratum is used to pass USB compliance test only, you could disable this workaround
on your board if you don't any USB issue on normal use case, I think it's fine.
Regard,
Ran
> Thanks in advance.
>
> bye,
> Heiko
> --
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-52 Fax: +49-8142-66989-80 Email: hs at denx.de
More information about the U-Boot
mailing list