bootm of 2019.01.0 doesn't load/start images

bootm of 2019.01.0 doesn't load/start images

[Kai Volkmar]

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.

Best regards,

Kai



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: bootm of 2019.01.0 doesn't load/start images

[Andrey Smirnov]

On Wed, Jan 30, 2019 at 11:26 AM Kai Volkmar <kai.volkmar@nexgo.de> 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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: bootm of 2019.01.0 doesn't load/start images

[Kai Volkmar]

On 31.01.19 00:35, Andrey Smirnov wrote:
> On Wed, Jan 30, 2019 at 11:26 AM Kai Volkmar <kai.volkmar@nexgo.de> 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
>
Hi Andrey,

thanks for your quick answer. I'm not familiar with git bisect yet, but
I just identified the last working and the first defective release.

18.07.2 works (as well as 18.07.0 did), 18.08.0 doesn't.

So I assume the relevant change being near

https://git.pengutronix.de/cgit/barebox/commit/?h=v2018.08.0&id=0e8bd85d9b2f981ad24847badda70c73397d8385

I'll try to get an imagination of what's going on but it seems a quit
difficult task for a beginner :-).

Best regards,
Kai




_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: bootm of 2019.01.0 doesn't load/start images

[Roland Hieber]

Hi Kai,

On Thu, Jan 31, 2019 at 11:47:54AM +0100, Kai Volkmar wrote:
> On 31.01.19 00:35, Andrey Smirnov wrote:
> > On Wed, Jan 30, 2019 at 11:26 AM Kai Volkmar <kai.volkmar@nexgo.de> wrote:
> thanks for your quick answer. I'm not familiar with git bisect yet, but
> I just identified the last working and the first defective release.
> 
> 18.07.2 works (as well as 18.07.0 did), 18.08.0 doesn't.

Git bisect does the same as you (pobably manually) did just now, but
more efficiently with a binary search. Here is a short descriptive
chapter in the Git book:

https://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git

-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox