This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi All,
I am using blu-eco elma amc chessis and trying to boot 6678 evm (shannon) in PCIe mode with this chessis.
But the problem is that, it is not detecting the evm 6678. I have gone through on TI community and come to know
that there is no PCIe connectivity with amc chessis as it does not have any FRU data regarding PCIe connectivity
I just want to know that where this FRU data is stored?? and how it is updated so that i can boot evm with amc chessis
in PCI boot mode.
Please check the MMC code in the following link
https://gforge.ti.com/gf/project/msp430_mmc_code/ Click on files on the left.
mentioned in the below thread:
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/115240.aspx?pi73802=4
The README file of the MMC package states the PCIe is supported since v1.32 and the MMC code works with NAT, Advantech, and Vadatech MCH cards.
Hope it is working with your AMC chassis as well.
Hi Steven Ji
in My case user LED are glowing and blinking when I reset the c6678evm, and I Followed your LInk and loaded the mmc code again
but In my jumpgen card ,It does not detect any thing about pcie card
below is my lspci log
0:00.0 Host bridge: Intel Corporation 3100 Chipset Memory I/O Controller Hub
Subsystem: Intel Corporation 3100 Chipset Memory I/O Controller Hub
Flags: bus master, fast devsel, latency 0
Capabilities: [40] Vendor Specific Information: Len=05 <?>
Kernel driver in use: e752x_edac
Kernel modules: e752x_edac
00:00.1 Class ff00: Intel Corporation 3100 DRAM Controller Error Reporting Registers
Subsystem: Intel Corporation 3100 DRAM Controller Error Reporting Registers
Flags: fast devsel
00:01.0 System peripheral: Intel Corporation 3100 Chipset Enhanced DMA Controller
Subsystem: Intel Corporation 3100 Chipset Enhanced DMA Controller
Flags: fast devsel, IRQ 11
Memory at dfbff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [b0] MSI: Enable- Count=1/2 Maskable- 64bit-
00:02.0 PCI bridge: Intel Corporation 3100 Chipset PCI Express Port A (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000f000-0000ffff
Memory behind bridge: dff00000-dfffffff
Capabilities: [50] Power Management version 2
Capabilities: [58] MSI: Enable+ Count=1/2 Maskable- 64bit-
Capabilities: [64] Express Root Port (Slot+), MSI 00
Kernel driver in use: pcieport
Kernel modules: shpchp
00:08.0 System peripheral: Intel Corporation 3100 Extended Configuration Test Overflow Registers
Flags: fast devsel
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 01) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: dfe00000-dfefffff
Prefetchable memory behind bridge: 00000000c0000000-00000000c01fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Gammagraphx, Inc. (or missing ID) Device 0000
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2 (rev 01) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: dfd00000-dfdfffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Gammagraphx, Inc. (or missing ID) Device 0000
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3 (rev 01) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: dfc00000-dfcfffff
Prefetchable memory behind bridge: 00000000c0400000-00000000c05fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Gammagraphx, Inc. (or missing ID) Device 0000
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 01) (prog-if 00 [UHCI])
Subsystem: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1
Flags: bus master, medium devsel, latency 0, IRQ 23
I/O ports at bcc0 [size=32]
Kernel driver in use: uhci_hcd
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 01) (prog-if 20 [EHCI])
Subsystem: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at dfbfe800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c9) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=05, sec-latency=64
Capabilities: [50] Subsystem: Intel Corporation 82801 PCI Bridge
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 01)
Subsystem: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller
Flags: bus master, medium devsel, latency 0
Kernel modules: iTCO_wdt, intel-rng
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 01) (prog-if 8a [Master SecP PriP])
Subsystem: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at bcb0 [size=16]
Memory at dfbfec00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [70] Power Management version 2
Kernel driver in use: ata_piix
Kernel modules: ata_generic, pata_acpi
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 01)
Subsystem: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller
Flags: medium devsel, IRQ 19
I/O ports at bce0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c-i801
01:00.0 Ethernet controller: Intel Corporation 82598EB 10-Gigabit AT CX4 Network Connection (rev 01)
Subsystem: Intel Corporation Device a15f
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at dff20000 (32-bit, non-prefetchable) [size=128K]
Memory at dff40000 (32-bit, non-prefetchable) [size=256K]
I/O ports at fcc0 [size=32]
Memory at dfff4000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [60] MSI-X: Enable+ Count=18 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Kernel driver in use: ixgbe
Kernel modules: ixgbe
01:00.1 Ethernet controller: Intel Corporation 82598EB 10-Gigabit AT CX4 Network Connection (rev 01)
Subsystem: Intel Corporation Device a15f
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at dffc0000 (32-bit, non-prefetchable) [size=128K]
Memory at dff80000 (32-bit, non-prefetchable) [size=256K]
I/O ports at fce0 [size=32]
Memory at dfff8000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [60] MSI-X: Enable+ Count=18 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Kernel driver in use: ixgbe
Kernel modules: ixgbe
02:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
Subsystem: Intel Corporation Device 115f
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at dfe40000 (32-bit, non-prefetchable) [size=128K]
Memory at dfe60000 (32-bit, non-prefetchable) [size=128K]
I/O ports at ecc0 [size=32]
Expansion ROM at dfe80000 [disabled] [size=128K]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Kernel driver in use: e1000e
Kernel modules: e1000e
02:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
Subsystem: Intel Corporation Device 115f
Flags: bus master, fast devsel, latency 0, IRQ 51
Memory at dfea0000 (32-bit, non-prefetchable) [size=128K]
Memory at dfec0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at ece0 [size=32]
Expansion ROM at dfee0000 [disabled] [size=128K]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Kernel driver in use: e1000e
Kernel modules: e1000e
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Device 0000
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at dfde0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at dce0 [size=32]
Memory at dfddc000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
Kernel driver in use: e1000e
Kernel modules: e1000e
04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation Device 0000
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at dfce0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at cce0 [size=32]
Memory at dfcdc000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [a0] MSI-X: Enable+ Count=5 Masked-
Kernel driver in use: e1000e
Kernel modules: e1000e
Anshul,
We were not able to complete integration of the C6678 EVM with the Jumpgen processor card. We had the standard Jumpgen card which did not support a clock configuration that we supported at that time. I do not recall the details but we were told that we needed to order the Jumpgen card which supported a different configuration. Since that time we added support to the C6678 EVM for external PCIe clock.
I believe the PCIe clocking solution that will work is one where both the Jumpgen processor card and the C6678 EVM are both properly configured for external PCIe clock over the FCLK channel. This means that you will need to have an MCH with a clock module that can generate and distribute this clock to each module. The C6678 EVM can operate with either a narrow-band clock or a spread spectrum clock as long as both ends of the PCIe link are using the same clock.
What MCH are you using? Did you buy these components individually or through a System Integrator? Are you using the standard AMC.0 backplane or the one TI helped Elma create for our EVMs?
Please note that our EVMs are AMC-compatible. We do not advertize full AMC.0 compliance. That was beyond our support model. The software in the MMC is very simple and presents hard-coded responses to support e-keying queries. However, the currently available MMC code has been shown to support PCIe operation in multiple chassis configurations.
Tom
em using amc Blue-Eco Emla artical no 040033 index A.(serial no. 10561699 native sxpt rev A) and NAT-MCH as clock module and
PRM-100 jumpgen card (with fedora 64-bit os on it).
On which jumpgen card you have tested ?
Anshul,
It appears that the chassies we used contained the PRM-110.
We also were using the NAT MHC with the clock module option. Did you buy through a systems integrator or did you buy your parts individually?
Tom
I buy
-> jumpgen from Jumpgen System
-> blue eco elma and NAT MCH from NAT GMBH
-> do you want to say MCH instead of MHC
-> If you were using prm 110 then does it mean there is no way to run on prm 100 ( i dont have budget to buy prm 110 again).
-> just to inform you, I have not used nor or nand writer. does that hinders
Anshul,
I do not know the relative capabilities of the Jumpgen cards. You will need to contact Jumpgen for integration assistance. Specifically you need to know whether it operates on a local narrow-band clock or whether it can be configured to accept an external clock. Assuming the supported option is for it to accept an external clock, you then need to work with NAT to get the clock module on the MCH to provide an appropriate 100MHz FCLK to the Jumpgen card AND to the slot containing the EVM. Then we can help you get the EVM configured for external PCIe clock operation. You will also need to get a backplane diagram from NAT or ELMA that shows the PCIe link connectivity to make sure you use the proper slots.
Tom
Anshul,
This is what I explained above: Assuming the supported Jumpgen PCIe clock option is for it to accept an external clock, you then need to work with NAT to get the clock module on the MCH to provide an appropriate 100MHz FCLK to the Jumpgen card AND to the slot containing the EVM. You will also need to get a backplane diagram showing the port mapping from NAT or ELMA that shows the PCIe link connectivity to make sure you use the proper slots.
Tom
Ok I am going through user manual of MCH and blue eco
Tom Thanks for direction
