Problem in PCI with MPC5200B

Problem in PCI with MPC5200B

[Ram Prasad H L]

hi all,
	We are using a customised board which is based on
	the reference design of lite5200B. But our board is customised by adding
	a PCI-PCI Bridge on the primary bus. On the secondary bus we have added
	a DSP(DM642) along with 2 PCI slots, which are routed through
	bridge (PCI2250) to MPC5200B.

	As far as software is concerned we are using "mpc5200_lite_K26-BSP-b30"
	BSP downloaded from freescale's website for lite5200B. This BSP has a
	u-boot-1.1.3 and linux kernel-2.6.11.7. As far as u-boot is concerned
	the PCI devices are allocated and assigned with proper resources (BAR's)
	which come under the range for Mem region(40000000 - 4fffffff) and I/O
	region (50000000 - 50ffffff). But during the boot process of linux we
	are getting the following errors:


****************************************************************************
***
	PCI: Probing PCI hardware
	PCI: Cannot allocate resource region 1 of PCI bridge 1
	PCI: bridge 1 resource 1 moved to 4ff00000..4fffffff
	PCI: Cannot allocate resource region 2 of PCI bridge 1
	PCI: bridge 1 resource 2 moved to 4fe00000..4fefffff
	PCI: Failed to allocate mem resource #0: 400000 @ 50000000 for 0000:01:08.0
	PCI: Failed to allocate mem resource #1: 800000 @ 50000000 for 0000:01:08.0
	PCI: Failed to allocate I/O resource #2: 10 @ 1000 for 0000:01:08.0

****************************************************************************
****

	where 0000:01:08.0 is the dev function address for DM642(DSP).

	I'm stuck up with this problem since long time. Plz help me in giving some
pointers
	for overcoming this problem as i'm a newbie to linux-pci. Any patches for
the kernel
	2.6.11.7 which can resolve the above problem would be of great help.


Thanks and regards,
Ramprasad



The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s)and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender or administrator@tataelxsi.co.in

Re: Problem in PCI with MPC5200B

[Sylvain Munaut]

Hi,

> 	As far as software is concerned we are using "mpc5200_lite_K26-BSP-b30"
> 	BSP downloaded from freescale's website for lite5200B. This BSP has a
> 	u-boot-1.1.3 and linux kernel-2.6.11.7.

I'm not familiar with that BSP and then without knowing
exactly what's in that kernel and what's not it's hard
to answer.

Can you provide a link to it ?


      Sylvain


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Problem in PCI with MPC5200B

[Ram Prasad H L]

hi all,
	we are using a customized board based on the reference design of lite5200B.
The PCI bus heirarchy in the board is as follows:
											     |---------> DM642(TMS320C642)
	OnChip-Host-Bridge(MPC5200B) ----> PCI-to-PCI Bridge (TI2250) ---|
											     |---------> Empty Slot
                                                                       |

|---------> Empty Slot

	The linux kernel used is 2.6.11.7. with u-boot-1.1.3. The problem we are
facing is that
I'm able to access the PCI Memory and I/O Region of DM642 from my Host
(MPC5200B) ie.upstream.
But when it comes to other way around ie. with Host Bridge being the PCI
slave and DM642 being the
master, the transaction is failing to complete. But not getting any
exceptions like master abort
and target abort. The BAR Configuration is as follows

Host (MPC5200B):

	BAR0 -- 0x41000000 (256MB) Non prefetchable
	BAR1 -- 0x00000000 (1GB)   prefetchable

PCI-PCI Bridge (TI2250):
	BAR0 -- 0x00000000  {Both are defaulted to 0's and are Read Only}
	BAR1 -- 0x00000000

DM642:
	BAR0 -- 0x40000000 (4MB) 	prefetchable
	BAR1 -- 0x40800000 (8MB) 	Non prefetchable
	BAR2 -- 0x00fff001 (16 bytes) I/O

	If anyone can provide pointers and suggestions to overcome this problem, it
will be of great help, as
we are stuck up with it since long time.

thanks and regards,
Ramprasad H L

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s)and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender or administrator@tataelxsi.co.in

Re: Problem in PCI with MPC5200B

[Heiko Schocher]

Hello Ram,

