XUPV2P, Kernel 2.6.17 boot problem

XUPV2P, Kernel 2.6.17 boot problem

[Benjamin Heyne]

Dear all,
I am currently trying to get the 2.6.17.1 Linux kernel
running on the Xilinx Virtex. I have the 2.4 kernel up
and running - No problems there...

But when using the 2.6 kernel (have copied xparameters file,
patched for using TEMAC driver) with the same hardware configuration
the following happens:


loaded at:     00400000 0061813C
board data at: 00616124 0061613C
relocated to:  00405148 00405160
zimage at:     0040585D 00615F42
avail ram:     00619000 20000000

Linux/PPC load: console=ttyS0,9600.....

Uncompressing Linux...inflate returned FFFFFFFB
exit


Now, I am not really sure where to start searching for the bug
(I just want to implement some drivers - not the kernel itself ;-).
The zImage.elf file is about 2MB large. Did anyone encounter
a similar error? Does anyone have some hints where to
look at for debugging, or what might be wrong?

Thanks in advance
Best regards
-- 
Benjamin Heyne

Re: XUPV2P, Kernel 2.6.17 boot problem

[Ameet Patil]

Try this if it helps!

http://www.linux.get2knowmore.com/

-Ameet

Benjamin Heyne wrote:
> Dear all,
> I am currently trying to get the 2.6.17.1 Linux kernel
> running on the Xilinx Virtex. I have the 2.4 kernel up
> and running - No problems there...
> 
> But when using the 2.6 kernel (have copied xparameters file,
> patched for using TEMAC driver) with the same hardware configuration
> the following happens:
> 
> 
> loaded at:     00400000 0061813C
> board data at: 00616124 0061613C
> relocated to:  00405148 00405160
> zimage at:     0040585D 00615F42
> avail ram:     00619000 20000000
> 
> Linux/PPC load: console=ttyS0,9600.....
> 
> Uncompressing Linux...inflate returned FFFFFFFB
> exit
> 
> 
> Now, I am not really sure where to start searching for the bug
> (I just want to implement some drivers - not the kernel itself ;-).
> The zImage.elf file is about 2MB large. Did anyone encounter
> a similar error? Does anyone have some hints where to
> look at for debugging, or what might be wrong?
> 
> Thanks in advance
> Best regards

Re: XUPV2P, Kernel 2.6.17 boot problem

[David H. Lynch Jr.]

Benjamin Heyne wrote:
> Dear all,
> I am currently trying to get the 2.6.17.1 Linux kernel
> running on the Xilinx Virtex. I have the 2.4 kernel up
> and running - No problems there...
>
> But when using the 2.6 kernel (have copied xparameters file,
> patched for using TEMAC driver) with the same hardware configuration
> the following happens:
>
>
> loaded at:     00400000 0061813C
> board data at: 00616124 0061613C
> relocated to:  00405148 00405160
> zimage at:     0040585D 00615F42
> avail ram:     00619000 20000000
>
> Linux/PPC load: console=ttyS0,9600.....
>
> Uncompressing Linux...inflate returned FFFFFFFB
> exit
>
>   
    Zlib was upgraded with 2.6.17. The updated Zlib is broken on ppc32.
I am pretty certain it is fixed in 2.6.18-rc3


> Now, I am not really sure where to start searching for the bug
> (I just want to implement some drivers - not the kernel itself ;-).
> The zImage.elf file is about 2MB large. Did anyone encounter
> a similar error? Does anyone have some hints where to
> look at for debugging, or what might be wrong?
>
> Thanks in advance
> Best regards
>   


-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too
numerous to list.

"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction."
Albert Einstein

Re: XUPV2P, Kernel 2.6.17 boot problem

[Peter Korsgaard]

>>>>> "DHL" == David H Lynch <dhlii@dlasys.net> writes:

>> Linux/PPC load: console=ttyS0,9600.....
>> 
>> Uncompressing Linux...inflate returned FFFFFFFB exit
>> 

DHL>     Zlib was upgraded with 2.6.17. The updated Zlib is broken on
DHL> ppc32.  I am pretty certain it is fixed in 2.6.18-rc3

No, that was ony added in 2.6.18-rc1 (and the fix was only added
post-rc3), so that can't be it..

