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

CCS PCD used for PIC24. If using PIC16 - any differences?

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



Joined: 17 Jun 2019
Posts: 627
Location: Des Moines, Iowa, USA

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

CCS PCD used for PIC24. If using PIC16 - any differences?
PostPosted: Wed Jul 23, 2025 8:16 am     Reply with quote

We use PIC24 chips and the PCD CCS C Compiler.

Is what I am used to different for PIC16? If I needed to work on a PIC16 design, would PCD be the tool that would be used, or something different?
_________________
Allen C. Huffman, Sub-Etha Software (est. 1990) http://www.subethasoftware.com
Embedded C, Arduino, MSP430, ESP8266/32, BASIC Stamp and PIC24 programmer.
http://www.whywouldyouwanttodothat.com ?

Using: 24FJ256GA106, 24EP256GP202 and 24FJ64GA002.
jeremiah



Joined: 20 Jul 2010
Posts: 1395

View user's profile Send private message

PostPosted: Wed Jul 23, 2025 8:46 am     Reply with quote

It would be a different compiler depending on "which" pic16 you are using (12bit or 14bit). See the diagram here:
https://www.ccsinfo.com/compilers.php

Now if you have PCWHD (vs just plain PCD), you can compile for any PIC CCS supports
allenhuffman



Joined: 17 Jun 2019
Posts: 627
Location: Des Moines, Iowa, USA

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

PostPosted: Wed Jul 23, 2025 9:12 am     Reply with quote

jeremiah wrote:
It would be a different compiler depending on "which" pic16 you are using (12bit or 14bit). See the diagram here:
https://www.ccsinfo.com/compilers.php

Now if you have PCWHD (vs just plain PCD), you can compile for any PIC CCS supports


I suppose my actual question is ... will I know how to use it (same IDE) or is it a completely different thing? If they go with PIC16, and I already know how to use the tools and be productive immediately (Configuration Wizard and such), that's great.

If it's different and has to be learned, they might just go with the free tools from Microchip.
_________________
Allen C. Huffman, Sub-Etha Software (est. 1990) http://www.subethasoftware.com
Embedded C, Arduino, MSP430, ESP8266/32, BASIC Stamp and PIC24 programmer.
http://www.whywouldyouwanttodothat.com ?

Using: 24FJ256GA106, 24EP256GP202 and 24FJ64GA002.
jeremiah



Joined: 20 Jul 2010
Posts: 1395

View user's profile Send private message

PostPosted: Wed Jul 23, 2025 9:32 am     Reply with quote

allenhuffman wrote:

I suppose my actual question is ... will I know how to use it (same IDE) or is it a completely different thing? If they go with PIC16, and I already know how to use the tools and be productive immediately (Configuration Wizard and such), that's great.

If it's different and has to be learned, they might just go with the free tools from Microchip.


I don't know if it helps, but I'm using PCWHD (the IDE) and it is the same IDE for all chips.
dyeatman



Joined: 06 Sep 2003
Posts: 1963
Location: Norman, OK

View user's profile Send private message

PostPosted: Wed Jul 23, 2025 3:24 pm     Reply with quote

I use PCWHD with the CCS IDE and ICDU40.
Switching between 10,12,14, 16, 18, 24 and dspic is virtually seamless for me.
I use it the same for any chip I choose, with minor differences due to the
change in number of bits. (header settings typically, since many of
the lesser series lacks some peripherals in the 24.)
I run two instances of the IDE for multi-core chips
_________________
Google and Forum Search are some of your best tools!!!!
asmallri



Joined: 12 Aug 2004
Posts: 1649
Location: Perth, Australia

View user's profile Send private message Send e-mail Visit poster's website

PostPosted: Wed Jul 23, 2025 6:08 pm     Reply with quote

allenhuffman wrote:
jeremiah wrote:
It would be a different compiler depending on "which" pic16 you are using (12bit or 14bit). See the diagram here:
https://www.ccsinfo.com/compilers.php

Now if you have PCWHD (vs just plain PCD), you can compile for any PIC CCS supports


I suppose my actual question is ... will I know how to use it (same IDE) or is it a completely different thing? If they go with PIC16, and I already know how to use the tools and be productive immediately (Configuration Wizard and such), that's great.

If it's different and has to be learned, they might just go with the free tools from Microchip.


