Other Parts Discussed in Thread: SYSCONFIG
Using SysConfig Editor I modified the board type from the CC1352P LaunchPad to a custom board. Now the ti_drivers_config.c produces __attribute__((weak)) implementations for rfDriverCallback() and rfDriverCallbackAntennaSwitching() functions. The weakly defined version of rfDriverCallbackAntennaSwitching() function has a call to you_must_implement_rfDriverCallbackAntennaSwitching_see_generated_ti_drivers_config_c_in_debug_folder_or_sysconfig_preview() in order to get the developer's attention that a strongly defined version of rfDriverCallbackAntennaSwitching() is required.
As suggested, I created strongly defined implementations for rfDriverCallback() and rfDriverCallbackAntennaSwitching(). These functions compile without issue, yet the linker complains there is an unresolved symbol for you_must_implement_rfDriverCallbackAntennaSwitching_see_generated_ti_drivers_config_c_in_debug_folder_or_sysconfig_preview(). I can only guess my strongly defined function calls are not "overriding" the weakly defined functions in ti_drivers_config.c.
What am I doing incorrectly or what settings do I need to adjust to satisfy the linker?
Environment details:
- CC Studio version = 10.1.0.00010
- compiler version = TI v.20.2.1.LTS
- SimpleLink CC13x1 26x2 SDk version = 4.10.00.78