YUNTU SafLib (Safety Library) provides peripheral self-tests and software safety mechanisms for AUTOSAR application integration. This document describes SafLib 3.0.0 for YTM32B1HA0.

Required dependency: MCAL 3.0.0. SafLib 3.0.0 must be integrated with MCAL 3.0.0.

1.1 Release Type

Major Version — SafLib 3.0.0.

Status: Internal Release Notes | Release Date: TBC | Issue Snapshot: 2026-10-28

1.2 Release Highlights

• DmaTst Configuration — Improved startup-test defaults, runtime-test configuration and DMA channel validation.
• ClkTst Frequency Tolerance — Added a configurable tolerance for enabled clock sources; zero remains the default.
• FmuTst Clock Restoration — Corrected clock configuration restoration after FMU configuration tests.
• MCAL Integration — Safety MCAL 3.0.0 adaptation covers Resource configuration, module MemMap, regression tests and demos.
• EccTst Interrupt Handling — Fixed application hangs when ECC flags are already pending before the test; the ISR is installed before interrupts are enabled.
• SecureBoot Reset Compatibility — Fixed SLOWBUS clock-test failures after a board-button reset by using the active clock and effective divider settings.

1.3 Version Evolution

2. Support Toolchains

YUNTU SafLib software package uses 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

2.3 Recommended Debugger

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

3. Release List

The following list summarizes changes for YTM32B1HA0:

• [Opt]-[SafLib]-[4] Adapt SafLib resources, SchM MemMap, regression tests and demos to Safety MCAL 3.0.0
• [Opt]-[DmaTst]-[1] Improve DmaTst YCT defaults, runtime configuration and DMA channel validation
• [Opt]-[FmuTst]-[1] Correct clock configuration restoration after FMU configuration tests
• [Opt]-[ClkTst]-[1] Add configurable frequency tolerance for each enabled clock source, with a default value of zero
• [Fix]-[EccTst]-[3] Fix EccTst application hangs caused by pending ECC flags by installing the ISR before enabling interrupts and clearing interrupts after the test
• [Fix]-[ClkTst]-[2] Fix HA0 SLOWBUS clock-test failures after a SecureBoot hardware reset by deriving injection thresholds from the active clock source and DIVSTS dividers

Type labels for EccTst-ISSUE-189 are classified from the issue content because the source Type field is empty.

4. Known Issues / Limitation

4.1 Integration Notes

• EccTst (EL3): Update EccTst wherever the module is used. Install the ISR before enabling ECC interrupts, then execute the test and clear interrupts. Revalidate startup and boot-to-application paths with ECC flags already pending.
• SecureBoot / ClkTst (EL2): Revalidate SLOWBUS high- and low-threshold tests after both board-button reset and debugger reset; derive thresholds from the active clock source and effective DIVSTS dividers.
• DmaTst: Regenerate and review configuration for startup-test defaults, the minimum hardware-channel count, the single runtime container and channel-link constraints.
• ClkTst: The tolerance value defaults to zero. Select any nonzero value according to the clock specification and project safety analysis.
• MCAL Integration: Confirm Resource and module MemMap changes, SUT/SIT/SQT regression and demo updates when integrating Safety MCAL 3.0.0.
• Release Baseline: Confirm the 3.0.0 version record, package identifier, delivery contents and regression reports. Issue closure does not replace release-package qualification evidence.

Annex

Release list naming rule

Each release list item contains the following elements:

[Type]-[Module]-[Effect_Level] [Brief Description / Details Link]

• Type: Fix — bug fixes; Opt — optimization; New — new functionality; Demo — demonstration projects; Doc — documentation updates.
• Module: The SafLib module affected by the change. Module names in this document do not constitute a complete device support matrix.
• Effect_Level:
  • 0: No effect on the previous software version / project.
  • 1: Update recommended but optional.
  • 2: Update the affected module if the application uses the related functionality.
  • 3: Update the affected module if it is used.
  • 4: Update if the software package is used.
  • TBC: The source issue does not specify an effect level.
• Details Link: The linked YT_SafLib issue provides the analysis, corrective action and verification records.

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.