-- 
Bye, Peter Korsgaard

Re: XUPV2P, Kernel 2.6.17 boot problem

[David H. Lynch Jr.]

[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]

Peter Korsgaard wrote:
>>>>>> "DHL" == David H Lynch <dhlii@dlasys.net> writes:
>>>>>>             
>
>   
>>> Linux/PPC load: console=ttyS0,9600.....
>>>
>>> Uncompressing Linux...inflate returned FFFFFFFB exit
>>>
>>>       
>
> DHL>     Zlib was upgraded with 2.6.17. The updated Zlib is broken on
> DHL> ppc32.  I am pretty certain it is fixed in 2.6.18-rc3
>
> No, that was ony added in 2.6.18-rc1 (and the fix was only added
> post-rc3), so that can't be it..
>   
    I am not sure of the details, but I had the exact same problem, I
used "git bisect" to isolate it.
    and it bisected down to the Zlib patch I backed that out and I was
able to go from 2.6.16.21. all the way to 2.6.18-rc2.
    I beleive there is another problem of some kind that effects Xilinx
ppc's that went in and got fixed between 2.6.16.21 and 2.6.18-rcx.
    Though my symptoms were different for that one, and I was never able
to isolate it because even though I could not get 2.6.17 to work,
    The stuff in the 2.6 git tree did.
   
    Have you tried 2.6.18.x to see if your stuff works with it ?




-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein


