Hello Wolfgang,
Wolfgang Denk wrote:
Dear Albert ARIBAUD,
In message 4CCC1F6C.7040603@free.fr you wrote:
Could people with ARM NAND-based boards on the list test their own board > with Alexander's DEBUG and printf() added, and see what this gives on > their board?
Here the results from tx25:
Thanks for doing this. I also made such a log for Alexander on 27.10.2010 in u-boot%irc.freenode.org (couldn;t find this in the history :-( ) after we foun out, that on his board nand_chip resist on the old address before relocation ...
and I said to him, that it works fine on this board, and ... we came to the opinion, that it maybe is a toolchain issue ... IIRC he uses gcc-4.5x ... and he wanted to try ELDK-4.2 ...
U-Boot 2010.12-rc1-00026-g0c0892b-dirty (Oct 30 2010 - 16:55:43)
U-Boot code: 81200000 -> 812291A0 BSS: -> 812322A0 CPU: Freescale i.MX25 at 399 MHz
monitor len: 000322A0 ramsize: 02000000 TLB table at: 81ff0000 Top of RAM usable for U-Boot at: 81ff0000 Reserving 200k for U-Boot at: 81fbd000 Reserving 1024k for malloc() at: 81ebd000 Reserving 24 Bytes for Board Info at: 81ebcfe8 Reserving 92 Bytes for Global Data at: 81ebcf8c New Stack Pointer is: 81ebcf88 RAM Configuration: Bank #0: 80000000 32 MiB relocation Offset is: 00dbd000 monitor flash len: 000291A0 Now running in RAM - U-Boot at: 81fbd000 NAND: 128 MiB ## nand_chip: 81fe91a0
Yep, that look good, and I don;t think it is a code problem.
Alexander, did you tried (as you thought to do) ELDK-4.2 with gcc-4.2.x ? Are you sure your toolchain works correct with -pie?
bye, Heiko