Developer Guide

  • 2022.1
  • 09/08/2022
  • Public
Contents

Set Up the Hardware

  1. Select hardware based on the following recommended configuration:
Units Needed
Equipment Specifications
2
The target systems: See Get Started Guide for UEFI BIOS (Public Document) or the Get Started Guide for Slim Bootloader (Public Document). Each target system contains an integrated TSN-compatible Intel® Ethernet Controller that you will use for this demo.
1
Minimum CAT-5E Ethernet cable
  1. Assign the system roles as follows:
Board A
Transmitter: The platform on which the Precision Time Protocol (PTP) clock of the TSN-compatible Intel® Ethernet Controller acts as the secondary clock.
Board B
Receiver: The platform on which the Precision Time Protocol (PTP) clock of the TSN-compatible Intel® Ethernet Controller acts as the primary clock.
  1. Set up the hardware:
    1. Make sure you have completed the steps in the Get Started Guide for UEFI BIOS (Public Document) or the Get Started Guide for Slim Bootloader (Public Document) with each board.
    2. Connect one end of a CAT-5e or better (for example, ‘CAT-6’) Ethernet cable to the RJ45 connector of
      Board A
      .
    3. Connect the other end of the cable to the RJ45 connector of
      Board B
      .
    4. Power on the two boards.
    5. To run the sample in the optimized mode, the boards must be configured to have at least 128 KB of L2 cache for allocation. Make sure you have configured the cache appropriately with the Cache Configurator. If you want to limit cache usage, update the L2 buffer size setting in the configuration file
      ${HOME}/.tcc.config
      to 131072 on both boards. See details on the configuration file at the How the System Allocates Buffers section.
    For details on how to configure the system to use cache allocation library, see the Before Using the Cache Allocation Library section.

Check for the Run-Time dependencies

The Real-Time Communication Demo depends on a number of System tools, and it implements checking for the availabitily of required run-time dependencies before running the Sample. Here is the list of required tools used in all modes:
ip
,
tc
,
ethtool
,
ptp4l
,
phc2sys
,
pmc
,
hwstamp_ctl
,
taskset
, and
killall
. The
iperf3
tool is also required when best effort traffic is requested to run with the sample (the
--no-best-effort
argument is
not
specified). See Command-Line Options for more details. Additionally, the
ssh
, and
scp
tools are required in the remote launch mode. See Run the SISO Example From One Side (Board A) for details.

Run the Demo

In the following steps, you will run the demo in two scenarios:
Basic
and
Single-Input Single-Output (SISO)
. You will collect and analyze the workload execution latencies and inter-packet latencies of both scenarios.

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.