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.

CCS/TMS320F28335: Flashing code in one-shot

Part Number: TMS320F28335

Tool/software: Code Composer Studio

Hello,

I would like to inquire about one especial problem: I am developing a new application at the moment, which is launched and debugged from RAM, linker script is attached below. Unfortunately, I have encountered a lack of this memory. In my code there are some well working parts, so, in my opinion, there is a possibility to move them into FLASH and after that download them in MCU at once. How could I achieve it? Shall I insert some pragma sections like "#pragma CODE_SECTION()  in my code or is there any other way to place well-tried code into FLASH? I remind: it must be in one-shot and following debugging etc must go only from RAM again :-)

Thank you very much for your advices.

Miroslav

/*
// TI File $Revision: /main/11 $
// Checkin $Date: April 15, 2009   09:57:28 $
//###########################################################################
//
// FILE:    28335_RAM_lnk.cmd
//
// TITLE:   Linker Command File For 28335 examples that run out of RAM
//
//          This ONLY includes all SARAM blocks on the 28335 device.
//          This does not include flash or OTP.
//
//          Keep in mind that L0 and L1 are protected by the code
//          security module.
//
//          What this means is in most cases you will want to move to
//          another memory map file which has more memory defined.
//
//###########################################################################
// $TI Release:   $
// $Release Date:   $
//###########################################################################
*/

/* ======================================================
// For Code Composer Studio V2.2 and later
// ---------------------------------------
// In addition to this memory linker command file,
// add the header linker command file directly to the project.
// The header linker command file is required to link the
// peripheral structures to the proper locations within
// the memory map.
//
// The header linker files are found in <base>\DSP2833x_Headers\cmd
//
// For BIOS applications add:      DSP2833x_Headers_BIOS.cmd
// For nonBIOS applications add:   DSP2833x_Headers_nonBIOS.cmd
========================================================= */

/* ======================================================
// For Code Composer Studio prior to V2.2
// --------------------------------------
// 1) Use one of the following -l statements to include the
// header linker command file in the project. The header linker
// file is required to link the peripheral structures to the proper
// locations within the memory map                                    */

/* Uncomment this line to include file only for non-BIOS applications */
/* -l DSP2833x_Headers_nonBIOS.cmd */

/* Uncomment this line to include file only for BIOS applications */
/* -l DSP2833x_Headers_BIOS.cmd */

/* 2) In your project add the path to <base>\DSP2833x_headers\cmd to the
   library search path under project->build options, linker tab,
   library search path (-i).
/*========================================================= */

/* Define the memory block start/length for the F28335
   PAGE 0 will be used to organize program sections
   PAGE 1 will be used to organize data sections

   Notes:
         Memory blocks on F28335 are uniform (ie same
         physical memory) in both PAGE 0 and PAGE 1.
         That is the same memory region should not be
         defined for both PAGE 0 and PAGE 1.
         Doing so will result in corruption of program
         and/or data.

         L0/L1/L2 and L3 memory blocks are mirrored - that is
         they can be accessed in high memory or low memory.
         For simplicity only one instance is used in this
         linker file.

         Contiguous SARAM memory blocks can be combined
         if required to create a larger memory block.
*/


