From: "\"XOL\" " <xol@mail.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot for EmbeddedPlanet EP862 board
Date: Mon, 21 Jul 2003 20:35:03 +0400 [thread overview]
Message-ID: <E19edct-0004wX-00.xol-mail-ru@f15.mail.ru> (raw)
In-Reply-To: <200307211136.35702.jbeisert@eurodsn.de>
Hello.
I'm trying to run u-boot on EmbeddedPlanet EP862 board.
I based on RPXClassic configuration and made some changes.
For a while without success. The u-boot stuck without any output.
The problem could be because of the way I try to run it.
My board has 16MB flash at
FF00_0000 - FFFF_FFFF
The original EP bootloader is burned at
FF00_0000 - FF08_FFFF
I do not want to erase it and put u-boot instead untill I'm sure
it will work. Otherwise I can loose a board because I have no
BDM to burn it externally.
So I put u-boot at FF80_0000
After board power up it runs EP bootloader which has
interractive commands shell.
I issue
go FF80_0000
to make it branch to specifyed address and thus run u-boot.
At this point the system stuck.
While configuring u-boot I updated FLASH definitions to
FF80_0000 address.
My question is if this approach can work?
What can be a problem of stuck. Does it metter to u-boot
to run on board after power up or reset or to run on already
configured board.
What about epprom and nvram usage. EP boot loader use them for itself
can this false u-boot and stuck him?
Maybe anyone has configuration for EP862 board.
Thank you in advance.
Xol.
next prev parent reply other threads:[~2003-07-21 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200307211005.32005.jbeisert@eurodsn.de>
2003-07-21 8:36 ` [U-Boot-Users] Debugging u-boot with BDI2000 Wolfgang Denk
2003-07-21 9:36 ` Juergen Beisert
2003-07-21 16:35 ` "XOL" [this message]
2003-07-21 17:25 ` [U-Boot-Users] u-boot for EmbeddedPlanet EP862 board Wolfgang Denk
2003-07-22 8:41 ` "XOL"
2003-07-22 9:09 ` 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=E19edct-0004wX-00.xol-mail-ru@f15.mail.ru \
--to=xol@mail.ru \
--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.