On Wed, Jan 30, 2019 at 11:26 AM Kai Volkmar <kai.volkmar@xxxxxxxx> wrote: > > Hi everyone, > > I tried to renew the barebox of an EDB9302 by 2019.01.0. > I used to load the new image by bootm command of the old version which > worked fine in at least 2018.01.0: > > Loading ARM barebox image 'barebox.bin' > commandline: <NULL> > aÿch_number: 538 > > 2019.01.0's bootm recognizes the file type but fails afterwards with > > Loading ARM barebox image 'barebox.bin' > handler failed with: Function not implemented > > . > > I'm not able to boot zImages by 2019.01.0's bootm as well which worked > with 2018.01.0 so I assume bootm is broken anywere between 2018.01.0 and > 2019.01.0. > > Anyway, it is possible to boot zImages by bootz. > > Could you please point me in the right direction - I'm quite new at this > field, maybe I'm mistaking? > > I can try other releases as well if this would be of any help. > Since you know both "good" and "bad" revisions already, doing git bisect would probably simplest, fastest and most straightforward way to figure out which commit broke things on your board. Once offending commit is know it should be much easier to figure out if this is a genuine bug or something else. Hope this helps. Thanks, Andrey Smirnov _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
