On Fri, Jan 22, 2021 at 10:47:09AM +0100, Andrej Picej wrote: > > > On 22. 01. 21 09:12, Sascha Hauer wrote: > > On Thu, Jan 21, 2021 at 01:23:16PM +0100, Andrej Picej wrote: > > > Hi Sascha, > > > > > > yes, unfortunately we have. We applied this just because we experienced > > > hangs in device booting tests. After this patch the NAND booting problems > > > went away. The booting failed during DMA page reading. > > > I just tested this again and after excluding the changes in this patch the > > > device fails at executing DMA commands. The boot fails in approximately one > > > out of 10 boots. > > > > Where exactly did it hang? In the xloader or later in the real barebox > > driver? > > You probably mean that it hangs in the xloader. Sorry to ask, but I'm > > still trying to understand. That would mean the ROM leaves the GPMI in > > an unusable state and I really wonder how this can happen. > > > > Sascha > > > > Sorry for not being clear enough the first time. You are correct, it hangs > in xloader. > > Maybe some additional information that may be relevant. When we boot barebox > without PBL support barebox boots without problem and NAND behaves normal, > so i guess the ROM sets the GPMI in usable state. > Just a thought: could it be that the problem is in xloader and we somehow > repair or reset the GPMI with this errata fix, so it works with xloader? It could be that the ROM changes parts of the clock tree after having loaded the image from NAND and before it jumps to the payload. It might be that we would have the same problem in the real barebox driver if we wouldn't reconfigure the clocks anyway in the clock driver. Sascha -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
