Hello Ki, Thanks for your support and reproducing my setup! Yes, the dependencies are all installed, I confirmed that. I am also able to import and build the example from the mcu+sdk: Import step: ortfeld@Buildserver:~/ti/ccs12.0.0/ccs/eclipse$ ./eclipse -noSplash -data ~/ccs-workspace/ -application com.ti.ccstudio.apps.projectImport -ccs.location ~/ti/mcu_plus_sdk_am64x_09_01_00_41/examples/empty/am64x-evm/r5fss0-0_nortos/ti-arm-clang/example.projectspec SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. -------------------------------------------------------------------------------- Importing project from '/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/examples/empty/am64x-evm/r5fss0-0_nortos/ti-arm-clang/example.projectspec'... NOTE: Compiler version 'TICLANG_3.2.0' is not currently installed! - defaulting to 'TICLANG_3.2.0.LTS'. Done! Build Step: ortfeld@Buildserver:~/ti/ccs12.0.0/ccs/eclipse$ ./eclipse -noSplash -data ~/ccs-workspace/ -application com.ti.ccstudio.apps.projectBuild -ccs.projects empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% CCS headless build starting... [Wed Jul 03 12:19:47 CEST 2024] %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Pre processing... ================================================================================ Building... **** Build of configuration Debug for project empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang **** /home/ortfeld/ti/ccs12.0.0/ccs/utils/bin/gmake -k -j 8 all -O Building file: "../example.syscfg" Invoking: SysConfig "/home/ortfeld/ti/sysconfig_1.18.0/sysconfig_cli.sh" -s "/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/.metadata/product.json" --script "/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/example.syscfg" --context "r5fss0-0" -o "syscfg" --part Default --package ALV --compiler ticlang Running script... Validating... info: CONFIG_MPU_REGION3(/kernel/dpl/mpu_armv7) attributes: Region shared among cores is marked as cached. info: /kernel/dpl/debug_log uartLog.baudRate: Actual Baudrate Possible: 115385 (0 % error) Generating Code (example.syscfg)... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_dpl_config.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_dpl_config.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_drivers_config.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_drivers_config.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_drivers_open_close.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_drivers_open_close.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_pinmux_config.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_power_clock_config.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_board_config.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_board_config.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_board_open_close.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_board_open_close.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_enet_config.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_enet_config.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_enet_open_close.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_enet_open_close.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_enet_soc.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_enet_lwipif.c... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_enet_lwipif.h... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/ti_pru_io_config.inc... Writing /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg/linker.cmd... Finished building: "../example.syscfg" Building file: "syscfg/ti_drivers_config.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_drivers_config.d_raw" -MT"syscfg/ti_drivers_config.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_drivers_config.o" "syscfg/ti_drivers_config.c" tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] Finished building: "syscfg/ti_drivers_config.c" Building file: "syscfg/ti_power_clock_config.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_power_clock_config.d_raw" -MT"syscfg/ti_power_clock_config.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_power_clock_config.o" "syscfg/ti_power_clock_config.c" tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] Finished building: "syscfg/ti_power_clock_config.c" Building file: "../empty.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"empty.d_raw" -MT"empty.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"empty.o" "../empty.c" Finished building: "../empty.c" Building file: "syscfg/ti_pinmux_config.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_pinmux_config.d_raw" -MT"syscfg/ti_pinmux_config.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_pinmux_config.o" "syscfg/ti_pinmux_config.c" tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] Finished building: "syscfg/ti_pinmux_config.c" Building file: "syscfg/ti_board_open_close.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_board_open_close.d_raw" -MT"syscfg/ti_board_open_close.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_board_open_close.o" "syscfg/ti_board_open_close.c" Finished building: "syscfg/ti_board_open_close.c" Building file: "syscfg/ti_dpl_config.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_dpl_config.d_raw" -MT"syscfg/ti_dpl_config.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_dpl_config.o" "syscfg/ti_dpl_config.c" Finished building: "syscfg/ti_dpl_config.c" Building file: "syscfg/ti_board_config.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_board_config.d_raw" -MT"syscfg/ti_board_config.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_board_config.o" "syscfg/ti_board_config.c" Finished building: "syscfg/ti_board_config.c" Building file: "syscfg/ti_drivers_open_close.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -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"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_drivers_open_close.o" "syscfg/ti_drivers_open_close.c" tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] Finished building: "syscfg/ti_drivers_open_close.c" Building file: "syscfg/ti_enet_config.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_enet_config.d_raw" -MT"syscfg/ti_enet_config.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_enet_config.o" "syscfg/ti_enet_config.c" Finished building: "syscfg/ti_enet_config.c" Building file: "syscfg/ti_enet_open_close.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_enet_open_close.d_raw" -MT"syscfg/ti_enet_open_close.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_enet_open_close.o" "syscfg/ti_enet_open_close.c" Finished building: "syscfg/ti_enet_open_close.c" Building file: "syscfg/ti_enet_soc.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_enet_soc.d_raw" -MT"syscfg/ti_enet_soc.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_enet_soc.o" "syscfg/ti_enet_soc.c" Finished building: "syscfg/ti_enet_soc.c" Building file: "syscfg/ti_enet_lwipif.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"syscfg/ti_enet_lwipif.d_raw" -MT"syscfg/ti_enet_lwipif.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"syscfg/ti_enet_lwipif.o" "syscfg/ti_enet_lwipif.c" Finished building: "syscfg/ti_enet_lwipif.c" Building file: "../main.c" Invoking: Arm Compiler "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -c -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -I"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/include/c" -I"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source" -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -MMD -MP -MF"main.d_raw" -MT"main.o" -I"/home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/syscfg" -o"main.o" "../main.c" tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] tiarmclang: warning: argument unused during compilation: '-gstrict-dwarf' [-Wunused-command-line-argument] Finished building: "../main.c" Building target: "empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.out" Invoking: Arm Linker "/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/bin/tiarmclang" -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -DSOC_AM64X -D_DEBUG_=1 -gstrict-dwarf -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -Wl,-m"empty.Debug.map" -Wl,-i"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source/kernel/nortos/lib" -Wl,-i"/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/source/drivers/lib" -Wl,-i"/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS/lib" -Wl,--reread_libs -Wl,--diag_suppress=10063 -Wl,--diag_wrap=off -Wl,--display_error_number -Wl,--warn_sections -Wl,--xml_link_info="empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang_linkInfo.xml" -Wl,--ram_model -o "empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.out" "./empty.o" "./syscfg/ti_dpl_config.o" "./syscfg/ti_drivers_config.o" "./syscfg/ti_drivers_open_close.o" "./syscfg/ti_pinmux_config.o" "./syscfg/ti_power_clock_config.o" "./syscfg/ti_board_config.o" "./syscfg/ti_board_open_close.o" "./syscfg/ti_enet_config.o" "./syscfg/ti_enet_open_close.o" "./syscfg/ti_enet_soc.o" "./syscfg/ti_enet_lwipif.o" "./main.o" -Wl,-l"syscfg/linker.cmd" -Wl,-lnortos.am64x.r5f.ti-arm-clang.debug.lib -Wl,-ldrivers.am64x.r5f.ti-arm-clang.debug.lib -Wl,-llibc.a -Wl,-llibsysbm.a tiarmclang: warning: Strict DWARF is not supported. [-Winvalid-command-line-argument] Finished building target: "empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.out" /home/ortfeld/ti/ccs12.0.0/ccs/utils/bin/gmake -C /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang -f makefile_ccs_bootimage_gen OUTNAME=empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang PROFILE=Debug MCU_PLUS_SDK_PATH=/home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41 CG_TOOL_ROOT=/home/ortfeld/ti/ti-cgt-armllvm_3.2.0.LTS CCS_INSTALL_DIR=/home/ortfeld/ti/ccs12.0.0/ccs CCS_IDE_MODE=desktop DEVICE=am64x Boot image: am64x:r5fss0-0:nortos:ti-arm-clang /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage ... /home/ortfeld/ti/ccs12.0.0/ccs/tools/node/node /home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/tools/boot/out2rprc/elf2rprc.js Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.out >> Debug/temp_stdout_Debug.txt cp empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc cp /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc_tmp rm -f /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc /home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/tools/boot/xipGen/xipGen.out -i /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc_tmp -o /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc -x /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc_xip --flash-start-addr 0x60000000 -v > Debug/temp_stdout_Debug.txt /home/ortfeld/ti/ccs12.0.0/ccs/tools/node/node /home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/tools/boot/multicoreImageGen/multicoreImageGen.js --devID 55 --out /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc@4 >> Debug/temp_stdout_Debug.txt /home/ortfeld/ti/ccs12.0.0/ccs/tools/node/node /home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/tools/boot/multicoreImageGen/multicoreImageGen.js --devID 55 --out /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage_xip /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc_xip@4 >> Debug/temp_stdout_Debug.txt python3 /home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/tools/boot/signing/appimage_x509_cert_gen.py --bin /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage --authtype 1 --key /home/ortfeld/ti/mcu_plus_sdk_am64x_09_01_00_41/tools/boot/signing/rom_degenerateKey.pem --output /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs Generating certificate for /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage ... rm -f /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage rm -f /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rprc_tmp Boot image: am64x:r5fss0-0:nortos:ti-arm-clang /home/ortfeld/ccs-workspace/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang/Debug/empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs Done !!! . **** Build Finished **** ================================================================================ CCS headless build complete! 0 out of 1 projects have errors. Both steps seem to be same with your output. I also see the Note that it defaults to the TICLANG_3.2.0.LTS Compiler during import. I wonder if it matters, whether my project to be imported is initially created with a Linux or Windows based system? I gave it a fresh setup, trying a project created on a Linux machine and one created on a windows machine. For the project initially created on windows it is still the same behaviour as described in my first post (This was also a windows based project). The project created on the linux machine can not even be imported: ortfeld@Buildserver:~/ti/ccs12.0.0/ccs/eclipse$ ./eclipse -noSplash -data ~/ccs-workspace2/ -application com.ti.ccstudio.apps.projectImport -ccs.location ~/ccs-projects/linux-based/ccs12-test/r5f_freertos/prj/ SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. -------------------------------------------------------------------------------- Importing project from '/home/ortfeld/ccs-projects/linux-based/ccs12-test/r5f_freertos/prj/'... !ERROR: Import failed for project 'prj' because its meta-data cannot be interpreted. Please contact support. Done! Do you have any comments regarding the successful example or the linux vs. windows based project thoughts? Thank you! Daniel

