Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32

Forum List Topic List

[ prev topic ]  

Unable to select the target board "Current board target is invalid !"

Posted by rohit.deshpande on 2020-02-04 20:50

Hi,
I am trying to compile a project which I auto generated using STM32CubeMX

STM32CubeMX = 5.5.0
embedded software version = 1.24.1
Systems Workbench = AC6 C/C++ Embedded Development Tools for MCU v2.9.1.2

I am not able to compile the project, it shows the following error:

make all
Building file: ../Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.c
Invoking: MCU GCC Compiler

    1. PATH##\Debug

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32F446xx -I”##PATH##/Inc” -I”##PATH##/Drivers/STM32F4xx_HAL_Driver/Inc” -I”##PATH##/Drivers/STM32F4xx_HAL_Driver/Inc/Legacy” -I”##PATH##/Drivers/CMSIS/Device/ST/STM32F4xx/Include” -I”##PATH##/Drivers/CMSIS/Include” -O0 -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF”Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.d” -MT”Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.o” -o “Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.o” “../Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.c”

C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s: Assembler messages:
C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s:241: Error: selected processor does not support `dsb 0xF’ in Thumb mode
C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s:252: Error: selected processor does not support `isb 0xF’ in Thumb mode
C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s:907: Error: selected processor does not support `dsb 0xF’ in Thumb mode
C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s:929: Error: selected processor does not support `dsb 0xF’ in Thumb mode
C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s:1305: Error: selected processor does not support `dmb 0xF’ in Thumb mode
C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s:1381: Error: selected processor does not support `dsb 0xF’ in Thumb mode
C:\Users\DESHPA~1\AppData\Local\Temp\cc3ksJgX.s:1392: Error: selected processor does not support `isb 0xF’ in Thumb mode
Drivers/STM32F4xx_HAL_Driver/Src/subdir.mk:69: recipe for target ‘Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.o’ failed
make: *** Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal_cortex.o Error 1

I am also not able to select a board or a chip from the project properties, it shows me “Current board target is invalid !”. Nothing happens when I click on “Define board target” button. I tried to reinstall both CubeMX and Systems workbench but nothing helps.

Thanks for help in advance !

Reads: 5288
Link
Posted by rohit.deshpande on 2020-02-10 17:43

Figured out that there is an error in the new STM32CubeMX (V5.5) tool that it does not generate the linker script file(maybe because of anti-virus tool deleting that file), so that is why it is not able to find the required path. To solve this problem I actually installed the SMT32CubeMX as a plugin to the Systems Workbench IDE and then was able to generate the required files and compile the project correctly.

-Rohit

Link

Posted by N3utron3ngin3 on 2020-04-07 13:35

Hi,
Same problem on STM32CubeMX version 5.6, the auto-generated code is missing the linker script and the target is not defined.
Resolved by importing the linker script from an example project located in the STM32Cube repository folder and by defining the mcu name inside the auto-generated “project name”.xml file ( the element name that define the mcu is “mcuId”).

Link