[U-Boot] u-boot stucks before rellocation

[German Strous]

Hello, 
I'd like to add that I used a JTAG tracer to debug this issue.
The tracer shows me that I have a 'Data Abort'. 
Besides, if I comment out the crc check code, every thing works fine.
Seems like an - unneeded check. 
German.

From: German Strous <germanstrous at yahoo.com>
To: "u-boot at lists.denx.de" <u-boot at lists.denx.de>
Sent: Tuesday, August 16, 2011 11:02 AM
Subject: [U-Boot] u-boot stucks before rellocation

Hello,

I am moving to u-boot version 03.2011.
I have a custom board which has OMAP 3530 (such as beagleboard's).
I'm using NOR flash to store my environment.
The problem is that u-boot checks crc on the env memory, and it falls into 'Data Abort' exception
when trying to do it. 
The crc check happens in 'env_init' function in board_init_f (prioir the rellocation).
What should I do? Is it a bug that the env_init touches the NOR memory prioir the rellocation?
The problem seems to be very similar to the one below.
Thank you very much,
German.
--------------------------------
Hi Michael,

Le 30/01/2011 22:39, Michael Schwingen a écrit :
>Hi,
>
>ist it allowed to call pci_init before relocation?
>
>The code looks like this is not supposed to happen. However, on ARM,
>arm_pci_init (which calls pci_init in turn) is called from
>init_sequence, which happens before relocation.
>
>Am I overlooking some way in which this can actually work? Are there
>boards using this?
>
>If I move pci_init down into board_init_r, I can get PCI working on
>IXP42x, but I am worried if this will cause problems on other boards.
I cannot see a reason why pci_init should not work before relocation as 
long as it does not read or write BSS variables or write non-const 
initialized data -- or overflow the (admittedly limited) C stack.

Are you asking because you discovered that pci_init does not work when 
called from board_init_f? If so, did you determine exactly what goes wrong?

>cu
>Michael
Amicalement,
-- 
Albert.