The MCUSW package consists of MCAL Driver & Demos/Applications for J721E/J7200 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.
Data Sheet information is NOT included on ti.com public release and is available in the ADDON package for Processor SDK RTOS Automotive SDK for J7200/J721E.Once the ADDON package is installed, the datasheet can be found here ${PSDKRA_ADDON_PATH}/mcusw/mcal_drv/docs/datasheet/index.html
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 |
[HTML] |
Dependencies (NOT included in MCUSW Package):
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 |
J7200 | Windows / Linux, EB configurator only on Windows | NO OS or TI RTOS | J7200 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-5052 | [Spi]External Device Id is mapping to wrong MCSPI Hardware Unit |
MCAL-5044 | Configuring multiple filters for one MCAN HW buffer creates a problem |
MCAL-5034 | [Eth]EthDemEventParameterRefs configuration not generated correctly |
MCAL-5032 | [Can] Issue in Can driver transition from SLEEP to STOPPED |
MCAL-5022 | Eth: include of Eth_Cfg.h in Eth_GeneralTypes.h |
MCAL-5020 | FLS MCAL: OSPI_Control API definition and declaration mismatch |
MCAL-5019 | [Gpt] GPT Configuration name generated in the EB Tresos is incorrect |
MCAL-5013 | CAN-FD flag is not set in the CAN driver when CanIf_RxIndication is called |
MCAL-4935 | MCUSW Boot App: Fails to boot Linux in any boot mode due to misaligned Sciclient Board data |
MCAL-4510 | MCUSW Demo: CAN Response and Bootloader Demo Application: MMCSD boot fails to boot linux |
MCAL-5070 | MCUSW Boot App has boot errors when using DMA with OSPI boot |
MCAL-5048 | [EthTrcv]EthTrcvDemEventParameterRefs configuration not generated correctly |
ID | Description | Workaround | Comments |
MCAL-5062 | FLS MCAL: Code being written at two locations | None | No impact to the code application behavior |
MCAL-4970 | [Eth]Only Pre-Compile Variant is supported in Eth Configurator | None | No impact to the supported features |
MCAL-2503 | [Can] Can message lost case is not supported by hardware in polling mode | Switch to Asynchronous mode or Interrupt mode | |
MCAL-2502 | [Can] Message is not received for 50kbps baud rate configuration in PCAN Tool | Switch to high baud rate | PCAN tool was used to generate CAN packets at 50 Kbps baud rate, suspected to be a tool issue |
MCAL-5068 | [XIP]Dem Errors are reported for Can Profile XIP on J721E | None | Functionality is fine, DEM errors are reported and performance degradation is observed |
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 |