On Wed, Aug 02, 2017 at 10:32:40PM +0200, Sam Ravnborg wrote: > Hi Uwe. > > I havn't looked at it, but it is included in my barebox as I'm using > > 2017.08.0 + some patches. > And I did not expect it to solve your problem, only to give you > inspiration what could be the issue. > > > > > Reading through the patch description, it doesn't match my situation. > OK > > > I'm doing USB-Booting because when I made eMMC work all my available > > remote hands already called it a day. So unless the boot ROM does > > something strange (impossible!) barebox is the first spi user. > > > > What seems to be similar is that TESTREG.TXCNT is != 0. For me this > > smells clk-related. On i.MX6 I recently identified a problem (but didn't > > come around yet to mainline a fix) that might match at least your > > problem. > > > > Can you still reproduce? > We have used the patch from Sascha for a long time now (from before it > hit barebox-next, and on our proprietary IMX6 target we never > saw the SPI related error since. > > Sam > > > How does your clk-tree look like (clk_dump)? > > This is with: > $ version > barebox 2017.03.0-1 #1 Sun May 14 16:17:24 CEST 2017 > + some of our own patches (nothing clk related). Which SoC are you using? Doesn't seem to match my problem. I don't know what Sascha did, I'd route ecspi_root to cko2 and check if there is a clk in the failing situation. (Assuming that pin is accessible on your machine of course.) Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
