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.

TMS320F28069: Flash API Programming fails when not directly programmed by CCS

Part Number: TMS320F28069
Other Parts Discussed in Thread: CONTROLSUITE

Hello

Im working on a Project wich needs to be loaded Standalone from Flash and I have to save data to Flash. Based on SPRA958L I implemented the functionality to copy my Programm Code, the .econst and the .switch Symbols to Ram at Startup. I used SPRAB60 to implement a EEPROM Emulation in one Flash Sector and I used the 2806x_BootROM_API_TABLE_Symbols_fpu32.lib

If I programm the Device with CCS it works fine. My Code operates as it should and I'm able to write to Flash. If I reset the Device and let it boot from Flash the code works also but I'm not able to write to flash.I have figured out, that the Flash_Program Function of the API gets called but Returns a Error Code 30 which means Program Fail.

I'm wondering why it works when loaded from CCS but not from Flash. I've attached my linker cmd File below. Is there something different in the initilization when booted from Flash?

Thank You and best Regards

Andri

MEMORY
{
PAGE 0 :   /* Program Memory */
           /* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE1 for data allocation */
   RAMM0       : origin = 0x000050, length = 0x0003B0     /* on-chip RAM block M0 */
   RAML0       : origin = 0x008000, length = 0x000800     /* on-chip RAM block L0 */
   RAML3       : origin = 0x009000, length = 0x001000	  /* on-chip RAM block L3 */
   OTP         : origin = 0x3D7800, length = 0x000400     /* on-chip OTP */

   FLASHG      : origin = 0x3DC000, length = 0x004000     /* on-chip FLASH */
   FLASHF      : origin = 0x3E0000, length = 0x004000     /* on-chip FLASH */
   FLASHE      : origin = 0x3E4000, length = 0x004000     /* on-chip FLASH */
   FLASHD      : origin = 0x3E8000, length = 0x004000     /* on-chip FLASH */
   FLASHC      : origin = 0x3EC000, length = 0x004000     /* on-chip FLASH */
   FLASHA      : origin = 0x3F4000, length = 0x003F80     /* on-chip FLASH */
   CSM_RSVD    : origin = 0x3F7F80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */
   BEGIN       : origin = 0x3F7FF6, length = 0x000002     /* Part of FLASHA.  Used for "boot to Flash" bootloader mode. */
   CSM_PWL_P0  : origin = 0x3F7FF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA */

   FPUTABLES   : origin = 0x3FD860, length = 0x0006A0	  /* FPU Tables in Boot ROM */
   IQTABLES    : origin = 0x3FDF00, length = 0x000B50     /* IQ Math Tables in Boot ROM */
   IQTABLES2   : origin = 0x3FEA50, length = 0x00008C     /* IQ Math Tables in Boot ROM */
   IQTABLES3   : origin = 0x3FEADC, length = 0x0000AA	  /* IQ Math Tables in Boot ROM */

   ROM         : origin = 0x3FF3B0, length = 0x000C10     /* 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 */
   RAMM1       : origin = 0x000400, length = 0x000400     /* on-chip RAM block M1 */
   RAML1       : origin = 0x008800, length = 0x000400     /* on-chip RAM block L1 */
   RAML2       : origin = 0x008C00, length = 0x000400     /* on-chip RAM block L2 */
   RAML4       : origin = 0x00A000, length = 0x002000     /* on-chip RAM block L4 */
   RAML5       : origin = 0x00C000, length = 0x002000     /* on-chip RAM block L5 */
   RAML6       : origin = 0x00E000, length = 0x002000     /* on-chip RAM block L6 */
   RAML7       : origin = 0x010000, length = 0x002000     /* on-chip RAM block L7 */
   RAML8       : origin = 0x012000, length = 0x002000     /* on-chip RAM block L8 */
   USB_RAM     : origin = 0x040000, length = 0x000800     /* USB RAM		  */
   FLASHH      : origin = 0x3D8000, length = 0x004000     /* on-chip FLASH */
   FLASHB      : origin = 0x3F0000, length = 0x004000     /* 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
{
   .cinit              : > FLASHA,     PAGE = 0
   .pinit              : > FLASHA,     PAGE = 0
   .text               : > FLASHA,     PAGE = 0
   codestart           : > BEGIN,      PAGE = 0
   ramfuncs            : LOAD = FLASHD,
                         RUN = RAML3,
                         LOAD_START(_RamfuncsLoadStart),
                         LOAD_END(_RamfuncsLoadEnd),
                         RUN_START(_RamfuncsRunStart),
						 LOAD_SIZE(_RamfuncsLoadSize),
                         PAGE = 0

   csmpasswds          : > CSM_PWL_P0, PAGE = 0
   csm_rsvd            : > CSM_RSVD,   PAGE = 0

   /* Allocate uninitalized data sections: */
   .stack              : > RAMM1,      PAGE = 1
   .ebss               : > RAML4,      PAGE = 1
   .esysmem            : > RAML2,      PAGE = 1

   /* Initalized sections to go in Flash */
   /* For SDFlash to program these, they must be allocated to page 0 */
   .econst             : LOAD = FLASHB,
                         RUN = RAML6,
                         LOAD_START(_EconstLoadStart),
                         RUN_START(_EconstRunStart),
                         LOAD_SIZE(_EconstLoadSize),
                         PAGE = 1
   .switch             : LOAD = FLASHA,
                         RUN = RAMM0,
                         LOAD_START(_SwitchLoadStart),
                         RUN_START(_SwitchRunStart),
                         LOAD_SIZE(_SwitchLoadSize),
                         PAGE = 0

   /* Allocate Memory for Register Map: */
   .register           : > RAML1,      PAGE = 1

   /* Allocate IQ math areas: */
   IQmath              : > FLASHA,     PAGE = 0            /* Math Code */
   IQmathTables        : > IQTABLES,   PAGE = 0, TYPE = NOLOAD

   /* Allocate FPU math areas: */
   FPUmathTables       : > FPUTABLES,  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)

   }
   */
    /* Uncomment the section below if calling the IQNasin() or IQasin()
       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.
    */
    /*
    IQmathTables3    : > IQTABLES3, PAGE = 0, TYPE = NOLOAD
    {

               IQmath.lib<IQNasinTable.obj> (IQmathTablesRam)

    }
    */

   /* .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

}

  • Andri,

    These are the following things I would check:-

    1) Did you make sure the addresses you trying to program where in erase condition to begin with.

    2) Did you make sure your PLL settings match with CPU_RATE definition mentioned in Flash2806x_API_Config.h

    3) Check CLKOUT to make sure you are running the configured frequency

    4) Do you see the problem in different addresses?

    5) Is this problem observed on multiple devices?

    Regards,
    Manoj
  • Dear Manoj,

    I checked the Address and Clocking Configuration and everything seems fine. As I mentioned the code works when directly loaded from CCS. I also used another Flash Sector and another Device, the Problem still occurs.

    I suppose there is a Problem with booting the Device from Flash, maybe with copying part of the code to RAM.

    I understood that the Flash API Functions are stored in the Boot Rom and therefore I don't have to copy them to RAM. But do I have to specifiy them in the linker cmd File like it's done for the FPUTABLES or the IQTABLES?

    Can there be a Problem with the CodeSecurityModule? The Documentation says it needs to be unlocked if the access is done from a unsecure section. I assume that the BootRom from where the Flash API accesses the Flash is unsecure so I've tried to unlock the CSM with a dummy Read (see the following code) as mentioned in the documentation. Or is it unlocked per Default?

    Best regards

    Andri

    Page_Pointer = (Uint16 *)0x3F7FF8; //Adress of PWL Register
    	for(i=0;i<8;i++) {
    		dummy = *(Page_Pointer++);
    	}

  • Andri,

    Is your device locked? If locked, you can't program / erase flash by running flash API functions from un-secure memory (BOOTROM). You have to unlocked it first.

    You can use CsmUnlock function found in F2806x_SysCtrl.c. Also, If you have already reviewed <controlSUITE>\libs\utilities\flash_api\2806x\v100a\Example_Flash2806x_API_FPU example. Please do so.

    Uint16 CsmUnlock()
    {
    volatile Uint16 temp;

    // Load the key registers with the current password. The 0xFFFF's are dummy
    // passwords. User should replace them with the correct password for the DSP.

    EALLOW;
    CsmRegs.KEY0 = 0xFFFF;
    CsmRegs.KEY1 = 0xFFFF;
    CsmRegs.KEY2 = 0xFFFF;
    CsmRegs.KEY3 = 0xFFFF;
    CsmRegs.KEY4 = 0xFFFF;
    CsmRegs.KEY5 = 0xFFFF;
    CsmRegs.KEY6 = 0xFFFF;
    CsmRegs.KEY7 = 0xFFFF;
    EDIS;

    // Perform a dummy read of the password locations
    // if they match the key values, the CSM will unlock

    temp = CsmPwl.PSWD0;
    temp = CsmPwl.PSWD1;
    temp = CsmPwl.PSWD2;
    temp = CsmPwl.PSWD3;
    temp = CsmPwl.PSWD4;
    temp = CsmPwl.PSWD5;
    temp = CsmPwl.PSWD6;
    temp = CsmPwl.PSWD7;

    // If the CSM unlocked, return succes, otherwise return
    // failure.
    if (CsmRegs.CSMSCR.bit.SECURE == 0) return STATUS_SUCCESS;
    else return STATUS_FAIL;

    }

    Regards,
    Manoj
  • Manoj

    I added your code to unlock the the Device and verfied it by reading the specific bit. My Device is unlocked but it didn't resolved the Problem.

    I could reproduce the error after programming the device with CCS by Disconnecting and Reconnecting the Target. After Programming I'm able to write to Flash, but after the Reconnect the API Function Flash_Program fails permanently with the Error Code #30.

    I checked the .map File of the Output and the Flash Related Symbols are mapped as follows:

    1       00000d02  _Flash_CallbackPtr     
    1        00000d04  _Flash_CPUScaleFactor
    abs   003ffebb  _Flash2806x_Program    
    abs   003ffebd  _Flash2806x_Erase 

    I couldn't find any Ressource to check if they are correct, but in my understanding Disconnect and Reconnect the Target should not change anything in the mapping.

    Thank You
    Andri

  • Andri,

    Yes, disconnecting and reconnecting the target shouldn't change anything in mapping.

    In this stage, I would compare your code with controlsuite example implementation. So, I just wanted to highlight that you don't need to use software flash api library as API is already available in BOOTROM.

    Regards,
    Manoj
  • Just FYI... in case you didn't know such example existed...
    Example projects available in controlSuite shows how both software flash API and ROM flash API needs to be integrated in your project.

    Regards,
    Manoj
  • Manoj

    As you recommended I compared my code with the examples and could resolve the Problem.

    Unitl now I worked with the "Flash_API_Example" from the Libraries Section. Today I checked also the "Example_2806xFlashProgramming" from the Device Specific Folder and realized that I have to put EALLOW/EDIS around the Scale Factor and Callback Ptr initialization.

     EALLOW;

     Flash_CPUScaleFactor = SCALE_FACTOR;

     Flash_CallbackPtr = 0;

     EDIS;

    For some Reason this is not done in the Examples found in the Flash_API Library. Thank you for your assist to resolve my Problem.

    Andri