>Try storing the compressed image at a higher address >(like 0x400000 or so).
Originally I had relocation address be 0x00400000; I also tried 0x00500000 and finally 0x00600000 (shown below) - all 3 cases give the same error. loaded at: 00180000 00268160 relocated to: 00600000 006E8160 board data at: 006E6124 006E6140 relocated to: 0060509C 006050B8 zimage at: 0060587D 006E5F82 avail ram: 006E9000 02000000 Linux/PPC load: console=ttyCPM0 panic=3 root=/dev/ram Uncompressing Linux... in gzip after zalloc after zlib_inflateInit2 after zlib_inflate inflate returned FFFFFFFD exit -----Original Message----- From: wd at denx.de [mailto:[EMAIL PROTECTED] Sent: Thursday, December 30, 2004 6:09 PM To: Povolotsky, Alexander Cc: linuxppc-embedded at ozlabs.org Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ? Hi Alex, in message <313680C9A886D511A06000204840E1CF0A647439 at whq-msgusr-02.pit.comms.marconi.co m> you wrote: > > After few days of wondering through debugging (and with > great help) I fixed (by inserting watch dog resets into > beginning of while loops in zlib functions) my first problem > - strange reboot failures during decompression of You know why I recommended U-Boot :-) > Now I am getting "controlled" failure (during the same > decompression as described above): > > I_BAD > return Z_DATA_ERROR > after zlib_inflate > inflate returned FFFFFFFD > exit > > what does this error exactly mean ? Most probably it means that the areas where the compressed image is stored and to where you copy the uncompressed code to are over-lapping. Try storing the compressed image at a higher address (like 0x400000 or so). Best regards, Wolfgang Denk -----Original Message----- From: Nigel Cunningham [mailto:[EMAIL PROTECTED] Sent: Thursday, December 30, 2004 5:45 PM To: Povolotsky, Alexander Cc: linuxppc-embedded at ozlabs.org; linuxppc-embedded-bounces at ozlabs.org Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ? Hi. linuxppc-embedded-bounces at ozlabs.org wrote on 31/12/2004 09:27:53: > Hi, > > After few days of wondering through debugging (and with > great help) I fixed (by inserting watch dog resets into > beginning of while loops in zlib functions) my first > problem -strange reboot failures during decompression of > the kernel image by the bootloader. > However my luck expired beyond this fix so far ... ;-). > Now I am getting "controlled" failure (during the same > decompression as described above): > > I_BAD > return Z_DATA_ERROR > after zlib_inflate > inflate returned FFFFFFFD > exit > > what does this error exactly mean ? Going from include/linux/zlib.h, it is a data error: your compressed stream has somehow been corrupted? Regards, Nigel --