Where do you see the min freq spec? Why do you want to set 20kHz? BTW, can you please UCC28950 instead?

Hello, you didn’t understand me, when a 4 kW PFC operates at low loads, the SCM mode ends - the controller switches the choke to intermittent mode, which leads to overheating of the magnetic circuit, in order to return the controller with the choke to its original state, SCM mode, you either need to lower the voltage by input of the inductor, or increase the frequency at which the controller and inductor operate, As the frequency increases, the inductor increases its resistance, the current through it decreases and the controller is forced to switch to SCM mode from the intermittent mode, the inductor stops heating, and thus A PFC can work optimally as a voltage stabilizer at high and low loads, that is, it would be nice if the 28070 could also automatically change the frequency depending on the load, Am I right??? Thank you for your attention, 99 / 5 000 Результаты перевода Перевод Hello, you didn’t understand me, the 4 kW KKM works at low loads when the SCM mode ends

@Ning Tan thank you for your return. UCC2895 is also ok. For this device, in "6.3 Recommended Operating Conditions" of the datasheet, it's mentioned that the minimum switching frequency is 50kHz and the maximum is 1000kHz. 20kHz is ok for many parameters considerations in our design. For 100V input, we have 3kV output. ratio of 30. For the UCC28950 you recommend, is it a problem to use it at 20kHz ? Thanks !