MEMORY
{
PAGE 0 :
   /* BEGIN is used for the "boot to SARAM" bootloader mode      */

   BEGIN      : origin = 0x000000, length = 0x000002     /* Boot to M0 will go here                      */
   RAMM0      : origin = 0x000050, length = 0x0003B0
   RAML0      : origin = 0x008000, length = 0x001000
   RAML1      : origin = 0x009000, length = 0x001000
   RAML2      : origin = 0x00A000, length = 0x001000
   RAML3      : origin = 0x00B000, length = 0x001000
   RAML4      : origin = 0x00C000, length = 0x001000
   //RAML5      : origin = 0x00D000, length = 0x001000
   //RAML6      : origin = 0x00E000, length = 0x001000
   //ZONE7A     : origin = 0x200000, length = 0x00FC00    /* XINTF zone 7 - program space */ /* disabled, all ext. RAM will be in DATA section */
   CSM_RSVD   : origin = 0x33FF80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */
   CSM_PWL    : origin = 0x33FFF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA            */
   ADC_CAL    : origin = 0x380080, length = 0x000009
   RESET      : origin = 0x3FFFC0, length = 0x000002
   IQTABLES   : origin = 0x3FE000, length = 0x000b50
   IQTABLES2  : origin = 0x3FEB50, length = 0x00008c
   FPUTABLES  : origin = 0x3FEBDC, length = 0x0006A0
   BOOTROM    : origin = 0x3FF27C, length = 0x000D44


PAGE 1 :
   /* BOOT_RSVD is used by the boot ROM for stack.               */
   /* This section is only reserved to keep the BOOT ROM from    */
   /* corrupting this area during the debug process              */

   BOOT_RSVD  : origin = 0x000002, length = 0x00004E     /* Part of M0, BOOT rom will use this for stack */
   RAMM1      : origin = 0x000400, length = 0x000400     /* on-chip RAM block M1 */
   RAML5      : origin = 0x00D000, length = 0x001000
   RAML6      : origin = 0x00E000, length = 0x001000
   RAML7      : origin = 0x00F000, length = 0x000FF0     /* on-chip RAM block L1 */
   FLASH_FLAG : origin = 0x00FFF0, length = 0x00000F
   FLASH_CRC  : origin = 0x300000, length = 0x000002     /* Application CRC */
   ZONE7	    : origin = 0x200000, length = 0x100000	/* Ext. RAM of 1Mx16b */
   ZONE6      : origin = 0x100000, length = 0x080000  /* Ext. NV RAM 512kx16b */
}


SECTIONS
{
   /* Setup for "boot to SARAM" mode:
      The codestart section (found in DSP28_CodeStartBranch.asm)
      re-directs execution to the start of user code.  */
   codestart        : > BEGIN,     PAGE = 0
   ramfuncs         : > RAML0,     PAGE = 0
   // two > means that linker can split .text section to multiple RAM zones
   .text            : >> RAML0 | RAML1 | RAML2 | RAML3 | RAML4,     PAGE = 0
   .cinit           : > RAML0,     PAGE = 0
   .pinit           : > RAML0,     PAGE = 0
   .switch          : > RAML0,     PAGE = 0

   .stack           : > RAML4,     PAGE = 0
   .ebss            : >> RAML5 | RAML7      PAGE = 1
   .econst          : >> RAML6 | RAML7,     PAGE = 1
   .esysmem         : > RAMM1,     PAGE = 1
   .sysmem			: > RAML0,	   PAGE = 0
   .cio				: > RAML0,	   PAGE = 0

   diagbuff        : > RAMM1,     PAGE = 1

   flash_crc       : > FLASH_CRC   PAGE = 1
   flash_flag      : > FLASH_FLAG  PAGE = 1

   IQmath           : > RAML0,     PAGE = 0
   IQmathTables     : > IQTABLES,  PAGE = 0, TYPE = NOLOAD

   /* Uncomment the section below if calling the IQNexp() or IQexp()
      functions from the IQMath.lib library in order to utilize the
      relevant IQ Math table in Boot ROM (This saves space and Boot ROM
      is 1 wait-state). If this section is not uncommented, IQmathTables2
      will be loaded into other memory (SARAM, Flash, etc.) and will take
      up space, but 0 wait-state is possible.
   */
   /*
   IQmathTables2    : > IQTABLES2, PAGE = 0, TYPE = NOLOAD
   {

              IQmath.lib<IQNexpTable.obj> (IQmathTablesRam)

   }
   */

   FPUmathTables    : > FPUTABLES, PAGE = 0, TYPE = NOLOAD

   DMARAML4         : > RAML4,     PAGE = 0
   //DMARAML5         : > RAML5,     PAGE = 0
   //DMARAML6         : > RAML6,     PAGE = 0
   DMARAML7         : > RAML7,     PAGE = 1

   //ZONE7DATA        : > ZONE7B,    PAGE = 1 /* redefined below */
   ZONE7DATA		    : > ZONE7,	   PAGE = 1
   ZONE6DATA        : > ZONE6,     PAGE = 1

   .reset           : > RESET,     PAGE = 0, TYPE = DSECT /* not used                    */
   csm_rsvd         : > CSM_RSVD   PAGE = 0, TYPE = DSECT /* not used for SARAM examples */
   csmpasswds       : > CSM_PWL    PAGE = 0, TYPE = DSECT /* not used for SARAM examples */

   /* Allocate ADC_cal function (pre-programmed by factory into TI reserved memory) */
   .adc_cal     : load = ADC_CAL,   PAGE = 0, TYPE = NOLOAD

}

