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.

TMS320F280049: ROM Flash API

Part Number: TMS320F280049

Hi expert,

My customer used flash API earlier in their project. Recently, they want to save more RAM memory for other use.

So they try a way but failed, I just read flash API guide and know that,ROM flash API will save more RAM memory.

F021_ROM_API_F28004x_FPU32.lib – This is the Boot ROM Flash API symbols library for
TMS320F28004x devices. This contains the addresses of the various Flash API functions that
are embedded into the device Boot ROM. Since all of the functions reside in ROM, adding the
boot ROM symbols to the application takes up only a small amount of Flash and/or RAM space
when compared to that of the Software API library.

so I simply suggest them to use F021_ROM_API_F28004x_FPU32.lib.

and they just do 2 things.

1. change the file add to the project

2.change the file search path:

Customer want to check two things 

1. do they need to any other changes? such as change CMD file?

2. any potentail risk to use ROM Flash API?

BR

Emma

  • Hi Emma,

    Our F021 Flash API expert is out of office today. Please expect a delay in response

    Regards,

    Peter

  • Emma,

    1. In the linker command file, there is no need to map the ROM flash API library (for flash load and RAM run).

    2. No risk. Note that flash API is in unsecure ROM.  If customer wants to erase/program secured flash sectors, then the flash API should be executed from either the secured RAM or from the other secured flash bank on which the flash operations are not targeted (this secured RAM/flash bank should be of the same security zone as that of the target bank on which the erase/program operations are targeted).

    Thanks and regards,
    Vamsi