CCS C Software and Maintenance Offers
FAQFAQ   FAQForum Help   FAQOfficial CCS Support   SearchSearch  RegisterRegister 

ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CCS does not monitor this forum on a regular basis.

Please do not post bug reports on this forum. Send them to CCS Technical Support

old code broken in new compiler version: PIC18F2550 CPUDIV1

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
equack



Joined: 21 Sep 2009
Posts: 21

View user's profile Send private message

old code broken in new compiler version: PIC18F2550 CPUDIV1
PostPosted: Wed Sep 01, 2010 1:14 pm     Reply with quote

Just a heads up:


I discovered the hard way that the old version of the compiler (4.095) defaulted to fuse "CPUDIV1".

The new version of the compiler (4.111) does not.

If you don't specify CPUDIV1 (or some other value) your code will not work. Delay_ms() will take too long and the RS-232 baud rate will be wrong.
It will annoy you and make you curse the compiler upgrade until you figure it out.

Hopefully this post will save someone else the aggravation!

cheers,

-Erik
smanzer



Joined: 14 Sep 2009
Posts: 24
Location: Ontario, Canada

View user's profile Send private message Visit poster's website

Compiler Upgrades
PostPosted: Thu Sep 02, 2010 7:51 am     Reply with quote

Hi Eric,

I have learned that the CCS upgrades do not appear to be properly tested by CCS. They fix one thing, that affects other things. It appears to me that they do not have a proper test proceedure to verify their releases.

4.093 was stable, 4.104 and 4.106 gave memory errors when using MALLOC and RS232 problems while 4.110 looks ok.

My advise to anyone using CCS is to install the updated version in another directory than the one you are currently using. Test and retest your code with the new version. When you are happy, move the new compiler over top the old version so it is in the PICC dir.

I too have wasted many hours "fixing" my code that was not broken.

Overall the CCS compiler is great, and CCS do actively try to improve the product. I guess we all have to put up with the growing pains.

Steve
_________________
"I am always doing that which I can not do, in order that I may learn how to do it."
- Pablo Picasso
armondo_522



Joined: 20 Mar 2010
Posts: 9

View user's profile Send private message

PostPosted: Fri Oct 29, 2010 1:42 pm     Reply with quote

I have never gotten anything after 4.087 to work on existing code.
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group