All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Mitidieri <carlos.mitidieri@sysgo.com>
To: linux-mips@linux-mips.org
Subject: Re: "Uncompressing Linux at load address"
Date: Mon, 11 Sep 2006 17:25:11 +0200	[thread overview]
Message-ID: <200609111725.12209.carlos.mitidieri@sysgo.com> (raw)
In-Reply-To: <2156B1E923F1A147AABDF4D9FDEAB4CB1727D5@blr-m2-msg.wipro.com>

thanks for commenting
Since my APPRAMBASE in umon is 0xa0300000, I have changed my parametes in a 
way that the kernel would be loaded above that address:

AVAIL_RAM_START=0xb0a00000
AVAIL_RAM_END=0xb0f00000
LOADADDR =0xb0000000

unfortunately, the problem persists, i.e., the systems hangs just after the 
messages:

 zImage: size=680372 base=0xa0300000
loaded at:     A0300000 A03A4000
 zimage at:     A0306180 A03A3EE1
 Uncompressing Linux at load address B0000000

I am pretty sure that the problem relates to where the things are loaded, but 
I don't realize exactly what.



On Monday 11 September 2006 15:55, you wrote:
> I had faced similar issue with AU1100 based boards which also use the
> zImage patch. It turned out to be board initialization issue rather that
> a zImage problem, since after uncompressing the image control is
> transferred to kernel_entry.
>
> Thanks
> Hemanth
>
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Carlos Mitidieri
> Sent: Monday, September 11, 2006 7:00 PM
> To: linux-mips@linux-mips.org
> Subject: "Uncompressing Linux at load address"
>
> Hi,
>
> I am trying to boot a zImage from micromonitor on a csb655 board
> (Au1550 processor).
>
> For that matter, I patched my kernel 2.6.15 with the zImage_2_6_10.patch
> from
> Popov.
>
> In the arch/mips/boot/compressed/au1xxx/Makefile, I have set:
> 	1) RAM_RUN_ADDR=0xa0300000, which is the value got  from the
> umon's
> APPRAMBASE environment variable.
> 	2) AVAIL_RAM_START=0x80500000
>             AVAIL_RAM_END=0x80900000
>      	3) LOADADDR =0x80100000, which is the same value I have set in
> an
> entry for this board in arch/mips/Makefile.
>
> I can compile and link the zImage with home build gcc cross tools, based
> on
> gcc-3.4.4 and glibc-2.3.4 . When the (binary) zImage is decompressed on
> the
> target, I get these messages:
>
> zImage: size=680372 base=0xa0300000
> loaded at:     A0300000 A03A4000
> zimage at:     A0306180 A03A3EE1
> Uncompressing Linux at load address 80100000
>
> and then the target resets.
> This zImage is very small, so the decompressed image is not going beyond
> the
> AVAIL_RAM limits. Would you have any guess on what is going on?
>
> I have looked for this information the list through, but anyone seems to
> have
> had this problem before. Thanks for any comment.

-- 
Carlos Mitidieri
SYSGO AG - Office Ulm
Lise-Meitner-Str. 15
D-89081 Ulm

Tel: +49 731 94683 16
Fax: +49 731 94683 10
Web: www.sysgo.com

Meet us at our next event:

RTS Embedded Systems 2006
April 4-6, 2006
Paris, La Défense
http://www.birp.com/rts

      reply	other threads:[~2006-09-11 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 13:30 "Uncompressing Linux at load address" Carlos Mitidieri
2006-09-11 13:55 ` hemanth.venkatesh
2006-09-11 13:55   ` hemanth.venkatesh
2006-09-11 15:25   ` Carlos Mitidieri [this message]

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=200609111725.12209.carlos.mitidieri@sysgo.com \
    --to=carlos.mitidieri@sysgo.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.