• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 32 subscribers
  • Views 392 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.

MSPM0G1519: Can't seem to use 128k SRAM ?

Philip Neaves
Intellectual 340 points

Part Number: MSPM0G1519
Other Parts Discussed in Thread: MSPM0G3519, SYSCONFIG

Tool/software:

Seem to run out of SRAM memory when using more than 64k.

Do I have to do something special to use both banks ?

Are they contiguous ?

Using GCC.

Regards

Phil

  • 0
    Guru 102725 points

    The top of mspm0g3519.cmd says:

    /*
 * Note: SRAM on this device is continuous memory but partitioned in the 
 * linker into two separate sections. This is to account for the upper 64kB
 * of SRAM being wiped out upon the device entering any low-power mode 
 * stronger than SLEEP. Thus, it is up to the end-user to enable SRAM_BANK1 for
 * applications where the memory is considered lost outside of RUN and SLEEP Modes.
 */

    If you don't plan to use the lower-power modes, I suppose you can combine the two banks (double the size of SRAM_BANK0, delete SRAM_BANK1). Otherwise you'll probably have to put any "expendable" variables in a separate section and put them ">SRAM_BANK1".

  • 0 in reply to Bruce McKenney
    Intellectual 340 points

    Thanks..I guess RTFM,,,but where is mspm0g3519.cmd ???

    I do not see it in explorer in CCS Theia.

    --

    Phil

  • 0 in reply to Philip Neaves
    Intellectual 340 points

    ...I do not use low power modes...."If you don't plan to use the lower-power modes, I suppose you can combine the two banks (double the size of SRAM_BANK0, delete SRAM_BANK1)."

    How do I do this ?

  • 0 in reply to Philip Neaves
    Guru 102725 points

    I found mspm0g3519.cmd in "C:\ti\ccs2001\ccs\ccs_base\arm\include". Historically CCS would put a copy of this in your project, but if you're using sysconfig, it generates instead a "device_linker.lds" (in "Generated Source").

    To edit this:

    1) Copy device_linker.lds to your source directory (up one level).

    2) Turn off "Project Configuration Files->Linker File Generation". [The next build will delete the .lds file, thus the need for step (1).]

    3) I expect the actual change would look like:

    [before:]

        SRAM_BANK0      (RWX) : ORIGIN = 0x20200000, LENGTH = 0x00010000
    SRAM_BANK1      (RWX) : ORIGIN = 0x20210000, LENGTH = 0x00010000

    [after:]

        SRAM_BANK0      (RWX) : ORIGIN = 0x20200000, LENGTH = 0x00020000

    I just tried this and it built. I don't have a G3519 to run it on.

  • 0 in reply to Philip Neaves
    TI__Mastermind 31205 points

    Hi Philip,

    You can also click on exclude in build, shown as below:

    Then copy the generated lds files and paste it into main project path.

    B.R.

    Sal