This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F280049: Flash sectors configuration

Part Number: TMS320F280049
Other Parts Discussed in Thread: C2000WARE

Hello Champs,

In C2000ware F28004x example codes "28004x_generic_flash_lnk.cmd" file, there is "FLASH_BANK0_SEC0" definitions:

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

/* Flash sectors */

/* BANK 0 */

FLASH_BANK0_SEC0 : origin = 0x080002, length = 0x000FFE /* on-chip Flash */

FLASH_BANK0_SEC1 : origin = 0x081000, length = 0x001000 /* on-chip Flash */

FLASH_BANK0_SEC2 : origin = 0x082000, length = 0x001000 /* on-chip Flash */

FLASH_BANK0_SEC3 : origin = 0x083000, length = 0x001000 /* on-chip Flash */

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

.text : >>FLASH_BANK0_SEC1 | FLASH_BANK0_SEC2 | FLASH_BANK0_SEC3, PAGE = 0, ALIGN(4)

What about the SEC0 usage? Why the ".text" section is starting from SEC1 but not SEC0? 

Would you please kindly help? Thanks!

Best Regards,

Linda

  • Linda,

    Some users may reserve the first sector for something like custom loaders which they don't want to erase along with their application. In such cases, users map their .text section to other sectors.

    Apart from that, we used to have passwords in the first and/or last sectors of a flash bank (ex: F28M35x, F2802x etc.) - and some users like to avoid erase/program of those sectors since a power loss during erase/program of those sectors can result in permanent lockup of the device. However, this concern is not applicable for F28004x devices since passwords are in OTP and not in Flash bank.

    You can have your .text section mapped to sector 0 - no issues.

    Thanks and regards,
    Vamsi