Product Release Notes
Table of Contents
Introduction
This is the release notes for MCUSW 01.05.00 release, produced on 2022-03-29.
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 .
Licensing
Refer to Processor SDK Automotive manifest at top level and MCUSW Manifest for MCUSW Manifest.
Getting Started
The MCUSW User Guide provides the documentation and references necessary to begin development on TI’s platforms using MCUSW
Datasheet
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
Documentation
- 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.
- MCUSW 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.
Dependencies
NOT Included in MCUSW Package:
MCUSW MCAL Configurator Lists the steps required to get the same
Configurator package name is MCUSW_01_05_00_01_CONFIG-windows-installer.exe, contains following items
- EB Installer (${EB_INSTALL_DIR}/mcal_drv/mcal_config/Elektrobit/installer)
- EB License Administrator (${EB_INSTALL_DIR}/mcal_drv/mcal_config/Elektrobit/installer)
- EB Documentation (${EB_INSTALL_DIR}/mcal_drv/mcal_config/Elektrobit/docs)
What’s New
New features supported in this release:
- Supported SoCs: J721E & J7200
- AUTOSAR Specification Version: 4.3.1
- MCAL is abstracted to separate the SoC specific integration and core MCAL driver implementation. In this way the core MCAL modules can be re-used and/or expanded for future devices. The existing CSL-R and CSL-FL for the hardware IP modules that will be used by the MCAL drivers will be reused from SDK as applicable for the software to interface with the hardware. It will be included in the MCAL software package itself and will be renamed in order to avoid conflicts with the existing CSL code and usage. MCAL is architected such that new SoC variant support can be added without disturbing the existing support. Some point to note about MCAL architecture: · The core driver code (along with the HW IP source code) has been implemented in way that is SoC agnostic. This means that this code would not need any modification when new SoC support is added (given that HW IP stays the same). · All the SoC specific code is moved to the configuration plugins for each driver modules. When a new SoC is added, the new plugin source created will accommodate the SoC level changed required (ex. instance numbers). · Each SoC will have its individual configuration plugin per driver module. User will have to choose based on SoC of interest.
- We have officially de-scoped the use of SYS/Bios for the demos.
Compatibility
- None different than last release.
Device Support
| 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 |
Validation
This release was built and validated using the following tools. Please refer Validation Notes Main Page
Build Tools (included in Processor SDK)
- ti-cgt-armllvm_1.3.0.LTS
- Free RTOS: 6.83.00.18
- GCC: 9.2-2019.12
Fixed Defects
| ID | Summary |
|---|---|
| MCAL-5217 | MCUSW: SPI MCAL: Not able to set SpiSupportConcurrentSyncTransmit in EB |
| MCAL-5107 | TimingValues parameter wrongly populated in Can_BaudConfigStruct and Can_FdBaudConfigStruct |
Open Defects
| ID | Summary |
|---|---|
| MCAL-7962 | Misspelling of Icu_GetTimestampIndex |
| MCAL-7960 | The FLS example for J7200 mcu2_1 uses a different interrupt that J721E. |
| MCAL-7933 | ICU for mcu2_1 on J721e gets stuck |
| MCAL-7906 | SPI test for mcu2_1 core does not finish |
| MCAL-7893 | Timed waits in module init shall not use GetCounterValue |
| MCAL-5415 | Issue with Tresos plugins from MCUSW_01_03_02_04_CONFIG in ETH |
| MCAL-5217 | MCUSW: SPI MCAL: Not able to set SpiSupportConcurrentSyncTransmit in EB |
| MCAL-5205 | can_profile_app not giving CAN TX signal output on J721E HS device |
| MCAL-5185 | MCUSW: SPI MCAL: DMA Mode is not working if length is not FIFO aligned |
| MCAL-5174 | ICU: Timestamp API results in Incorrect Values |
| MCAL-5163 | Eth MCAL: mcusw eth_app polling mode error |
| MCAL-5068 | [XIP]Can Profile XIP on J721E performance degradation |
| MCAL-5062 | FLS MCAL: Code being written at two locations |
| MCAL-4970 | [Eth]Only Pre-Compile Variant is supported in Eth Configurator |
Known Limitations
| ID | Description | Workaround | Comments |
| MCAL-5174 | [ICU] Icu module TimeStamp API returns incorrect counter values. | None | Usage of this API will result in delta counter values, instead of absolute counter values. Please note that only preliminary testing has been performed for this module. Extensive validation is planned for future release. |
| MCAL-5185 | [SPI] DMA mode is not working if lenght is not FIFO aligned. | None | Please note that only preliminary testing as been performed for this SPI DMA feature. Extensive validation is planned for future release. |
Support
For technical support and additional assistance, visit E2E or contact local TI Field Application Engineer.
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 2021, Texas Instruments Incorporated