linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Xilinx Virtex boot
@ 2007-08-29 23:34 Robert Woodworth
  2007-08-30  0:29 ` Grant Likely
  0 siblings, 1 reply; 6+ messages in thread
From: Robert Woodworth @ 2007-08-29 23:34 UTC (permalink / raw)
  To: linuxppc-embedded

I'm trying to port Linux to a new Virtex Platform.  The kernel will not
uncompress, I get the following on the console:



loaded at:     00400000 004FB19C
board data at: 004F9120 004F919C
relocated to:  00404054 004040D0
zimage at:     00404E50 004F8409
avail ram:     004FC000 04000000

Linux/PPC load: console=ttyUL root=/dev/xsa2
Uncompressing Linux...
zlib_inflateInit2 returned 00506530
exit



Any ideas what causes this error??
Is something mis-configured on my EDK project?


I have 64MB DDR on the OPB *not* the PLB.
Is that a problem??



Rob.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Xilinx Virtex boot
  2007-08-29 23:34 Xilinx Virtex boot Robert Woodworth
@ 2007-08-30  0:29 ` Grant Likely
  2007-08-30 14:44   ` Robert Woodworth
  2007-08-30 14:50   ` Xilinx Virtex boot Robert Woodworth
  0 siblings, 2 replies; 6+ messages in thread
From: Grant Likely @ 2007-08-30  0:29 UTC (permalink / raw)
  To: Robert Woodworth; +Cc: linuxppc-embedded

On 8/29/07, Robert Woodworth <rwoodworth@securics.com> wrote:
> I'm trying to port Linux to a new Virtex Platform.  The kernel will not
> uncompress, I get the following on the console:
>
> loaded at:     00400000 004FB19C
> board data at: 004F9120 004F919C
> relocated to:  00404054 004040D0
> zimage at:     00404E50 004F8409
> avail ram:     004FC000 04000000
>
> Linux/PPC load: console=ttyUL root=/dev/xsa2
> Uncompressing Linux...
> zlib_inflateInit2 returned 00506530
> exit
>
> Any ideas what causes this error??
> Is something mis-configured on my EDK project?
>

Possibly, do you know that EDK has your ram is configured correctly
(ie. have you run a memory test application)?

>
> I have 64MB DDR on the OPB *not* the PLB.
> Is that a problem??

It shouldn't be the problem, but why are you doing that?

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Xilinx Virtex boot
  2007-08-30  0:29 ` Grant Likely
@ 2007-08-30 14:44   ` Robert Woodworth
  2007-08-30 15:02     ` Grant Likely
  2007-08-30 16:07     ` Xilinx Virtex boot (And MPMC) Stephen Neuendorffer
  2007-08-30 14:50   ` Xilinx Virtex boot Robert Woodworth
  1 sibling, 2 replies; 6+ messages in thread
From: Robert Woodworth @ 2007-08-30 14:44 UTC (permalink / raw)
  To: Grant Likely; +Cc: linuxppc-embedded

On Wed, 2007-08-29 at 18:29 -0600, Grant Likely wrote:
> On 8/29/07, Robert Woodworth <rwoodworth@securics.com> wrote:
> > I'm trying to port Linux to a new Virtex Platform.  The kernel will not
> > uncompress, I get the following on the console:
> >
> > loaded at:     00400000 004FB19C
> > board data at: 004F9120 004F919C
> > relocated to:  00404054 004040D0
> > zimage at:     00404E50 004F8409
> > avail ram:     004FC000 04000000
> >
> > Linux/PPC load: console=ttyUL root=/dev/xsa2
> > Uncompressing Linux...
> > zlib_inflateInit2 returned 00506530
> > exit
> >
> > Any ideas what causes this error??
> > Is something mis-configured on my EDK project?
> >
> 
> Possibly, do you know that EDK has your ram is configured correctly
> (ie. have you run a memory test application)?

Yes, I ran the sample memory test application that EDK builds
automatically.  It ran fine.

The fact that the above prints on the console, tells me that the
zImage.elf is getting loaded at the correct start location and that its
partly executing.

What is the return code that I'm seeing??  I have been unable to figure
that out from the source yet.


> >
> > I have 64MB DDR on the OPB *not* the PLB.
> > Is that a problem??
> 
> It shouldn't be the problem, but why are you doing that?

We are building an image-processing application inside the FPGA.  The
application is very memory intensive.  I have been told that the PPC
always has priority on the PLB and that if I want to have my FPGA module
have priority on memory, that I should place the memory and my FPGA
module on the OPB.  Yes, this can significantly slow down the PPC, but
in my case the PPC is only used for UI and networking.

I will actually build in *two* OPBs one for the memory + my module and
the second for the other peripherals. 


Woody.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Xilinx Virtex boot
  2007-08-30  0:29 ` Grant Likely
  2007-08-30 14:44   ` Robert Woodworth
@ 2007-08-30 14:50   ` Robert Woodworth
  1 sibling, 0 replies; 6+ messages in thread
