From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Wegner Date: Thu, 14 Jan 2010 17:53:07 +0100 Subject: [U-Boot] U-Boot (porting) problem on MCF5445x board In-Reply-To: <20100114161533.GD4092@leila.ping.de> References: <20100114143353.GC4092@leila.ping.de> <20100114161533.GD4092@leila.ping.de> Message-ID: <20100114165307.GE4092@leila.ping.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.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 , 0x4002e22e , 0x400205ca , 0x40026ad2 , 0x4002ce4e , 0x40030262 , 0x400338e8 , 0x4002ff80 , 0x40020596 , 0x4002056c , 0x40020510 , 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