mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: command bootu to start kernel
Date: Wed, 27 Oct 2010 15:54:38 +0200	[thread overview]
Message-ID: <20101027135438.GL6017@pengutronix.de> (raw)
In-Reply-To: <201010271533.15954.jbe@pengutronix.de>

On Wed, Oct 27, 2010 at 03:33:15PM +0200, Juergen Beisert wrote:
> Belisko Marek wrote:
> > I have mini2440 board with barebox running from RAM.
> > I try to start uImage kernel for that platform but I'm little bit
> > confused how to do it.
> >
> > I do tftp uImage and the bootu uImage but it always hangs :
> >
> > commandline: console=ttySAC0,115200
> > arch_number: 1999
> >
> > I track down that theKernel pointer point to 0xffffffff (memmap return
> > (void*)-1) which is obviously wrong.
> > If I understand correctly bootu function take first parameter and try to
> > open a file and memmap. If file isn't opened successfully then convert
> > string address which is then taken for
> > theKernel pointer.
> >
> > Is this correct procedure or do I something wrong?
> 
> Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do not 
> work.

bootz is for starting zImages. At least this command has a convenient
name :)
bootz should work on your system aswell. If not, please complain loudly.
bootu is a bit tricky though. To start a raw linux image it has to be
copied to the exact address is is expected to run, for most boards this
is start of sdram + 0x8000, but this may differ on some boards (it's
basically PHYS_OFFSET + TEXT_OFFSET in the kernel)

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 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:[~2010-10-27 13:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 12:42 Belisko Marek
2010-10-27 13:33 ` Juergen Beisert
2010-10-27 13:54   ` Sascha Hauer [this message]
2010-10-27 14:03     ` Belisko Marek
2010-10-27 14:38     ` Juergen Beisert
2010-10-29  6:08       ` Belisko Marek
2010-10-29  7:49         ` Belisko Marek
2010-10-29  8:04           ` Marc Reilly
2010-10-29  8:20             ` Belisko Marek
2010-10-29  8:34               ` Baruch Siach
2010-10-29  8:45                 ` Belisko Marek
2010-10-29  8:50                   ` Marc Kleine-Budde
2010-10-29  9:04                     ` Belisko Marek
2010-10-29  9:12                       ` Marc Kleine-Budde
2010-10-29  9:21                         ` Belisko Marek
2010-10-29  9:26                           ` Marc Kleine-Budde
2010-10-29  9:30                             ` Uwe Kleine-König
2010-10-29  9:31                             ` Belisko Marek
2010-10-29 12:36                               ` Juergen Beisert
2010-11-02 13:53                                 ` Belisko Marek
2010-10-27 13:46 ` 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=20101027135438.GL6017@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.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