/*
//===========================================================================
// End of file.
//===========================================================================
*/

 

 

 

 

 

 

  • Miroslav,
    I would recommend debugging out of RAM, if you load part of your code into flash the flash will have to be erased, rewritten and verified every time you make a small change in your RAM based code. Load times into RAM are much faster!

    Once you have your code fully debugged you can then move your code into Flash. After moving your project to flash I would still recommend that you copy your code into RAM for the best performance.

    However you really want to break your code up, using a #Pragma should work.

    Regards,
    Cody
  • Hello Cody,

    thank you for your answer. Yes, at the moment I am debugging and launching my very extensive application from RAM, but as I mentioned yesterday, there has already been the lack of this memory. On the other side the essential part of my code is ready, so I would like to move it to FLASH at once and after that continue with debbuging of new parts in RAM again. Simply, my aim is to clear RAM for other development.

    The main problem of TMS320F28335 is really a small number of FLASH memory rewrites - due to I need perform it at once.

    I don't understand this: "Once you have your code fully debugged you can then move your code into Flash. After moving your project to flash I would still recommend that you copy your code into RAM for the best performance." Do you mean to place only ISRs etc. in RAM or the whole code?

    Nice day,

    Miroslav
  • Hello everybody,

    I am just ready to say, that the mentioned problem is solved at the moment. There are several steps to achieve it:

    1. you must create a new linker file with flash section (flashfuncs) like attached

    2. if your part of code is done and ready to be moved into FLASH, you will have to mark it with #pragma CODE_SECTION or #pragama DATA_SECTION to place it into specific memory section.

    3. Download code and start debugging

    4. After that, if you want to change something in your application and debug it only in RAM, you will have to set up configuration of debugger : Debug configuration -> Traget -> Flash Settings -> in Flash program setting please check "Load RAM only".  OK, you can download your code now again, but be sure, your flash remains in last state :-)

    /*
    // TI File $Revision: /main/10 $
    // Checkin $Date: July 9, 2008   13:43:56 $
    //###########################################################################
    //
    // FILE:	F28335.cmd
    //
    // TITLE:	Linker Command File For F28335 Device
    //
    //###########################################################################
    // $TI Release:$
    // $Release Date:$
    //###########################################################################
    */
    
    /* ======================================================
    // For Code Composer Studio V2.2 and later
    // ---------------------------------------
    // In addition to this memory linker command file, 
    // add the header linker command file directly to the project. 
    // The header linker command file is required to link the
    // peripheral structures to the proper locations within 
    // the memory map.
    //
    // The header linker files are found in <base>\DSP2833x_Headers\cmd
    //   
    // For BIOS applications add:      DSP2833x_Headers_BIOS.cmd
    // For nonBIOS applications add:   DSP2833x_Headers_nonBIOS.cmd    
    ========================================================= */
    
    /* ======================================================
    // For Code Composer Studio prior to V2.2
    // --------------------------------------
    // 1) Use one of the following -l statements to include the 
    // header linker command file in the project. The header linker
    // file is required to link the peripheral structures to the proper 
    // locations within the memory map                                    */
    
    /* Uncomment this line to include file only for non-BIOS applications */
    /* -l DSP2833x_Headers_nonBIOS.cmd */
    
    /* Uncomment this line to include file only for BIOS applications */
    /* -l DSP2833x_Headers_BIOS.cmd */
    
    /* 2) In your project add the path to <base>\DSP2833x_headers\cmd to the
       library search path under project->build options, linker tab, 
       library search path (-i).
    /*========================================================= */
    
    /* Define the memory block start/length for the F28335  
       PAGE 0 will be used to organize program sections
       PAGE 1 will be used to organize data sections
    
        Notes: 
              Memory blocks on F28335 are uniform (ie same
              physical memory) in both PAGE 0 and PAGE 1.  
              That is the same memory region should not be
              defined for both PAGE 0 and PAGE 1.
              Doing so will result in corruption of program 
              and/or data. 
              
              L0/L1/L2 and L3 memory blocks are mirrored - that is
              they can be accessed in high memory or low memory.
              For simplicity only one instance is used in this
              linker file. 
              
              Contiguous SARAM memory blocks can be combined 
              if required to create a larger memory block. 
     */
    
    
    MEMORY
    {
    PAGE 0:    /* Program Memory */
               /* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE1 for data allocation */
    
       BEGIN      : origin = 0x000000, length = 0x000002     /* Boot to M0 will go here */
       RAMM0      : origin = 0x000050, length = 0x0003B0
      // ZONE0       : origin = 0x004000, length = 0x001000     /* XINTF zone 0 */
       RAML0       : origin = 0x008000, length = 0x001000     /* on-chip RAM block L0 */
       RAML1       : origin = 0x009000, length = 0x001000     /* on-chip RAM block L1 */
       RAML2       : origin = 0x00A000, length = 0x001000     /* on-chip RAM block L2 */
       RAML3       : origin = 0x00B000, length = 0x001000     /* on-chip RAM block L3 */
       RAML4       : origin = 0x00C000, length = 0x001000     /* on-chip RAM block L1 */
    //   FLASH_CRC   : origin = 0x300000, length = 0x000002     /* Application CRC */
       FLASHH      : origin = 0x300002, length = 0x007FFE     /* on-chip FLASH */
       FLASHG      : origin = 0x308000, length = 0x008000     /* on-chip FLASH */
       FLASHF      : origin = 0x310000, length = 0x008000     /* on-chip FLASH */
       FLASHE      : origin = 0x318000, length = 0x008000     /* on-chip FLASH */
       FLASHD      : origin = 0x320000, length = 0x008000     /* on-chip FLASH */
       FLASHC      : origin = 0x328000, length = 0x008000     /* on-chip FLASH */
       FLASHB      : origin = 0x330000, length = 0x007FFE     /* on-chip FLASH */
     //  BEGIN_APP   : origin = 0x33FFF6, length = 0x000002     /* Part of FLASHA.  Used for "boot to Flash" bootloader mode. */
       FLASHA      : origin = 0x338000, length = 0x007F80     /* on-chip FLASH */
       CSM_RSVD    : origin = 0x33FF80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */
       CSM_PWL     : origin = 0x33FFF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA */
       OTP         : origin = 0x380400, length = 0x000400     /* on-chip OTP */
       ADC_CAL     : origin = 0x380080, length = 0x000009     /* ADC_cal function in Reserved memory */
       
       IQTABLES    : origin = 0x3FE000, length = 0x000b50     /* IQ Math Tables in Boot ROM */
       IQTABLES2   : origin = 0x3FEB50, length = 0x00008c     /* IQ Math Tables in Boot ROM */  
       FPUTABLES   : origin = 0x3FEBDC, length = 0x0006A0     /* FPU Tables in Boot ROM */
       BOOTROM     : origin = 0x3FF27C, length = 0x000D44     /* Boot ROM */
       RESET       : origin = 0x3FFFC0, length = 0x000002     /* part of boot ROM  */
       VECTORS     : origin = 0x3FFFC2, length = 0x00003E     /* part of boot ROM  */
    
    PAGE 1 :   /* Data Memory */
               /* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE0 for program allocation */
               /* Registers remain on PAGE1                                                  */
       
       BOOT_RSVD   : origin = 0x000000, length = 0x000050     /* Part of M0, BOOT rom will use this for stack */
      // RAMM0       : origin = 0x000050, length = 0x0003B0     /* on-chip RAM block M0 */
       RAMM1       : origin = 0x000400, length = 0x000400     /* on-chip RAM block M1 */
       RAML5       : origin = 0x00D000, length = 0x001000     /* on-chip RAM block L1 */
       RAML6       : origin = 0x00E000, length = 0x001000     /* on-chip RAM block L1 */
       RAML7       : origin = 0x00F000, length = 0x000FF0     /* on-chip RAM block L1 */
       FLASH_FLAG  : origin = 0x00FFF0, length = 0x00000F
       ZONE7       : origin = 0x200000, length = 0x100000     /* Ext. RAM of 1Mx16b */
       ZONE6       : origin = 0x100000, length = 0x080000     /* Ext. NV RAM 512kx16b */
       FLASH_CRC   : origin = 0x300000, length = 0x000002     /* Application CRC */
       //FLASHB      : origin = 0x330000, length = 0x008000     /* on-chip FLASH */
    }
    
    /* Allocate sections to memory blocks.
       Note:
             codestart user defined section in DSP28_CodeStartBranch.asm used to redirect code 
                       execution when booting to flash
             ramfuncs  user defined section to store functions that will be copied from Flash into RAM
    */ 
     
    SECTIONS
    {
     
       /* Allocate program areas: */
       codestart        : > BEGIN,     PAGE = 0
       ramfuncs         : > RAML0,     PAGE = 0
       flashfuncs       : >>FLASHB  | FLASHC   PAGE = 0
       flashdata		: > FLASHD	   PAGE = 0
       // two > means that linker can split .text section to multiple RAM zones
       .text            : >> RAML0 | RAML1 | RAML2 | RAML3 | RAML4,     PAGE = 0
       .cinit           : > RAML0,     PAGE = 0
       .pinit           : > RAML0,     PAGE = 0
       .switch          : > RAML0,     PAGE = 0
    
       .stack           : > RAML4,     PAGE = 0
       .ebss            : >> RAML5 | RAML7      PAGE = 1
       .econst          : >> RAML6 | RAML7,     PAGE = 1
       .esysmem         : > RAMM1,     PAGE = 1
       .sysmem			    : > RAML0,	   PAGE = 0
       .cio				      : > RAML0,	   PAGE = 0
    
       flash_crc           : > FLASH_CRC   PAGE = 1
       flash_flag          : > FLASH_FLAG  PAGE = 1
    
      // csmpasswds          : > CSM_PWL     PAGE = 0
      // csm_rsvd            : > CSM_RSVD    PAGE = 0
       
       diagbuff           : > RAMM1,      PAGE = 1
    
       /* Initalized sections go in Flash */
       /* For SDFlash to program these, they must be allocated to page 0 */
       
       //.switch             : > FLASHB      PAGE = 0   
    
       /* Allocate IQ math areas: */
       IQmath              : > FLASHC      PAGE = 0                  /* Math Code */
       IQmathTables     : > IQTABLES,  PAGE = 0, TYPE = NOLOAD 
       
       /* Uncomment the section below if calling the IQNexp() or IQexp()
          functions from the IQMath.lib library in order to utilize the 
          relevant IQ Math table in Boot ROM (This saves space and Boot ROM 
          is 1 wait-state). If this section is not uncommented, IQmathTables2
          will be loaded into other memory (SARAM, Flash, etc.) and will take
          up space, but 0 wait-state is possible.
       */
       /*
       IQmathTables2    : > IQTABLES2, PAGE = 0, TYPE = NOLOAD 
       {
       
                  IQmath.lib<IQNexpTable.obj> (IQmathTablesRam)
       
       }
       */
       
       FPUmathTables    : > FPUTABLES, PAGE = 0, TYPE = NOLOAD 
             
       /* Allocate DMA-accessible RAM sections: */
       DMARAML4         : > RAML4,     PAGE = 0
       //DMARAML5         : > RAML5,     PAGE = 1
       //DMARAML6         : > RAML6,     PAGE = 1
       DMARAML7         : > RAML7,     PAGE = 1
       
       ZONE7DATA        : > ZONE7,    PAGE = 1
       ZONE6DATA        : > ZONE6,    PAGE = 1
    
       /* .reset is a standard section used by the compiler.  It contains the */ 
       /* the address of the start of _c_int00 for C Code.   /*
       /* When using the boot ROM this section and the CPU vector */
       /* table is not needed.  Thus the default type is set here to  */
       /* DSECT  */ 
       .reset              : > RESET,      PAGE = 0, TYPE = DSECT
       //vectors             : > VECTORS     PAGE = 0, TYPE = DSECT
       csm_rsvd         : > CSM_RSVD   PAGE = 0, TYPE = DSECT /* not used for SARAM examples */
       csmpasswds       : > CSM_PWL    PAGE = 0, TYPE = DSECT /* not used for SARAM examples */
       
       /* Allocate ADC_cal function (pre-programmed by factory into TI reserved memory) */
       .adc_cal     : load = ADC_CAL,   PAGE = 0, TYPE = NOLOAD
    
    }
    
    /*
    //===========================================================================
    // End of file.
    //===========================================================================
    */