VLAN Configuration

IBF VLAN aka VLAN 200 AKA TACP VLAN

Intra-board function VLAN is used for communication between onboard devices like Aurix, Tegra, and switches. No Ethernet frames over this VLAN go outside the board. IBF VLAN is used for the following:

  1. Tegra-Tegra communication
  2. Tegra-Aurix communication
  3. Aurix OTA from Tegra
  4. Switch Firmware over-the-air (OTA) updates

VLAN 200 Config in P3710

In 3710, the following ports and controllers are part of VLAN 200.

  • Tegra MGBE-2 interface
  • Aurix Ethernet interface
  • Switch-1: P0 (Internal CPU) , P10 (interfacing MGBE-2), P8 (Aurix interfacing port ) and P7 (Switch-2 interfacing port )
  • Switch-2: P0 (Internal CPU) and P1 (Switch-2 interfacing port )

VLAN 200 Config in P3663

In 3663, the following ports and controllers are part of VLAN 200.

  • Tegra MGBE-2 interface
  • Aurix Ethernet interface
  • Switch-1: P0 (Internal CPU) , P10 (interfacing MGBE-2) and P8 (Aurix interfacing port )

TACP Networking VLAN Configuration

The VLAN networking configuration to set up this channel occurs in three distinct places in standard or safety operating systems.

  1. Tegra (Orin) side configuration
  2. Network switch configuration
  3. Aurix AUTOSAR configuration

Tegra (Orin) Side Configuration

For standard OS the TACP VLAN configuration parameters are stored in the device tree while the safety OS has its values within a configuration file.

Standard OS

For standard OS the TACP VLAN configuration parameters are stored in the device tree, which has files located here:

<top>/hardware/nvidia/platform/t23x/automotive/kernel-dts/

They are further broken down by the board type. The networking information is in the following device tree files under the node board_config.

p3710/common/tegra234-p3710-0010.dtsi
p3663/common/tegra234-p3663-0001.dtsi

The configuration file supports these parameters under the board config node required for the TACP VLAN setup.

  • Tegra (Orin) IP address
  • VLAN ID and interface name 
board_config {
 		TEGRA_IP_ADDRESS="10.42.0.28";
 		aurix {
 			/* Provide instance.200 as aurix interface,
 			 * where instance is network controller
 			 * interface name */
 			aurix_linux_interface="mgbe2_0.200";
 			aurix_qnx_interface="mgbe2_0.200";
 			AURIX_IP_ADDRESS="10.42.0.146";
 		};

Where aurix_qnx_interface/ aurix_linux_interface = <MAIN_ETH_IFACE>.<VLANID> : <MAIN_ETH_IFACE> is the network interface over the VLAN is supposed to created and <VLANID> is the vlan ID of the newly created VLAN interface. TEGRA_IP_ADDRESS= <IP_ADDRESS> : IP address for Tegra tacp VLAN interface

Tegra-side TACP VLAN Customization

Tegra side TACP VLAN customization is possible for the following parameters by changing the value assigned in the board-specific device tree in standard OS, and by changing the hardcoded values in the bootup script.

  • Tegra IP address
  • VLAN ID and interface name
  • Changes in VLAN parameters requires corresponding changes in the Aurix AFW for new VLAN support along with the new VLAN configuration in the network switches.
  • Changes in IP address (if other subnet) requires a change in IP address of the VLAN interface on the Aurix MCU side.

Network Switch VLAN Configuration

In NVIDIA platforms, network switch configuration occurs via Aurix MCU firmware or through the network switch firmware. These configuration cannot be altered in run time.

Aurix MCU VLAN Configuration

Refer to the MCU Porting Guide for details.