[U-Boot] {Spam?} u-boot relocation

Marcel korgull at home.nl
Thu Dec 30 23:34:50 CET 2010


On Thursday, December 30, 2010 08:38:36 pm Marcel wrote:
> On Tuesday, December 28, 2010 05:48:20 pm Simon Glass wrote:
> > Hi,
> > 
> > (Is there documentation about this somewhere? - I couldn't find it). I
> > assume your board is hanging during relocation.
> > 
> > You could try putting this function back (but without the __ prefix)
> > 
> > void dram_init_banksize(void)
> > {
> > 
> >        gd->bd->bi_dram[0].start = CONFIG_SYS_SDRAM_BASE;
> >        gd->bd->bi_dram[0].size =  gd->ram_size;
> > 
> > }
> 
> Unfortunately no change by doing this, but thanks for the suggestion.

I tried gdb, but the output doesn't get me much further. It detects an infinite 
loop, but 

BFD: /arm/u-boot-usb/u-boot: invalid string offset 37 >= 0 for section `'
BFD: /arm/u-boot-usb/u-boot: invalid string offset 1 >= 0 for section `'
BFD: /arm/u-boot-usb/u-boot: invalid string offset 20 >= 0 for section `'
BFD: /arm/u-boot-usb/u-boot: invalid string offset 82 >= 0 for section `'
BFD: /arm/u-boot-usb/u-boot: invalid string offset 67 >= 0 for section `'
BFD: /arm/u-boot-usb/u-boot: invalid string offset 32 >= 0 for section `'
BFD: /arm/u-boot-usb/u-boot: invalid string offset 53 >= 0 for section `'
Remote debugging using localhost:65501
_start () at start.S:56
56              b       reset
Current language:  auto; currently asm
(gdb) c
Continuing.
_start () at start.S:56
56              b       reset
Infinite loop detected       
(gdb)

I have no cpu_init_f, is this normal ?

(gdb) b board_init_f
Breakpoint 1 at 0xe20: file board.c, line 283.
(gdb) b cpu_init_f
Function "cpu_init_f" not defined.
Make breakpoint pending on future shared library load? (y or [n]) n

Regards,
Marcel


More information about the U-Boot mailing list