RE: [U-Boot-Users] u-boot ...bootup warning bad crc

Hi All,
thanx all for ur kind help...the problem was neither due to Memory Mapping nor CRC check... I tried the same old routine method of debugging, which is the best... puts( ).. It was all due to the assignment statement in devices_init( ) in devices.c "gd->flags |= "..... which is declared using DECLARE_GLOBAL_DATA_PTR in asm/global_data.h
Well as of now i have commented that, and my board seems to boot fine... But while loading Linux....phew!!! Have a look below...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
:>tftpboot ARP broadcast 1 ARP broadcast 2 TFTP from server 192.168.6.200; our IP address is 192.168.6.221 Filename 'vmlinuz-2.4.4.n2'. Load address: 0x100000 Loading: ################################################################# ################################################################# # done Bytes transferred = 666865 (a2cf1 hex) :>bootm ## Booting image at 00100000 ... Image Name: Linux 2.4.4 (allfs) Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 666801 Bytes = 651.2 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Now my system hangs.....Any guesses guys....????? Again, i have already started looking into to Kernel using grep and xargs......thanx to Jerry and Marius ... thanx again...
adios Sid.

In message 002b01c2fda0$69bd3f00$a606a8c0@siddharth you wrote:
thanx all for ur kind help...the problem was neither due to Memory Mapping nor CRC check... I tried the same old routine method of debugging, which is the best... puts( ).. It was all due to the assignment statement in devices_init( ) in devices.c "gd->flags |= "..... which is declared using DECLARE_GLOBAL_DATA_PTR in asm/global_data.h
Please understand that this assignment is perfectly fine and works without a problem on some 100+ other boards.
Well as of now i have commented that, and my board seems to boot fine...
The important word here is "seems".
But while loading Linux....phew!!! Have a look below...
Please undo the change you made, go back one step and look foir the _real_ cause of your problem.
Wolfgang Denk
participants (2)
-
Siddharth
-
Wolfgang Denk