• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 646 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.

debugging with CCS5.1 on OMAPL138

Iain Scott
Expert 1230 points

I have just migrated from CCS4 to CCS5.1.

In the former I started the ARM until it goes into a loop waiting for the C6748 to initialse.

I then select Target->Launch TI Debugger and wait for the USB510 emulator to initialise.

Once initialised I am then able to Target->Connect Target.

Once the target is connected I can then load the symbols and the debugger goes to a while loop at the end of main() in my program. I can then move the cursor to the next line of the code and run the debugger.

I am struggling to see how I can achieve the same thing with CCS5.1.

The only option seems to be to run the debugger which gives a connection error.

Can someone point me in the right direction please?

Thanks in advance

 Iain

  • 0
    TI__Guru**** 480521 points

    Hi Iain,

    Iain Scott said:
    I then select Target->Launch TI Debugger and wait for the USB510 emulator to initialise.

    This is the only step that changed in your use case between v4 and v5. To launch the debugger without a project association, use the step outlined in slides 38 and 39 of: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/workshops/CCSv5/CCSv5_AdvancedWorkshop.pdf 

    The rest of the steps should be the same.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1230 points

    Thanks ki,

    The answer is always there somewhere. It is a matter of knowing where the information is to be found!

    Regards Iain

  • 0 in reply to Iain Scott
    Prodigy 10 points

    In my opinion removing “Launch TI Debugger”/”Connect target” from the run-menu as it was in CCSv4 isn’t such a great idea. From what I see with the “new method” you still have to do the same; Launch the Target Configuration (same as Launch TI Debugger) and “Connect to target”. The only difference is that the first step has been hidden from the user in a context-menu in a view that isn’t always present to the user. Connecting to the device is what i consider a basic operation and it is unfortunate that it has been so well hidden.

    Having to right-click in a view not always visible on the screen and then go to the run-menu to connect to the target doesn’t follow an intuitive pattern GUI-wise in my opinion. The task just became more complicated.

    Compiling the project and debugging it isn’t always the correct use-case for me. I often connect to devices to program them with the original out-files of a pristine CCS-project (the latest official build shipped to our customers), and I expect my customers to be able to achieve the same without any fuzz.

    I’m sure there is a way to create Target Configurations that doesn’t compile the project and just loads the symbols, but having to work with multiple Target Configurations and keeping track of what is active/default is equally cumbersome when the prior method worked just fine without any special configuration.

    What about presenting the option to Launch the in the Right-click menu for the Target Configuration file the Project Menu? This would be a lot less convoluted and you don’t have to find an e2e-posting to be able to achieve what you want, namely doing something as basic as just connecting to the device...


    The method of using an “Active” and/or “Default” Target Configuration File is a bit lost when it comes to just connecting to the device, if you have to browse to and actively select which Target Configuration file you want to connect to anyway. Having an option to just connect to the active/default in the Run-menu would be greatly appreciated by not only me, I’m sure. The problem is especially clear if you have a project with a lot of Build Configurations spanning many kit-types and connection methods.

    Frank Audun Kvamtrø

    Crosshairs Embedded

  • 0 in reply to Frank Audun Kvamtro
    Expert 1230 points

    Hi Frank,

    You are absolutely correct in what you say.

    It was more obvious in ccsv4. Another case of improvements having a negative effect!

    I hope TI will take note.

    Regards Iain