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/TMS320F28379D: Speed up program download time when using flash memory?

Part Number: TMS320F28379D
Other Parts Discussed in Thread: UNIFLASH, TMS320F28377D, C2000WARE

Tool/software: Code Composer Studio

After utilizing flash memory the amount of time it takes to download a program has grown significantly, which slows down debugging time.

Is it necessary for CCS to erase the flash memory every time a download is initiated?  Or, more generally, what can be done to speed up program download times?

Kindly,

Graham

  • Graham,

    I assume you are using CCS Flash Plugin or UniFlash. Which version are you using?

    Regarding erase: There is no need to erase the entire Flash bank every time a download is initiated. In the On-Chip Flash Plugin GUI (CCS Debug view -> Tools menu -> On-Chip Flash GUI), you can choose the option "Necessary Sectors Only (for Program Load)" under Erase settings. This will erase only the sectors that are supposed to be reprogrammed (based on your linker cmd file).

    Since you are in development stage, I would suggest to uncheck "Verify Flash after Program" under Download Settings. This will help save some more time for you.

    If you have multiple sections in your linker cmd file, you can try enabling "Combine Sections during Program Load to increase Performance" under Performance Settings. If you don't have too many sections, this is not suggested. When you use this feature, multiple sections in your executable will be combined together and programmed at once - While doing this, all the holes in between the sections will be filled with all 1s data and ECC also gets programmed for this all 1s data.

    A general note: XDS100 or 110 are low performance emulators. You will not get much performance improvement when using low speed emulators.  XDS200 is the best choice - not as expensive as XDS510/560, but competes with their performance. 


    If you are using UniFlash, you will find similar options in UniFlash GUI as well.

    Thanks and regards,
    Vamsi

  • Thanks Vamsi. This is very helpful.

    Graham
  • Hi Graham,

    Also note the following link.  May help you decide if an debug probe/emulator investment is worthwhile:
    http://dev.ti.com/tirex/#/?link=Development%20Tools%2FDebug%20Probes%2FXDS%2FDocuments%2FDebug%20Probe%20Performance%20Comparison


    Thank you,
    Brett

  • Graham,

    Search for TMS320F28377D in the above link to see performance of different emulators with C2000 devices.

    Thanks and regards,
    Vamsi
  • Hi Vamsi,

    We're going to upgrade to the XDS200.  Our development setup is the F28379D controlCard with the controlCard docking station.  

    Could you verify that we do or do not need any additional adapters?  There is a 14-pin JTAG connector on the docking station and a small high density connector at J9 on the controlCard.

    Kindly,

    Graham

  • Graham,

    I notified this to our CC expert to suggest you on this.

    Thanks and regards,
    Vamsi
  • Graham,

    J8, the high-density connector, is not used for JTAG or emulation. It provides access EMIF and some other communication signals.

    J2, the 14pin pin header on the docking station, was added to enable the use of external emulators.

    • Assuming you have a 14pin emulator you do not need any extra hardware.
    • The XDS200 uses TI's standard 20 pin emulator connector, so be sure that you buy one that comes with the 20-14 pin adapter.
    • Please note you will need to make change switch configurations on the controlCARD. These are documented in the user's guide that is included in C2000Ware.

    Regards,
    Cody