public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: DaveKucharczyk <david.kucharczyk@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot stuck after relocation attempt on MX51 board
Date: Tue, 24 Feb 2015 19:19:47 -0700 (MST)	[thread overview]
Message-ID: <1424830787325-206738.post@n7.nabble.com> (raw)

I'm porting U-Boot for an MX51 based board. 

This is the boot sequence with debug on...

U-Boot 2014.07-svn10 (Feb 24 2015 - 15:49:39)

initcall: 9ff85820
U-Boot code: 9FF80000 -> 9FFA6824  BSS: -> 9FFD944C
initcall: 9ff8118c
CPU:   Freescale i.MX51 rev3.0 at 800 MHz
initcall: 9ff858ac
I2C:   ready
initcall: 9ff85894
DRAM:  initcall: 9ff81ff4
initcall: 9ff85a04
Monitor len: 0005944C
Ram size: 10000000
Ram top: A0000000
initcall: 9ff855b0
initcall: 9ff857c8
TLB table from 9fff0000 to 9fff4000
initcall: 9ff855c8
initcall: 9ff8577c
Reserving 357k for U-Boot at: 9ff96000
initcall: 9ff85750
Reserving 1280k for malloc() at: 9fe56000
initcall: 9ff85850
Reserving 88 Bytes for Board Info at: 9fe55fa8
initcall: 9ff855d0
initcall: 9ff8571c
Reserving 216 Bytes for Global Data at: 9fe55ed0
initcall: 9ff856b8
initcall: 9ff855e4
initcall: 9ff859ec
initcall: 9ff85948

RAM Configuration:
Bank #0: 90000000 256 MiB
 
DRAM:  256 MiB
initcall: 9ff8569c
New Stack Pointer is: 9fe55eb0
initcall: 9ff85618
initcall: 9ff85648
Relocation Offset is: 00016000
Relocating to 9ff96000, new gd at 9fe55ed0, sp at 9fe55eb0

And that's where it hangs and resets in a continuous loop. 

I confirmed that the entire init_sequence completed in board_f.c, but never
makes it to board_r.c

So...according to ./arch/arm/lib/crt0.S ...

/* assembly code */

board_init_f          <--we make it out of here

/* assembly code */   <-- stuck somewhere in here

relocate_code           <-- stuck somewhere in here

/* assembly code */   <-- stuck somewhere in here

board_init_r          <--we never make it here

I can't sprinkle any debug statements where it's stuck because it's all
assembly. Before I break out the BDI tomorrow does anyone have any ideas? 

BTW it works on our 512MB board, but not the 256MB board. Thanks.



--
View this message in context: http://u-boot.10912.n7.nabble.com/U-Boot-stuck-after-relocation-attempt-on-MX51-board-tp206738.html
Sent from the U-Boot mailing list archive@Nabble.com.

             reply	other threads:[~2015-02-25  2:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25  2:19 DaveKucharczyk [this message]
2015-02-25 15:49 ` [U-Boot] U-Boot stuck after relocation attempt on MX51 board DaveKucharczyk
2015-02-25 20:40 ` Benoît Thébaudeau
2015-02-25 21:23   ` DaveKucharczyk
2015-02-25 22:05     ` Fabio Estevam
2015-02-25 22:08       ` DaveKucharczyk
2015-02-25 23:56         ` Benoît Thébaudeau
2015-02-26 10:38           ` Albert ARIBAUD
2015-02-26 21:15             ` Benoît Thébaudeau
2015-02-26 14:19           ` DaveKucharczyk
2015-02-26 22:01             ` Benoît Thébaudeau
2015-02-28 16:00               ` Fabio Estevam
2015-02-26 21:10       ` Benoît Thébaudeau
2015-02-28 15:56         ` Fabio Estevam
2015-03-01 15:30           ` Albert ARIBAUD
2015-03-01 18:01             ` Fabio Estevam

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=1424830787325-206738.post@n7.nabble.com \
    --to=david.kucharczyk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox