MCU-PLUS-SDK-AM243X: DebugP_ASSERT_ENABLED always 1?

Felix Heil

Hello,

we wanted to deactivate the DebugP_assert-implementation for our release-builds to shrink the code-size. Unfortunately the flag for that is only present in the DebugP.h under source/kernel/dpl.

Since our environment builds on top of the sdk, we have no chance to overwrite this flag since we precompile the sdk and use it as a library. We also had this topic with the FreeRTOS-Configuration where we included our own config-header then, but we wanted to keep the impact at the sdk as minimal as possible.

Is there another way to disable the asserts?

Regards

Felix

over 3 years ago

0 Ming Wei over 3 years ago

TI__Guru 57065 points

Hi Felix,

I think the best way to disable the DebugP_ASSERT_ENABLED in source/kenel/dpl/DebugP.h

#define DebugP_ASSERT_ENABLED 0

and re-build the libraries.

You can also try to define your own DebugP_assert() in your application code which does nothing. Hopefully, it will overwrite the one in the MCU+ SDK library. This way, you may avoid changes in the MCU+ SDK and rebuild the libraries.

Best regards,

Ming

0 Felix Heil over 3 years ago in reply to Ming Wei

Expert 1265 points

Hey Ming,

so I tried the following: I included a header into the DebugP.h which already defines the DebugP_ASSERT_ENABLED but in our case to 0, since we want to disable it. but then the build failes because this is already defined in an udma-file.

So this was not the solution and as said we do not want to deactivate it for all our projects using the SDK.

I then tried the other option with replacing the function(s). this did only work if I declared them weak inside the SDK, which meant I needed to touch it anyway. Anyways they would be redefined.

Btw. I don't understand this problem. I had the same issue with another funtion and we had a thread about it with George: https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1161383/mcu-plus-sdk-am243x-lts1-3-0-linker-option---symbol_map-does-not-work/4375763?tisearch=e2e-sitesearch&keymatch=%2525252525252520user%252525252525253A453845#4375763

it was not really solved and the last answer from another one may also be the point here but I checked and the compiler-manual says as default is always compiles with -ffunction-sections and -fdata-sections, which should prevent the redefinition-problem since the linker may then replace that function. Which it does only if the function is weak.

Well we found a solution then, but we needed to touch the SDK for that

Arm-based microcontrollers

Arm-based microcontrollers forum

MCU-PLUS-SDK-AM243X: DebugP_ASSERT_ENABLED always 1?