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/TMS320F28022: Is there a more automated way to decide wether to program FLASH?

Part Number: TMS320F28022

Tool/software: Code Composer Studio

Win7 SP1 32bit, CCSv6.1, C2000 tools.

I am developing a project that I have put some routines into FLASH, and run others from ram.

Many times I do not change the routines or data that is already in FLASH, and in that case I would like to not erase and burn the FLASH.

Currently, I have a .h file the linker looks at and a #ifdef #else in the command file that either LOADs or NOLOADs parts depending on if I have changed that code.

Sometimes I forget to change the content of that .h file, and of course my program then goes into the weeds or I burn the FLASH unnecessarily.

Can Code Composer automatically decide for me whether to burn the flash or not?

Maybe an external routine of some kind to read the FLASH and compare it to the .out file.

Ideas?

Thanks, Mark.

  • Hi Mark,

    Cool Javelin said:
    Can Code Composer automatically decide for me whether to burn the flash or not?

    One possible way to implement this is via a DSS script that you can run from CCS. You can write a DSS script that will verify the program (parts that will go to flash) vs the actual contents in flash and if that it matches, just have DSS load RAM only and leave the flash alone. If the verification fails, you can have DSS load everything. I'll see if I can put together a simple example for this

    Thanks

    ki

  • Holy Crap a whole new tool. Now what am I gonna do.

    I haven't heard about DSS till now, I may have to spend the next month or two learning it.

    :)