public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] bl cpu_init_f jumps to an wrong point.
Date: Wed, 04 Jan 2006 09:10:28 -0500	[thread overview]
Message-ID: <43BBD754.3060304@smiths-aerospace.com> (raw)
In-Reply-To: <7a2ed4090601040531g5d2c63abpb82b78557b634af0@mail.gmail.com>

Nekto Peresmeshnik wrote:
> Hello community,
> 
> I've problem with jump to cpu_init_f. I trace the begin of u-boot 
> execution, i.e. assembler code. It is okay, until it achieves the jump 
> to cpu_init_f. Then it jumps to a random point. "Random" means that it 
> is same point for every compilation. After next compilation this point 
> changes randomly.
> 
> The picture is next: in debugger I see that cpu_init_f placed on the 
> address 0xfff06924.
> I see same when I do disassemble the u-boot image.
> 
> Please hint where may I be mistaken?
> 
> The board: custom 8247A based, 2 M. flash.
> Compilation: configured and compiled for 8260. Neither error nor 
> warnings during compilation.
> Toolchain: ELDK version 3.1.1 Build 2005-06-07
> Linux: SuSE 9.3 kernel 2.6.11.4-21.9-default

It undoubtedly is _not_ a random address, it is where the linker placed 
cpu_init_f that u-boot is jumping to.  My guess is that the problem is 
that you didn't program the code where it belongs.  The reset vector is 
getting programmed properly but the code (BR0 flash mapping) is not 
where it is expected by the linker.

Check your configuration, especially where you placed flash in your 
linker control file vs. where flash is on power up vs. where you 
configured BR0/OR0 to point to.

gvb

      reply	other threads:[~2006-01-04 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 13:31 [U-Boot-Users] bl cpu_init_f jumps to an wrong point Nekto Peresmeshnik
2006-01-04 14:10 ` Jerry Van Baren [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=43BBD754.3060304@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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