I just wanted to add on top of Anton's reply that this is probably a bad naming that was chosen at the beginning for those macros and that stuck with: despite being defined as "ROM", the expectation is for it to mark a memory area which should be treated as read only for code, not an actual physical ROM.

Thanks, Antonio

From: Anton Komlev via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Tuesday, November 5, 2024 08:41
To: Michael Khoyilar <mkhoyilar@innophaseiot.com>; tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>
Subject: [TF-M] Re: Use of ROM address - flash_layout.h
 

Hi Michael,

 

If I understand your question correctly you are confused about ROM and Flash memory. Flash is treated as RO memory and the address represents where Flash is mapped in a device address space. Does this answer your question?

 

Hope that helps,

Anton

 

From: Michael Khoyilar via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Monday, November 4, 2024 11:52 PM
To: tf-m@lists.trustedfirmware.org
Subject: [TF-M] Use of ROM address - flash_layout.h

 

Hi all,

 

I am getting to know the TF-M, yet I do not understand the following comment and code where ROM (Read Only) is mentioned and its address used to store Code Data (flash_layout.h)!! Can someone help me understand this better? Thanks


BR

 

Michael

 

 

/* Use flash memory to store Code data */

#define S_ROM_ALIAS_BASE  (0x10000000)

#define NS_ROM_ALIAS_BASE (0x00000000)