mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: you xiaojie <84640926@qq.com>
Cc: barebox@lists.infradead.org
Subject: Re: bug report: fail to boot barebox in marvell 6281 board
Date: Thu, 2 Apr 2020 09:41:54 +0200	[thread overview]
Message-ID: <20200402074154.GF27288@pengutronix.de> (raw)
In-Reply-To: <2790507.TRZ85U3XWg@allan-home>

On Thu, Apr 02, 2020 at 03:03:41PM +0800, you xiaojie wrote:
> the debugging message.
> 
> allan@allan-home:/media/allan/c6293bbf-6fa1-49ca-9b01-24855a810e0e/barebox-
> test/barebox$ ./scripts/kwboot -b ./images/barebox-huanshuo-hs50a.img -n 15 -B 
> 115200 -t /dev/ttyUSB0 
> Sending boot message. Please reboot the target...
> Got expected NAKs
> Sending boot image...
>  86 % [......................................................................]
>  89 % [......................................................................]
>  91 % [......................................................................]
>  93 % [......................................................................]
>  96 % [......................................................................]
>  98 % [.............................................]
> [Type Ctrl-\ + c to quit]
> uncompress.c: memory at 0x00000000, size 0x20000000
> uncompress.c: enabling MMU, ttb @ 0x1ffe4000
> uncompress.c: uncompressing barebox binary at 0x010053e0 (size 0x00057dfe) to 
> 0x1fe00000 (uncompressed size: 0x000a4ee0)
> uncompress.c: jumping to uncompressed image at 0x1fe00000
> start.c: memory at 0x00000000, size 0x20000000
> start.c: found DTB in boarddata, copying to 0x1fdfcc40
> start.c: initializing malloc pool at 0x0fefe620 (size 0x0fefe620)
> start.c: starting barebox...
> initcall-> globalvar_init+0x0/0x48

This looks all perfectly fine until here. I have no idea what goes wrong
here. You need a binary.0 file for this board, right? Are you sure that
works? Did you extract it from some working U-Boot?
It might also be a toolchain related issue. Which toolchain are you
using?

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2020-04-02  7:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 16:30 youxiaojie
2020-04-02  7:03 ` you xiaojie
2020-04-02  7:41   ` Sascha Hauer [this message]
2020-04-02  8:02     ` you xiaojie
2020-04-02  9:25       ` Sascha Hauer
2020-04-02 10:58         ` you xiaojie
  -- strict thread matches above, loose matches on Subject: below --
2020-03-31 16:24 you xiaojie
2020-03-31 16:12 you xiaojie
2020-04-01  6:08 ` Sascha Hauer

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=20200402074154.GF27288@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=84640926@qq.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