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.

TMS320F280049C: Confusion about .cmd file layout in flashapi_ex3_live_firmware_update example

Part Number: TMS320F280049C
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hi,

I'm working with the F280049C LaunchPad and currently reviewing the `flashapi_ex3_live_firmware_update` example provided in C2000Ware. I come across some question in .cmd file.

Here is the relevant section of the memory definition:

BEGIN : origin = 0x08EFF0, length = 0x000002

FLASH_BANK0_SEC14 : origin = 0x08E000, length = 0x000FF0

FLASH_BANK0_SEC15 : origin = 0x08EFF2, length = 0x00100E

1. The `BEGIN` section is placed between SEC14 and SEC15, spanning two bytes (`0x08EFF0` to `0x08EFF1`). What is the purpose of placing `BEGIN` here? Is it related to bootloading, or does it help avoid prefetch ECC issues?

2. Based on my understanding, each Flash sector is typically 4KB in size, but in this case, the length of `FLASH_BANK0_SEC15` is set to `0x00100E`, which appears to exceed the sector boundary. Why is this done, and is it safe?

Best regards,
Riddy