Developer Guide

  • 2022.1
  • 09/08/2022
  • Public
Contents

Troubleshooting

Option
Description
tcc_rt_communication_ demo
reports:
Unknown interface name was specified.
Specify the valid interface name (you can check the valid interface name with the "ifconfig" command)
Make sure you provide the correct interface name for the TSN-compatible Intel® Ethernet Controller:
Run:
lspci -v
Locate the Peripheral Component Interconnect (PCI) bus information (example: 01.00.0) of the TSN-compatible Intel® Ethernet Controller:
Run:
ethtool -i <enp1s0>
and find the bus information (example: 0000:01:00.0) that matches the previously found address.
tcc_rt_communication_demo
reports:
Required tool "<tool>" is not available in the system
Make sure the required
<tool>
is availalbe in the system, update the
PATH
environment variable if needed.
tcc_rt_communication_ demo
reports:
Directory <path> with
configuration profiles does not exist.
Make sure you provide the correct path to the directory containing configuration files for the demo. If the directory does not exist, create it and add subdirectories containing configuration files for the basic and SISO modes.
tcc_rt_communication_ demo
reports:
Path to output file (<path name>)
does not exist.
Make sure you provide the correct path to the directory for the output file. If the directory does not exist, create it.
tcc_rt_communication_ demo
reports:
Profile <profile name> not supported.
Use [-h] to see help information.
Make sure to run the
tcc_rt_communication_demo
script with a supported profile. Supported profiles are:
basic-a-opt
,
basic-a-noopt
,
basic-b-opt
,
basic-b-noopt
,
siso-single-a-opt
,
siso-single-a-noopt
,
siso-single-b-opt
, and
siso-single-b-noopt
.
tcc_rt_communication_ demo
reports:
Mode <mode name> not supported.
Use [-h] to see help information.
Make sure to run the
tcc_rt_communication_demo
script with a supported mode. Supported modes are:
clock
,
tsn
,
run
,
setup
, and
all
.
tcc_rt_communication_ demo
reports:
Binary "<binary name>" was not found in
directories provided by PATH environment variable.
Try to launch script with [-e] option and provide path
to binary executables manually.
Make sure the following binary executables are installed in one of the directories indicated by the PATH environment variable:
  • opcua-server
If the binaries are not installed in one of these directories, specify the correct directory using the [-e] CLI option.
tcc_rt_communication_ demo
reports:
Path to directory with binary
executables (<path name>) does not exist.
Make sure you provide the correct path to the directory with the following binary executables:
  • opcua-server
If the directory does not exist, create it and place the binaries into it.
Loss of connectivity with the board after using a network interface name that is not related to the internal communication between Board A and Board B.
Restart the board using one of the following methods:
  1. Through the GUI shell interface if the board is connected to a keyboard, video, and mouse (KVM) device.
  2. By pressing the reset button.
Loss of connectivity between Board A and Board B during demo execution.
Restart the boards using one of the following methods:
  1. Through the GUI shell interface if the board is connected to a keyboard, video, and mouse (KVM) device.
  2. By pressing the reset button.
The transmission latency is too long for the SISO example, more than 100 ms.
Make sure the compute and the monitor select the same base time (can be checked in the console logs). If the base time is different, try launching the compute and the monitor at the same time (with the time difference of less than 2 seconds).
The transmission latency is very large or negative.
The time synchronization is lost. Check the following log files:
/var/log/ptp4l.log
and
/var/log/phc2sys.log
on both boards. Run the
tcc_rt_communication_demo
script with added
[-m clock]
option. This command will restart the time synchronization.
tcc_rt_communication_demo
in the optimized mode fails to start. The console logs show:
Error: cannot allocate buffer for the pointer chasing workload
.
Possible solutions:
  • 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.
  • Make sure the
    Intel® TCC Mode
    and
    Software SRAM
    options are enabled in BIOS.
  • Make sure you have enabled the runtime support for software SRAM on each board by running the
    tcc_setup_ssram.sh enable
    script.
  • Make sure the L2 buffer size setting in the configuration file
    ${HOME}/.tcc.config
    is at least 131072 on both boards or set to zeroes.
  • Export the
    TCC_LOG_LEVEL=DEBUG
    environment variable and run the sample again. This variable enables the console logs for the cache allocation library to show errors about the software SRAM allocation.
  • Disable the software SRAM by running
    tcc_setup_ssram.sh disable
    , then enable the software SRAM by running
    tcc_setup_ssram.sh enable
    .

Product and Performance Information

1

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