On Mon, 25 Jan 2016 16:15:02 +0100, Albert ARIBAUD <albert.u.b...@aribaud.net> wrote: > Hello all, > > I /think/ I've got the bug cornered (actually, I had a patch for it > already submitted...) but it is not the only problem with 2016.01 on > Open-RD. > > One, major, other problem is that the 2016.01 Open-RD U-Boot does not > have the "sf" command. Once the boot issue is fixed, you can flash that > U-Boot on the NOR SPI... And then next time you want to flash a new > U-Boot, you're SOL because "sf probe" and "sf write" won't work. :/ > > I am working on reintegrating the "sf" command. Once this is done, I'll > be able to properly test the boot bug and /then/ the U-Boot package can > be updated.
Sorry, I mixed up different boards... no sf command on OpenRD. The fix consists in two patches. I have tested the fix for the boot issue by applying the two patches over the non-functional source code of the package, then re-building for openrd, running the kwb via JTAG and finally flashing it -- all works fine. These two patches /will/ end up in mainline U-Boot (they're actually an ongoing submission of mine), but the first official release where they'll appear will be 2016.04. Meanwhile, I think a new 2016.01 Debian package should be pushed with the two patches added, so that the faulty package gets superseded. How do we proceed from here? Should I post the patches in this discussion? Amicalement, -- Albert.
