[U-Boot-Users] Unable to boot linux on ARM based board: gunzip hangs

Hi, I am trying to make Linux work on omap 850 based board which has an ARM926EJS. I have u-boot ported and installed on it and minimal linux support for the board is also there. The kernel image is in format expected by u-boot and I have followed all the needed steps like using mkimage etc. While uncompressing the linux image the system hangs, in gunzip function which is defined in inflate.c. No error is returned, it just hangs. I have checked whether the image overwrites itself after uncompression, but it does not since the addresses etc are given appropriately. I am thinking may be the DDR SDRAM might not be initialized properly (like refresh rate etc), but then how come u-boot is running properly?
Any pointers?
-pharaoh.

Hi,
I am trying to make Linux work on omap 850 based board which has an ARM926EJS. I have u-boot ported and installed on it and minimal linux support for the board is also there. The kernel image is in format expected by u-boot and I have followed all the needed steps like using mkimage etc. While uncompressing the linux image the system hangs, in gunzip function which is defined in inflate.c. No error is returned,
One possibility is that you have your sdram not well configured. Do you have a lowlevel debug in linux? Regards Michael

On 5/9/07, Michael Trimarchi trimarchi@gandalf.sssup.it wrote:
Hi,
I am trying to make Linux work on omap 850 based board which has an ARM926EJS. I have u-boot ported and installed on it and minimal linux support for the board is also there. The kernel image is in format expected by u-boot and I have followed all the needed steps like using mkimage etc. While uncompressing the linux image the system hangs, in gunzip function which is defined in inflate.c. No error is returned,
One possibility is that you have your sdram not well configured. Do you have a lowlevel debug in linux? Regards Michael
I dont think so, since I have re-checked it. I tried with a new kernel image and now I am getting gunzip error :
I am making the image as
6# mkimage -A arm -O linux -T kernel -C gzip -a 0x10009000 -n "Kernel Image" -d linux.bin.gz uImage.cc Image Name: Kernel Image Created: Wed May 9 16:02:57 2007 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1172.10 kB = 1.14 MB Load Address: 0x10009000 Entry Point: 0x10009000
and then I do bootm 0x10009000..
Booting image at 10009000 ... Image Name: Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1.1 MB Load Address: 10009000 Entry Point: 10009000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover
Is it because of I am having wrong addresses?
It is a arm 926 based board.

Hi,
Pharaoh . schrieb:
On 5/9/07, Michael Trimarchi trimarchi@gandalf.sssup.it wrote:
Hi,
I am trying to make Linux work on omap 850 based board which has an ARM926EJS. I have u-boot ported and installed on it and minimal linux support for the board is also there. The kernel image is in format expected by u-boot and I have followed all the needed steps like using mkimage etc. While uncompressing the linux image the system hangs, in gunzip function which is defined in inflate.c. No error is returned,
One possibility is that you have your sdram not well configured. Do you have a lowlevel debug in linux? Regards Michael
I dont think so, since I have re-checked it. I tried with a new kernel image and now I am getting gunzip error :
I am making the image as
6# mkimage -A arm -O linux -T kernel -C gzip -a 0x10009000 -n "Kernel Image" -d linux.bin.gz uImage.cc Image Name: Kernel Image Created: Wed May 9 16:02:57 2007 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1172.10 kB = 1.14 MB Load Address: 0x10009000 Entry Point: 0x10009000
and then I do bootm 0x10009000..
Booting image at 10009000 ... Image Name: Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1.1 MB Load Address: 10009000 Entry Point: 10009000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover
Is it because of I am having wrong addresses?
It is a arm 926 based board.
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
I had similar problems on my board. U-Boot work fine, but the Kernel hangs on different places for different images. My fault was the configuration of the row and column address width.
regards, Stefan

