Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Carlos Mitidieri <carlos.mitidieri@sysgo.com>
To: linux-mips@linux-mips.org
Subject: "Uncompressing Linux at load address"
Date: Mon, 11 Sep 2006 15:30:13 +0200	[thread overview]
Message-ID: <200609111530.14447.carlos.mitidieri@sysgo.com> (raw)

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

             reply	other threads:[~2006-09-11 13:30 UTC|newest]

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

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=200609111530.14447.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox