• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 872 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.

CCS4.1 and F28035 - problem

Todd Anderson2297
Expert 4240 points
Other Parts Discussed in Thread: CONTROLSUITE

All:

I have not been able to download the CLA-FIR example to the F28035 Control Card using CCS 4.1  It does work fine with CCS 3.3.

Here is the message I receive:

"Exception occured during launch

Reason: Failed to load program 'Example_2803xClaAdcFir.out' on any of the targets.

Reason: The target 'Texas Instruments XDS100 USB Emulator_0/C28xx' could not be found."

 

Anything I can do to fix this?

I have successfully used the experimenter's board with F2808 and F28027 cards. I have also successfully used the 28335 eZdsp board with CCS 4.1

Regards,

Todd Anderson

 

  • 0
    TI__Guru* 93100 points

    Todd,

    I've been unable to reproduce this. 

    I have the latest CCS 4.1 ( Version: 4.1.0.02003 ) and I've downloaded the header file examples from controlSUITE. 

    I've tried it with

    1) Spectrum Digital XDS510USB+,

    2)  XDS100v1 and \

    3) XDS100v2

    Can you check that you have the latest 4.1 and not a previous beta?

    -Lori

     

  • 0 in reply to Lori Heustess
    TI__Guru* 93100 points

    Todd,

    I'm still unable to reproduce this. I'm going to move the thread to the CCS forum to see if they have any suggestions.

    Todd Anderson said:


    Lori:

    Thanks for looking into this. I recently deleted ccs4.0 and downloaded the same version as you have. (4.1.0.02003)

    I have not tried SD XDS510USB, but I have had success with everything but my two 28035 controlcards.


    Regards,
    Todd Anderson
    MCU Field Applications
    Minneapolis
    952-876-5931
    New Cellphone: 952-221-2446


  • 0 in reply to Lori Heustess
    TI__Expert 4240 points

    All:

    The Debug Launch icon in CCS4.1 does not work for F28035. This needs to be fixed.

    To load and execute F28035 code, here is the procedure that needs to be done:

    In C/C++ view

    1. Do not use "Debug Launch" icon.

    2. Go to "Target Configurations" tab.

    3. Right click on configuration for F28035. (If one does not exist, you will need to create one by going to Target-->New Target Configuration)

    4. Choose "Launch selected configuration."

    In (resulting) Debug view

    5. Connect to target by Target-->Connect Target

    6. Load code by Target-->Load Program (A window will come up - browse to the .out file for the project you are loading.)

    At this point, you will be at "main," and you can continue from there.

  • 0 in reply to Todd Anderson2297
    TI__Guru**** 162935 points

    Todd,

    I think this is a case of not understanding how the bug button works.

    The default behavior of the bug button is to debug the active project.  This will look at the active project and use the active target configuration from that project, if there is no target config it will use the one that is set as default in the target configurations view.

    I suspect that when you are clicking the button it is not using the configuration that you want.

     

    John

     

     

  • 0 in reply to JohnS
    TI__Expert 4240 points

    John:

    Thanks for your reply. The F28035 is different from all of the other C28x family, in that it has a CPU and a CLA on-board. The procedure that I described in the earlier note is essentially a workaround to allow code to be loaded into the F28035.

    If I use the F28035-XDX100 configuration file as the default, I get an error when clicking on the bug button, as described above.

    Regards,

    Todd Anderson

  • 0 in reply to Todd Anderson2297
    TI__Guru**** 162935 points

    Todd,

    The only thing I can think of is to try deleting the launch configuration.  This is an eclipse concept that we abstract in CCS.  If you go to the debug button and click the down arrow beside it, select Debug...

    Expand the "Project Debug Session" node, select the name of your project, press delete, say yes, close the dialog.

    Now try clicking the bug.

    John

  • 0 in reply to JohnS
    TI__Guru**** 162935 points

    Todd did you get a chance to try deleting the launch configuration?

  • 0 in reply to JohnS
    TI__Guru**** 162935 points

    Based on some other issues we have seen could you try this?

     

    Right click on your project.

    Select Debug Properties.

    Select the Debugger tab

    Set the option to connect to exact CPU, select the 28x core

    Click Apply and Ok.

    Now try debugging the active project.

     

     

    Alternatively you could bypass the CLA in your target configuration.