![]() |
![]() |
The MCUSW package consists of MCAL Driver & Demos/Applications for J721E/AM65X family of devices . The MCAL modules are compliant to AUTOSAR specification versioned 4.3.1.
Refer to Processor SDK Automotive manifest at top level and [HTML] for MCUSW Manifest
The MCUSW User Guide [HTML] provides the documentation and references necessary to begin development on TI's platforms using MCUSW.
Refer to following documentation for further details:
MCUSW User Guide | This document details Supported driver, Installation, Dependencies, Build instructions, Steps to run example applications, Module Specific User Guides, API Guide, Test Reports, Design Document and others | [HTML] |
MCAL Configurator User Guide | Refer this before attempting to reconfigure MCAL modules. This include steps to Install Configurator (EB), Configurator Licensing, Generation of MCAL Configurations and others Note that for J721E & DRA80X, the configurator package has to be installed separately, please refer Link |
[HTML] |
New features supported in this release:
SoC | HOST (OS) | Target (OS) | Test Platform |
J721E | Windows / Linux, EB configurator only on Windows | NO OS or TI RTOS | J721E EVM |
AM65X | Windows / Linux, EB configurator only on Windows | NO OS or TI RTOS | AM65X EVM |
This release was built and validated using the following tools. Please refer [Detailed Validation Report]
Build Tools (included in Processor SDK):
ID | Description |
MCAL-5034 | [Eth]EthDemEventParameterRefs configuration not generated correctly |
ID | Description | Workaround | Comments |
MCAL-2503 | [Can] Lost messages are not reported, when CAN driver is operated in Sync/Polled mode | Switch to Asynchronous mode or interrupt mode | |
MCAL-2502 | [Can] Message is not received for 50kbps baud rate | Switch to higher baud rates | PCAN tool was used to generate CAN packets at 50 Kbps baud rate, suspected to be a tool issue |
MCAL-4935 | MCUSW Boot App: Fails to boot Linux in any boot mode due to misaligned Sciclient Board data | N/A | Cannot properly boot Linux all the way to kernel prompt due to mismatched Sciclient board_data (expected by Linux), currently loaded by the SBL |
ID | Description | Workaround | Comments |
MCAL-2527 | [EB] Generation of module configuration using EB Tresos command line is not supported | Use EB Tresos GUI Mode | Please note that EPD / ARXML can be generated from XDM files |
MCAL-3962 | [Build] Custom SBL build break in Windows Environment | Use linux environment to build | In cases where only CCS is used to debug/run applications, exclude SBL Custom from build. Please refer [HTML] for details |
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 |