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.

LAUNCHXL-F28379D: LAUNCHXL-F28379D

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

1. Can you please suggest the changes or command file for the storing the .text in FLASH and other data in RAM, Because what happens when i select eh RAM configuration all the executable code and data going to to RAM and when i am selecting the FLASH cmd file all the executable code and data is going in Flash.

But our need is that the data should go to RAM and executable code should go into Flash , kindly help with this. 

2. Other thing is that how can i make the burning program in FLASH fast by removing the erasing the memory again and again and only erase the flash size which has been filled. please provide me the option in the CCS, how to do this.

Kindly help

  • Hi,

    1. The default Flash linker cmd file in C2000ware places all teh code in Flash and data in RAM. Can you give me more details on where you found all code and data going to Flash?

    2. Please see if this works

     Use the option Necessary settings only under erase settings

    Regards,

    Veena

  • Hi Veena,

                By the way how can i see this option wh on chip flash?

    other query -  I am using 2837xD_RAM_lnk_cpu1 file for the programm, In this file section init , .text is going to RAM which is maing the  RAM full or overlapping error with very small code.

    SECTIONS
    {
    codestart : > BEGIN, PAGE = 0
    .text : >> RAMD0 | RAMLS0 | RAMLS1 | RAMLS2 | RAMLS3 | RAMLS4, PAGE = 0
    .cinit : > RAMM0, PAGE = 0
    .switch : > RAMM0, PAGE = 0
    .reset : > RESET, PAGE = 0, TYPE = DSECT /* not used, */
    .stack : > RAMM1, PAGE = 1

    Can we increase the RAM section like and make it error free.

    RAMD1 : origin = 0x00B800, length = 0x000800

    RAMLS5 : origin = 0x00A800, length = 0x000800

    RAMGS0 : origin = 0x00C000, length = 0x001000
    RAMGS1 : origin = 0x00D000, length = 0x001000
    RAMGS2 : origin = 0x00E000, length = 0x001000
    RAMGS3 : origin = 0x00F000, length = 0x001000
    RAMGS4 : origin = 0x010000, length = 0x001000

    3. If we are using the RAM command file , does it mean all code is going into RAM only?? if yes then help for  our requirement is that , the code should be placed in flash and data should be placed in RAM.  Please clearify my doubts.

  • Yes, RAM cmd puts all the sections to RAM only. But the Flash linker cmd keep only code and constants in Flash, data goes to RAM only

    On-chip Flash option is available under Tools

  • But the problem is that the while using the flash, it is taking too much time to flash the code into mcu. how can we make it fast?

  • Please try the option I suggested. It will only erase the required sections.

    Regards,

    Veena

  • I dont see this option in tools, can you please tell where or how can see this option.

  • It us under Tools

    You need to be in the Debug view.