AM623: ti-linux-firmware source code of V10.00.08

When we are looking at the version number of an SDK release, the least significant number basically indicates how many versions of the SDK we tested before we decided that the SDK was ready to release. So Linux SDK 10.0 looks like it went through 7 "release candidate" versions before it was ready to release, while MCU+ SDK 10.0 went through 14 versions. You just care about matching the major version numbers (i.e., 10.0).

The versioning for ti-linux-firmware v10.00.XX should be similar.

Regards,

Nick

But the MCU SDK version is 10.00.00.14, not 10.00.14. is it still test round? Customer need to confirm the modification won't introduce other bug, they can't take the risk.

What does the version number for ti-linux-firmware tell us?

The released version of Linux SDK 10.0 is 10.0.7.4. It looks like the ti-linux-firmware is tagged with which version of the Linux SDK it is intended to be used with (i.e., 10.0.7), instead of being tagged with the version of MCU+ SDK that was used to generate the files.

So let's check which MCU+ SDK version was used to generate those binaries that were tested for the PLL fix.

We can check the version that is reported in the DM R5F trace log. For future readers, refer to this FAQ for more information:
[FAQ] Linux: How to check what binary is running on the DM R5F 

What version is reported with the default 10.0.7 version of ti-linux-firmware? 

This is the output when using the firmware from tag 10.00.07 that is linked in the SDK docs here:
https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/10_00_07_04/exports/docs/devices/AM62X/linux/Release_Specific_Migration_Guide.html

root@am62xx-evm:~# cat /sys/kernel/debug/remoteproc/remoteproc1/trace0
[r5f0-0]     0.000887s : Sciclient direct init..... SUCCESS
[r5f0-0]     0.002874s : Sciserver Testapp Built On: Jul 25 2024 06:35:21
[r5f0-0]     0.007476s : Sciserver Version: v2024.07.0.0-REL.MCUSDK.K3.10.00.00.08+
[r5f0-0]     0.012963s : RM_PM_HAL Version: v10.00.08
[r5f0-0]     0.015711s : Starting Sciserver..... PASSED
[r5f0-0]     0.018642s : [IPC RPMSG ECHO] Version: REL.MCUSDK.K3.10.00.00.08+ (Jul 25 2024 06:36:51):

What version is reported with the released version of MCU+ SDK 10.0.0.14? 

When I rebuilt the firmware with the MCU+ SDK 10.0, this was my trace log:

cat /sys/kernel/debug/remoteproc/remoteproc1/trace0
[r5f0-0]     0.000891s : Sciclient direct init..... SUCCESS
[r5f0-0]     0.002892s : Sciserver Testapp Built On: Aug 17 2025 21:29:50
[r5f0-0]     0.007492s : Sciserver Version: v2024.08.0.0-REL.MCUSDK.K3.10.00.00.14+
[r5f0-0]     0.012978s : RM_PM_HAL Version: v10.00.08
[r5f0-0]     0.015728s : Starting Sciserver..... PASSED
[r5f0-0]     0.018658s : [IPC RPMSG ECHO] Version: REL.MCUSDK.K3.10.00.00.14+ (Aug 17 2025 21:42:46):

So the trace log reported Version does exactly match the MCU+ SDK version of 10.00.00.14.

Where can I get the exact version of the MCU+ SDK that was used to generate v10.0.7 of ti-linux-firmware?

That means that the exact version of code that was used to generate the firmware in 10.00.07 of the ti-linux-firmware came from here:
https://github.com/TexasInstruments/mcupsdk-core-k3/releases/tag/REL.MCUSDK.K3.10.00.00.08 

Regards,

Nick

TODO actions:

If we are going to build the DM R5F firmware with MCU+ SDK 10.0.0.8 instead of MCU+ SDK 10.0.0.14, we should check the commits between x.8 and x.14 to make sure that there is not any critical code that would be missing.

