MCUSW Release Notes

Version: 01.02.01.00

Introduction
Licensing
Getting Started
Documentation
What's New
Upgrade and Compatibility Information
Device Support
Validation Information
Fixed Issues
Known Issues
Technical Support
Package Versioning

Introduction

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.

Licensing

Refer to Processor SDK Automotive manifest at top level and [HTML] for MCUSW Manifest

Getting Started

The MCUSW User Guide [HTML] provides the documentation and references necessary to begin development on TI's platforms using MCUSW.

Documentation

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]

What's New

New features supported in this release:

This is a patch release on top of MCUSW_01.02.00 which includes bug fix MCAL-5034.Please refer Fixed Issues section for more details.
Supported SoC: J721E & AM65X
MCAL Drivers:

AUTOSAR Specification Version 4.3.1

Support for v4.2.1 has been deprecated starting this release

FLS MCAL Driver on MCU R5 : J721E only

FLS MCAL support for 'M35XU512' Flash part on J721E EVM
FLS MCAL support for storage mode (read, write, erase)
FLS MCAL support for XIP (No write/Erase support while in XIP mode)
Sample Example Application & Elektrobit based configurator

Refer [Support MCAL Driver] for complete list of supported drivers
Defect Fixes
MCUSW Demo Applications:

[Execute In Place (XIP)] , Demonstrates execution of MCAL demo applications from external flash.

Boot App & CAN Response Updates : J721E only

[Early CAN response & Boot Application] , Demonstrates early CAN response and boot of other processing cores

Adds demonstration of Early CAN response on a J721E GP device in less than 50 ms

[Boot HLOS] , Demonstrates booting A72 with HLOS (QNX) or TI RTOS, and also booting other MAIN domain R5F, C66x, and C7x cores

Boot App can support QNX boot on A72, along with booting Vision Apps binaries on other cores (required for 3D SRV, etc.)
Adds specific R5 MPU config for the Boot App to avoid HLOS boot issues seen when using default PDK R5 MPU config
Adds board pinmux config setup in Boot App for Ethernet RMII and CPSW9g MDIO usage
Boot App now leaves OSPI flash in SPI mode after booting remote cores - allows HLOS to take control of OSPI
Boot App now expands the original 2-stage booting to 3-stage booting with flexible ordering of cores. Default config allows faster Eth. Switch F/W loading

Updated OSPI flash addresses to be used with new 3-stage booting
Fixed conflicts with boot media usage (OSPI / MMCSD), by booting other remote cores before booting HLOS
Updated makemulticore.sh to call a script to generate the .appimage files for each of the 3 boot stages

Upgrade and Compatibility Information

Compatibility Break

AUTOSAR Version : AUTOSAR version has been migrated to 4.3.1. AUTOSAR 4.2.1 has been deprecated
Can : Can interface parameters are changed due to 4.3.1 porting.

Feature NOT supported

Demo : Boot Demos : Not supported on AM65X/DRA80X

Device Support

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

Validation Information

This release was built and validated using the following tools. Please refer [Detailed Validation Report]

Build Tools (included in Processor SDK):

ARM R5F Code Generation Tools version: 20.2.0.LTS
XDC Tool: 3_61_00_16_core
TI RTOS: 6_82_01_19

Dependencies (NOT included in MCUSW):

MCUSW MCAL Configurator Lists the steps required to get the same

EB Installer (mcusw/mcal_drv/mcal_config/Elektrobit/installer)
EB License Administrator (mcusw/mcal_drv/mcal_config/Elektrobit/installer)
EB Documentation (mcusw/mcal_drv/mcal_config/Elektrobit/installer)

Fixed Issues

ID Description

MCAL-5034 [Eth]EthDemEventParameterRefs configuration not generated correctly

Known Issues

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

Known Limitations

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

Technical Support

[E2E]

Package 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

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]

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

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