• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 127 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM263P4-Q1: Is DebugP_ASSERT_ENABLED In the Release Libraries

Kier
Mastermind 9655 points

Part Number: AM263P4-Q1

Hello,

Regarding the advice here:

AM263Px MCU+ SDK: Optimizing applications with MCU SDK

It mentions disabling assertions and rebuilding the libraries. However, I would have assumed that TI has already done that when building the release version of the libraries. i.e.

C:\ti\mcu_plus_sdk_am263px_10_02_00_15\source\kernel\nortos\lib\nortos.am263px.r5f.ti-arm-clang.release.lib

C:\ti\mcu_plus_sdk_am263px_10_02_00_15\source\drivers\lib\drivers.am263px.r5f.ti-arm-clang.release.lib

Can you confim whether my assumption is correct or not please?

Obviously I don't want to rebuild the release libraries if you've already done it.

  • +1
    TI__Mastermind 22702 points

    No, DebugP_assert is NOT automatically disabled in release builds. By default, assertions are enabled in both debug AND release profiles.

    You will have to disable it, and re-build the lib via command line. Usually, the release build provided in the SDK does not equate to  the most optimised build, it just has some additional optimisation flags, further optimisation is possible and has to done based on the requirement.

    To disable the debug assertions:
    - Update DebugP.h to #define DebugP_ASSERT_ENABLED 0
    - OR define DebugP_ASSERT_ENABLED as compiler build macro and assign value 0
    - Rebuild all the libraries (software-dl.ti.com/.../MAKEFILE_BUILD_PAGE.html)
    - Rebuild the application"

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Mastermind 9655 points

    OK, thanks for the confirmation.