• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 952 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/TMS320F2812: Flashing target takes very long

Michiel van Rijnbach81
Intellectual 330 points

Part Number: TMS320F2812

Tool/software: Code Composer Studio

Hi,

I am flashing my target (TMS320F2812) using Code Composer Studio 7.2.0.00013 and a TI Docking station USB-EMU R3. It takes a very long time, about 20 minutes. It works, it just takes a very long time. I think the code is about 86 MB. Can I change some settings to increase the speed?

Best regards, Michiel van Rijnbach.

  • 0
    TI__Mastermind 42195 points

    MIchiel,

    you will find a few questions and tips below!

    1. does it take 20 minutes just to flash the device, or does this include building the project as well?
    2. You say your code is 86MB... I assume you mean your C project, as the F2812's flash size is much smaller than that, is my understanding correct?
    3. How long does it take to load a RAM only project?
      1. If both Flash and RAM are slow, check that the JTAG TCLK Frequency is set to 1.0MHz. We do not recommend changing this from 1.0MHz.
        1. Open your target configuration by double clicking on it. 1. click on advanced; 2. click on "Texas Instruments XDS100v1 USB Debug Probe_0"; 3. check that the JTAG TCLK Frequency is set to 1MHz
      2. If the Flash programming is still slow you should also check the Flash Settings.
        1. To check the flash settings 1.Right click on your target configuration and select properties.; 2. Click on "F2812 Flash Settings" ; 3. check OSCLK and PLLCR.
          1. OSCLK is hardware dependent, but you can adjust PLLCR.

    Regards,
    Cody

  • 0 in reply to Cody Watkins
    Intellectual 330 points

    Hi Cody,

    thank you for your elaborate answer. I'll try to give answers to your questions:

    1. It took 20 minutes to only flash the device. However, I did it again today and now it took 'only' 7 minutes.

    2. Yeah, I guess I talked nonsense there. During the flashing I saw: .text: 32752 of 83314 at 0x3d8000 (Texas Instruments XDS100v1 USB Emulator_0/C28xx), so I thought it was 83314 kB (even misread the 83), but I guess that is 83 kB then?

    3. I haven't tried to load a RAM project yet. Actually I don't know what I need to do to change the project for this purpose. I think I'll have to change EZdspTMS320F2812_ROM_lnk.cmd (got this from an external supplier example file) to F2812_EzDSP_RAM_lnk.cmd (I'm using the eZdsp evaluation board) and change the jumper setings. I think I need to change some things in the code as well right?

    1. The JTAG TCLK frequency is also set to 1.0 MHz

    2. The Flash settings are also the same (OSCLK=30 MHz and PLLCR=10). I think this means that the internal frequency becomes 30x10/2=150 MHz right? This is already the highest setting I think.

    So I guess I'll still need to see what I need to do to load the code to RAM. I must also say that it is strange that the flashing went faster today.

    Best regards, Michiel.

  • 0 in reply to Michiel van Rijnbach81
    TI__Mastermind 42195 points

    Michiel,

    83KB sounds more reasonable.

    To load a RAM only code: You will need to use the command file to place the sections of code into RAM. The easiest way to test with a RAM only project is to use an example project, you can find one of those here.

    Your flash settings seem to be correct.

    I would expect flash programming times to be about the same day to day, not varying by minutes day to day.

    Regards,
    Cody