Update CW6.0 Project to CW6.1

[v_dave]

Hello All,

OK I just comitted the ultimate developer mistake, I upgraded my dev tools in the middle of my project and now my project is broken.

I am working on a project for the 9S08AW60 microcontroller and using Special Edition CW6.0 everything was fine. 

I also own a full license to CW for DSC56800E and that was recently upgraded to the develpers suite which includes a full license to CW for Microcontrollers.  My project was approaching the 32K limit of Special Edition so I thought might as well take advantage of the new license and upgrade.  So I downloaded the latest CW (6.1) and when I went to install I nticed I only had 1.5GB of space availible on my HD so I uninstalled 6.0 so I would have space for the new version.  All went fine with the uninstall - install process.

Now when I opened my existing project for the first time under CW6.1 I imeediately got an error in my CPU bean that said my interupt vector table was mapped incorrectly to address 0000.  So I looked up the proper location and entered 0xFFC0 as the start of the table (page 70 in the datasheet). 

Now my code generates and compiles without any errors and the application appears to run.  But something is wrong with the memory settings because a few of my variables are getting stepped on by some routine. 

My questions:

Has anyone had an issue with upgrading their project from CW6.0 to CW 6.1? 

Has anyone seen this issue before and what fixed it on your end?

What memory mappings seemed to get changed when upgrading rom CW6.0 to CW6.1?  I did not do anything special with memory in CW6.0 so as far as I know everything was set to defaults so I did not expect any issues in this area.

Anyone have a link to download CW6.0?  This is worst case but might be my only option.

Any tips would be greatly appreciated.

Thanks,

Dave

Message Edited by v_dave on 2008-04-23 11:04 AM

[ProcessorExpert]

Hello Dave,

We are not aware of such issue and we cannot reproduce it. Could you pleas provide your original project for us team to analyse it?

Thank you very much

Processor Expert Support Team
www.processorexpert.com

[v_dave · Accepted solution]

Hello All,

OK I just figured out the problem.  I was lucky that I found an old copy of my project that I had emailed to my colleague (from a couple days before the upgrade).  I opened the .map file and compared it to my upgraded .map file and found that I had made a change to the Stack size, an increase.  Somehow when I upgraded the project the stack size was reset to the default of 128 Bytes.  I increased the stack size to the correct size and now my project works just as it did before.

Lessons to be learned here:

1) Keep track of all the memory map settings.

2) When looking for a backup your Sent folder is always a good place to start looking.

Thanks to anyone who viewed and thought about a solution.

[allawtterb]

---

v_dave wrote:

Lessons to be learned here:

1) Keep track of all the memory map settings.

2) When looking for a backup your Sent folder is always a good place to start looking.

Another lesson, if you have variables getting stepped on a good starting point is to check for a stack overflow.

[bigmac]

Hello Dave,

Presumably, when the project was upgraded to use CW 6.1, it reverted to using the default PRM file.  Had you changed anything else in this file, apart from STACKSIZE?

Regards,

Mac

[v_dave]

Hello bigmac,

The only memory segment I touched was the Stack size.  I just forgot that I did make that change so I didn't think to look there.  I was also a little surprised that moving my project from CW6.0 to CW6.1 had this effect. 

I had started an SR on this issue before I found the problem.  When I reported the solution and pointed out that this was not expected all I got for a response was "Congratulations! You have solved the problem. Should you need to contact us with regard to this message, please see
the notes below."

I was kind of hoping for "Congratulations you have solved the problem.  We will look into the issue of moving a project from 6.0 to 6.1 and the effects it had on your CPU bean." 

Thanks again for the reposnse.