C2833x Peripheral Examples - Cannot debug in CCSv5 - No source available

Dear Robert,

Please confirm the emulator for connection and try to launch selected configuration.

If you could tell us more information such as compiler version, it will be better for troubleshooting.

Best regards,
Janet

I re-launched several times.  It always says it is connected, but it has this in the debug window:

main() 0x009474 (main has only skeletal debug info)

It also gave me a warning when the project built:

This project was created using an older version of compiler that is not currently installed: 5.2.1 [C2000]. A newer version of the compiler has been used:

6.0.2. Please properly migrate the project to a newer compiler version, or install the older version of the compiler.

Is the code being placed in the right place?  I can't quite see how that could cause the debugger to not see the source code.

Thanks for your help.

- Bob

Robert,

This sometimes occurs in CCSv5 and it may have something to do with the way the project was imported.  If you still have the original project, make sure you choose the correct import option (use import legacy project if the project was created prior to CCSv4).  This has been a known bug for a short period of time.  If you do not have the latest version (or all the updates installed), I recommend downloading the update and seeing if this resolves the problem.  Otherwise, the next release should have this fixed.

Kris

Just to note, while this is an undoubtedly an annoyance, you should still be able to debug the project just fine.  The expressions window, disassembly, and memory browser windows should all still function properly.  If you need breakpoints, you can insert an

asm(" ESTOP0");

line in your code where you would like to set the breakpoint and recompile.  I would still try updating first though as this may already be resolved.

Kris

Still no solution, but here's what I have done since my last post:

1. I wiped the project and re-imported it.  It is a CCSv4 project, and CCSv5 imports it silently.  In other words, it does not ask me if I want to convert a legacy project.  It just imports it and replaces the .project and .cdtbuild files with new ones.  I rebuilt it and started a debug session.  Same results as before.
2. I found an eZdsp board and tried running on it.  Same issues as with the in-house board.
3. I downloaded the latest version of the XDC tools before doing any of the above.

Robert,

What is your full CCS version number?  This can be found in the About Code Composer Studio option under the Help menu.

Are you by chance using the same workspace as you did with CCSv4?  Even if you are not, they can become corrupted occasionally.  Let's try making a new one.  Here are some other general tips (made for CCSv4, but are applicable here):

http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#General_IDE

Kris

Kris,

The full CCS version number is 5.1.0.08020.

I have already tried all of those tips.  I deleted the information in the workspace and I run -clean each time I start CCSv5.

I was able to build and debug when I was working with the C6748 DSP.  This problem only came up with the F28335.

- Bob

Bob,

My experience with this bug has been that it is only certain projects which are subject to it.  I've contacted our CCS experts.  They should be able to tell us if you just need the latest version or if this wll be fixed in the upcoming release.

Kris

The CCS version # mentioned is for a beta version of 5.1 so I would definitely recommend installing the production tools.  CCSv5.1.1 is the latest production tool, 5.2.0 will be out in May.

One thing I would try is to switch your project to explicityly use the newer compiler. It is set to use 5.2.1 but is using 6.0.1.  I would update it in the properties to use 6.0.1.   Right click on the project, select properties.  Select General in the tree and the option will be on the right. 

After doing that go into the build options and make sure that debug information is enabled.  Right click on the project select Properties.  Under C2000 Compiler select Debug Options.  The first drop down box is for debug information.  Select Full symbolic debug.

Regards,

John

Kris,

I appreciate the help.  Here is some more information if it helps.  I installed CCSv5 in its own folder in order to be sure it would not interfere with any previous versions of Code Composer on my PC.  I put it in a folder called "ti_cc5" at the same level as the "ti" folder.  Is there any way that this is causing problems?

I have 4 versions of Code Composer on my computer:  2.2, 3.3, 4.x and 5.1.  All exist in totally different locations.  For example, 4.x is located under the "Program Files" folder.  They have all managed to co-exist up to now.

If I decide to uninstall CCSv5 and re-install it, are there any suggestions to make it go smoothly?  (I don't plan on doing that until I hear something from your CCS experts.)

- Bob

Kris,

Loading the latest production version worked!  I built the project and launched the debugger.  It connected to the XDS510 and I was able to see the source code, set breakpoints, etc.

One thing I was not able to do was to explicitly set the version of compiler as John suggested.  I followed his directions, but after clicking on "properties" and then "C/C++ General" I could not find anything that would let me select the compiler to use.

But it works, and now I can start playing with the different peripherals on the 28335.

Thanks to both of you,

- Bob

Bob,

Great news! Glad to hear we got this working.  I've attached a screenshot showing how to update the compiler version.  This happened to be the first project I had opened.  Let me know if the process doesn't seem to flow the same for you.

Kris

Kris,

This is the page that appears when I select proprties:

If I select C/C++ Build - Settings I can see the compiler version, but it is grayed out and I cannot change it.  I've tried searching the help files to tell me how to select the compiler, but I haven't found any mention of it.

- Bob

There is where to change it in v5.

here i shwere to change it in v4.2

What build is the capture you showed from?  it looks different than mine.  I know there are some issues when importing some of the old non ControlSuite example projects that were originally imported from v3.x which changing this type of setting.   The ControlSuite projects do not have this issue.

John

John,

This is very strange.  The screen I included with my previous post is what shows up when I open the properties for the two C28x projects that I have been working with.  Both are from my DSP2833x_examples_ccsv4 folder.  If I open the project properties for one of the C6000 labs that I did when I took my C6000 Embedded Design Workshop, I get the screen you are showing.

I had no idea that the actual screens you see would be tied to the project.  Note that I imported these projects from the ccsv4 folder; not the older (ccsv3.3) folder.

Is there a source for newer versions of these peripheral examples?  All of these funky tool-related issues are really slowing my development down.

Here is another issue.  I can't open any of the projects directly from the ControlSuite menu.  I think it may be because I loaded CCSv5 into a different directory than the default.  I put it in c:\ti_cc5 instead of in c:\ti.  Is that why the projects won't open?

Thanks,

- Bob

Hi,

I get the same problem when compiling the example projects for TMS320F2812, i.e. DSP281x_v120.

I have added the extracted folder to TI Resource Explorer and imported the project from there.

One thing that I noticed is that the project looks completely different in this example project compared to my normal project. E.g. the General tab is missing as it shows in Johns screen shot. I guess that the example projects are special somehow.

Is there some way to get around this, or do I need an upgraded version of the example source code/scripts?

/ Joakim