public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Claudio Scordino <cloud.of.andor@gmail.com>
To: ecos-discuss@sources.redhat.com
Cc: msalter@redhat.com, list@kiekerjan.isdronken.nl
Subject: [ECOS] Re: Re: unable to execute linux kernel with Redboot
Date: Mon, 04 Sep 2006 10:34:00 -0000	[thread overview]
Message-ID: <200609041234.38050.cloud.of.andor@gmail.com> (raw)

On Monday 04 September 2006 12:20, Claudio Scordino wrote:
> >>>>> Jan van de Wijdeven writes:
> >
> > Hi,
> > I'm unable to run a linux kernel from the Redboot bootloader. I'm
> > using a XScale board through a serial port.
> >
> > First I load the zImage into memory with the "load" command. Then I
> > give the "exec" command. This doesn't do anything and I have to reset
> > the board. I've been trying to find a solution and some people speak
> > of an entry point for the linux kernel. My redboot manual states this
> > to be 0xc0008000 for the SA1100, but since this processor is similar
> > to the XScale I tried that one.
> > Here's the command I give:
>
> 0xc0008000 is the kernel entry point, not the zImage entry port. And its
> wrong for XScale.
>
> RedBoot> exec 0xc0008000 -c "console=ttyS0,115200n8"
>
> > Using base address 0x00017c00 and length 0x000b1660
> >
> > Then nothing happens.
>
> No surprise.
>
> > Can anyone tell me what I'm doing wrong? The redboot manual doesn't
> > give me any more information.
>
> You need to find out where the zImage wants to be. This depends on the
> kernel version with later zImage being relocatable. If not relocatable,
> you want to use ZTEXTADDR. ZTEXTADDR is a physical address, so you need
> to convert to virtual address for RedBoot to use for the load command.
> ZTEXTADDR is typically defined in arch/arm/boot/Makefile.
>
> So, assume ZTEXTADDR is 0xA0080000. Just clear the top bits to get the
> virtual address in RedBoot (at least for most XScale boards). In this
> case, 0x80000. Therefore, something like this should work:
>
>   RedBoot> load -r -b 0x80000 zImage
>   RedBoot> exec -b 0x80000 -l 0 -c "console=ttyS0,115200" 0xA0080000
>
> Note that the last part of the exec command is the physical address.
> This should also work for a relocatable zImage.

Hi,

     I'm having the same problem with my IXDP465 board with RedBoot 2.02.

My documentation suggests to use

load -r -v -b 0x01600000 zImage
load -r -v -b 0x00800000 ramdisk.gz

which does not work.

My linux-2.6.x/arch/arm/boot/compressed/Makefile sets ZTEXTADDR to 0, so
based on Mark's instructions, my RedBoot commands would be something like 

RedBoot> load -r -b 0x0000 zImage
RedBoot> exec -b 0x0000 -l 0 -c "console=ttyS0,115200" 0x000000

which is very odd, and probably makes no sense.

Any suggestion is welcome.

Many thanks,

                Claudio

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-09-04 10:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 10:34 Claudio Scordino [this message]
2006-09-04 11:14 ` [ECOS] " Amitesh Singh
     [not found]   ` <200609051509.40563.cloud.of.andor@gmail.com>
2006-09-05 13:51     ` Amitesh Singh
2006-09-05 13:58       ` Claudio Scordino
2006-09-06  6:58         ` [ECOS] little mistake in redboot.cdl? Wang Cui
2006-09-07  5:42           ` [ECOS] How to build a executed-in-flash application? Wang Cui
2006-09-07  7:38             ` Andrew Lunn
2006-09-07  9:35               ` wang cui
2006-09-07  9:43                 ` Andrew Lunn
2006-09-08  2:53                   ` wang cui
2006-09-07 13:38             ` Bart Veer
2006-09-08  1:22               ` wang cui
2006-09-04 15:08 ` [ECOS] Re: Re: unable to execute linux kernel with Redboot Mark Salter
2006-09-05  0:53   ` [ECOS] Multiple code images in flash Laurie Gellatly
2006-09-05  7:37     ` Bart Veer
2006-09-05  8:48       ` Ilija Koco
2006-09-05  9:31         ` Bart Veer
2006-09-05 11:25           ` Laurie Gellatly

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=200609041234.38050.cloud.of.andor@gmail.com \
    --to=cloud.of.andor@gmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=list@kiekerjan.isdronken.nl \
    --cc=msalter@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).