YTM32B1MC0x_sMCAL_3_0_0 Release Notes

Frankie

1. Overview

YUNTU MCAL(Microcontroller Abstract Layer) software package is designed by YTMicro AE team to support customers on AUTOSAR compliant application software development. The YUNTU MCAL is developed according to the AUTOSAR CP Release v4.4.0 standard.

1.1 Release Type

Major Release — This is a major version upgrade, representing a significant milestone in the YUNTU MCAL product lifecycle.
Status: Internal Released | Release Date: 2026-08-04

1.2 Release Highlights

The 3.0.0 release is the result of a comprehensive software architecture refactoring and quality upgrade program with the following goals:

ASPICE Process Compliance — Full software lifecycle activities conducted in accordance with ASPICE CL2 processes, covering SWE.1 through SWE.6, MAN.3, SUP.1,SUP.8, SUP.9 and SUP.10.
ASIL-D Functional Safety Qualification — The MCAL software package has been re-engineered to meet ISO 26262 ASIL-D functional safety requirements, including enhanced safety mechanisms and systematic capability.
Code Refactoring — A comprehensive code refactoring has been performed across all MCAL modules, with refinements to module architecture and detailed design. While the overall structure remains aligned with the AUTOSAR CP specification, customers should expect minor variations in module interfaces, internal design patterns, and configuration parameters compared to the 2.3.0 release.
Overall Quality Enhancement — Strengthened static analysis compliance (MISRA C:2012),HIS metrics improved test coverage to ASIL-D required levels, and systematic configuration and change management baselining.

1.3 Version Evolution

Item	Previous Release	Current Release (3.0.0)
Version	2.3.0	3.0.0
AUTOSAR CP	v4.4.0	v4.4.0
ASPICE Capability	N.A	Level 2
ASIL Qualification	QM	ASIL-D

Important — Not a drop-in replacement: This release is the result of an extensive code refactoring across the MCAL stack to achieve ASIL-D qualification from a QM baseline. Due to the scale of architectural changes — including redesigned safety mechanisms, restructured module interfaces, updated configuration parameters, and new ASIL-D-specific requirements on integration .
Customers must perform a thorough impact analysis and managed upgrade before migrating:

Review all Breaking Changes listed in Section 6.1 and assess impact on the existing integration.

Regenerate and re-validate MCAL configuration using YCT v3.2.0 or higher; configuration from 2.3.0 is not directly portable.

Re-integrate and re-test all affected software components at unit, integration, and qualification levels.

Conduct a project-specific safety impact analysis per ISO 26262 to confirm that the ASIL-D MCAL assumptions are valid and consistent with the system-level safety requirement.

2. Support Toolchains

YUNTU MCAL software package has been tested and validated with the following toolchains / IDEs:

2.1 Recommended Configuration Tool

YCT (Yuntu Config Tool) v3.2.0 or higher version

Tip: YCT can be downloaded from YTMicro Account or updated from an installed older version.

2.2 Recommended IDE / Compilers

IDE / Compiler	Minimum Version	Notes
IAR	v9.50
VSCode (Ninja + CMake + GCC/IAR)	VSCode v1.80	Cross-platform build system
GCC for ARM	v10.3
Green Hills	v2022.1.4

2.3 Recommended Debugger

SEGGER J-LINK v9.2 or higher hardware + v6.96 or higher software/driver
- Required: YTM32B1MC0x patch installed

3.Release List

The following list summarizes all functional changes, fixes, and new features introduced in this release compared to the previous release:

[Opt]-[CddUart]-[0] Optimize redundant YCT channel-count parameters and incorrect DMA channel validation rules for CddUart
[New]-[CddI2c]-[2] Add CddI2c Pin Low Timeout event detection support
[Fix]-[Icu]-[2] Fix Icu signal measurement anomaly on MC0
[Fix]-[Gpt]-[2] Fix Gpt not truly using the MCU clock source mapped by GptClockReferencePoint
[Fix]-[Lin]-[1] Fix Lin Slave not enabling Break detection after sending wake-up signal when using UART as LIN
[Fix]-[Fee]-[2] Add Fee cluster sector continuity validation in configuration
[Opt]-[Port]-[1] Add XTAL/EXTAL pins into UnTouchedPortPin defaults to avoid crystal misconfiguration
[Opt]-[Mcu]-[1] Add LinFlexD clock frequency limit checks in Mcu module
[Opt]-[Platform]-[0] Fix MC0 GHS compiler build error related to DSP instruction generation
[Fix]-[Platform]-[3] Fix GCC/GHS linker templates where section name equals memory region name causing wrong startup init size
[Fix]-[GUI]-[2] Remove default BOR disabled setting in YCT config (related to errata E110002)
[Fix]-[Can]-[1] Fix incorrect default value of Can SSP
[New]-[Mcu]-[2] Add Mcu module Errata Check items
[Opt]-[Can]-[1] Add Full type support for Can HoH
[Fix]-[Crypto]-[1] Fix Crypto Random async API that actually runs synchronously
[Fix]-[Fls]-[2] Fix Fls ECC fault handling
[Fix]-[Fls]-[1] Fix incorrect MemIf include between Fee and Fls
[Fix]-[Can]-[1] Fix Can module code generation bug
[Opt]-[CddDma]-[0] Enable CddDma scatter-gather and channel link to be used at the same time
[Fix]-[Crypto]-[2] Fix Crypto AES-CBC with async DMA not working

4.Known Issues/Limitation

N.A

Annex

Release list naming rule

Each release list item shall contain the following elements:

[Type] - [Sub-Type/Module] - [Effect_Level] [Brief/Overview Description][Reference/Details Link]

[Type]
- Fix: Bug fixes / issue resolution
- Opt: Code performance optimization
- New: New feature implementation
- Demo: Example / demonstration project
- Doc: Documentation updates
[Sub-Type/Module]
- MCAL: Mcu/Dio/Port/Can/Lin/Spi/Gpt/Pwm/Adc/Icu/Ocu/Fls/Fee/Platform/CddUart/CddSai/CddPpu/CddI2c/CddDma/CddTrg
- SafLib: CorTst/RamTst/FlsTst/IntTst/WdgTst/CrcTst/DmaTst/PpuTst/EfmTst/StkTst/EccTst/FmuTst
- GUI: the YCT XDM config GUI update for the MCAL/SafLib SW package, the YCT Vue config GUI update for the SDK/Middleware SW package(no code change/modification)
[Effect_Level]
- 0: No effect to the old version SW/project
- 1: Recommend but optional to update, for example the performance optimization
- 2: Must update for a specified SW module/components if the customer application used the related feature/functionality
- 3: Must update for a specified SW module/components if it is used
- 4: Must update if the SDK/MCAL/SafLib package is used
[Brief/Overview Description]
- [Type] = Fix: Fixed the xxx issue/bug of the yyy HW/SW functionality/feature caused by condition
- [Type] = Opt: Optimized the performance of the yyy HW/SW functionality/feature
- [Type] = New: Added the new feature/functionality support of xxx
- [Type] = Demo: added/updated the demo project: brief description
[Reference/Details Link]
- Errata: give out the detailed Errata number
- others: the link to the bug/issue analysis, it can be:
  - Link to a YUNTU form post [if it is derived from a FAE/customer feedback]
  - Link to a YUNTU form blog [if it is derived from a YUNTU form blog discussion]
  - Link to a Feishu/Meegle project issue detail page

Disclaimer

Copyright and Contact Information

YTMicro and its subsidiaries reserve the right to change, correct, enhance, modify and improve YTMicro products or this document at any time without notice. Before placing an order, purchasers should obtain and understand the latest relevant information about the products. YUNTU's products are sold according to YUNTU team and sales conditions at the time of order confirmation. Purchasers have the sole responsibility for selecting, choosing and using YUNTU products, and YUNTU has no responsibility for assisting purchasers in product design and application. YUNTU does not grant any express or implied license to any intellectual property herein. Resale of YUNTU products with information different from that described herein will make any warranty of YUNTU for such product void. YTMicro and YTMicro logo are trademarks of YTMicro. All other product or service names are the property of their respective owners. The information in this document replaces and supersedes any previously provided information in any prior version of this document. 2020 - 2026 YUNTU Microelectronics co.,ltd. All rights reserved.

Contact us: Website: www.ytmicro.com.

YunTu Forum