Hi SP, PMP design is a test report, so we don't have a details design guide such as TIDA design, basically, we will follow UCC28740 calculation sheet to generate the design parameters, thanks

The old installs are disabled. You can reinstall on your computer now. David

Hello Vitalij, You are right, I don't understand what you are trying to tell me. Please define what you mean by SCM mode and intermittent mode. In a web search, could not find a reference to these modes in the context of PFC design. But maybe you are referring to continuous conduction mode (CCM) and discontinuous conduction mode (DCM) of current in the inductor? In a fixed-frequency boost converter, at some current level (light load), inductor current will change from CCM to DCM. This is not a heating problem. The inductor does not heat up at light loads, it cools down. DCM operation has no effect on the output voltage regulation. A different type of boost-PFC that has automatic variable frequency operates the inductor current in transition mode (TM) sometimes also known as critical conduction mode (CrCM or CrM) or boundary conduction mode (BCM or BM). Here the inductor current operates the transition point or boundary between CCM and DCM. The switching frequency changes with peak current: lower frequency at higher peaks and higher frequency at lower peaks. Maybe that is what you are thinking of. TM-PFC is usually not considered practicable to use at power levels higher than 1kW, and is usually used between 100W to ~800W. Theoretically, TM-PFC can be used at any power level, even megawatts, but the "limitation" to <1kW is due to practical considerations of the peak currents through the power-processing components (inductor, switch, diode, etc.) To conclude, the UCC28070 fixed-frequency CCM-PFC is well suited for use in a 4kW application. Output voltage regulation is maintained from 0% to 100% load, and there is no heating of magnetics at light load. The worst heat (power loss) is at full-load, at the lowest input voltage. Regards, Ulrich

