Forum Discussion
Altera_Forum
Honored Contributor
17 years agoBoot failures when zImage size goes a little over 3MB?
Has anyone else seen an issue like this? A zImage that's 3.0MB (4.6MB uncompressed), the kernel boots without fault. The vmlinux image, when stored as a u-boot uImage also boots. When ...
Altera_Forum
Honored Contributor
17 years agoHi Steve,
did you try to increase the parameter 'Link address offset for booting'? This is from the old NiosWiki: <div class='codetop'>CODE</div><div class='codemain' style='height:200px;white-space:pre;overflow:auto'>If your kernel image is large, you will need to change this config. Processor type and features-->(0x00500000) Link address offset for booting. The zImage load address is ( your sdram base address + link address offset ). The boot loader will uncompress the code to the beginning of sdram. If the uncompressed code is bigger than the default 5M, the two area will overlap and corrupt. The compressed image offset should be adjusted to a higher value when the kernel image is big, eg, large files in romfs dir. You can change this value to about 2/3 of the size of your sdram, eg, 20M out fo 32M. I suggest 2/3 because the gzip compression ratio is about 1:2. The zImage boot loader does not relocate/move itself. </div> We had to increase it to: kernel configuration --> Processor type and features ---> (0x01300000) Link address offset for booting Good luck, Ricardo.