If you already are very familiar with PCD and like the tool chain then you would have to have rocks in your head to go down the completely broken path you are suggesting.
_________________
Regards, Andrew

http://www.brushelectronics.com/software
Home of Ethernet, SD card and Encrypted Serial Bootloaders for PICs!!
Ttelmah



Joined: 11 Mar 2010
Posts: 19909

View user's profile Send private message

PostPosted: Fri Jul 25, 2025 1:26 am     Reply with quote

Think of it being like the difference between driving a Ford [spam] and
a Fiesta. The ride is different because of the different size and weight,
but 95% of the controls are in exactly the same place. Some thins are
missing, and the performance is different, but very similar. Trying to switch
to the MicroChip system is like trying to change to a bus instead.
The biggest things to bear in mind, are the fuse settings, and the
sizes. Keeping it in your head that an 'int' is an int8, and that by default
variables are unsigned, is something you will need to keep reciting to
yourself when working on the smaller chips......
dyeatman



Joined: 06 Sep 2003
Posts: 1963
Location: Norman, OK

View user's profile Send private message

PostPosted: Fri Jul 25, 2025 3:48 am     Reply with quote

Quote:
Keeping it in your head that an 'int' is an int8, and that by default
variables are unsigned, is something you will need to keep reciting to
yourself when working on the smaller chips......


That's why I use int8, uint8, int16, uint16 etc. in all my code,. it is keeps that
from being an issue when switching chips or porting code.
_________________
Google and Forum Search are some of your best tools!!!!
Ttelmah



Joined: 11 Mar 2010
Posts: 19909

View user's profile Send private message

PostPosted: Fri Jul 25, 2025 7:38 am     Reply with quote

Totally agreed. You will see that I recommend using the full names 'by
default'.
However, especially when including old code, or just being a bit 'casual',
it is easy to forget, especially the signed/unsigned part. Sad
asmallri



Joined: 12 Aug 2004
Posts: 1649
Location: Perth, Australia

View user's profile Send private message Send e-mail Visit poster's website

PostPosted: Fri Jul 25, 2025 7:44 am     Reply with quote

Ttelmah wrote:
Think of it being like the difference between driving a Ford [spam] and
a Fiesta. The ride is different because of the different size and weight,
but 95% of the controls are in exactly the same place. Some thins are
missing, and the performance is different, but very similar. Trying to switch
to the MicroChip system is like trying to change to a bus instead.
The biggest things to bear in mind, are the fuse settings, and the
sizes. Keeping it in your head that an 'int' is an int8, and that by default
variables are unsigned, is something you will need to keep reciting to
yourself when working on the smaller chips......


There is also the issue of "what if I want to modify a suppied driver"" to do something different. Pretty easy to do with CCS, a mind boggling complexity with the alterntive due to the very complex harmonized driver library.
_________________
Regards, Andrew

http://www.brushelectronics.com/software
Home of Ethernet, SD card and Encrypted Serial Bootloaders for PICs!!
temtronic



Joined: 01 Jul 2010
Posts: 9547
Location: Greensville,Ontario

View user's profile Send private message

PostPosted: Fri Jul 25, 2025 8:47 am     Reply with quote

ah, but you NEVER modify a supplied driver !
You copy,save as MYdriver, THEN modify MYdriver.
That way you'll always have ORIGINAL driver to fall back on.
dyeatman



Joined: 06 Sep 2003
Posts: 1963
Location: Norman, OK

View user's profile Send private message

PostPosted: Fri Jul 25, 2025 9:13 am     Reply with quote

But also, the CCS drivers usually have the proper integer sizes/types already
so I don't typically have to make any changes to them.
_________________
Google and Forum Search are some of your best tools!!!!
asmallri



Joined: 12 Aug 2004
Posts: 1649
Location: Perth, Australia

View user's profile Send private message Send e-mail Visit poster's website

PostPosted: Fri Jul 25, 2025 7:42 pm     Reply with quote

temtronic wrote:
ah, but you NEVER modify a supplied driver !
You copy,save as MYdriver, THEN modify MYdriver.
That way you'll always have ORIGINAL driver to fall back on.


I completly agree but also to support the other issue of a software update over writing your modified driver which would happen f you did not use the MYdriver method
_________________
Regards, Andrew

http://www.brushelectronics.com/software
Home of Ethernet, SD card and Encrypted Serial Bootloaders for PICs!!
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