the commits for x.14 are here:
https://github.com/TexasInstruments/mcupsdk-core-k3/commits/REL.MCUSDK.K3.10.00.00.14/

and x.8 are here:
https://github.com/TexasInstruments/mcupsdk-core-k3/commits/REL.MCUSDK.K3.10.00.00.08/ 

I can take a look at the commits tomorrow.

Regards,

Nick

#1. The firmware V10.00.08 log version is 10.00.00.08. 

#2. The MCUSDK.K3.10.00.00.08 download from upper link can't built through,there is not trace.h file.

Public released mcu_sdk has this file: ./source/drivers/device_manager/rm_pm_hal/rm_pm_hal_src/include/lib/trace.h, But there is not the directory in REL.MCUSDK.K3.10.00.00.08/ 

tony@ubuntu22:~/ti/mcupsdk-core-k3-REL.MCUSDK.K3.10.00.00.08$ make -s -f makefile.am62x libs
Compiling: sciclient_direct.am62x.r5f.ti-arm-clang.release.lib: sciclient.c
sciclient.c:48:10: fatal error: 'lib/trace.h' file not found
#include <lib/trace.h>
         ^~~~~~~~~~~~~
1 error generated.
make[1]: *** [makefile.am62x.r5f.ti-arm-clang:143: sciclient.obj] Error 1
make: *** [makefile.am62x:550: sciclient_direct_r5f.ti-arm-clang] Error 2
tony@ubuntu22:~/ti/mcupsdk-core-k3-REL.MCUSDK.K3.10.00.00.08$ ^C
tony@ubuntu22:~/ti/mcupsdk-core-k3-REL.MCUSDK.K3.10.00.00.08$ find ./ -name sciclient.c
./source/drivers/sciclient/sciclient.c
./source/drivers/device_manager/sciclient_direct/sciclient.c
tony@ubuntu22:~/ti/mcupsdk-core-k3-REL.MCUSDK.K3.10.00.00.08$ find ./ -name trace.h
tony@ubuntu22:~/ti/mcupsdk-core-k3-REL.MCUSDK.K3.10.00.00.08$ cd ..

tony@ubuntu22:~/ti$ cd mcu_plus_sdk_am62x_10_00_00_14/
tony@ubuntu22:~/ti/mcu_plus_sdk_am62x_10_00_00_14$ find ./ -name trace.h
./source/drivers/device_manager/rm_pm_hal/rm_pm_hal_src/include/lib/trace.h

tony@ubuntu22:~/ti/mcu_plus_sdk_am62x_10_00_00_14$ cd ..
tony@ubuntu22:~/ti$ cd mcupsdk-core-k3-REL.MCUSDK.K3.10.00.00.08/source/drivers/device_manager/rm_pm_hal/

tony@ubuntu22:~/ti/mcupsdk-core-k3-REL.MCUSDK.K3.10.00.00.08/source/drivers/device_manager/rm_pm_hal$ ls rm_pm_*
ls: cannot access 'rm_pm_*': No such file or directory

seems the archive is wrong.

Hello Tony,

Are there any critical commits between MCU+ SDK 10.0.0.8 and 10.0.0.14? 

Before we do any development on 10.0.0.8, let's make sure we are not missing anything important that is on 10.0.0.14.

Most commits are either for documentation, for the test/ folder (which does not impact generated binaries), or only affect other processors. The only commits I see that might have an impact are related to how the MCU+ SDK OSPI driver interacts with the Voltage & Thermal Manager (VTM):
https://github.com/TexasInstruments/mcupsdk-core-k3/commit/e462be836680e8a2c3be943d86b1ffb1c7e52d0a
https://github.com/TexasInstruments/mcupsdk-core-k3/commit/96345fe5745ea29f2c191e5e7a9dafd1d7f1c713

I will check with the team to make sure that the DM R5F code does not need these commits.

I also broswered the diff log, it is long, most are .doc update. even about support new device. 

But how to download theses diff log in a package for customer?