Hi, I got confirmation from my board "vendor" that: "The watch dog is enabled by the boot monitor, so it must be handled by the loader and by the kernel too." At this point I do not know the watch dog's time out period. The boot monitor is custom modified (by the board "vendor") pSOS bootloader for which I do not have the code. The compressed kernel image for Linux 2.6 is considerably larger than for Linux 2.4 (which works fine) - perhaps I need to put more watch dog resets into zlib code ... ? - Any advise on where to put those resets, etc. ?
Thanks, Best Regards, Alex -----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 --