On Wed, 7 Jun 2006 11:05:16 +0530 Ram Prasad H L wrote
> hi all,
> 	We are using a customised board which is based on
> 	the reference design of lite5200B. But our board is customised by adding
> 	a PCI-PCI Bridge on the primary bus. On the secondary bus we have added
> 	a DSP(DM642) along with 2 PCI slots, which are routed through
> 	bridge (PCI2250) to MPC5200B.
> 
> 	As far as software is concerned we are using "mpc5200_lite_K26-BSP-b30"
> 	BSP downloaded from freescale's website for lite5200B. This BSP has a
> 	u-boot-1.1.3 and linux kernel-2.6.11.7. As far as u-boot is concerned
> 	the PCI devices are allocated and assigned with proper resources (BAR's)
> 	which come under the range for Mem region(40000000 - 4fffffff) and I/O
> 	region (50000000 - 50ffffff). But during the boot process of linux we
> 	are getting the following errors:
> 
> 
> ****************************************************************************
> ***
> 	PCI: Probing PCI hardware
> 	PCI: Cannot allocate resource region 1 of PCI bridge 1
> 	PCI: bridge 1 resource 1 moved to 4ff00000..4fffffff
> 	PCI: Cannot allocate resource region 2 of PCI bridge 1
> 	PCI: bridge 1 resource 2 moved to 4fe00000..4fefffff
> 	PCI: Failed to allocate mem resource #0: 400000 @ 50000000 for 0000:01:08.0
> 	PCI: Failed to allocate mem resource #1: 800000 @ 50000000 for 0000:01:08.0
> 	PCI: Failed to allocate I/O resource #2: 10 @ 1000 for 0000:01:08.0
> 
> ****************************************************************************
> ****

I had a similar problem with a 2.4.25 Kernel. I get the following
errors:

PCI: Cannot allocate resource region 0 of device 00:1b.0
PCI: moved device 00:1b.0 resource 0 (200) to e0000000

I solved the problem by adding

hose->last_busno = pciauto_bus_scan(hose, hose->first_busno);

at the end of the function mpc5xxx_find_bridges() in
arch/ppc/kernel/mpc5xxx_pci.c

I didnt looked in the 2.6.11.7 Kernel, but maybe this helps you!

Best regards
Heiko

MPC5200 fec frame corruption

[Asier Llano Palacios]

Hello,

We have been working with the MPC5200 fec and a linux-2.6.10 with some
patches extracted from Sylvain's bitkeeper repository. We have 3
different boards that worked properly with that kernel.

We upgraded to the new MPC5200B and it still worked properly with the
2.6.10 kernel.

We upgraded to the new code of the Sylvain's git repository and the FEC
transmitted frames are corrupted. This corruption only happens with the
current git repository and the MPC5200B.

                MPC5200   MPC5200B
linux-2.6.10:     OK         OK
Sylvain's git:    OK       CORRUPT

The problem is that the lite5200 and the lite5200b work flawlessly, but
our architecture is essentialy the same but with different PHYs (Marvell
88E6095F and 88E6060). Our architecture works properly with the
linux-2.6.10, so we don't think that it is a hardware related problem.
We have been watching the MII bus by osciloscope and the errors are
clearly transmitted by the MPC5200B (no noise or distortion).

We have inserted traces in the functions of the FEC driver with the
buffer information that is sent to the DMA and the frames are correct.

The corruption pattern is as follows:
Transmition frame:
0000  ff ff ff ff ff ff 00 11  22 33 44 55 e0 00 e0 73
0010  00 11 22 33 44 55 66 77  88 99 aa bb cc dd ee ff
0020  12 23 34 45 56 67 78 89  9a ab bc cd de ef f0 01
0030  24 35 46 57 68 79 8a 9b  ac bd ce df e0 f1 02 13
0040  36 47 58 69 7a 8b 9c ad  be cf d0 e1 f2 03 14 25
0050  48 59 6a 7b 8c 9d ae bf  c0 d1 e2 f3 04 15 26 37
0060  5a 6b 7c 8d 9e af b0 c1  d2 e3 f4 05 16 27 38 49
0070  6c 7d 8e 9f a0 b1 c2 d3  e4 f5 06 17 28 39 4a 5b
0080  7e 8f 90 a1 b2 c3 d4 e5  f6 07 18 29 3a 4b 5c 6d

Reception frame (corrupted bytes marked):
0000 (7e)ff ff ff ff ff 00 11  22 33 44 55 e0 00 e0 73
0010  00 11 22 33 44 55 66 77  88 99 aa bb cc dd ee ff
0020  12 23 34 45 56 67 78 89  9a ab bc cd de ef f0 01
0030  24 35 46 57 68 79 8a 9b  ac bd ce df e0 f1(ee)13
0040  36 47 58 69 7a 8b 9c ad  be cf d0 e1 f2 03 14 25
0050  48 59 6a 7b 8c 9d ae bf  c0 d1 e2 f3 04 15 26 37
0060  5a 6b 7c 8d 9e af b0 c1  d2 e3 f4 05 16 27 38 49
0070  6c 7d 8e 9f a0 b1 c2 d3  e4 f5 06 17 28 39(26)5b
0080  7e 8f 90 a1 b2 c3 d4 e5  f6 07 18 29 3a 4b 5c 6d

The corrupted bytes are sometimes correct, sometimes overwriten
by the byte that is 0x20 bytes before, and sometimes changed
by the bytes that is 0x40 bytes before. About 50% of the time
the marked bytes are worong.

I'd like to know if anything here makes any sense to you, so
that I can understand the origin of the problem, or any
additional test to perform.

Thank you in advance,
Asier Llano=20
=20
----------------------------------------- PLEASE NOTE =
-------------------------------------------
This message, along with any attachments, may be confidential or legally =
privileged.=20
It is intended only for the named person(s), who is/are the only =
authorized recipients.
If this message has reached you in error, kindly destroy it without =
review and notify the sender immediately.
Thank you for your help.
=B5SysCom uses virus scanning software but excludes any liability for =
viruses contained in any attachment.
=20
------------------------------------ ROGAMOS LEA ESTE TEXTO =
-------------------------------
Este mensaje y sus anexos pueden contener informaci=F3n confidencial y/o =
con derecho legal.=20
Est=E1 dirigido =FAnicamente a la/s persona/s o entidad/es rese=F1adas =
como =FAnico destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elim=EDnelo sin =
revisarlo ni reenviarlo y notif=EDquelo inmediatamente al remitente. =
Gracias por su colaboraci=F3n. =20
=B5SysCom utiliza software antivirus, pero no se hace responsable de los =
virus contenidos en los ficheros anexos.

Re: MPC5200 fec frame corruption

[Sylvain Munaut]

Hi Asier,
> We have been working with the MPC5200 fec and a linux-2.6.10 with some
> patches extracted from Sylvain's bitkeeper repository. We have 3
> different boards that worked properly with that kernel.
>
> We upgraded to the new MPC5200B and it still worked properly with the
> 2.6.10 kernel.
>
> We upgraded to the new code of the Sylvain's git repository and the FEC
> transmitted frames are corrupted. This corruption only happens with the
> current git repository and the MPC5200B.
>
>                 MPC5200   MPC5200B
> linux-2.6.10:     OK         OK
> Sylvain's git:    OK       CORRUPT
>   
I must admit I don't have bitkeeper anymore installed on my machine so I
don't
remeber exactly what in there.

Could you put somewhere on line the diff between 2.6.10 and you tree,
eventually minus all the irrelevant/confidential stuff ?
What would be needed woud be the arch/ppc/syslib/bestcomm ,
drivers/net/fec_mpc52xx
and the board setup code.
> The problem is that the lite5200 and the lite5200b work flawlessly, but
> our architecture is essentialy the same but with different PHYs (Marvell
> 88E6095F and 88E6060). Our architecture works properly with the
> linux-2.6.10, so we don't think that it is a hardware related problem.
> We have been watching the MII bus by osciloscope and the errors are
> clearly transmitted by the MPC5200B (no noise or distortion).
>
> We have inserted traces in the functions of the FEC driver with the
> buffer information that is sent to the DMA and the frames are correct.
>
>
> [... logs stripped ...]
> The corrupted bytes are sometimes correct, sometimes overwriten
> by the byte that is 0x20 bytes before, and sometimes changed
> by the bytes that is 0x40 bytes before. About 50% of the time
> the marked bytes are worong.
>
> I'd like to know if anything here makes any sense to you, so
> that I can understand the origin of the problem, or any
> additional test to perform.
>   
Any sense not really. But I would check first the options in the board
setup.
Things like cache snooping, comm bus prefetching, xlb priority settings and
pipelining, ...

Then the microcode of the task themselves and the options wich are used when
loading them.

Finally compare the driver code itself.


        Sylvain

Re: MPC5200 fec frame corruption

[Asier Llano Palacios]

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

Thank you very much for your fast and helpful answer.

I've found a way to solve our issue (or the way to hide it). The
difference between the previous kernel I was using and the current
kernel (from your git repository) is the XLB bus pipelining. Removing
the code that disables the pipelining it works again. (See the attached
patch).

Of course, I don't expect to remove that code from the repository,
because it seems to solve another issue of other configurations (I don't
use ATA), but I would like to know a little more information about it.

The only problem is that I don't see why does it fail when pipelining is
disabled. My only concern is that maybe the pipelining hides the true
issue. Should it work with pipelining disabled? If so, what do you think
about it?

Thank you very much in advance,
Asier Llano

El mar, 12-09-2006 a las 19:26 +0200, Sylvain Munaut escribió:
> Hi Asier,
> > We have been working with the MPC5200 fec and a linux-2.6.10 with some
> > patches extracted from Sylvain's bitkeeper repository. We have 3
> > different boards that worked properly with that kernel.
> >
> > We upgraded to the new MPC5200B and it still worked properly with the
> > 2.6.10 kernel.
> >
> > We upgraded to the new code of the Sylvain's git repository and the FEC
> > transmitted frames are corrupted. This corruption only happens with the
> > current git repository and the MPC5200B.
> >
> >                 MPC5200   MPC5200B
> > linux-2.6.10:     OK         OK
> > Sylvain's git:    OK       CORRUPT
> >   
> I must admit I don't have bitkeeper anymore installed on my machine so I
> don't
> remeber exactly what in there.
> 
> Could you put somewhere on line the diff between 2.6.10 and you tree,
> eventually minus all the irrelevant/confidential stuff ?
> What would be needed woud be the arch/ppc/syslib/bestcomm ,
> drivers/net/fec_mpc52xx
> and the board setup code.
> > The problem is that the lite5200 and the lite5200b work flawlessly, but
> > our architecture is essentialy the same but with different PHYs (Marvell
> > 88E6095F and 88E6060). Our architecture works properly with the
> > linux-2.6.10, so we don't think that it is a hardware related problem.
> > We have been watching the MII bus by osciloscope and the errors are
> > clearly transmitted by the MPC5200B (no noise or distortion).
> >
> > We have inserted traces in the functions of the FEC driver with the
> > buffer information that is sent to the DMA and the frames are correct.
> >
> >
> > [... logs stripped ...]
> > The corrupted bytes are sometimes correct, sometimes overwriten
> > by the byte that is 0x20 bytes before, and sometimes changed
> > by the bytes that is 0x40 bytes before. About 50% of the time
> > the marked bytes are worong.
> >
> > I'd like to know if anything here makes any sense to you, so
> > that I can understand the origin of the problem, or any
> > additional test to perform.
> >   
> Any sense not really. But I would check first the options in the board
> setup.
> Things like cache snooping, comm bus prefetching, xlb priority settings and
> pipelining, ...
> 
> Then the microcode of the task themselves and the options wich are used when
> loading them.
> 
> Finally compare the driver code itself.
> 
> 
>         Sylvain
> 
> 
 
----------------------------------------- PLEASE NOTE -------------------------------------------
This message, along with any attachments, may be confidential or legally privileged. 
It is intended only for the named person(s), who is/are the only authorized recipients.
If this message has reached you in error, kindly destroy it without review and notify the sender immediately.
Thank you for your help.
µSysCom uses virus scanning software but excludes any liability for viruses contained in any attachment.
 
------------------------------------ ROGAMOS LEA ESTE TEXTO -------------------------------
Este mensaje y sus anexos pueden contener información confidencial y/o con derecho legal. 
Está dirigido únicamente a la/s persona/s o entidad/es reseñadas como único destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elimínelo sin revisarlo ni reenviarlo y notifíquelo inmediatamente al remitente. Gracias por su colaboración.  
µSysCom utiliza software antivirus, pero no se hace responsable de los virus contenidos en los ficheros anexos.

[-- Attachment #2: linux-mp5200-pipeline.patch --]
[-- Type: text/x-patch, Size: 754 bytes --]

diff -urP linux-2.6.17.13/arch/ppc/syslib/mpc52xx_setup.c linux-2.6.17.13-mp5200-pipeline/arch/ppc/syslib/mpc52xx_setup.c
--- linux-2.6.17.13/arch/ppc/syslib/mpc52xx_setup.c	2006-09-09 05:23:25.000000000 +0200
+++ linux-2.6.17.13-mp5200-pipeline/arch/ppc/syslib/mpc52xx_setup.c	2006-09-13 17:54:32.000000000 +0200
@@ -252,11 +252,6 @@
 	out_be32(&xlb->config, in_be32(&xlb->config) | MPC52xx_XLB_CFG_SNOOP);
 	out_be32(&xlb->snoop_window, MPC52xx_PCI_TARGET_MEM | 0x1d);
 
-	/* Disable XLB pipelining */
-	/* (cfr errate 292. We could do this only just before ATA PIO
-	    transaction and re-enable it after ...) */
-	out_be32(&xlb->config, in_be32(&xlb->config) | MPC52xx_XLB_CFG_PLDIS);
-
 	/* Unmap reg zone */
 unmap_regs:
 	if (cdm)  iounmap(cdm);