STM32cubeMx project to ac6 dsp 0xF THUMBmode

[RShiv.1]

Hi,

I am a new bee to STM ...tried generating the code to get the UART up for STM32L476 series discovery board...but could not compile the code in ac6 compiler as this gives following error

Error: selected processor does not support `isb 0xF' in Thumb mode

as I found we need to enter -mcpu-cortex-m3 ..but could not do so in ac6..kindly guide me and let me know how I can proceed further also any configuaration missing let me know.

thanks for all your support

Ravi chandran

[Khouloud OTHMAN]

Hello RShiv.1,

I can't reproduce the issue, Could you please share your .ioc file?

BR,

Khouloud.

[RShiv.1]

Hi,

thanks for your response attached is my test_UART ioc file.Kindly let me know where the problem is so that I can compile and flash and run in the virtual com port.

regards

Ravi chandran

[RShiv.1]

Hi ,

These are the errors seen in ac6 ..

Error: selected processor does not support `dsb 0xF' in Thumb mode

Drivers/STM32L4xx_HAL_Driver/Src/subdir.mk:72: recipe for target 'Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.o' failed

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:286: Error: selected processor does not support `isb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:330: Error: selected processor does not support `dsb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:351: Error: selected processor does not support `dsb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:935: Error: selected processor does not support `dsb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:946: Error: selected processor does not support `isb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:983: Error: selected processor does not support `dmb 0xF' in Thumb mode

also wanted to know why in ac6 directly when I open after generating the code from STMcube..not able to see STM MCU part number under MCU settings..any pointers to error there.let us know

--Ravi

[Khouloud OTHMAN]

Hello RShiv.1,

The problem is not reproduced from my side, the build has finished without any errors which is weird.

Please could you share your .log file for further check.

BR,

Khouloud.

[RShiv.1]

Hi,

when you say log file are you referring to the build conf??..as follows

14:02:58 **** Incremental Build of configuration Debug for project test_UART ****

make all 

Building file: ../Src/main.c

Invoking: MCU GCC Compiler

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32L476xx -I../Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32L4xx/Include -I../Drivers/CMSIS/Include -Os -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF"Src/main.d" -MT"Src/main.o" -o "Src/main.o" "../Src/main.c"

Finished building: ../Src/main.c

Building file: ../Src/stm32l4xx_hal_msp.c

Invoking: MCU GCC Compiler

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32L476xx -I../Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32L4xx/Include -I../Drivers/CMSIS/Include -Os -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF"Src/stm32l4xx_hal_msp.d" -MT"Src/stm32l4xx_hal_msp.o" -o "Src/stm32l4xx_hal_msp.o" "../Src/stm32l4xx_hal_msp.c"

Finished building: ../Src/stm32l4xx_hal_msp.c

Building file: ../Src/stm32l4xx_it.c

Invoking: MCU GCC Compiler

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32L476xx -I../Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32L4xx/Include -I../Drivers/CMSIS/Include -Os -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF"Src/stm32l4xx_it.d" -MT"Src/stm32l4xx_it.o" -o "Src/stm32l4xx_it.o" "../Src/stm32l4xx_it.c"

Finished building: ../Src/stm32l4xx_it.c

Building file: ../Src/syscalls.c

Invoking: MCU GCC Compiler

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32L476xx -I../Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32L4xx/Include -I../Drivers/CMSIS/Include -Os -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF"Src/syscalls.d" -MT"Src/syscalls.o" -o "Src/syscalls.o" "../Src/syscalls.c"

Finished building: ../Src/syscalls.c

Building file: ../Src/system_stm32l4xx.c

Invoking: MCU GCC Compiler

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32L476xx -I../Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32L4xx/Include -I../Drivers/CMSIS/Include -Os -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF"Src/system_stm32l4xx.d" -MT"Src/system_stm32l4xx.o" -o "Src/system_stm32l4xx.o" "../Src/system_stm32l4xx.c"

Finished building: ../Src/system_stm32l4xx.c

Building file: ../Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal.c

