public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: NZG <ngustavson@emacinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] mcf5272 hanging while relocating
Date: Tue, 31 May 2005 16:18:21 -0500	[thread overview]
Message-ID: <200505311618.21651.ngustavson@emacinc.com> (raw)
In-Reply-To: <429CC647.4090606@scottygroup.com>

> > The current 82 code had a lot of problems in
> > the fec, timers, and initialization area. If the 5272 code is in a
> > similar state then you may need to either use a preloader, or start with
> > the patched 5282 base and modify it up to offer similar support to the
> > 5282.
>
> Guess there's some work ahead to get the rest running when u-boot finally
> runs from RAM.
The 82 and 72 are similar in a lot of ways, you may be better off starting 
from the working 82 code.

> I did already do a diff from the EMAC release to the current release
> version 1.1.2. Did you use a CVS version of the yet unreleased version
> 1.1.3 to base your changes on?
Actually Zach started the project, and I got the code from him, but I believe 
he started with 1.1.3.

> No I did not take this part of your code where you copy a small code
> segment to the internal ram which activates the approtiate CSx or internal
> flash. I don't see a need for that. I was woundering why that's really
> needed - at least on the 5282.
When you first boot up, the processor will locate either it's external or 
internal flash at address zero, depending on it's hardware configuration.
The initialization code needs to move the flash, then jump to it.
Of course, once the flash is moved, the jump instruction will disappear if 
your running from flash, causing a trap.
The 5282 port gets around this by writing this small section of code to 
internal RAM and jumping to it first.
This way the flash can be moved without removing the next instruction.
There may be a way around this, maybe relocating the vector table first and 
using the trap to redirect the code or something,  but the situation will 
have to be handled somehow.

If you can do it without writing to the internal RAM, please share with the 
rest of the class!

thx,
NZG.

  reply	other threads:[~2005-05-31 21:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 12:46 [U-Boot-Users] mcf5272 hanging while relocating Friedrich Lobenstock
2005-05-17 12:53 ` Wolfgang Denk
2005-05-17 13:31 ` Zachary Landau
2005-05-30 22:10   ` Friedrich Lobenstock
2005-05-30 22:53     ` Friedrich Lobenstock
2005-05-30 23:10       ` Friedrich Lobenstock
2005-05-31 15:23         ` NZG
2005-05-31 20:17           ` Friedrich Lobenstock
2005-05-31 21:18             ` NZG [this message]
2005-05-31 23:30               ` Friedrich Lobenstock
2005-06-01 14:43                 ` NZG
2005-06-01 23:06                   ` Friedrich Lobenstock

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