mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Kai Volkmar <kai.volkmar@nexgo.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: bootm of 2019.01.0 doesn't load/start images
Date: Thu, 31 Jan 2019 11:47:54 +0100	[thread overview]
Message-ID: <ae549ae2-65a0-f63b-2d52-8c190c90bbb6@nexgo.de> (raw)
In-Reply-To: <CAHQ1cqG3YLtHG8TsNnEk2Wk4h1KEA1YBzzkXUXPTM6Ffe0mFQw@mail.gmail.com>

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

  reply	other threads:[~2019-01-31 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 19:25 Kai Volkmar
2019-01-30 23:35 ` Andrey Smirnov
2019-01-31 10:47   ` Kai Volkmar [this message]
2019-01-31 12:46     ` Roland Hieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ae549ae2-65a0-f63b-2d52-8c190c90bbb6@nexgo.de \
    --to=kai.volkmar@nexgo.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox