cancel
Showing results for 
Search instead for 
Did you mean: 

Flash Memory Configuration for UART Bootloader and Application – STM32U5 Series

ram_jan
Associate II

Hi Team,

Could you please guide me on how to correctly configure the internal Flash memory for the STM32U5 series? Specifically, I would like to understand how to:

  • Modify the Flash start and end addresses

  • Set appropriate lengths

  • Partition the Flash to allocate separate regions for the bootloader and the application image

  • Are there any configurations in STM32 Cube IDE to make those changes (Referred Version: 1.18.0)
  • UART Read failing While sending image over a xmodem, does it fail because of any configurations issue?

Thanks and Regards

ram_jan

 

5 REPLIES 5
Andrew Neil
Super User

@ram_jan wrote:
  • UART Read failing While sending image over a xmodem, does it fail because of any configurations issue?

You'd need to give more details of the particular failure to be able to answer that, but UART operation shouldn't be affected by Flash configuration.

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Hi Andrew Neil,

I am currently working on the SBL UART operation for an STM32U5x-based SoC and referring to the implementation from the link mentioned earlier. My goal is to partition the internal flash into two sections:

  • Bootloader: 32KB

  • Application Image: Remaining flash space

By default, the internal flash base address is 0x08000000, but I need to modify this to suit the partitioning requirement. With the default flash configuration, I am attempting to receive the .bin application image over XMODEM. However, the execution halts and hits the following error:

"No source available for "<signal handler called>() at 0xfffffffe"

Could you please guide me on how to correctly configure the internal flash memory for the STM32U5 series? Specifically, I would like to know whether any settings need to be changed in STM32CubeMX or elsewhere to support this flash partitioning and prevent the above error.

Note : Please Guide me on modifying the starting address of internal flash for Application image, Please share your thoughts on how do it using any settings in CubeMX etc ?

Thanks,

 

 

 

I don't know about the flash configuration.

 


@ram_jan wrote:

I am attempting to receive the .bin application image over XMODEM. However, the execution halts and hits the following error:

"No source available for "<signal handler called>() at 0xfffffffe"


The IDE should show you the call stack for how it got there.

Sounds like a Hard Fault:

https://community.st.com/t5/community-guidelines/how-to-write-your-question-to-maximize-your-chances-to-find-a/tac-p/708193/highlight/true#M51

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Hi,

Could you please forward this email to the appropriate person or team who can assist me with modifying the internal flash address for the STM32U5 series?

I’m currently working on splitting the flash for a bootloader (32KB) and an application image (remaining space), and need guidance on how to correctly configure the memory mapping—especially in STM32CubeMX and the linker script.

Thank you for your support.

This is a public community forum - all posts are visible to all users.

If you want direct support from ST, contact your FAE or raise a support case:

AndrewNeil_0-1747992552283.png

https://ols.st.com/s/

https://www.st.com/content/st_com/en/support/support-home.html

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.