> A lot of '.' and then:
>
> crc error
> -- System halted
> The gunzip function put data from 0x00074C8C to 0x0010CC8C.
> So, what is wrong in my kernel ?
> Why I can't use the original configuration at adress 0x10008000 ?
> Does it mean that i need to remap the DRAM at 0x10000000 before loading the
> kernel image ? It's that possible with Angel ? I don't think so!
Did your kernel ever worked with the board? Did you checked it without
your debug mesgs. ( nothing wrong in doing but just to make sure all the
hardware is intact ). You may even try with linux-2.4.0 with phillip's
patch. I haven't checked my board with 2.4.1 and rmk. ( No time, want to
test it in two days )
As for as I know we dont need to remap dram in to any other location.
B'cos when switched on the angel debug monitor remaps dram on to
0x00000000 onwards and maps angel area ( boot flash etc.) to 0x10000000
onwards. The kernel knows it , and we are downloading the kernel directly
to ram. Once the copying ( Uncompressing ) of kernel is done the the final
work is disabling the MMU which remaps dram to its physical location.
Now it is kernel job to enable MMU and remap dram as it requires.
( Having said all these I also admit that its only from my understanding
and this can be wrong also ;-)
Regards,
_Saran_
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
