Gateway Demo Release Notes

Version: 01.01.00.02

Contents

  1. Introduction
  2. Getting Started
  3. What's New
  4. Device Support
  5. Validation Information
  6. Fixed Issues
  7. Known Issues
  8. Technical Support
  9. Package Versioning

Introduction

The Gateway Demo package consists of all demos related to Automotive Gateway for J721E family of devices . These demos use AUTOSAR compliant drivers. At present only CAN-Ethernet Gateway demo is part of the package.

Getting Started

Refer to following documentation for further details:

Module Description Document Link
CAN-Eth Gateway Demo This document details Hardware and Software requirements, Installation, Dependencies, Build instructions, Steps to run the demo, Changes over previous release and Limitations [HTML]

What's New

Module Changes Over Previous Release
CAN-Eth Gateway Demo
  • Optimizations in application and drivers to improve performance
  • Packets are received in polled mode instead of interrupt mode
  • Routing Table architecture has been simplified. Routing can now be configured by the user per CAN ID. See User Guide
  • Changes in CPU Load calculation methodology

Device Support

SoC HOST (OS) Target (OS) Test Platform
J721E Linux TI RTOS J721E EVM + GESI card

Validation Information

This release was built and validated using the following tools.

Build Tools (included in Processor SDK):

Fixed Issues

ID Description Module
ADASVISION-3729 Test tool reports high Max latency (milliseconds) occassionally for Eth-to-CAN routing CAN-Eth Gateway
ADASVISION-3961 Unexplained packet drop for Ethernet to CAN routing CAN-Eth Gateway

Known Issues

ID Description Workaround Comments Module
ADASVISION-4002 Gateway app build system doesn't take care of library dependency. For example if a file is changed in CAN driver in MCUSW or Eth FW Delete the contents of binary folder and build NA CAN-Eth Gateway
ADASVISION-4152 Gateway app does not boot ocassionally with OSPI boot Try to boot with CCS or try again if it fails NA CAN-Eth Gateway

Known Limitations

ID Description Workaround Comments Module
NA NA NA NA CAN-Eth Gateway

Technical Support

For technical support and additional assistance, visit or [E2E] contact local TI Field Application Engineer

Package Versioning

Each package version is composed of 4 period-delimited numbers - represented here by the letters M, m, p and b [M.m.p.b]. The table below provides a descriptive reference regarding package version numbering.

Digit Meaning Description
1 (M=Major) Major revision Incremented when the new version is substantially different from the previous For example, a new module added or an existing module's algorithm significantly altered.
2 (m=minor) Minor revision Incremented when the new version has changed but not in a major way. For example, some minor changes in the API or feature set.
3 (p=patch) Patch number Incremented for all other source code changes. This include any packaging support code.
4 (b=build) Build number Incremented for each release delivery to CM. Reset for any change to M, m or p

Copyright 2020, Texas Instruments Incorporated