Hello,
My company is recently migrating from CCS2.2 to CCS 3.1. I'm opening
the CCS 2.2 projects in CCS 3.1, lettting CCS 3.1 convert the CDB file and then
saving the project.
One of the projects I migrated is not working. When the project is compiled
using 3.1 The behavior is like that of an errant pointer, we've debugged
with an emulator and watched the execution "go out into the woods". When the
original CCS 2.2 project is compiled in CCS 2.2 it works just fine.
All the source files, linker command files, libraries are the same. Nothing has
changed except for the fact that the project CDB file has been converted to CCS
3.1. I compared the CCS 2.2 CDB file and the CCS 3.1 CDB file and the settings
are the same.
I know that CCS 3.1 has been out for a while and that my company is behind the
curve on migrating to CCS 3.1 Are there common or known issues that others have
run into during their migration to CCS 3.1? I'm hoping someone has
experienced this before and can give me an idea where to start looking. Right
now I'm not sure where to look to even start debugging this.
CCS2.2 to CCS3.1 Migration Problems, Compiled Codes Run Differently
Started by ●November 11, 2008
Reply by ●November 11, 20082008-11-11
We are in somewhat of the same situation. Using CCS 2.2 and CCS 3.3 doesn't
seem to work the same. Unfortunately we haven't solved the issue either.
Good luck to the both of us !
- Andrew
----- Original Message ----
From: "d...@thalescomminc.com"
To: c...
Sent: Monday, November 10, 2008 4:26:39 PM
Subject: [code-comp] CCS2.2 to CCS3.1 Migration Problems, Compiled Codes Run Differently
Hello,
My company is recently migrating from CCS2.2 to CCS 3.1. I'm opening the CCS 2.2 projects in CCS 3.1, lettting CCS 3.1 convert the CDB file and then saving the project.
One of the projects I migrated is not working. When the project is compiled using 3.1 The behavior is like that of an errant pointer, we've debugged with an emulator and watched the execution "go out into the woods". When the original CCS 2.2 project is compiled in CCS 2.2 it works just fine.
All the source files, linker command files, libraries are the same. Nothing has changed except for the fact that the project CDB file has been converted to CCS 3.1. I compared the CCS 2.2 CDB file and the CCS 3.1 CDB file and the settings are the same.
I know that CCS 3.1 has been out for a while and that my company is behind the curve on migrating to CCS 3.1 Are there common or known issues that others have run into during their migration to CCS 3.1? I'm hoping someone has experienced this before and can give me an idea where to start looking. Right now I'm not sure where to look to even start debugging this.
Good luck to the both of us !
- Andrew
----- Original Message ----
From: "d...@thalescomminc.com"
To: c...
Sent: Monday, November 10, 2008 4:26:39 PM
Subject: [code-comp] CCS2.2 to CCS3.1 Migration Problems, Compiled Codes Run Differently
Hello,
My company is recently migrating from CCS2.2 to CCS 3.1. I'm opening the CCS 2.2 projects in CCS 3.1, lettting CCS 3.1 convert the CDB file and then saving the project.
One of the projects I migrated is not working. When the project is compiled using 3.1 The behavior is like that of an errant pointer, we've debugged with an emulator and watched the execution "go out into the woods". When the original CCS 2.2 project is compiled in CCS 2.2 it works just fine.
All the source files, linker command files, libraries are the same. Nothing has changed except for the fact that the project CDB file has been converted to CCS 3.1. I compared the CCS 2.2 CDB file and the CCS 3.1 CDB file and the settings are the same.
I know that CCS 3.1 has been out for a while and that my company is behind the curve on migrating to CCS 3.1 Are there common or known issues that others have run into during their migration to CCS 3.1? I'm hoping someone has experienced this before and can give me an idea where to start looking. Right now I'm not sure where to look to even start debugging this.