Invoking: MCU GCC Compiler

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32L476xx -I../Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32L4xx/Include -I../Drivers/CMSIS/Include -Os -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF"Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal.d" -MT"Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal.o" -o "Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal.o" "../Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal.c"

Finished building: ../Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal.c

Building file: ../Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.c

Invoking: MCU GCC Compiler

arm-none-eabi-gcc -mthumb -mfloat-abi=soft -DUSE_HAL_DRIVER -DSTM32L476xx -I../Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc -I../Drivers/STM32L4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32L4xx/Include -I../Drivers/CMSIS/Include -Os -g3 -Wall -fmessage-length=0 -ffunction-sections -c -fmessage-length=0 -MMD -MP -MF"Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.d" -MT"Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.o" -o "Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.o" "../Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.c"

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s: Assembler messages:

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:275: Error: selected processor does not support `dsb 0xF' in Thumb mode

Drivers/STM32L4xx_HAL_Driver/Src/subdir.mk:72: recipe for target 'Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.o' failed

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:286: Error: selected processor does not support `isb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:330: Error: selected processor does not support `dsb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:351: Error: selected processor does not support `dsb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:935: Error: selected processor does not support `dsb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:946: Error: selected processor does not support `isb 0xF' in Thumb mode

C:\Users\RAVI\AppData\Local\Temp\ccicODeQ.s:983: Error: selected processor does not support `dmb 0xF' in Thumb mode

make: *** [Drivers/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_cortex.o] Error 1

14:03:05 Build Finished (took 7s.190ms)

I know we need -mcpu -cortex -m4 ..you are able to get in your MCU gcc compiler option...also but why I am not able to get the same..anything related to Java..initially I had some java error ...kindly let me know why this is not refelcting in my build environment??

I think if I get this through I can also buld the same

--Thanks

Ravichandran

[RShiv.1]

Hi,

How did you include STM32L476VGTx_Flash file..how did you generate in STM cube and also include in the Inc folder??..this did not work for me..I think them -mcpu -cortex-m4 wil get included..let me know how you generated the flash file??.

regards

Ravi chandran

[Khouloud OTHMAN]

Hello RShiv.1,

You'll find the STM32CubeMX.log file under <user>/.stm32cubemx folder. Otherwise if the linker file STM32L476VGTx_FLASH.ld isn't generated once you generate code through CubeMX, then your issue may be related to the JAVA version. Please check the version installed on your machine. JAVA 13 is not supported by STM32CubeMX, the max supported version is actually JAVA 11.

More information on installation requirements and procedure is in the STM32CubeMX for STM32 configuration and initialization C code generation user manual (UM1718).

BR,

Khouloud.

[RShiv.1]

Hi,

attached is the log file.I even downloaded java 11 ..again tried..but still showing same error..let me know if there are any mistakes..still not able to generate

STM32L476VGTx_FLASH.ld file.Kindly guide me in this

--ravi

[Khouloud OTHMAN]

Hi RShiv.1,

Backing to .log file you have shared you are using java 14 which not supported by CubeMX.

Please uninstall this version and correctly install a Java version supported by STM32CubeMX ( max java 11). This will surely solve your issue.

The use of Java Run Time Environment 1.8_45 64-bit is strongly advised to prevent the unavailability of some features such as code generation for the STM32CubeIDE toolchain.

BR,

Khouloud

[RShiv.1]

Hi Khouloud,

I installed java 11 and was able to build the project.also I did install 1.8_45 64-bit Jre.Now that I have .elf how can I flash and run the same.I need to send some msg to UART and see the same in my console.How to falsh the same using ac6 build environment

An internal error occurred during: "Launching test_uart Run".

java.lang.NullPointerException

even as C application same error

rror starting process.

Cannot run program "C:\Users\RAVI\Documents\STM\test_uart\Debug\test_uart.elf": Launching failed

Cannot run program "C:\Users\RAVI\Documents\STM\test_uart\Debug\test_uart.elf": Launching failed

Cannot run program "C:\Users\RAVI\Documents\STM\test_uart\Debug\test_uart.elf": Launching failed

Kindly can you let me know what I need to configure.

regards

Ravi