From: Robert Woodworth @ 2007-08-30 14:50 UTC (permalink / raw)
  To: Grant Likely; +Cc: linuxppc-embedded

On Wed, 2007-08-29 at 18:29 -0600, Grant Likely wrote:
> On 8/29/07, Robert Woodworth <rwoodworth@securics.com> wrote:
> > I'm trying to port Linux to a new Virtex Platform.  The kernel will not
> > uncompress, I get the following on the console:
> >
> > loaded at:     00400000 004FB19C
> > board data at: 004F9120 004F919C
> > relocated to:  00404054 004040D0
> > zimage at:     00404E50 004F8409
> > avail ram:     004FC000 04000000
> >
> > Linux/PPC load: console=ttyUL root=/dev/xsa2
> > Uncompressing Linux...
> > zlib_inflateInit2 returned 00506530
> > exit
> >
> > Any ideas what causes this error??
> > Is something mis-configured on my EDK project?
> >
> 
> Possibly, do you know that EDK has your ram is configured correctly
> (ie. have you run a memory test application)?
>
>
> >
> > I have 64MB DDR on the OPB *not* the PLB.
> > Is that a problem??
> 
> It shouldn't be the problem, but why are you doing that?

I did notice in my configuration, that when the memory is on the PLB it
has an interrupt flag and when it's on the OPB it doesn't.  What is the
interrupt for?  DMA's?

Could Linux be doing a DMA in the uncompression where the lack of an
interrupt causes and error?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Xilinx Virtex boot
  2007-08-30 14:44   ` Robert Woodworth
@ 2007-08-30 15:02     ` Grant Likely
  2007-08-30 16:07     ` Xilinx Virtex boot (And MPMC) Stephen Neuendorffer
  1 sibling, 0 replies; 6+ messages in thread
From: Grant Likely @ 2007-08-30 15:02 UTC (permalink / raw)
  To: Robert Woodworth; +Cc: linuxppc-embedded

On 8/30/07, Robert Woodworth <rwoodworth@securics.com> wrote:
> On Wed, 2007-08-29 at 18:29 -0600, Grant Likely wrote:
> > On 8/29/07, Robert Woodworth <rwoodworth@securics.com> wrote:
> > > I'm trying to port Linux to a new Virtex Platform.  The kernel will not
> > > uncompress, I get the following on the console:
> > >
> > > loaded at:     00400000 004FB19C
> > > board data at: 004F9120 004F919C
> > > relocated to:  00404054 004040D0
> > > zimage at:     00404E50 004F8409
> > > avail ram:     004FC000 04000000
> > >
> > > Linux/PPC load: console=ttyUL root=/dev/xsa2
> > > Uncompressing Linux...
> > > zlib_inflateInit2 returned 00506530
> > > exit
> > >
> > > Any ideas what causes this error??
> > > Is something mis-configured on my EDK project?
> > >
> >
> > Possibly, do you know that EDK has your ram is configured correctly
> > (ie. have you run a memory test application)?
>
> Yes, I ran the sample memory test application that EDK builds
> automatically.  It ran fine.
>
> The fact that the above prints on the console, tells me that the
> zImage.elf is getting loaded at the correct start location and that its
> partly executing.
>
> What is the return code that I'm seeing??  I have been unable to figure
> that out from the source yet.

IIRC, the return code is the result of the CRC calculation.  If it is
non-zero, then the CRC was incorrect.  That says to me that you've got
either memory or download issues.

I have seen corruption in the past when downloading zImages larger
than about 1.2MB over JTAG.

> > > I have 64MB DDR on the OPB *not* the PLB.
> > > Is that a problem??
> >
> > It shouldn't be the problem, but why are you doing that?
>
> We are building an image-processing application inside the FPGA.  The
> application is very memory intensive.  I have been told that the PPC
> always has priority on the PLB and that if I want to have my FPGA module
> have priority on memory, that I should place the memory and my FPGA
> module on the OPB.  Yes, this can significantly slow down the PPC, but
> in my case the PPC is only used for UI and networking.

<offtopic> You might want to take a look at the MPMC ipcore.  It
allows multiple PLBs to address a single memory region.</offtopic>

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: Xilinx Virtex boot (And MPMC)
  2007-08-30 14:44   ` Robert Woodworth
  2007-08-30 15:02     ` Grant Likely
@ 2007-08-30 16:07     ` Stephen Neuendorffer
  1 sibling, 0 replies; 6+ messages in thread
