Debug Crash after importing to 5.1 from 4

Hi,

The Debugging JTAG Connections page may be helpful to solve this issue. Check:

http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

Hope this helps,

Rafael

OK...

My JTAG connects just fine.  It always has, I don't have a connection problem with version 4.  The blackhawk says it's fine.

I think I have two issues here (well, maybe three)

A.  The 4 to 5.1 conversion.  Many of the build settings, as in type of chip, type of emulator...all blown away, needing to be reset.  My target configuration may also need to be adjusted.

B. I created a new workspace for my 5.1 work, so as not to lose my last point of development in 4.  When I imported to a new workspace, even though it's on the same machine, it seems that it lost certain links to files in the project.

C.  The project was initially created by starting with the Renewable Energy Kit and then modifying Renewable_main.c and build configurations to suit my project (TMS320F28035 with Blackhawk USB2000).   

So...I think that I've solved, or at least can figure out A.

B and C are stifling me.  In the project, there are many files in the "Includes" folder.  During the import, the path to all of those files was lost. (see example below)  Further inspection showed that these are files that probably came with the original Renewable Energy Kit Board Specific Software.  I went to document sprugo7a on the TI website to get instructions for downloading that documentation.  I followed the instructions to go to the http://www.ti.com/c2000tools website and choose the "Renewable Energy Kit Board Specific Software" (see page 3 of sprugo7a instructions)   I CANNOT FIND "RENEWABLE ENERGY KIT BOARD SPECIFIC SOFTWARE" on the c2000tools website.

example: C:\renewable_energy_kit\DSP2803x_headers     there are 12 other missing files with a similar path.

Where can I find these files?

Furthermore, does anyone have a checklist of settings for a new or imported files...even a somewhat complete list...of settings that need to be made.  For instance:

If you know your chip type (TMS320F28035)...you'll need to set this in....build configuration, target configuration, etc

If you know your chip type, you'll need a minimum of these header files (fill in the blank) to properly compile/link...

If you know your emulator type...you'll need to set this in (fill in the different spots in the project settings where this matters)

Right now, I have instructions from evaluation boards and kits that are very specific; but they don't give me the broad understanding that I could derive the specifics from.  They also don't give me the broad understanding that would allow me to deal with when things change.  I'm more of a top down learner.  I like to learn the overall way things work together, which will then direct me to take care of selected details. 

Thanks... 

Hi,

I am not necessarily sure what may have happened in A) above, but it seems you figured out most of the details.

Just like you, I could not find the software tools either in the page mentioned, only on this post.

Even still after downloading and installing it, I still couldn't find several dependencies of the project for this development kit. According to this forum post it seems to me the original project for CCSv3.3 has dependencies on a "baseline software package" that may be now called "C/C++ Header Files and Peripheral Examples" (as shown here). These files have a different directory structure as expected by the original CCSv3.3. project, therefore I am not 100% sure if that is the correct way to go.

In this case, since I am not an expert on the software package itself I will try to get some help from someone from the C2000 team. This way you will get help faster and more precise.

Sorry for not being of much help,

Rafael

Chris,

The TMDSENRGYKIT is beginning it's end of life process.   However, the link to the TMDSENRGYKIT was NOT supposed to go away yet, so we're in the process of re-putting the links on the site.  It may be a while before this happens.

To get all material for the TMDSENRGYKIT kit and get it fully functioning you will need:

• The board specific software for the TMDSENRGYKIT which contains the documenation, CCS3.3 projects, etc

• http://www.ti.com/lit/zip/sprc898

• The "baseline" software package (which contains all the underlying header files and etc)

• http://www.ti.com/lit/zip/sprc675

FYI, the reason this kit is going obsolete is that we are currently in the process of developing a new renewable energy kit which will replace the TMDSENRGYKIT.  However, the current TMDSENRGYKIT should show the advantages and features of the C2000 device in a renewable system .


Thank you,
Brett

CCS "import" Menu Item is hardly usable.

Since TI made a really bad project architecure, to import a project is very complicated. And the CCS can not automatically do it all.

My suggestion is create a new workspace and moving the files and configurations one by one by your self

Chris,

Thank you for reporting your conclusions. Although the original question refers to the connection troubles, unfortunately your second reply ended up throwing me off as it referenced possible project import issues.

The explanation for the connection issue is that the "free limited license" (the most probable version you were using as CCS does not allow using the evaluation license again after expiring) does not allow connecting to emulators other than the ones embedded into development boards or the XDS100. In this case, the details about the license in your last post explain why the Blackhawk emulator could not connect in v5 (free limited license), only in v4 (fully licensed).

Regarding the project import itself, it worked just fine when I downloaded the complete software packages shown by Brett. A few warnings were shown by the fact the original project has some invalid include directories (..\include, for example). Also, at the post-build stage, errors were thrown by some scripts (.bat files) that point to *.lkf files that are not used by CCS anymore. Apart from these details that are intrinsic to the original project, no problems were observed.

Best regards,

Rafael