How to migrate a code from CCS 3.1 to CCS 4.2.4

Hi Hiram,

have you tried importing instead of a more manual migration?  What if you try a fresh workspace and do a Project->Import Legacy CCSv3.3 Project?   Unfortunately some of these old versions are not in my area of much experience but please let us know if that works better for you.  It may be the better option despite our having seen a few hiccups with the legacy import.

Best Regards,
Lisa

Hi Lisa,

I've already imported my code to CCS4 and it seems is ok. I did that using a C6713 DSK board and XDS510 USB Emulator.

Now I need to move to our custom board, which it uses C6713 QFP package device, when I try to download my code into our board, CCS shows me an error:

I tried to change the target configuration in my project on CCS 4.2.4 in order to use C6713 device in my custom board but I could not be able to do that, I can´t see an C6713 device in the device options.

Could you help me in this issue?

Regards,

Hiram Hernandez

HI Hiram,

would you be willing to send us the ccxml file offline to have a look at?  You can do this in a friend request or conversation.  Also the details of what exact target you are using etc. Some devices the revision may play a role.

Best Regards,
LIsa

Hi Hiram,

thanks for the file.  You are correct, you should not be using the DSK version in the setup.  However, the C6713 is not supported by a pre-made file.  This does not mean not supported, you simply would need to build it manually.

I have attached a .ccxml for you to try/start with.  I zipped the .ccxml ... so give that a try.

This wiki topic will also be good

http://processors.wiki.ti.com/index.php/Target_Configuration_-_Custom_Configurations

For the C6713 it is simple as there is no ice pick or jtag chain etc.  You can simply add your emulator and the C671x CUP in the advanced tab.  You can also look at your v3 configuration details and try to match those.

Please keep us informed how this goes/if it helps.

Best Regards,

Lisa0525.trial.zip

Hi Lisa,

I already used the ccxml file that you sent to me, but I guess I need a gel file for C6713 device, because I used the DSK6713 gel file and I got the same error.

Could you help me about to generetare a custom gel file?

Hi Hiram,

before getting into doing something custom, there is a GEL file for your device in this path on the CCSv5 installation tree.

C:\CCS\5_1_009\ccsv5\ccs_base\emulation\gel

The gel file you want to point to is called DSP621x_671x.gel

Please let us know how that goes.

Best Regards,

Lisa

Lisa,

I did the modification on my target configuration, using the DSP621x_671x.gel file, but it didn't work.

Do you have any idea? CCS showed me the same error.

Regards,
Hiram Hernandez

Hi Hiram,

let me see if I can pull in some colleagues.   Have you compared the settings to those you used in v3?  Ie JTAG settings etc..

Best Regards,
Lisa

Hi Lisa,

In v3.1, we used the DSK board only, and the USB emulator which comes into the board. Now, we want to test our board using the XDS510 USB Emulator to debug our app.

So, I guess the configuration in v3.1 should be different that in v4.2.4, isn't it?

Furthermore, if I use the DSK board then I'm able to download the code into DSP in v4.

Regards,

Hiram Hernandez

Lisa TI said:

Hi Hiram,

have you tried importing instead of a more manual migration?  What if you try a fresh workspace and do a Project->Import Legacy CCSv3.3 Project?   Unfortunately some of these old versions are not in my area of much experience but please let us know if that works better for you.  It may be the better option despite our having seen a few hiccups with the legacy import.

Best Regards,
Lisa

Hi Lisa,

I just did a little change in my code, basically I put a comment and saved it. After that, CCS sent me some errors, I'll attach an image showing these errors.

I guess, when I was downloading the code to DSK board, CCS used the .out file that was genereted in v3.1. And as soon as I made a change and tried to debug my code, CCS tried to make a new .out file.

How can I fix those errors?

Hi Hiram,

it seems like it could be there is an include path not resolving properly.  Please check your path variable, build variables and include paths.  You can compare your includes from v3 in case there is a library reference missing etc. 

Have a look at that.  If anything specific comes up I can then help direct you to where to input some of these under the Project->Properties.

Basically

linked resource paths and variables are under Resource

Paths that need to be included ... are under the compiler and linker options.

Keep us informed.

Best Regards,

Lisa

Hi Hiram,

another thing to double check.  It seems like you never tried you board under either CCS version so I would do some general JTAG debugging as it seems with our discussion we have guided you on the ccxml and configuration in CCS.

You can start checking your JTAG integrity outside of CCS with SDConfigEx.

Once again please keep us informed.

Best Regards,

LIsa

Hi Lisa,

I´ve checked if there was some inconsistency on the include paths from v3.1 to v4.2.4, but I could not find anything.

I'll attach images, first one with v3.1 files in the include folder, and second one image in v4.2. I think all files are ok.

Do you think could be a problem with DSP/BIOS? As I know, In v3.1 we used a DSP/BIOS v4.9 and CCS 4.2.4 uses DSP/BIOS 6.

I've been reading about to convert cdb file to tcf file, so I found a tool "cdb2tcf.exe" in order to do that, I tried to open this tool but I can't use it, when I open it, it was closed immediately.

As far I know CCS 4.2.4 needs DSP/BIOS 6 and the files for v6 are *.cfg, so I guess I must to convert cdb file to cfg file, doesn´t it? But I don't know how to do that, any suggestion?

Regards,

Hiram Hernandez