TMS320F280049C: Why different cmd files, the same Flash API function will compiler different content?

Shaoxing Ke

Expert 3590 points

Part Number: TMS320F280049C

Tool/software:

Hi Experts,

I am asking for my customer here.

They used the same Flash API function, and also copy Flash API from Flash to RAM.

RAM_APILIB         : origin = 0x009600, length = 0x000A00
FLASH_APILIB       : origin = 0x083000, length = 0x001000
 
      GROUP
        {
            APIramLib
            { -l F021_API_F28004x_FPU32.lib}
 
        }  LOAD = FLASH_APILIB,
            RUN = RAM_APILIB,
            LOAD_START(_RamfuncsAPILoadStart),
            LOAD_END(_RamfuncsAPILoadEnd),
            RUN_START(_RamfuncsAPIRunStart),
            PAGE = 0, ALIGN(4)

The specified RAM_APILIB does not store other content. we checked the assembly of the Fapi_initializeAPI function and found that there is an abnormal statement LCR FS$$DIV in the Fapi_initializeAPI function. The same statement, compiled using the cmd of bank0 and bank1, has different contents programming into the flash.

#1.Use bank1 cmd to compile, burn and debug: the left side is the Fapi_initializeAPI function assembly code, and the right side is the flash memory