LAUNCHXL-F28069M: Saving code to non-volatile memory

Hello Divyesh,

Have you verified that the code in the .text section of the linker command file is using the Flash memory? If you want to see a working example, you can load one of the Flash examples from C2000Ware to see the linker command file (which is where most of the work will need to be done). Once you have your program loaded to Flash and running, to modify Flash at runtime you will need to use the Flash API from RAM.

For Flash C2000Ware examples which also include some Flash API usage, refer to C2000Ware_5_01_00_00device_support\f2806x\examples\c28\flash_programming. Note that you only need to do the memcpy if you plan on running the code from RAM but storing it in Flash so resets won't prevent the program from running afterwards.

Hello Omer,

Thank you for your response, I'm not sure how do you verify the .text in the .cmd file, I mean .text file states to allocate program in "FlashA_B" of page 0, the FLASHA_B holds memory address from 0x3F0000 to 0x3F7F80, which I've verified are being updated.

I found the F28069M.cmd file in C2000Ware_5_01_00_00\device_support\f2806x\common\cmd including which I could see the memory addresses being updated or cleared (As shown in the picture previously). So estimating I'm able to update the flash, I tried calling memcpy function (as mentioned below) but I run into errors like "errors encountered during linking" or "unresolved symbol remain" 

I as well tried updating the flash example but I run into the error "program won't fit into the memory" on .ebss of cmd file

Thank you for your aiding replies,

Omer Amir said:

Based on your screenshots, your program should be loaded to Flash correctly. Let me know if you don't see the program at the specified addresses at the boot up of your device

I can see the code being successfully updated at the address 

Omer Amir said:

Since you've already determined what memory section is full, you can add more memory units (preferrably contiguous locations) to the section. To do this, you can replace ".ebss : > RAML2_3, PAGE=1" with ".ebss : >> RAML2_3 | RAMx, PAGE=1", where RAMx is another RAM unit in page 1 (you need to choose memories within the same page of the same memory type).

I previously tried doing that but encountered the same result, I've tried adding ".ebss: > M0SARAM | M1SARAM, PAGE = 1" or allotting whole M0SARAM to .ebss and M1SARAM to others. none favoured.

Omer Amir said:

Please take a look at the console output and find what symbols are not properly defined. You'll need to find out what these are and if you have the proper header files included so that the compiler can locate the variables/functions.

I could figure out the unresolved symbols :
_RamfuncsLoadSize ./main.obj
_RamfuncsLoadStart ./main.obj
_RamfuncsRunStart ./main.obj 

this functions are not declared in the code, so I had used RamfuncsLoadSize,RamfuncsLoadStart and RamfuncsRunStart in my main code, I did update them in the cmd file as well, like I've tried doing both "using _Ramsfuncs in my main program, while keeping the F28069M.cmd as it is" and "using Ramfuncs in the main function and then updating them in the .cmd file" yet I'm forwarded to the following error.

I did try adding:

extern Uint16 RamfuncsLoadStart;
extern Uint16 RamfuncsLoadEnd;
extern Uint16 RamfuncsRunStart;
extern Uint16 RamfuncsLoadSize;

to my main file, which changes the error to the warning saying "#169-D argument of type "Uint16" is incompatible with parameter of type "const void *__restrict__""

EDIT: The issue is resolved, I added "Example_MemCopy(Uint16 *SourceAddr, Uint16* SourceEndAddr, Uint16* DestAddr)" function from flash programming and it worked, thank you for your assistance through out.