[-- Attachment #2: Type: text/html, Size: 2675 bytes --]

Re: XUPV2P, Kernel 2.6.17 boot problem

[Peter Korsgaard]

>>>>> "David" == David H Lynch <dhlii@dlasys.net> writes:

Hi,

David>     Have you tried 2.6.18.x to see if your stuff works with it
David> ?

Yes, 2.6.18-rc3 + my zlib fix
(http://thread.gmane.org/gmane.linux.kernel/428436) or -rc4 once it
hits kernel.org works fine on my v2p-based board.

-- 
Bye, Peter Korsgaard

Re: XUPV2P, Kernel 2.6.17 boot problem

[Benjamin Heyne]

And so it came to pass, that on Mon, 07 Aug 2006 09:40:14 +0200
Peter Korsgaard <jacmet@sunsite.dk> wrote as thus:

> >>>>> "David" == David H Lynch <dhlii@dlasys.net> writes:
> 
> Hi,
> 
> David>     Have you tried 2.6.18.x to see if your stuff works with it
> David> ?
> 
> Yes, 2.6.18-rc3 + my zlib fix
> (http://thread.gmane.org/gmane.linux.kernel/428436) or -rc4 once it
> hits kernel.org works fine on my v2p-based board.

Well, unfortunately I am still getting the inflate error
as soon as the image grows >2MB (about). Have you tried with
images of this size? If the image is smaller, everything works
fine...

Best regards
Benjamin Heyne

XUPV2P, which kernel 2.6. device drivers are available?

[Benjamin Heyne]

Hi all,
despite having problems with zlib, I'd like to know which
device drivers for the XUPV2P have already been ported
to the 2.6 kernel? - I don't want to do work twice ;-).

For practicing, I just ported the original Xilinx ENET 100MBit
driver (seems to work in FIFO mode, including MII - At least I
can mount and use a NFS root file system)...but that has probably
already been done elsewhere. I saw that work is going on for 
the SystemACE. - So what about VGA, AC97, PS/2, SATA?

Best regards
Benjamin Heyne

Re: XUPV2P, which kernel 2.6. device drivers are available?

[Ameet Patil]

Hi Benjamin,
    I had ported the ENET driver but it was a bit buggy. Could you send 
me your driver patch so I can test it?

Thanks,
-Ameet

Benjamin Heyne wrote:
> Hi all,
> despite having problems with zlib, I'd like to know which
> device drivers for the XUPV2P have already been ported
> to the 2.6 kernel? - I don't want to do work twice ;-).
> 
> For practicing, I just ported the original Xilinx ENET 100MBit
> driver (seems to work in FIFO mode, including MII - At least I
> can mount and use a NFS root file system)...but that has probably
> already been done elsewhere. I saw that work is going on for 
> the SystemACE. - So what about VGA, AC97, PS/2, SATA?
> 
> Best regards
> Benjamin Heyne
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

Re: XUPV2P, which kernel 2.6. device drivers are available?

[Benjamin Heyne]

And so it came to pass, that on Mon, 07 Aug 2006 17:03:22 +0100
Ameet Patil <ammubhai@gmail.com> wrote as thus:

> Hi Benjamin,
>     I had ported the ENET driver but it was a bit buggy. Could you send 
> me your driver patch so I can test it?
> 

Hi,
I have put all necessary files into an archive. I have implemented
the driver into a patched version of the 2.6.18-rc3 kernel, so
I thought it would be the best to provide all modified files in an
archive (also, I am not familiar with generating patches and stuff... ;-).
Please feel free to provide a "real" patch.

Ok, here we go:

http://www.dt.e-technik.uni-dortmund.de/mitarbeiter/heyne/xilinx/xilinx_emac_26.zip

Be warned:
This driver probably can be considered as BadHack(TM) -
It's the first one I am providing to the public. So if
you have any suggestions for improving it, please tell me.

TODO (As far as I can tell):
	- Make it a real platform device
	- Make use of the XILINX_EDK config of the TEMAC driver patch
	  (Btw.: Will this be officially integrated into the kernel?).

Any feedback will be appreciated...

Best regards
-- 
Benjamin Heyne

Re: XUPV2P, Kernel 2.6.17 boot problem

[Milton Miller]

On Mon Aug  7 2006 04:46:43 AM CDT, Benjamin Heyne wrote:
> Peter Korsgaard <jacmet@sunsite.dk> wrote as thus:
> > >>>>> "David" == David H Lynch <dhlii@dlasys.net> 
> > David>     Have you tried 2.6.18.x to see if your stuff works with it
> > David> ?
> > 
> > Yes, 2.6.18-rc3 + my zlib fix
> > (http://thread.gmane.org/gmane.linux.kernel/428436) or -rc4 once it
> > hits kernel.org works fine on my v2p-based board.
> 
> Well, unfortunately I am still getting the inflate error
> as soon as the image grows >2MB (about). Have you tried with
> images of this size? If the image is smaller, everything works
> fine...

My first reaction when I saw this thread was that you didn't allocate 
something in memory and overlapped something.  However, looking
at your original post again, I think your kernel is growing larger than
4MB, which is the link address of the zImage.  This is based on the 
kernel is decompressed to address 0 in
ppc/boot/simple/misc-embedded.c, and a 50% compression factor 
and 2MB compressed image.

You can look at the file size of vmlinux to see if this is close.

milton

Re: XUPV2P, Kernel 2.6.17 boot problem

[Benjamin Heyne]

And so it came to pass, that on Fri, 11 Aug 2006 23:37:25 -0500
Milton Miller <miltonm@bga.com> wrote as thus:

> On Mon Aug  7 2006 04:46:43 AM CDT, Benjamin Heyne wrote:
> > Peter Korsgaard <jacmet@sunsite.dk> wrote as thus:
> > > >>>>> "David" == David H Lynch <dhlii@dlasys.net> 
> > > David>     Have you tried 2.6.18.x to see if your stuff works with it
> > > David> ?
> > > 
> > > Yes, 2.6.18-rc3 + my zlib fix
> > > (http://thread.gmane.org/gmane.linux.kernel/428436) or -rc4 once it
> > > hits kernel.org works fine on my v2p-based board.
> > 
> > Well, unfortunately I am still getting the inflate error
> > as soon as the image grows >2MB (about). Have you tried with
> > images of this size? If the image is smaller, everything works
> > fine...
> 
> My first reaction when I saw this thread was that you didn't allocate 
> something in memory and overlapped something.  However, looking
> at your original post again, I think your kernel is growing larger than
> 4MB, which is the link address of the zImage.  This is based on the 
> kernel is decompressed to address 0 in
> ppc/boot/simple/misc-embedded.c, and a 50% compression factor 
> and 2MB compressed image.
> 
> You can look at the file size of vmlinux to see if this is close.
> 
> milton

Well - That's exactly the case. But looking into misc-embedded.c, I noticed
that the load address for gunzip is fixed to 0x400000...shouldn't this
be dependent on CONFIG_BOOT_LOAD_BOOL and CONFIG_BOOT_LOAD?

I've changed the line to


#ifdef CONFIG_BOOT_LOAD_BOOL
	gunzip(0, CONFIG_BOOT_LOAD, zimage_start, &zimage_size);
#else	
	gunzip(0, 0x400000, zimage_start, &zimage_size);
#endif


and now it seems to work fine for big images (if CONFIG_BOOT_LOAD 
is set large enough of course...) - which wasn't the case before.


Best regards
-- 
Benjamin Heyne

Re: XUPV2P, Kernel 2.6.17 boot problem

[Milton Miller]

On Aug 14, 2006, at 4:10 AM, Benjamin Heyne wrote:

> And so it came to pass, that on Fri, 11 Aug 2006 23:37:25 -0500
> Milton Miller <miltonm@bga.com> wrote as thus:
>
>> On Mon Aug  7 2006 04:46:43 AM CDT, Benjamin Heyne wrote:
>>> Peter Korsgaard <jacmet@sunsite.dk> wrote as thus:
>>>>>>>>> "David" == David H Lynch <dhlii@dlasys.net>
>>>> David>     Have you tried 2.6.18.x to see if your stuff works with 
>>>> it
>>>
>>> Well, unfortunately I am still getting the inflate error
>>> as soon as the image grows >2MB (about). Have you tried with
>>> images of this size? If the image is smaller, everything works
>>> fine...
>>
>> I think your kernel is growing larger than
>> 4MB, which is the link address of the zImage.
>
> Well - That's exactly the case. But looking into misc-embedded.c, I 
> noticed
> that the load address for gunzip is fixed to 0x400000...shouldn't this
> be dependent on CONFIG_BOOT_LOAD_BOOL and CONFIG_BOOT_LOAD?
>
> I've changed the line to
>
> #ifdef CONFIG_BOOT_LOAD_BOOL
> 	gunzip(0, CONFIG_BOOT_LOAD, zimage_start, &zimage_size);
> #else	
> 	gunzip(0, 0x400000, zimage_start, &zimage_size);
> #endif
>
> and now it seems to work fine for big images (if CONFIG_BOOT_LOAD
> is set large enough of course...) - which wasn't the case before.

It shouldn't depend on CONFIG_BOOT_LOAD_BOOL.   CONFIG_BOOT_LOAD is
set all the time (the question is dependent on _BOOL not the variable
and the default is used).

milton

Re: XUPV2P, Kernel 2.6.17 boot problem

[Benjamin Heyne]

And so it came to pass, that on Mon, 14 Aug 2006 09:00:33 -0500
Milton Miller <miltonm@bga.com> wrote as thus:

> >>
> >> I think your kernel is growing larger than
> >> 4MB, which is the link address of the zImage.
> >
> > Well - That's exactly the case. But looking into misc-embedded.c, I 
> > noticed
> > that the load address for gunzip is fixed to 0x400000...shouldn't this
> > be dependent on CONFIG_BOOT_LOAD_BOOL and CONFIG_BOOT_LOAD?
> >
> > I've changed the line to
> >
> > #ifdef CONFIG_BOOT_LOAD_BOOL
> > 	gunzip(0, CONFIG_BOOT_LOAD, zimage_start, &zimage_size);
> > #else	
> > 	gunzip(0, 0x400000, zimage_start, &zimage_size);
> > #endif
> >
> > and now it seems to work fine for big images (if CONFIG_BOOT_LOAD
> > is set large enough of course...) - which wasn't the case before.
> 
> It shouldn't depend on CONFIG_BOOT_LOAD_BOOL.   CONFIG_BOOT_LOAD is
> set all the time (the question is dependent on _BOOL not the variable
> and the default is used).
> 
> milton
> 

OK - Thanks. So replacing

	gunzip(0, 0x400000, zimage_start, &zimage_size);
with
	gunzip(0, CONFIG_BOOT_LOAD, zimage_start, &zimage_size);

should do the trick. Maybe we should report this to the file maintainer,
if you'd consider this to be a bug, too....

Best regards
-- 
Benjamin Heyne