.. include:: ../substitutions.rst

miniPCIe
========

The PCI Express (PCIe) interface of the |product| SOM provides PCIe Gen. 2.0 (1-lane) functionality. Furthermore, the interface is backwards compatible to the Gen1 specification. This guide will show you how to do a basic functional test of the miniPCIe interface on the |product-cb| kit. To learn more information about the |product| PCIe interface, please see section |hw-ref-pcie| in the |hw-manual-link|.

.. jinja::
   :file: ../templates/interfaceguides/pcie-connector-location.jinja


Requirements
-------------

* Mini PCI Express Single Port RJ45 Ethernet 10/100/1000Mbps Gigabit LAN Card


Development Kit Setup
----------------------

* First, 'poweroff' the development kit.

  .. code-block:: console
     :substitutions:

     |target-prompt| poweroff

* With the power removed, insert the miniPCIe adapter into the development kit's miniPCIe slot.

  It is recommended to use some hardware to secure the miniPCIe card to the development kit carrier board. A small M2 bolt and nut should do the trick.

* Power on the development kit and stop in U-Boot when prompted.

Confirming Mini PCIe Connection
--------------------------------

* Once the system has booted into Linux, verify that the PCIe card has been detected by running:

.. code-block:: console
   :substitutions:

   |target-prompt| lspci
   00:00.0 PCI bridge: Texas Instruments Device b010
   01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

* This output confirms the presence of TI’s PCI bridge and the detected PCIe card. For more details about a specific device, specify the slot using the ``-s`` option:

.. code-block:: console
   :substitutions:

   |target-prompt| lspci -s 01:00.0 -vm
   Device: 01:00.0
   Class:  Ethernet controller
   Vendor: Intel Corporation
   Device: I210 Gigabit Network Connection
   Rev:    03
   ProgIf: 00

* Since this particular PCIe card is an Ethernet controller, an additional Ethernet interface should be available. Verify this using:

.. code-block:: console
   :substitutions:

   |target-prompt| ip link
   1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
       link/ether 00:b0:d0:63:c2:26 brd ff:ff:ff:ff:ff:ff
       altname eth0
   3: main_mcan0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 10
       link/can
   4: end1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
       link/ether 02:2a:c2:40:c1:4c brd ff:ff:ff:ff:ff:ff
       altname eth1

* For details on configuring and using Ethernet interfaces, refer to the |ref-eth| section.