P2041RDB PCIe Problem . (vxWorks)

kohyungeun — Thu, 17 Oct 2013 05:22:18 GMT

I have the p2041rdb Borad.

I got the vxWorks BSP from the WindRiber site.

I read a target.ref file. then compiled the bootrom and kernel.

I can the Tffs, SATA, ..

but I can't Pcie.

shell log ->

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

>vxBusShow

Registered Bus Types:

MII_Bus @ 0x002eb1ec

PCI_Bus @ 0x002eae5c

PLB_Bus @ 0x002eae78

Registered Device Drivers:

ppcIntCtlr at 0x002e92c4 on bus PLB_Bus, funcs @ 0x002e92b8

m85xxTimerDev at 0x002eada8 on bus PLB_Bus, funcs @ 0x002ead8c

fslSata at 0x002eb2f8 on bus PLB_Bus, funcs @ 0x002eb2e0

fslDma at 0x002e9f28 on bus PLB_Bus, funcs @ 0x002e9f1c

epic at 0x002ea0bc on bus PLB_Bus, funcs @ 0x002ea068

dtsec at 0x002eb0d0 on bus PLB_Bus, funcs @ 0x002eb000

ns16550 at 0x002ea4a8 on bus PLB_Bus, funcs @ 0x002ea3d8

ns16550 at 0x002ea460 on bus PCI_Bus, funcs @ 0x002ea3d8

dtsecMdio at 0x002eb2a0 on bus PLB_Bus, funcs @ 0x002eb274

genericPhy at 0x002eb234 on bus MII_Bus, funcs @ 0x002eb228

miiBus at 0x002eb1a4 on bus PCI_Bus, funcs @ 0x002eb148

miiBus at 0x002eb164 on bus PLB_Bus, funcs @ 0x002eb148

m85xxPci at 0x002e9e38 on bus PLB_Bus, funcs @ 0x002e9e2c

m85xxCCSR at 0x002ea134 on bus PLB_Bus, funcs @ 0x002ea128

QorIQFman at 0x002ea270 on bus PLB_Bus, funcs @ 0x002ea254

QorIQBman at 0x002ea214 on bus PLB_Bus, funcs @ 0x002ea1f8

fslGpio at 0x002ea1b8 on bus PLB_Bus, funcs @ 0x002ea19c

QorIQQman at 0x002ea350 on bus PLB_Bus, funcs @ 0x002ea32c

QorIQPciEx at 0x002e9edc on bus PLB_Bus, funcs @ 0x002e9e78

QorIQLaw at 0x002ea2ec on bus PLB_Bus, funcs @ 0x002ea2b0

plbCtlr at 0x002eaea0 on bus PLB_Bus, funcs @ 0x002eae94

Busses and Devices Present:

PLB_Bus @ 0x002fe368 with bridge @ 0x002eaee0

Device Instances:

ppcIntCtlr unit 0 on PLB_Bus @ 0x002ff328 with busInfo 0x00000000

epic unit 0 on PLB_Bus @ 0x002ff428 with busInfo 0x00000000

ns16550 unit 0 on PLB_Bus @ 0x002ff628 with busInfo 0x00000000

ns16550 unit 1 on PLB_Bus @ 0x002ff828 with busInfo 0x00000000

ns16550 unit 2 on PLB_Bus @ 0x002ffa28 with busInfo 0x00000000

ns16550 unit 3 on PLB_Bus @ 0x002ffc28 with busInfo 0x00000000

fslGpio unit 0 on PLB_Bus @ 0x002ffe28 with busInfo 0x00000000

QorIQLaw unit 0 on PLB_Bus @ 0x002fff28 with busInfo 0x0

QorIQBman unit 0 on PLB_Bus @ 0x00300028 with busInfo 0x00000000

QorIQQman unit 0 on PLB_Bus @ 0x00300128 with busInfo 0x00000000

QorIQFman unit 0 on PLB_Bus @ 0x00300228 with busInfo 0x00000000

QorIQPciEx unit 1 on PLB_Bus @ 0x0030d328 with busInfo 0x00000000

dtsec unit 0 on PLB_Bus @ 0x0030d628 with busInfo 0x0

dtsec unit 1 on PLB_Bus @ 0x0030d728 with busInfo 0x0

dtsec unit 2 on PLB_Bus @ 0x0030d828 with busInfo 0x0

dtsec unit 3 on PLB_Bus @ 0x0030d928 with busInfo 0x0

dtsec unit 4 on PLB_Bus @ 0x0030da28 with busInfo 0x0

dtsecMdio unit 0 on PLB_Bus @ 0x0030db28 with busInfo 0x00000000

m85xxTimerDev unit 0 on PLB_Bus @ 0x0030dc28 with busInfo 0x00000000

fslSata unit 0 on PLB_Bus @ 0x0030dd28 with busInfo 0x00000000

fslSata unit 1 on PLB_Bus @ 0x0030de28 with busInfo 0x00000000

fslDma unit 0 on PLB_Bus @ 0x0030df28 with busInfo 0x00000000

fslDma unit 1 on PLB_Bus @ 0x0030e028 with busInfo 0x00000000

miiBus unit 0 on PLB_Bus @ 0x0030e128 with busInfo 0x002fefa8

miiBus unit 1 on PLB_Bus @ 0x00312328 with busInfo 0x002fef68

miiBus unit 2 on PLB_Bus @ 0x00312528 with busInfo 0x002fefe8

miiBus unit 3 on PLB_Bus @ 0x00312728 with busInfo 0x002ff028

miiBus unit 4 on PLB_Bus @ 0x00312928 with busInfo 0x002ff068

Orphan Devices:

MII_Bus @ 0x002fefa8 with bridge @ 0x0030e128

Device Instances:

genericPhy unit 0 on MII_Bus @ 0x0030e228 with busInfo 0x00000000

Orphan Devices:

MII_Bus @ 0x002fef68 with bridge @ 0x00312328

Device Instances:

genericPhy unit 1 on MII_Bus @ 0x00312428 with busInfo 0x00000000

Orphan Devices:

MII_Bus @ 0x002fefe8 with bridge @ 0x00312528

Device Instances:

genericPhy unit 2 on MII_Bus @ 0x00312628 with busInfo 0x00000000

Orphan Devices:

MII_Bus @ 0x002ff028 with bridge @ 0x00312728

Device Instances:

genericPhy unit 3 on MII_Bus @ 0x00312828 with busInfo 0x00000000

Orphan Devices:

MII_Bus @ 0x002ff068 with bridge @ 0x00312928

Device Instances:

genericPhy unit 4 on MII_Bus @ 0x00312a28 with busInfo 0x00000000

Orphan Devices:

value = 1 = 0x1

-> pciDeviceShow

value = -1 = 0xffffffff

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

I used rcw file that rcw_5g_1500mhz.bin (RR_PH_0x19)

Re: P2041RDB PCIe Problem . (vxWorks)

addiyi — Fri, 18 Oct 2013 12:58:18 GMT

Hi,

Do you use a custom board? If not, why don't you use SDK 1.4 which is available on freescale.com. Also, you rcw file set PCIe on Slot1 and according with P2041 reference manual, your application should use PCIe2 controller for communication with PCIe device.

SerDes 0x19 -> Bank 1 C: SGMII1, D: SGMII2, E,F: PCIe2, G: SGMII3, H: SGMII4

Adrian

topic Re: P2041RDB PCIe Problem . (vxWorks) in P-Series

P2041RDB PCIe Problem . (vxWorks)

Re: P2041RDB PCIe Problem . (vxWorks)