AM625-Q1: Unit testing approach

Part Number: AM625-Q1

Hello TI Support,

We are developing software for the Cortex-M4F core on the AM62x platform using the MCU+ SDK. We would like guidance on the recommended approach for unit testing applications targeting this core.

In particular:

1. Does TI recommend running unit tests directly on the M4F target, on a host PC using mocked hardware dependencies, or using a combination of both approaches?

2. Are any unit-testing frameworks officially supported or commonly used with the MCU+ SDK?

3. Are there examples, templates, or documentation showing how to integrate unit tests into an MCU+ SDK project and automate them in a CI environment?

4. What is the recommended way to mock or isolate MCU+ SDK drivers, hardware registers, interrupts, timers, IPC, and other target-specific dependencies?

We would also like to understand how TI tests the MCU+ SDK itself:

• Are the SDK drivers and middleware covered by automated unit tests?

• Are those tests executed on target hardware, simulators, host machines, or a combination of these?

• Which test frameworks and code-coverage tools does TI use?

• Are any of TI’s internal unit tests, test infrastructure, or test reports available to customers?

• How do the example applications and SDK validation tests differ from the unit tests used during SDK development?

Our environment:

• SoC: AM6254ATGFHIAMCRQ1

• Core: Cortex-M4F

• MCU+ SDK version: 11.01

• Compiler/toolchain: TI Arm Clang Compiler 4.0.1.LTS

• RTOS: no RTOS

Any reference architecture, example project, or recommendation for structuring testable M4F application code around the MCU+ SDK would be very helpful.

Thank you.