Product Release Notes
Table of Contents
Introduction
This is the release notes for MCUSW 03.00.00 release, produced on 2023-02-10.
The MCUSW package consists of MCAL Driver & Demos/Applications for J721E/J7200/J721S2/J784S4 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/J721S2/J784S4.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_03_00_00_06_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 & J721S2 & J7200 & J784S4
- AUTOSAR Specification Version: 4.3.1
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 FreeRTOS | J721E EVM |
| J7200 | Windows / Linux, EB configurator only on Windows | NO OS or FreeRTOS | J7200 EVM |
| J721S2 | Windows / Linux, EB configurator only on Windows | NO OS or FreeRTOS | J721S2 EVM |
| J784S4 | Windows / Linux, EB configurator only on Windows | NO OS or FreeRTOS | J784S4 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-9475 | CAN app Example not working in non internal loop back mode |
| MCAL-9303 | WDG example MCU_SAFETY_ERRORn pin not driven low |
| MCAL-9230 | CDD IPC communication with A72 |
| MCAL-9024 | DIO - J784S4/J721S2 Reserved GPIO Pins incorrect |
| MCAL-9274 | ADC App testing for MCU2_1 core is hung in J7AHP |
| MCAL-9222 | FLASH: Fls_indac app not working with interrupt mode |
| MCAL-9275 | WDG App testing for MCU2_1 core is hung in J7AHP |
| MCAL-9512 | Vector Reported Compliance Issues For various Drivers |
| MCAL-9224 | ePwm Example App is hungs with PWM_NOTIFICATION_SUPPORTED. |
| MCAL-8925 | channel identifier CddIpcConf_IpcComChanId_Cdd_IpcMpu10 missing in the generated CddIpc_Demo_cfg |
| MCAL-8348 | WDG interrupt not working on mcu2_1 |
| MCAL-7960 | FLS example on J7AEP and J7200 with interrupt mode fail. |
| MCAL-7978 | CDD IPC: Cdd_IpcNewMsgCb() logic causes unnecessary callbacks from 7.1 SDK onwards |
| MCAL-9512 | Vector Reported Compliance Issues For various Drivers |
Open Defects
| ID | Summary |
|---|---|
| MCAL-8075 | CDD IPC MCAL: MPU core support needs to enabled. |
| MCAL-9282 | ICU: DET error in example app for PWM not initialized for mcu1_0 and mcu2_1 |
| MCAL-9144 | SPI Driver Loopback Disable API not present |
| MCAL-9504 | ICU: No value for Signalnotification for AEP MCU2_1 core |
Known Limitations
| ID | Description | Workaround | Comments |
| MCAL-9499 | FLASH: Interrupt Mode is not working | None | The FLS example for INDAC mode not working with interupt ON for mcu2_1 and mcu1_0 core. This causes DET error and prevents it from finishing. |
| MCAL-9503 | Redeclaration of types in Mcu.h and Mcu_Cfg.h | By using polling mode | Re declaration of Mcu_ClockConfigType,Mcu_ClockConfigPtrType and Mcu_ConfigType is found in Mcu.h and Mcu_Cfg.h (generated from "MCUSW_02_00_00_06_CONFIG" configurator). |
| MCAL-5231 | dummyIRQ not set to implemet WA for i2162 in . | None. | Integrate CAN functionality in any BIOS demo in MCUSW (apart from the can_profile_app and can_profile_xip_app). |
| MCAL-5208 | Ethernet firmware failed to load after BIST enabled is enabled in BootApp. | None | When BIST is enabled in the Boot Application, ethernet firmware loading on mcu2_0 hangs. Ethernet firmware tries to setup 250MHz clock for RGMII in below API in the file enet_apputils_k3.c file and this API seems hanging. |
| MCAL-9283 | CAN BUS OFF recovery not available. | None. | CAN bus off recovery sequence missing in the MCAL CAN applications. |
| MCAL-9179 | SPI Driver cannot communicate with External SPI Device. | with proper pinmux configuration, external loopback can be established. | The SPI driver is currently tested using only internal loopback enabled, and the examples are geared toward this as well. |
| MCAL-9463 | FLASH: Write/Read operation skips DATA bytes in interrupt mode. | None. | The Write/Read operations skips 512 bytes data in interrupt mode. |
| None | IPC Linux communication is not validated for other SOCs. | None. | support IPC Linux communication. |
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 2023, Texas Instruments Incorporated