From: Wolfgang Wegner <wolfgang@leila.ping.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot (porting) problem on MCF5445x board
Date: Thu, 14 Jan 2010 17:53:07 +0100 [thread overview]
Message-ID: <20100114165307.GE4092@leila.ping.de> (raw)
In-Reply-To: <20100114161533.GD4092@leila.ping.de>
Sorry for another self-followup...
With the modified linker script, I already have a failure in
board.c/board_init_f():
(gdb) break board.c:249
Breakpoint 1 at 0x4002089e: file board.c, line 249.
(gdb) c
Continuing.
Breakpoint 1, board_init_f (bootflag=0) at board.c:249
249 memset ((void *) gd, 0, sizeof (gd_t));
(gdb) n
252 if ((*init_fnc_ptr)() != 0) {
(gdb) print init_fnc_ptr
$1 = (init_fnc_t **) 0x40040000
(gdb) print init_sequence
$2 = {0x40033aca <get_clocks>, 0x4002e22e <env_init>,
0x400205ca <init_baudrate>, 0x40026ad2 <serial_init>,
0x4002ce4e <console_init_f>, 0x40030262 <display_options>,
0x400338e8 <checkcpu>, 0x4002ff80 <checkboard>, 0x40020596 <init_func_i2c>,
0x4002056c <init_func_spi>, 0x40020510 <init_func_ram>, 0}
(gdb) print *init_fnc_ptr
$3 = (init_fnc_t *) 0x1010101
(gdb) s
[gdb hangs here, does not reach get_clocks()]
The addresses from "print init_sequence" correspond to those found in
u-boot.map. I have to admit I am a bit puzzled by the behaviour of gdb
when printing pointers (did not use it for some years now...), but to
me the init_fnc_ptr looks ... weird. And somehow truncated (?) like the
fmt string in the debugged printf() from the last mail. I tried disabling
the cache which was formerly enabled already in cpu_init_f(), but this
did not change anything.
Have to give up for today, hopefully I see more clearly next morning.
Regards,
Wolfgang
next prev parent reply other threads:[~2010-01-14 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 14:33 [U-Boot] U-Boot (porting) problem on MCF5445x board Wolfgang Wegner
2010-01-14 16:15 ` Wolfgang Wegner
2010-01-14 16:53 ` Wolfgang Wegner [this message]
2010-01-19 13:17 ` [U-Boot] Solved: " Wolfgang Wegner
2010-01-19 14:04 ` 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=20100114165307.GE4092@leila.ping.de \
--to=wolfgang@leila.ping.de \
--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