Part Number: CODECOMPOSER Other Parts Discussed in Thread: TM4C129ENCPDT Tool/software: Hi, I am using CCS version 12.1.0. We use TM4C129ENCPDT microcontroller for most of our project. We noticed the Memory Allocation window will not change even if we introduce additional code or buffers etc. It will report same usage for Flash and SRAM. Here is the snapshot of the Memory Allocation Window. Thanks

Hi David, The customer wants to simulate the bode plot of this 4th-order high pass filter. But, when they run the program it gets the error. I'll upload their project here. e2e.ti.com/.../FILTRO-_2800_1_2900_.DSN Thank you for your usual support. Regards, Jonathan

Hi Sara, What part are you trying to simulate? PSpice for TI has a lot of built in test circuits. Those should all work properly. If you search for your part, right-mouse-button click on the found image should show you the test circuit. There may be both a transient and average model. Bode plots are generated from the average model. David

Hi Joseph, Digital isolators and pseudo-differential drivers (like RS485, RS422/RS232 and CAN) are modeled using IBIS to evaulated signal integrity. Functinoally, digital isolators work like level shifters with a fixed delay. Since IBIS is a drive strength/edge (or receiver loading impedence) event only, duty cycle and prop delay are not modeled. As a result, they can't be imported into TINA or PSpice. I can re-direct this to the product line for further support. David

Can you share your project? I mainly need the three .*project file in the project folder but having the contents of the whole project folder would be helpful. If you can zip the project folder and provide that, that would be helpful. You can send via private E2E message if your wish.

[quote userid="2210" url="~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1372551/codecomposer-ccs-headless-build-fails-because-of-missing-compiler-installation/5285078#5285078"]Can you share your project? [/quote] Actually I probably don't need it. I can reproduce the issue with an project I imported to and built with CCS IDE (the same empty project) windows. I think I have an inking of the issue. For the project you are trying to import... I assume you created the project and build it using the CCS IDE. Did you grab the SDK and clang compiler from CCS Resource Explorer instead of manually downloading/installing the standalone installers for them?

Update - I have been testing a bit and so far I see: Importing a project created/built from CCS 12.0.0 Windows to my Linux environment. I get metadata issues Importing a project created/built from CCS 12.0.0 Linux (this is a different Linux machine) to my Linux environment - works. I think this is reverse what is happening. I will also try with CCS 12.7.1 in case that version has some fix.

Hello, Can you provide a test case for use to try locally? Please provide the project and then also provide the additional code with the changes that are added. The goal is to first build the project as-is and see the Memory Allocation view output and the apply the additional code changes and build again. Thanks ki

Hi Niklas, Let me check with Cadence. PSpice for TI is a sand-boxed version of the full commercial version SPB. David

Actually, the current sensing is not good, very coarse. Just used for OCP, not for monitoring. Regards,

[quote userid="2210" url="~/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1372551/codecomposer-ccs-headless-build-fails-because-of-missing-compiler-installation/5285177#5285177"]I will also try with CCS 12.7.1 in case that version has some fix. [/quote] CCS 12.7.1 seems to work much better. The same projects created with CCS 12.0.0 IDE (from both Windows and Linux) import fine into my CCS 12.7.1 Linux environment. Can you try updating the CCS version?

Hi, I created a test project. I see it will update the memory map but some time. Please find attached test project. All the libraries are inclusive to the project. . e2e.ti.com/.../apsu_5F00_sps.zip

Can you have them archive the project. That'll have their sim profile as well. I'm getting circuit errors. Hopefully the project will resolve that. I also ran a bode plot for the OPAx828 test circuit included on PSpice for TI. No problems there. David