cancel
Showing results for 
Search instead for 
Did you mean: 

Bug : The STM32H563XX_FLASH.ld file is not generated in STM32CubeMX v6.15.0

Fumihiko
Associate II

Hi, 

I am using the following environment:

  • OS: Ubuntu 20.04 LTS

  • STM32CubeMX: 6.15.0

  • Visual Studio Code: 1.103.2

    • STM32Cube for Visual Studio Code : 3.5.1
  • Board: NUCLEO-H563ZI

 

I found a bug where the STM32H563XX_FLASH.ld file is not generated after generating code.

This bug can be reproduced by following the steps below:

  1. Create any cubemx project for STM32H563xx.
  2. Set "The Toolchain / IDE" to CMake.
  3. Click "Generate Code" .
  4. After generating code, the files "STM32H563xx_FLASH.ld" and "STM32H563xx_RAM.ld" are generated.

However, the CMake build environment requires only STM32H563XX_FLASH.ld. As a result, the CMake build fails and reports the error :

"my_project/STM32H563XX_FLASH.ld: No such file or directory"

 

On the other hand, I found that the "STM32H563XX_FLASH.ld" can be generated if "Apply Application Regions Settings to Linker Files: ON" is enabled in Memory Management Tool. 

3 REPLIES 3
Ghofrane GSOURI
ST Employee

Hello @Fumihiko 

I am checking this issue.I will get back to you asap.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hello @Fumihiko 

According to our documentation (UM1718, section 3.1.1), the officially supported Linux distributions are:

  • Ubuntu LTS 22.04
  • Ubuntu LTS 24.04
  • Fedora 41

GhofraneGSOURI_1-1758191622594.png

For best results, use a supported operating system such as Fedora 41 or Ubuntu LTS 22.04/24.04 in a virtual machine or container.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hi Ghofrane,

 

>For best results, use a supported operating system such as Fedora 41 or Ubuntu LTS 22.04/24.04 in a virtual machine or container.

Does this mean that the bug does not occur on Ubuntu 22.04 and later?

 

Best Regards,

Fumihiko