Other Parts Discussed in Thread: UNIFLASH
Tool/software:
Hi,
My customer wants to boot dual cores with OSPI boot. They tried below steps, but so far no success.
Could you review these steps and provide feedback?
Step#1 : Build SDK empty example "empty_am263px-cc_system_nortos".
Step#2 : In Uniflash, configure "empty_system.appimage" or "empty_system.mcelf" as Application image.
Step#3 : The customer tried to use "sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang" as SBL, but linker error was generated.
So they used "sbl_ospi_am263px-cc_r5fss0-0_nortos_ti-arm-clang" instead.
Linker error generated when "sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang" is used as SBL.
Building target: "sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.out" Invoking: Arm Linker "C:/ti/ti-cgt-armllvm_4.0.0.LTS/bin/tiarmclang.exe" -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -Os -DSOC_AM263PX -g -Wall -Wno-gnu-variable-sized-type-not-at-end -Wno-unused-function -Wl,-m"sbl_ospi_multicore_elf.Release.map" -Wl,-i"C:/ti/mcu_plus_sdk_am263px_10_01_00_34/source/kernel/nortos/lib" -Wl,-i"C:/ti/mcu_plus_sdk_am263px_10_01_00_34/source/drivers/lib" -Wl,-i"C:/ti/mcu_plus_sdk_am263px_10_01_00_34/source/board/lib" -Wl,-i"C:/ti/mcu_plus_sdk_am263px_10_01_00_34/source/security/lib" -Wl,-i"C:/ti/ti-cgt-armllvm_4.0.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="sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang_linkInfo.xml" -Wl,--ram_model -o "sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.out" "./board.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.am263px.r5f.ti-arm-clang.release.lib -Wl,-ldrivers.am263px.r5f.ti-arm-clang.release.lib -Wl,-lboard.am263px.r5f.ti-arm-clang.release.lib -Wl,-lsecurity.am263px.r5f.ti-arm-clang.release.lib -Wl,-llibc.a -Wl,-llibsysbm.a makefile:151: recipe for target 'sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.out' failed undefined first referenced symbol in file --------- ---------------- gI2cConfig C:/ti/mcu_plus_sdk_am263px_10_01_00_34/source/drivers/lib/drivers.am263px.r5f.ti-arm-clang.release.lib<i2c_v1.obj> gI2cConfigNum C:/ti/mcu_plus_sdk_am263px_10_01_00_34/source/drivers/lib/drivers.am263px.r5f.ti-arm-clang.release.lib<i2c_v1.obj> error #10234-D: unresolved symbols remain error #10010: errors encountered during linking; "sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.out" not built tiarmclang: error: tiarmlnk command failed with exit code 1 (use -v to see invocation) gmake[1]: *** [sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.out] Error 1 gmake: *** [all] Error 2 makefile:147: recipe for target 'all' failed **** Build Finished ****
Step#4 : Flash OSPI memory
Step#5 : Change boot mode as OSPI boot and power cycle the board. Below is terminal output.
Thanks and regards,
Koichiro Tashiro
