From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Kai Volkmar <kai.volkmar@nexgo.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: bootm of 2019.01.0 doesn't load/start images
Date: Wed, 30 Jan 2019 15:35:22 -0800 [thread overview]
Message-ID: <CAHQ1cqG3YLtHG8TsNnEk2Wk4h1KEA1YBzzkXUXPTM6Ffe0mFQw@mail.gmail.com> (raw)
In-Reply-To: <19d6d395-5263-26f0-b940-abbe60a0fc1b@nexgo.de>
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
next prev parent reply other threads:[~2019-01-30 23:35 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 [this message]
2019-01-31 10:47 ` Kai Volkmar
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=CAHQ1cqG3YLtHG8TsNnEk2Wk4h1KEA1YBzzkXUXPTM6Ffe0mFQw@mail.gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=kai.volkmar@nexgo.de \
/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