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.

Error with emulator since update to 4.02

Edit: LH: Moving thread to CCS forum

 

Hi

Since I've updated to CCC 4.02 (I was running CCC 4.0), I can't connect/debug with my F28035 Developer Kit.

It tells me "Eror initializing emulator" at the moment I want to launch the debugger.

I've tried to create a new Target Connection, without any luck

 

Any idea?

  • Jerome,

    I suggest posting this to the Code Composer Studio  forum - the guys there may be able to help. The  difference between 4.0 and 4.0.2 is that they added CLA support.  The emulator should still connect though. Have you tried creating a new workspace and trying in that workspace?

  • Hi

    I didn't have any solution posted on my message on the CCS forum.

    http://e2e.ti.com/forums/p/12922/50303.aspx#50303

    However I did find a way to launch the debugger, by bypassing the CLA0 inside Target Communication. However I do need the CLA for a project.

    What do you mean when you say they added CLA support inside 4.02? There's already 3 examples given for the F28035 that are using the CLA for CCSv4, and I was able to run the examples in 4.00. I can still run it in 4.02, but I don't understand how it runs since I disabled the CLA0 procecessor.

    Thx for your input

    Here's what I did:

    <p><img src="http://i48.tinypic.com/ojm1yt.png" border="0" /></p>

     

  • Jerome,

    What I mean is that the way CCSv4 is coded, it doesnt understand the CLA connection properties when starting up the target configuration (since CCSv4.0 does not have CLA support yet - CCSv4 treats CLA as a separate processor - but 4.0.0 does not have support for this. 4.0.2 does).  Yes, there are CCSv4 examples, but they will not run properly until CCSv4.0.2.

  • Any idea why it only works on 4.02 when I bypass the CLA? If I need to use the CLA, what should I do?

  • It should work with v4.0.2 without bypassing the CLA(works fine on my setup with XDS100) - I would post this to the Code Composer Studio forums, as they would be able to help you better with CCS-specific questions on your computer.

  • I posted a solution for this in the thread below. Can you see if this works. If not, we can continue to investigate this issue.

    http://e2e.ti.com/forums/p/12922/50303.aspx#50303

    Jerome,

    You need to recreate the target configuration file. When you re-use the configuration file that was generated in CCSv4.0 in CCSv4.0.2, the appropriate changes that support CLA are not being propagated properly. To force the regeneration of this configuration file, please de-select the board "Experimenter's Kit - Piccolo F28035_0"  and then select it again. Under the source tab, make sure you see a line that looks like the one below. I've attached the complete configuration file as well.

    <instance XML_version="1.2" href="drivers\tixds100cla.xml" id="drivers" xml="tixds100cla.xml" xmlpath="drivers"/>

     

     

    Raj

     

     

    Raj

  • Try creating a new Target Configuration File (.ccxml) in CCSv4.0.2, if you are using one from 4.0.0 or 4.0.1 it won't work.  I don't have all the details on why but it has to do with the fact that the earlier versions did not support CLA debug but 4.0.2 does and when it tries to use the settings in the old file it fails to launch the debugger.  Creating a new file should set everything up correctly.

    John