[U-Boot] Boot failure with a AT91RM9200 based custom board

[U-Boot] Boot failure with a AT91RM9200 based custom board

[Peter Kardos]

Greetings,

I'm looking for a AT91RM9200 specialist as I've got stuck porting board 
support from a old u-boot (v1.1.4) to the latest stable (v2016.07)...

I'm using the at91r9200ek board as a template to get things running...

With the patches i can get to the state below and here the board hangs. 
When patch 0004 is omitted, it seems the board doesn't boot at all (I'm 
basing this assumption on the current consumption of the system).

The console shows the following...
initcall: 1001cce0


U-Boot 2016.07-g95a02a7 (Aug 12 2016 - 01:43:34 +0200)

initcall: 1000b5bc
U-Boot code: 10000000 -> 10030338  BSS: -> 1006B424
initcall: 1000b3b4
initcall: 1000bae8
initcall: 1000b5e8
DRAM:  initcall: 100010b8
initcall: 1000b808
Monitor len: 0006B424
Ram size: 04000000
Ram top: 24000000
initcall: 1000b3dc
initcall: 1000b564
TLB table from 23ff0000 to 23ff4000
initcall: 1000b3f4
initcall: 1000b518
Reserving 429k for U-Boot at: 23f84000
initcall: 1000b4ec
Reserving 384k for malloc() at: 23f24000
initcall: 1000b6e8
Reserving 80 Bytes for Board Info at: 23f23fb0
initcall: 1000b3fc
initcall: 1000b4b8
Reserving 192 Bytes for Global Data at: 23f23ef0
initcall: 1000b440
initcall: 1000b414
initcall: 1000b884
initcall: 1000b7e0
initcall: 1000b738

RAM Configuration:
Bank #0: 20000000 64 MiB

DRAM:  64 MiB
initcall: 1000b424
New Stack Pointer is: 23f23ed0
initcall: 1000b6ac
initcall: 1000b640
Relocation Offset is: 13f84000
Relocating to 23f84000, new gd at 23f23ef0, sp at 23f23ed0

Some detail about the board:
AT91RM9200; external boot from /CS0
64Mbyte SDRAM (32bit)
32Mbyte NOR (16bit)
Micrel KSZ8721

Any ideas, pointers, even flame is appreciated. If more info is needed 
I'm happy to deliver
Thanx in advance.
Cheers, Peter
-------------- next part --------------

[U-Boot] Boot failure with a AT91RM9200 based custom board

[Andreas Bießmann]

Dear Peter,

On 12.08.16 02:24, Peter Kardos wrote:
> Greetings,
> 
> I'm looking for a AT91RM9200 specialist as I've got stuck porting board
> support from a old u-boot (v1.1.4) to the latest stable (v2016.07)...
> 
> I'm using the at91r9200ek board as a template to get things running...

I haven't booted that board for a while ...

> With the patches i can get to the state below and here the board hangs.
> When patch 0004 is omitted, it seems the board doesn't boot at all (I'm
> basing this assumption on the current consumption of the system).

AFAIR the address 0x0 is mapped to the boot source until REMAP (also
depending on the BMS setting). It may be flash for your setup ...
writing the flash with a copy instruction should fail so this could be
the cause why it is not working.

> The console shows the following...
> initcall: 1001cce0
> 
> 
> U-Boot 2016.07-g95a02a7 (Aug 12 2016 - 01:43:34 +0200)
> 
> initcall: 1000b5bc
> U-Boot code: 10000000 -> 10030338  BSS: -> 1006B424
> initcall: 1000b3b4
> initcall: 1000bae8
> initcall: 1000b5e8
> DRAM:  initcall: 100010b8
> initcall: 1000b808
> Monitor len: 0006B424
> Ram size: 04000000
> Ram top: 24000000
> initcall: 1000b3dc
> initcall: 1000b564
> TLB table from 23ff0000 to 23ff4000
> initcall: 1000b3f4
> initcall: 1000b518
> Reserving 429k for U-Boot at: 23f84000
> initcall: 1000b4ec
> Reserving 384k for malloc() at: 23f24000
> initcall: 1000b6e8
> Reserving 80 Bytes for Board Info at: 23f23fb0
> initcall: 1000b3fc
> initcall: 1000b4b8
> Reserving 192 Bytes for Global Data at: 23f23ef0
> initcall: 1000b440
> initcall: 1000b414
> initcall: 1000b884
> initcall: 1000b7e0
> initcall: 1000b738
> 
> RAM Configuration:
> Bank #0: 20000000 64 MiB
> 
> DRAM:  64 MiB
> initcall: 1000b424
> New Stack Pointer is: 23f23ed0
> initcall: 1000b6ac
> initcall: 1000b640
> Relocation Offset is: 13f84000
> Relocating to 23f84000, new gd at 23f23ef0, sp at 23f23ed0

Could you please check, if the RAM initialisation is working properly?
AFAIR there was some problem with the u-boot RAM initialisation for this
board but never fixed (shame on me). Some set of known data and read
back before relocation should do the check.

Andreas

> Some detail about the board:
> AT91RM9200; external boot from /CS0
> 64Mbyte SDRAM (32bit)
> 32Mbyte NOR (16bit)
> Micrel KSZ8721
> 
> Any ideas, pointers, even flame is appreciated. If more info is needed
> I'm happy to deliver
> Thanx in advance.
> Cheers, Peter

[U-Boot] Boot failure with a AT91RM9200 based custom board

[Andreas Bießmann]

Hi Peter,

On 2016-08-17 11:31, Peter Kardos wrote:
> On Mon, Aug 15, 2016 at 10:43 PM, Andreas Bie?mann
> <andreas@biessmann.org> wrote:
> 
>> Dear Peter,
>> 
>> On 12.08.16 02:24, Peter Kardos wrote:

<snip>

>>> RAM Configuration:
>>> Bank #0: 20000000 64 MiB
>>> 
>>> DRAM:  64 MiB
>>> initcall: 1000b424
>>> New Stack Pointer is: 23f23ed0
>>> initcall: 1000b6ac
>>> initcall: 1000b640
>>> Relocation Offset is: 13f84000
>>> Relocating to 23f84000, new gd at 23f23ef0, sp at 23f23ed0
>> 
>> Could you please check, if the RAM initialisation is working
>> properly?
>> AFAIR there was some problem with the u-boot RAM initialisation
>> for this
>> board but never fixed (shame on me). Some set of known data and
>> read
>> back before relocation should do the check.
> 
> Yeah, this is my guess as well, as things seem to work up to this
> point (continue exec from RAM).
> 
> Thanks for the pointer, i'll have a look at the init magic and compare
> it with the old from v1.1.4.

Would be great if you come with a solution, so I could fix the 
at91rm9200ek board too.

> I guess the easiest way would be to mod the relocation routine and
> read back what was written...

sounds good as a quick test

Andreas