On 5/9/07, Stefan Herbrechtsmeier hbmeier@uni-paderborn.de wrote:
Hi,
Pharaoh . schrieb:
On 5/9/07, Michael Trimarchi trimarchi@gandalf.sssup.it wrote:
Hi,
I am trying to make Linux work on omap 850 based board which has an ARM926EJS. I have u-boot ported and installed on it and minimal linux support for the board is also there. The kernel image is in format expected by u-boot and I have followed all the needed steps like using mkimage etc. While uncompressing the linux image the system hangs, in gunzip function which is defined in inflate.c. No error is returned,
One possibility is that you have your sdram not well configured. Do you have a lowlevel debug in linux? Regards Michael
I dont think so, since I have re-checked it. I tried with a new kernel image and now I am getting gunzip error :
I am making the image as
6# mkimage -A arm -O linux -T kernel -C gzip -a 0x10009000 -n "Kernel Image" -d linux.bin.gz uImage.cc Image Name: Kernel Image Created: Wed May 9 16:02:57 2007 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1172.10 kB = 1.14 MB Load Address: 0x10009000 Entry Point: 0x10009000
and then I do bootm 0x10009000..
Booting image at 10009000 ... Image Name: Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1.1 MB Load Address: 10009000 Entry Point: 10009000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover
Is it because of I am having wrong addresses?
It is a arm 926 based board.
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
I had similar problems on my board. U-Boot work fine, but the Kernel hangs on different places for different images. My fault was the configuration of the row and column address width.
regards, Stefan
Hi Stefan,
Can you explain a little more about the configuration of the row and the column address width?

Pharaoh . schrieb:
On 5/9/07, Stefan Herbrechtsmeier hbmeier@uni-paderborn.de wrote:
Hi,
Pharaoh . schrieb:
On 5/9/07, Michael Trimarchi trimarchi@gandalf.sssup.it wrote:
Hi,
I am trying to make Linux work on omap 850 based board which has an ARM926EJS. I have u-boot ported and installed on it and minimal
linux
support for the board is also there. The kernel image is in format expected by u-boot and I have followed all the needed steps like using mkimage etc. While uncompressing the linux image the system hangs, in gunzip function which is defined in inflate.c. No error is returned,
One possibility is that you have your sdram not well configured.
Do you
have a lowlevel debug in linux? Regards Michael
I dont think so, since I have re-checked it. I tried with a new kernel image and now I am getting gunzip error :
I am making the image as
6# mkimage -A arm -O linux -T kernel -C gzip -a 0x10009000 -n "Kernel Image" -d linux.bin.gz uImage.cc Image Name: Kernel Image Created: Wed May 9 16:02:57 2007 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1172.10 kB = 1.14 MB Load Address: 0x10009000 Entry Point: 0x10009000
and then I do bootm 0x10009000..
Booting image at 10009000 ... Image Name: Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1.1 MB Load Address: 10009000 Entry Point: 10009000 Verifying Checksum ... OK Uncompressing Kernel Image ... Error: inflate() returned -3 GUNZIP ERROR - must RESET board to recover
Is it because of I am having wrong addresses?
It is a arm 926 based board.
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
I had similar problems on my board. U-Boot work fine, but the Kernel hangs on different places for different images. My fault was the configuration of the row and column address width.
regards, Stefan
Hi Stefan,
Can you explain a little more about the configuration of the row and the column address width?
I don't know your system. I used a XScale PXA270 with SDRAM and have to set the register for the memory controller. I make a mistake by setting the "Column Address Bits" and "Row Address Bit Count" to wrong values.

In message 61445c750705090341m78f23bb8va6497fa185ac9235@mail.gmail.com you wrote:
6# mkimage -A arm -O linux -T kernel -C gzip -a 0x10009000 -n "Kernel Image" -d linux.bin.gz uImage.cc Image Name: Kernel Image Created: Wed May 9 16:02:57 2007 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 1200234 Bytes = 1172.10 kB = 1.14 MB Load Address: 0x10009000 Entry Point: 0x10009000
^^^^^^^^^^
and then I do bootm 0x10009000..
^^^^^^^^^^
So U-Boot will start uncompressing the image stored at 0x10009000 and store the result at the same address, i. e. it will overwrite the not yet uncompressed code.
You CANNOT so that.
Did you read the FAQs? Especially 14.3.2. ?
Best regards,
Wolfgang Denk
participants (4)
-
Michael Trimarchi
-
Pharaoh .
-
Stefan Herbrechtsmeier
-
Wolfgang Denk