AM263P4: When the SWAP feature is enabled ,How can I use Flash operation APIs (Flash_read, Flash_write, etc.) in region A to manipulate data physically located in region B (e.g., at 0x60500000)?

mingzhe dai

Part Number: AM263P4

Tool/software:

When the SWAP feature is enabled with A and B partitions configured, actual testing revealed that after setting the active region to A (FSS_selectRegionA), calling Flash operation APIs like Flash_read to read data at offsets 0x100000 and 0x500000 always retrieves data from the physical address 0x60100000. Similarly, when set to region B, reading the same offsets (0x100000 and 0x500000) consistently returns data from the physical address 0x60500000.Specifically as follows:

This leads to a question: How can I use Flash operation APIs (Flash_read, Flash_write, etc.) in region A to manipulate data physically located in region B (e.g., at 0x60500000)?

One approach I'm considering is that when operating in region A but needing to access region B Flash data, I would first switch to region B using FSS_selectRegionB, perform the necessary Flash operations, and then switch back to region A (FSS_selectRegionA) before exiting. Is this method feasible? Are there any other more reliable or simpler methods available？

Thank you very much for your answer！！

2 months ago

0 Aswin Sankar 2 months ago

TI__Intellectual 1885 points

Hi Mingzhe Dai,

Allow me to check this and get back to you.

Regards,

Aswin

0 Aswin Sankar 2 months ago in reply to Aswin Sankar

TI__Intellectual 1885 points

Hi Mingzhe Dai,

This would be the approach to physically write into the address at 0x6050000.

With FOTA enabled, it would not be possible to write into this address when FSSA is enabled. You would need to switch to FSSB to write into this region.

Regards,

Aswin

0 mingzhe dai 2 months ago in reply to Aswin Sankar

Prodigy 20 points

Hello, may I confirm if this is the only effective method? Similarly, if I need to access data in physical Partition A (e.g., at address 0x60100000) from Partition B, must I also:

Switch to Partition A,
Perform the required data operations in Partition A,
Then switch back to Partition B?"

0 Aswin Sankar 2 months ago in reply to mingzhe dai

TI__Intellectual 1885 points

Hello Mingzhe Dai,

Typically we use the bootseg IP for image swapping. And we do not normally write into image locations as it would corrupt the firmware image. May I know what is the requirement behind this.

Regards,

Aswin

0 mingzhe dai 2 months ago in reply to Aswin Sankar

Prodigy 20 points

Hello，After activating the SWAP mechanism, we intend to configure the memory range 0x400000 - 0x481000 as a shared region accessible to both Partition A and Partition B. This design accounts for Partition B's bootloader starting at 0x481000. Note that a Secondary Bootloader (SBL) in Partition B is not required.

0 Aswin Sankar 2 months ago in reply to mingzhe dai

TI__Intellectual 1885 points

Hi Mingzhe Dai,

Another approach which can be considered is to set the boot seg and boot mask register as 0 (essentially disabling the translation). This can be done by calling FSS_addressBitMask() with mask and segment as 0. After performing write operation, bootseg can be configured back.

Regards,
Aswin

Arm-based microcontrollers

Arm-based microcontrollers forum

AM263P4: When the SWAP feature is enabled ,How can I use Flash operation APIs (Flash_read, Flash_write, etc.) in region A to manipulate data physically located in region B (e.g., at 0x60500000)?