| Feature | Module |
| TI ARM Clang compiler upgrade to 4.0.4 | BUILD |
| Support for FreeRTOS LTS 202406.01 LTS | DPL |
| FreeRTOS port shall include a default exception handler to aid in exception debug on C7x | DPL |
| SCICLIENT LLD is compliant to safety qualification approach (ASIL D) | DM |
| SafeRTOS DPL + Portable layer (R5, C7x) is compliant to safety qualification approach (ASIL B) | DPL |
| FVID2 LLD is compliant to safety qualification approach (ASIL B) | FVID2 |
| IPC LLD is compliant to safety qualification approach (ASIL B) | IPC |
| I2C LLD is compliant to safety qualification approach (ASIL B) | I2C |
| UDMA LLD is compliant to safety qualification approach (ASIL D) | UDMA |
| Tools | Supported CPUs | Version |
| Code Composer Studio | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | 20.3.1 |
| SysConfig | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | 1.26.2, build 4477 |
| TI ARM CLANG | MCU-R5F, WKUP-R5F, MAIN-R5F | 4.0.4.LTS |
| TI CGT | C75SS0, C75SS1 | 5.0.0.LTS |
| FreeRTOS Kernel | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | 11.1.0 |
| Module | Supported CPUs | SysConfig Support | OS support(NoRTOS only on R5F) |
| Address Translate | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | YES | SafeRTOS,FreeRTOS, NORTOS |
| Cache | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | YES | SafeRTOS,FreeRTOS, NORTOS |
| Clock | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | YES | SafeRTOS,FreeRTOS, NORTOS |
| CycleCounter | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | NA | SafeRTOS,FreeRTOS, NORTOS |
| Debug | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | YES | SafeRTOS,FreeRTOS, NORTOS |
| Heap | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | NA | FreeRTOS,NORTOS |
| Hwi | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | YES | SafeRTOS,FreeRTOS, NORTOS |
| MPU | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | YES | SafeRTOS,FreeRTOS, NORTOS |
| Semaphore | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | NA | SafeRTOS,FreeRTOS, NORTOS |
| Task | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | NA | SafeRTOS,FreeRTOS |
| Timer | MCU-R5F, WKUP-R5F, MAIN-R5F, C75SS0, C75SS1 | YES | SafeRTOS,FreeRTOS, NORTOS |
This section lists changes which could affect user applications developed using older SDK versions. Read this carefully to see if you need to do any changes in your existing application when migrating to this SDK version relative to previous SDK version. Also refer to older SDK version release notes to see changes in earlier SDKs.
| Module | Change Summary | Details |
| I2C | I2C_Transaction structure updated | Structure updated to align with modern Controller/Target terminology and support memory-mapped transactions:
- Renamed Fields:
slaveAddress → targetAddress, masterMode → controllerMode
- Type Changes:
writeBuf is no longer const
- New Features:
memTxnEnable and memTransaction pointer for memory read/write operations
- Status Reporting: Added
status field to track transaction results
Applications using I2C driver require updates to use new field names.
This change is done as per the naming recommendation.
|
| Build | In Boot Image Generation, authentication type used in appimage sigining is updated. | authtype used in appimage sigining is changed from 2 to 0. load address should be provided explicitly where the app image should be copied during authentication.
By default SBL expects the load address to be at address 0xC2000000 Example: --authtype 0 --loadaddr 0xC2000000 in appimage_x509_cert_gen.py
Auto-generated makefiles are updated; verify custom boot scripts if applicable. The authtype parameter in boot image signing specifies whether the binary should be copied to the specified load address during authentication.
The valid values for this field and their interpretation are described below.
- authtype 0: Image is copied to load address
- authtype 1: In-place authentication binary is not moved
- authtype 2: In place operation variant. Binary is moved to the beginning of the buffer
|
| Build | wake up r5 binary path in all mcu sdk examples is updated. | In all example makefiles, SCISERVER_IMAGE_PATH is updated to directly point to the sciclient example directory built for the Wake-up R5F core.
The prebuilt binary image is also present at ${MCUSDK_INSTALL_DIR}/tools/sysfw same as the previous release. |
| Build | command line parameters for generating linux app image is updated. | Linux application image generation for FASTBOOT_LINUX now uses FALCON_MODE parameter. When FALCON_MODE=1 is set, the kernel (Image) and device tree (DTB) are loaded directly instead of using SPL, bypassing the secondary bootloader.
Example: make FALCON_MODE=1 in tools/boot/linuxAppimageGen/ generates a boot image that loads the Linux kernel directly.
This parameter affects the boot image composition and loading behavior during Linux image initialization. |
| Build | Firmware binary naming: tifs → sysfw | All references updated from tifs-*.bin to sysfw-*.bin across boot scripts, makefiles, and image generation tools.
This affects build configurations and firmware deployment paths. |
| Build | SysConfig outputs regenerated | All SysConfig-generated .meta templates have been regenerated:
GPIO, I2C (including LLD templates), UART, DSS (v0/v1), UDMA (v0/v1), MMCSD, EEPROM Regenerate project configurations from SysConfig to apply updates. |
| Build | Removed module_cfg.h header | The module_cfg.h file has been removed from ${SDK_INSTALL_DIR}/source/drivers.
Update build configurations if this header was previously included in custom applications. |
1.8.20