![]() |
![]() |
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.
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] |
Module | Changes Over Previous Release |
CAN-Eth Gateway Demo |
|
SoC | HOST (OS) | Target (OS) | Test Platform |
J721E | Linux | TI RTOS | J721E EVM + GESI card |
This release was built and validated using the following tools.
Build Tools (included in Processor SDK):
ID | Description | Module |
NA | NA | CAN-Eth Gateway |
ID | Description | Workaround | Comments | Module |
ADASVISION-3729 | Test tool reports high Max latency (milliseconds) occassionally for Eth-to-CAN routing | Run at a lower inter packet gap and fewer number of packets | Not a major issue, does not affect routing as average latency is still low. | CAN-Eth Gateway |
ADASVISION-3961 | Unexplained packet drop for Ethernet to CAN routing | NA | Suspected to be a queue overflow issue, but not root caused. | CAN-Eth Gateway |
ID | Description | Workaround | Comments | Module |
ADASVISION-3962 | Implement polling mode for CAN to reduce average and min latencies | Run at a lower inter packet gap and fewer number of packets | This results in high latencies for CAN to CAN routing. Use workaround to see actual latencies or do manual routing | CAN-Eth Gateway |
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 |