All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sharad P. Katti <sharad.katti@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot for pxa255
Date: Mon, 6 Dec 2004 18:21:38 +0530	[thread overview]
Message-ID: <eae046ff04120604512f2fc069@mail.gmail.com> (raw)
In-Reply-To: <41B44108.6030702@gmx.net>

Hi,

Since I dont have the BDI connection interface,
I cannot debug the kernel, the board is of XSCALE arch,
and has 32MB RAM, and i've given TEXT_BASE as 0xA07E0000,
which is inside the 32MB, and I have put the kernel as uncompressed,
and the XIP patch is already applied for that.(I'm using MVLinux 2.4.20)

I have given the entry point to the kernel as 0x00021000, 
and the load address is 0x00020000, and then wrote the resulting
img to the flash,

options to the mkimage that i have given are,

#mkimage -n "newImg" -A arm -O linux -T kernel\
-C none -e 0x00021000 -a 0x00020000 -d zImage zImage.bin

once I boot from the target, i'm able to see the mesgs that display
the header contents, and it shows the entry point address also.


Since as I mentioned, i dont have the option to connect the BDI,
to my target board, how can i go about this.

best regards,
-- 
Sharad P.Katti

  reply	other threads:[~2004-12-06 12:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30  8:58 [U-Boot-Users] u-boot for pxa255 Sharad P. Katti
2004-11-30  9:28 ` Wolfgang Denk
2004-11-30 10:39   ` Sharad P. Katti
2004-11-30 11:47     ` Simon Sudler
2004-12-04  4:54       ` Sharad P. Katti
2004-12-06 11:22         ` Simon Sudler
2004-12-06 12:51           ` Sharad P. Katti [this message]
2004-12-06 15:36             ` Wolfgang Denk
2004-12-06 16:27             ` Simon Sudler
2004-11-30 11:55     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-10-27 16:35 [U-Boot-Users] U-boot " swamy
2004-10-27 18:47 ` Wolfgang Denk

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=eae046ff04120604512f2fc069@mail.gmail.com \
    --to=sharad.katti@gmail.com \
    --cc=u-boot@lists.denx.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 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.