Product Release Notes

Table of Contents

Introduction

This is the release notes for mcusw 11.01.00 release, produced on 2025-08-22. The MCUSW package consists of MCAL Driver & Demos/Applications for J721E/J7200/J721S2/J784S4/J742S2 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

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 User Guide Top

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.

MCUSW Configurator User Guide

Dependencies

List of items needs along with MCUSW Package:

  • MCUSW Configurator installer

    • Configurator package contains following items:

  • MCAL Configurator Plugins (${EB_INSTALL_DIR}/mcal_drv/mcal_config).
  • MCAL Compliance Support Package with Safety Collateral.

    • Configurator package is released as a secure resource. Please contact TI represtative to get access for same. Refer user guide for detailed steps of installing and using the configurator package.

    What’s New

    New features supported in this release:

    1. Several Fixed Defects.
    2. Multi-flash support features

    Compatibility

    IMPORTANT NOTE: User should ensure to use below modules version for MCUSW_J7_11.01.00 release. User should take care to not mis-match or mix-and-match the versions with various MCUSW releases. Bundle Version of all plugins is 11.1.0.

    Module Previous Module Verson Current Module Version Remarks
    ADC 9.2.0 9.2.0 None
    CAN 10.2.0 10.2.1 Patch version Update
    CDD IPC 11.2.0 11.3.0 Minor version Update
    DIO 10.1.0 10.1.0 None
    GPT 9.2.0 9.2.1 Patch version Update
    ICU 9.1.0 9.1.0 None
    PWM/EPWM 11.1.0 11.1.0 None
    MCU 10.0.0 10.1.1 Minor and Patch Version Update
    SPI 9.2.0 9.2.1 Patch version Update
    FLS 11.1.0 12.0.0 Major Version Update
    WDG 9.1.0 9.1.0 None
    ETH 11.0.0 11.0.0 None
    ETH TRCV 11.0.0 11.0.0 None
    OS 9.0.1 9.0.1 None
    EcuM 9.0.0 9.0.0 None
    DEM 9.0.0 9.0.0 None

    Device Support

    Supported SoCs: J721E & J721S2 & J7200 & J784S4 & J742S2

    Validation

    This release was built and validated using the following tools.

    Build Tools (included in Processor SDK)

    ti-cgt-armllvm_4.0.1.LTS

    Fixed Defects

    ID Summary
    MCAL-30607 WDG: Watchdog Reaction set as non configurable parameter in Configurator
    MCAL-31713 GPT: Invalid allocation of Gpt_ChannelStateType size to channelWakeupEnFlag
    MCAL-31670 SPI: Wrong selection of external id in spi _copyconfig API
    MCAL-31473 IPC: CDD IPC control message boundary check is invalid
    MCAL-31460 SPI: Duplicate container for SpiDemEventParameterRefs in epd file
    MCAL-31459 MCU: Max value for McuResetReason is 3 in arxml file but default value supports higher value for reset reason
    MCAL-31458 FLS: Duplicate short-name and default-values tags in epd file
    MCAL-31457 IPC: Use of int32_t for prototype definition in CDD_IPC
    MCAL-30733 CAN: Wrong base address in Can_RegisterReadback API
    MCAL-30470 MCAN: MCAN module of MCAL has undefined register initialization
    MCAL-29774 FLS: DET reported by Fls_Erase when not aligned with NOR_BLOCK_SIZE
    MCAL-29484 IPC: In IPC,endpoint requested is greater than 256 error needs to be reported
    MCAL-28234 IPC: RPMessage_enqueMsg() handles incoming messages twice, first queue is ignored.
    MCAL-27141 MCU: Mcu_PerformSoftSysReset API doesn't perform soft system reset

    Known Limitations

    None

    Support

    For technical support and additional assistance, visit E2E or contact local TI Field Application Engineer.