AM2634-Q1: SDK compilation error with disabled DebugP_xxx

Eugene K

Part Number: AM2634-Q1
Other Parts Discussed in Thread: SYSCONFIG

Hello,

Using sysconfig_1.27.0.

Following suggestion in here https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/latest/exports/docs/api_guide_am263x/OPTIMIZING_APPLICATIONS_WITH_MCU_SDK.html#CHAPTER_OPTIMIZATION_SECTION_5 and setting DebugP_ASSERT_ENABLED=0 or DebugP_LOG_ENABLED=0 generates compile errors with default SDK otions accros multiple files.

For instance,

Arm Compiler - building file: "syscfg/ti_drivers_open_close.c"
"C:/ti/ti_cgt_arm_llvm_4.0.4.LTS/bin/tiarmclang.exe" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -Os -I"C:/ti/ti_cgt_arm_llvm_4.0.4.LTS/include/c" -I"C:/ti/mcu_plus_sdk_am263x_26_00_00_06/source" -DSOC_AM263X -DOS_NORTOS -DDebugP_ASSERT_ENABLED=0 -g -Wall -Werror -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_drivers_open_close.d_raw" -MT"syscfg/ti_drivers_open_close.o" -I"C:/Users/workspace_ccstheia/mcspi_loopback_interrupt_lld/Release/syscfg" -o"syscfg/ti_drivers_open_close.o" "syscfg/ti_drivers_open_close.c"
[2]syscfg/ti_drivers_open_close.c:70:13: error: variable 'status' set but not used [-Werror,-Wunused-but-set-variable]
70 | int32_t status = MCSPI_STATUS_SUCCESS;
| ^
[3]syscfg/ti_drivers_open_close.c:86:13: error: variable 'status' set but not used [-Werror,-Wunused-but-set-variable]
86 | int32_t status = MCSPI_STATUS_SUCCESS;
| ^
2 errors generated.

Regards,

Eugene

2 months ago

0 Shaunak Deshpande 2 months ago

TI__Mastermind 27222 points

Hi Eugene,

This is a known reported bug and an equivalent JIRA has been filed for a fix. Please see complete details here: AM263P4-Q1: Libraries Don't Build When DebugP_ASSERT_ENABLED is 0

Regards,
Shaunak

0 Eugene K 2 months ago in reply to Shaunak Deshpande

Intellectual 450 points

What is the target SDK release for this fix?

0 Shaunak Deshpande 2 months ago in reply to Eugene K

TI__Mastermind 27222 points

This would most probably be a part of v26.02 SDK release. The internal code-freeze for v26.01 SDK has already passed, and it is in testing phase, so this fix would be in the version next to that.

The v26.01 is being targeted for Sept 1st week. Im not sure if the v26.02 would be available before Nov end/early December. We also have a GitHub where fixes are pushed every 2/3 weeks. This is in sync with our internal development SDK. So this might be available sooner on GitHub, but i cannot provide a date/ETA for the fix.

Regards,
Shaunak

0 Eugene K 2 months ago in reply to Shaunak Deshpande

Intellectual 450 points

BTW, the file with error is part of the Sysconfig generated files.

+1 Shaunak Deshpande 2 months ago in reply to Eugene K

TI__Mastermind 27222 points

Hi Eugene,

Yes, i see the same errors being thrown for other libraries when re-built on setting the flags in DebugP.h file. I think the fix (mentioned in the above linked E2E) should work for this too.

Regards,
Shaunak

0 Eugene K 2 months ago in reply to Shaunak Deshpande

Intellectual 450 points

Hi Shaunak,

Thank you. Yes, compile option will definitely make error go away. I just want to make sure that SDK is fixed for next release and code we get is clean.

Regards,

Eugene

0 Eugene K 2 months ago in reply to Shaunak Deshpande

Intellectual 450 points

Shaunak Deshpande

Additional comment. I've noticed that somewhere in SDK code you have

#if DebugP_LOG_ENABLED

construct. AFIAK, that won't work with DebugP_LOG_ENABLED=0. It would need explicit compare.

Regards,

Eugene

0 Shaunak Deshpande 2 months ago in reply to Eugene K

TI__Mastermind 27222 points

Noted, I will add this as well in the scope of JIRA ticket.

Regards,
Shaunak

Arm-based microcontrollers

Arm-based microcontrollers forum

AM2634-Q1: SDK compilation error with disabled DebugP_xxx