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

#FUSES and covering the bases.

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



Joined: 24 Jul 2012
Posts: 163

View user's profile Send private message

#FUSES and covering the bases.
PostPosted: Tue May 07, 2019 3:30 pm     Reply with quote

Another thread I was involved in pointed out an error in my FUSES. Ok.....
Is there a comprehensive list of fuse tags somewhere? Yeah, I know, look at the datasheet, but the nomenclature in the datasheets does not always match that in the CCS .H files. For me, it is hard to determine what some of these fuses do and second, which ones I need to disable for safety and to head off odd behavior in the future. I am opening this discussion in hopes that either there is a descriptive database for fuses, or there will be. Seems like the place for this would be in the device's .H file as comments.

18F87K22
CCS 5.064
MPLAB 8.91
dluu13



Joined: 28 Sep 2018
Posts: 395
Location: Toronto, ON

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

PostPosted: Tue May 07, 2019 3:50 pm     Reply with quote

There's that file called fuses.txt that should be in your compiler's install directory.
beaker404



Joined: 24 Jul 2012
Posts: 163

View user's profile Send private message

PostPosted: Tue May 07, 2019 3:57 pm     Reply with quote

Copy that. Good to know.
I figured there was something, just did not know about it.
Ttelmah



Joined: 11 Mar 2010
Posts: 19481

View user's profile Send private message

PostPosted: Wed May 08, 2019 12:24 am     Reply with quote

and on 'covering the bases', I always build a 'header' for each project that
has the processor #include, fuses and clock setup, before anything else.
Temtronic I know does similar thing with a fuses file for each project.
So your main goes:
Code:

#include "prjsetup.h" //defines processor, fuses, clock
//Then PPS
//Then setup RS232. I2C etc.
//then #include drivers etc.

//Then main variables/code


Having the 'configuration' as a separate block, or include like this makes
it much easier to keep things tidy for each project. If I start a new project
with the same chip, just copy this file as the starting point. Smile
beaker404



Joined: 24 Jul 2012
Posts: 163

View user's profile Send private message

PostPosted: Fri May 10, 2019 10:17 am     Reply with quote

good tip, thanks.
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