>You need to load the >image into memory at a higher address like 0x400000.
Where the initial load address is getting set ? -----Original Message----- From: Dan Malek [mailto:[EMAIL PROTECTED] Sent: Sunday, January 02, 2005 10:33 AM To: Povolotsky, Alexander Cc: 'Jeff Angielski'; 'wd at denx.de'; linuxppc-embedded at ozlabs.org Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ? On Jan 2, 2005, at 12:58 AM, Povolotsky, Alexander wrote: > 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 You are doing this backward. You need to load the image into memory at a higher address like 0x400000. According to this message, you are loading at 0x180000. Don't change the relocation address for the build, just the address where you initially load it into memory. -- Dan -----Original Message----- From: Povolotsky, Alexander Sent: Sunday, January 02, 2005 12:58 AM To: 'wd at denx.de'; 'Jeff Angielski' Cc: linuxppc-embedded at ozlabs.org Subject: RE: inflate returned FFFFFFFD - what does this error exactly mean ? >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 --
