• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 195 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28069M: FLASH memory organisation

Pavlin Stoyanoff
Expert 1725 points

Part Number: TMS320F28069M

Greetings! I`ve notice that in the F28069M.cmd file the FLASH memory is devided in several sections like FLASHA_B, FLASHC, FLASHD and so on. Is there a problem to combine them into a single one? I want to put a large array and this devision prevents it. I also have instaSPIN Lib. The array contains symbols for 128x160 TFT display. So can I  add everything to FLASHA_B part? 

FLASHA_B    : origin = 0x3F0000, length = 0x007F80     /* on-chip FLASH */

to become

FLASHA_B      : origin = 0x3D8000, length = 0x01BF80     /* on-chip FLASH */

Thanks!

  • 0
    TI__Guru* 84270 points

    Pavlin,

    There is no restriction in combining multiple sectors into larger sections for code.  The only restriction for the flash is that the erase function has to be done on a whole sector at a time.

    For debug purposes this doesn't really effect you since Code Composer will handle erasing the correct regions(I think it just erases all sectors by default before programming).  But for a release, if you were planning on making FW updates you may want to consider placement of your code or data appropriately and the time it would take to erase multiple sectors if needed.

    Best,

    Matthew