|
|
The Gateway Demo package consists of all demos related to Automotive Gateway for J7 family of devices . These demos use AUTOSAR compliant drivers. At present CAN-Ethernet Gateway demo, CAN Generator application and Low Latency Demo are part of the package.
Refer to following documentation for further details:
| Module | Description | Document Link |
| All | 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 |
|
| CAN Generator Application |
|
| Low Latency CAN Demo Application |
|
| SoC | HOST (OS) | Target (OS) | Test Platform |
| J721E | Linux | TI RTOS | J721E EVM + GESI card |
| J7200 | Linux | TI RTOS | J7200 EVM + GESI card + SGMII card |
This release was built and validated using the following tools.
Build Tools (included in Processor SDK):
| ID | Description | Module | Platform |
| NA | NA | NA | NA |
| ID | Description | Workaround | Comments | Module | Platform |
| 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 | All |
| ADASVISION-4420 | Gateway combined image generates Invalid Magic number with OSPI boot | Use CCS Boot | NA | CAN-Eth Gateway and CAN Generator app | DRA829 |
| ADASVISION-4549 | Packet loss seen while receiving ethernet frames on J7VCL | NA | NA | CAN-Eth Gateway | DRA821 |
| ADASVISION-4901 | IPC with Main R5F 2_0 hangs in FreeRTOS | Use TI-RTOS binaries | NA | CAN-Eth Gateway | All |
| ADASVISION-4916 | Can-Eth Gateway OSPI Boot hangs in IPC for TI-RTOS | Use CCS Boot | NA | CAN-Eth Gateway | DRA821 |
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 |