Tool/software:
Using:
The project include search path is …
...
After a Clean and Build, oddly enough …
C:/ti/mcu_plus_sdk_am263px_10_01_00_31/source/security/security_common/drivers/secure_ipc_notify
… appears on the include path instead of …
C:/ti/mcu_plus_sdk_am263px_10_01_00_31/source/security
Oddly enough …
C:/ti/mcu_plus_sdk_am263px_10_01_00_31/source/security/security_common/drivers/security_ipc_notify/
Is mentioned as a non-existent directory (which it is), but …
Where is this directory referenced in the project?
Both appear in several subdir_rules.mk file …
"C:/ti/ti-cgt-armllvm_4.0.0.LTS/bin/tiarmclang.exe" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -O1 -I"C:/ti/ti-cgt-armllvm_4.0.0.LTS/include/c" -I"C:/ti/mcu_plus_sdk_am263px_10_01_00_31/source" -I"C:/ti/mcu_plus_sdk_am263px_10_01_00_31/source/security/security_common/drivers/security_ipc_notify/" -I"C:/ti/mcu_plus_sdk_am263px_10_01_00_31/source/security/security_common/drivers/secure_ipc_notify" -I"../" -I"../Includes" -I"../50019F-COD008_Crossover_Code/src" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/CAN BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/DTC BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/EEPROM BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/HW BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/J1939 BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/UDS BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/VDB BIOS" -I"../50019F-COD008_Crossover_Code/src/Husco_BIOS/XCP BIOS" -DSOC_AM263PX -D_DEBUG_=1 -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -ferror-limit=1 -v -MMD -MP -MF"50019F-COD008_Crossover_Code/src/Husco_BIOS/CAN BIOS/CAN_Init.d_raw" -MT"50019F-COD008_Crossover_Code/src/Husco_BIOS/CAN\ BIOS/CAN_Init.o" -I"C:/Software/50019F-HCS/50019F-COD007_HCS_Boot_Software/HCS_Boot_Software/Debug/syscfg" $(GEN_OPTS__FLAG) -o"$@" "$<"