From: Stephen Neuendorffer @ 2007-08-30 16:07 UTC (permalink / raw)
  To: Robert Woodworth, Grant Likely; +Cc: linuxppc-embedded


The MPMC would almost certainly be a better option here...

Steve

> -----Original Message-----
> From:=20
> linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs.org
> =20
> [mailto:linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@oz
labs.org] On Behalf Of Robert Woodworth
> Sent: Thursday, August 30, 2007 7:45 AM
> To: Grant Likely
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: Xilinx Virtex boot
>=20
> On Wed, 2007-08-29 at 18:29 -0600, Grant Likely wrote:
> > On 8/29/07, Robert Woodworth <rwoodworth@securics.com> wrote:
> > > I'm trying to port Linux to a new Virtex Platform.  The=20
> kernel will not
> > > uncompress, I get the following on the console:
> > >
> > > loaded at:     00400000 004FB19C
> > > board data at: 004F9120 004F919C
> > > relocated to:  00404054 004040D0
> > > zimage at:     00404E50 004F8409
> > > avail ram:     004FC000 04000000
> > >
> > > Linux/PPC load: console=3DttyUL root=3D/dev/xsa2
> > > Uncompressing Linux...
> > > zlib_inflateInit2 returned 00506530
> > > exit
> > >
> > > Any ideas what causes this error??
> > > Is something mis-configured on my EDK project?
> > >
> >=20
> > Possibly, do you know that EDK has your ram is configured correctly
> > (ie. have you run a memory test application)?
>=20
> Yes, I ran the sample memory test application that EDK builds
> automatically.  It ran fine.
>=20
> The fact that the above prints on the console, tells me that the
> zImage.elf is getting loaded at the correct start location=20
> and that its
> partly executing.
>=20
> What is the return code that I'm seeing??  I have been unable=20
> to figure
> that out from the source yet.
>=20
>=20
> > >
> > > I have 64MB DDR on the OPB *not* the PLB.
> > > Is that a problem??
> >=20
> > It shouldn't be the problem, but why are you doing that?
>=20
> We are building an image-processing application inside the FPGA.  The
> application is very memory intensive.  I have been told that the PPC
> always has priority on the PLB and that if I want to have my=20
> FPGA module
> have priority on memory, that I should place the memory and my FPGA
> module on the OPB.  Yes, this can significantly slow down the PPC, but
> in my case the PPC is only used for UI and networking.
>=20
> I will actually build in *two* OPBs one for the memory + my module and
> the second for the other peripherals.=20
>=20
>=20
> Woody.
>=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2007-08-30 16:07 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-29 23:34 Xilinx Virtex boot Robert Woodworth
2007-08-30  0:29 ` Grant Likely
2007-08-30 14:44   ` Robert Woodworth
2007-08-30 15:02     ` Grant Likely
2007-08-30 16:07     ` Xilinx Virtex boot (And MPMC) Stephen Neuendorffer
2007-08-30 14:50   ` Xilinx Virtex boot Robert Woodworth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).