2021-04-25 06:14 PM
Hello,
I am working on a project using STM32Cube_FW_WL_V1.0.0.
I cannot compile the 1_Image_SECoreBin project included in the BFU_1_Image sample project.
I am using STM32CubeIde on macOS Catalina.
I have also read these manuals.
"Getting started with the SBSFU of STM32CubeWL"
"Integration guide of SBSFU on STM32CubeWL (including KMS)"
Can you guys guide me?
Solved! Go to Solution.
2021-05-04 10:55 AM
Hi,
About bash option in Catalina this is quite strange as bash is supposed to be standard. I can't tell ...
About Win10 issue, this is a know issue related to latest STM32CubeIDE.
You can find the way to fix it in https://community.st.com/s/question/0D53W00000cRsLASA0/the-update-to-cubeide-160-cause-a-linker-error-compiling-the-userapp
Best regards
Jocelyn
2021-04-26 03:26 PM
Hi there,
I also tried on Windows 10.
I installed necessary tool chain for STM32CubeMXIde.
Then I prepared SBSFU_2_Images_DualCore sample project
I'm sure that, compiling the correct order according to Getting started with the SBSFU of STM32CubeWL (UM2767)
Compile order is;
The error is multiple definition error .
c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o: in function `SE_KMS_CloseSession':
(.SE_IF_Code+0xbd8): multiple definition of `SE_KMS_CloseSession'; ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o:(.SE_IF_Code+0xbd8): first defined here
c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o: in function `SE_KMS_DigestInit':
(.SE_IF_Code+0x121c): multiple definition of `SE_KMS_DigestInit'; ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o:(.SE_IF_Code+0x121c): first defined here
c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o: in function `SE_KMS_EncryptInit':
(.SE_IF_Code+0xedc): multiple definition of `SE_KMS_EncryptInit'; ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o:(.SE_IF_Code+0xedc): first defined here
c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o: in function `SE_KMS_DestroyObject':
(.SE_IF_Code+0xc94): multiple definition of `SE_KMS_DestroyObject'; ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o:(.SE_IF_Code+0xc94): first defined here
c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o: in function `SE_KMS_Encrypt':
(.SE_IF_Code+0xf3c): multiple definition of `SE_KMS_Encrypt'; ../../../2_Images_SBSFU/STM32CubeIDE/CM0PLUS/Debug\se_interface_app.o:(.SE_IF_Code+0xf3c): first defined here
I didn't do any code change, I just downloaded and opened in STM32CubeIde.
Is this related with STM32Cube_FW_WL_V1.0.0 ?
What's wrong ?
Thank you
2021-05-04 10:55 AM
Hi,
About bash option in Catalina this is quite strange as bash is supposed to be standard. I can't tell ...
About Win10 issue, this is a know issue related to latest STM32CubeIDE.
You can find the way to fix it in https://community.st.com/s/question/0D53W00000cRsLASA0/the-update-to-cubeide-160-cause-a-linker-error-compiling-the-userapp
Best regards
Jocelyn
2021-05-08 01:21 PM
Thank you Jocelyn,
The problem was caused by the macos. Catalina version uses default zsh instead of bash.
As a solution for those who encounter a similar problem: https://www.howtogeek.com/444596/how-to-change-the-default-shell-to-bash-in-macos-catalina/