Sonsivri

Here:

Many thanks ! Works perfect with old licence files ! :-)

Old Keygen work fine.

If someone doesn't have the old license files then they can be download the files from the attached file.
Just copy and paste in the default installation directory.

Folks, check the posts in the CCS 4 thread if you need keys. I know that alichan's link in post #71 is still working.

http://www.sonsivri.to/forum/index.php?topic=33138.msg147072#msg147072

Probably others are too.

New version: 5.008

See attachment to download CCS 5

For those having problems with mega.co.nz, here's another alternative.

Thanks duende_azul...

Version 5.009.  :o

(see attach file)

It seems that CCS is going to take a daily version.  ;D

It wouldn't be CCS otherwise.

you will be attacked by CCS lovers, be careful ;D

The IDE in 5.009 is a bit quirky......issues with resizing and getting bottom left/right corners win7 64 pro....maybe fixed in 5.010

Versión 5.010

  ;)

The IDE has been crap since day 0, delphi components they are using are very bad. I remember they use TMS components which cause this behavior.. add to it bad implementation..

@metal,

apart from that you like it  - right ?  ;D

I just use 12,16 and 18  PICs but want to switch to 24s.

Is it any good for this line of products?

Thanks.


And as stated before:
It wouldn't be CCS if they don't make daily updates.

TBH, I don't even use it :- )
sometimes I have to use it to compile existing codes by others.

Yes it works with the 24's.
Some issues reported with the CCS debug hardware (ex. ICD-U64) with clock speed above 100mhz. Some 24's can run at 140 Mhz. The ICD-U64 can upload( program) code that runs at 140Mhz it just can't run the same code in debug mode (many  PIC's have have debug capabilities...peek at registers display ram etc).
An aside
Some are adverse to CCS rapid versioning.
 Craftsmen and women don't blame their tools. They do choose the tools for the job. Many like their tools sharpened daily others like them blunt so they don't get cut.
CCS sharpens the tools weekly if not daily. Anyway some would rather accept imperfect compilers rather than wait months or years for a new version hoping the delay will lead to better results.  Its always a choice.

That's good to hear gan_canny.

I think I'll migrate one PIC18F4431 PPWM project to a PIC24FJ16MC101.  I've seen the device supported and looks like it does have a MC101 and MC102.

Compiled some old code with the setup_power_pwm and some #defines were modified for the PIC18F4431 (complementary or something).

I don't use ICD-U64 or CCS IDE, I use PICKIT3 and MPLAB; haven't gotten more than 40 MHZ so this 100MHZ won't be a problem.


I agree with your statement, whether CCS has a bad compiler or not, we use it, so it must be good (at least for us).


Waiting for 6.000    :P

Following macro not works on CCS 5.008

#define bit_toggle(var,bit) ((var&(1<<bit))!=0) ? (var &= ~(1<<bit)) : (var |= (1<<bit))

However it perfectly works on CCS 4.xxx

is anything is wrong ?

I don't know why that doesn't work but you can use a simpler and faster macro for bit toggling like the one below:

Some when given tools still want to do their own tool making. Sometimes it's for portability reasons other times it's just being stubborn.
Now there is always the KISS ( Keep it simple stupid) method with bit_set and bit_clear or even  ( less of a KISS)  a bit structure and a byte overlayed by a union. Anyway a purist coder's ego will often cause them to use the least obvious way. ( Job insecurity perhaps).

Seriously?

Hard to imaging why there are any C holdouts!

mainly it is portability. bit_set and bit_clr are crap.
for bit_set
PORTx |= (1 << bit)
and bit_clr
PORTx &= ~(1 << bit)

in localcrack's case, it is keep it strictly stupid, been sailing in dark oceans since CCS 4.xxx, imagine... I am afraid he will now ask about XOR logic:
https://en.wikipedia.org/wiki/Exclusive_or

Btw I realized there is no semicolon [;] at the end of the macro, you might be missing it when you are using the macro which may also be the reason why it doesn't work.

can some one please post a non mega.co.nz link for ver 5.010
hock

Never ending history  :P

Version 5.011

its a journey, not a destination

New version 5.012

Hello All,

Could someone check an issue for me?  choose one of the default colors in the editor properties which has a dark background -- Classic or Twilight.
Then load a file into the editor and right click its tab.  Choose New Edit Window.  In the new window, are the colors in tact? or are they infused with white background?
I am asking to see if it is a true bug or an issue with my PC.
Thanks!

Same here - I get a mostly white background in the new edit window, with some bits in black. Bug!

i am not able to use ver 5.011 and 5.012 with the keygen. i get the message that the license file is currept.
has some one else fased the same issue?

hock

I've never used a keygen, just copied the license files that I've had for years. Same ones as somewhere above in the thread probably.

However, I've just tried one of the keygens I have downloaded to generate new license files. It seemed to work for 5.012. No complaints about the files, and the 'about' box showed CCS licensed as expected. That was with a clean install on Windows XP SP3 if it makes any difference.

The keygen that I tried is called SCG-PCWHD-keygen and it is 10kB.

i am using the same one, it was uploaded in ccs 4 at post 71. when i try to pass the new license file after install it give erroe. it use to work fine for up to ver 5.010. now it is not working. let me try a fresh install.

mplab complains about a dll erro and exits.

this is the error message from mplab ide 8.92
works fine with ver 5.010
Error 44 "##################.c" Line 1(1,1): Internal Error - Contact CCS  PR-CODE ##############
hock

Has a solution been found for the license file issue under 5.012? I am having the same problem, using license files I have had for a long time.  Running the keygen yields the same results.

 Version 5.013 has been released and fixes a  problem with printf disabling interrupts on some parts.

New bugs update.  :P

CCS 5.013

hi

if someone here working the version 5 of pcwhd in the mpabx environment please share with us how to do that. In my place the official mpabx plugin make nothing.

regards
mitsos

For me is working;
Simply create project with CCS wizard, create project with Mplabx wizard (sure that use CCS plugin) and than add Your C File (from CCS) to Source file into mplabx project
than compile: all ok (also proteus vsm)....

to mitsos
Please install MPLABX as well as CCS in folders without space. go to MPLABX > tools> plugins> updates look for ccs c compiler. select and install
you must be connected to net.
now ccs is integrated with your MPLABX

please let me know if it works for you. working for me.

hi

I confirm that hock, share with us the solution to integrate successfully the ccs compiler to mplabx.

regards
mitsos

the first result in google search for ccs 5 mplabx: http://www.ccsinfo.com/pdfs/mplabx_ccs_tutorial.pdf

and I remember this one worked for me...

CCS 5.015

Has anyone else got the RapidUSB prototyping tool from CCS? I picked one up for $20 but I can't get it to program - the manual says to look for "RapidUSB Loader" under program, but all I get are E3 USB, Bootloader, and ICD.

Any chance of an update to the latest version  5.017 ?

Here:
CCS 5.017

hi duende_azul,

can you share the password of the RAR file? :)

Thnx

hi i try the default forum password but i dos not work :( :(
what is the correct password??

Sorry guys  :(...  

new link without password...

In case anyone's wondering - here's what I did to get my RapidUSB working.
1) Go to CCS->Options->IDE->Tools
2) Click "Add"
3) Enter the following:
      i) Name: RapidUSB Loader
     ii) Usage: Program Button
    iii) Command: "C:\Program Files (x86)\PICC\siow.exe" "BAUD=300" "+DTR" "+TERM" "DOWNLOAD=%H"
4) Press "Apply"
5) In SIOW, ensure that the last selected COM port is your RapidUSB stick
6) Compile, program, and unplug/replug the RapidUSB. Your program will start running!

Hope this helps someone!

CCS 5.018   ;D

CCS 5.019 .... never ending story  ;D

http://www.ddlstorage.com/sbnrots1z08h/pcwhdupd5019.rar.htm

can you provide a mirror? the domain is blocked in my country :)

thnx

If no one is having any trouble with Mega I would suggest sticking to it.
Tested links to older versions and they are still around, and the download speed is great.

Here are 5 mirrors.

5.020  ;D

https://mega.co.nz/#!shAWAILC!4GTpFyhLfwN1XOUyWBBsR3rlXfVAFJ7HqfClRvbWJCg

5.021 is here

https://mega.co.nz/#!M5RlQI6b!ztJrypzwbNeCyNI2NblJqCOBb_Kc52QNNud4KhwknMA

Look in post #4 of this thread: http://www.sonsivri.to/forum/index.php?topic=52924.msg152561#msg152561

I used attached keygen (from v4) and all worked fine.

I don't like the new ribbon used instead classic menus (well you can change it in many software but not all, anyway i dont like these defaults). I'd say i hate the ribbon. ;D

CCS 5.023

Is it v5.013 or, probably, v5.023?

 Is a 5.023.

5.024 it's here  ;)

See attached file for link

link in txt file please..

CCS 5.025

PCWHDupd 5.026 here!   :)

See attached file for link

Hi.

The link is dead.
 :'(

Rafael

So I was nice enough to warn you to post and this is how you repay me , your idea of a first post in 2 years after being warned and mine are not the same so I guess you didn't understand you were getting the boot if you didn't shape up I just didn't think the boot was coming out the same day

New link for 5.026

Link to 5.026 at a different site (requested)

PCWHDupd 5.027 here!   Smiley

See attached file for link

PCWHDupd 5.030 here!    :)

See attached file for link

Sorry, can you share PCWHDupd 5.030 to the different site? I have some problems with downloading, site is blocked in my country.

Test the google  DSN
8.8.8.8
8.8.4.4

Try this

Hi, is there any guide of CCS C changes between major 3->4->5 Compiler generations?
Especially, changes of the syntax of their specific CCS "embedded" functions so people can easily migrate code samples from 3 and 4.

Here is a list of updates since V4.001 if that helps. There are a couple of details missing from early V4, but I think it is complete from V4.024 onwards.

The biggest change I saw was going from v4.xx to v5.xx -- CCS left their traditional UI and went to a ribbon UI. A lot of people didn't like the new UI, so they stuck with v4.xx. You can see the latest v5 release notes here (http://www.ccsinfo.com/devices.php?page=versioninfo), but it doesn't cover anything v4 and prior.

Hi All, a small gift for all of you. Below the download link for version 5.034.

I also decided to write my own keygen (included in rar package). With this keygen you will be able to specify (if you have one) also the PCWHD reference number.
In the license type you can specify if you want to generate PCWHD or SXC keyfiles.

Merry Christmas to all of you!

what a nice Xmas gift.

many thanks

Not my intention to spoil the Christmas gift.

But i though we should all know the errors on this version(5.034) seems important for 16F users:
 
    5.035  A delay_us() problem in 5.034 where it takes more ROM than needed is fixed
    5.035  A RAM allocation problem with PIC16 parts that use interrupts and 32 bit math is fixed

In detail: http://www.ccsinfo.com/devices.php?page=versioninfo (http://www.ccsinfo.com/devices.php?page=versioninfo)

Uh, very bad  :o
Anyway no problem, below the link to version 5.035 + Keygen  :D

With ccs THE HITS JUST KEEP ON COMING

Below problems with 5.035 fixed with 5.036

 5.036  A problem with the IDE finding hex files in alternate output directories is fixed
 5.036  A problem with very large delays on chips with slow clocks is fixed
 5.036  Various IDE tweaks

version 5.036 + Keygen, link below  ;)

Hi, I was not able to run the Keygen. There was just no message... Tried to open it with admin rights as well as in compatibility mode but it didn't work.
PS. I'm using Windows 7 Ultimate edition.
Any help would be appreciated!
Thanks!

check your download, you should have two files, the kgen is 796kb, it works ok.

On Windows 7 Ultimate x64 keygen also doesn't work.
But on Win XP it works fine. So, just copied keyfiles from Win XP to Win 7.

On Win7 64 Professional keygen work perfect  8)

The keygen works, at least on Win7 x64. However, Nod32 detects Win32/Packed.MoleboxVS.N, but I supose it is a false positive because I used it and my computer is just fine. Thank you very much for the upload.

Hi Guys, I think some compatibility issues with MoleBox, used to pack the keygen executable.
Below the link to download unpacked keygen, sure that will run just fine  ;) And no more false positive!

Thanks cjack! It's working now in 7 Ultimate x64.

 Update on updates:

 yet another update for CCS 5.036:

 5.037  The PIC24 printf() %w no longer forces the leading zeros
 5.037  Extra trailing commas in initializers now generate a warning
 5.037  Some issues with pre-processor continuation lines (\) are now fixed
 5.037  Optimization bugs dealing with some ROM pointers and clear_interrupts(INT_RB) are fixed
 5.037  The new dsPIC33EV parts have been added

CCS C 5.036 Download Link Work Fine.
Thanks

Last versión: 5.037

If using version 5.037 please note the below problems:

5.038  A problem with clear_interrupts() on some interrupts is fixed

more fixes..

5.039  A problem with clear_interrupts() on some PIC24 interrupts is fixed

Even more fixes...

 5.040  An underserved warning about a #define blocking a C ID is fixed
 5.040  Memory allocation issues from 5.039 are fixed
 5.040  A bug with bit arrays indexed with constants inside structures is fixed

Please post ccs c 5.040 or 5.039 download link.

Hi, I cannot see the attachemnt.. could you please post the link?

#94 has link for 5.037
#90 has link for KG
There has been no posts for version above 5.037 

Version 5.040..  new bugs and more fun  ;)

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.041

Recent changes include:
5.041  An access violation for some users starting the PIC24 Wizard is fixed
5.041  A problem with %w where if the digit after the . was 0 it did not output on the PIC24 is fixed
5.041  Syntax errors that should have appeared for poorly formed bit_test() calls now appear
5.041  A bug is fixed that occurred with packed structures inside unpacked structures accessed with ->
5.041  Some issues with bit arrays inside non-RAM structures is fixed
5.041  An error for two RS232 ports without stream names is removed


Updated:  PIC12F1612
Updated:  PIC16F1613
New:      PIC16F1614
New:      PIC16F1615
New:      PIC16F1618
New:      PIC16F1619

I would like to add to that list:

5.042  An error 103 on Win7/8 computers with full access control enabled is fixed

New Version currently: 5.042

Wow, CCS released a new version in a few days...

http://www.ccsinfo.com/devices.php?page=versioninfo

lol

The version I was using is 5.012 !!!

Many updates!!!    ;)

I guess the only positive is that all software has bugs, and at least CCS are quick to issues updates.
I see lots of complaints on the Mikro site criticising  no updates for new PICs etc etc.

CCS should do more testing though

Rapid versioning often is the best of both worlds. The user can save off a trusted version at any time but if the user suspects a defect in the trusted version there is always  a newer version available that might fix the issue. Some compilers are rarely updated so if there is an issue months may go by before it is resolved.
Anyway some compiler writers sharpen their tools every day, others twice yearly, so the tool is sometimes blunt and won't cut. A sharp tool does cut but care is needed to avoid a bleeding edge.

Although I am using an older version, it's really great to see that has updates.

Nothing is 100% sure!!! However, they work for it!!!

And this is important!!!

 ;D

It's good to see that they update CCS frequently, but I think that they should test their software more deeply before releasing new versions. As a student, I have developed my project under an older version and I can't complain about it because I didn't pay for it. However, once I get a job and I have to make the decision  of buying a compiler, I have doubts about whether CCS is a trustable one or not.

It is good that they seem to create versions that support newer chips quickly. But . . . .

The quality of their code base must truly be terrible. It is probably written by one programmer that has created a mess and does not know how to fix it properly.

The types of bugs that keep getting fixed mean that the code is certainly poorly tested. I have managed programmers in the past that just had no idea of how to create a quality product. One guy would consider the code complete if it worked for one test case. Once he flagged a few hundred lines of code as complete, I could always find at least 10 bugs by simply providing test data that was not well-formed. i.e. Try to add something that was already there, or maybe add to the beginning or end of the data, or add some data with an invalid field. He would never code or test for those sort of edge conditions. Before I came along, he would ship that sort of code out to customers. After I left, he continued doing that sort of thing and the company is now pretty much bankrupt, just supporting one or two remaining customers, but not making any money at it.

I will give CCS credit though in that they have a difficult product to test. You can't just create a set of test cases and do automated testing. To properly test that code, you need to load it into a PIC and test it. But that often needs specialized hardware to test each function. The other thing they have to deal with is the huge number of PICs that Microchip produces. It would be pretty much impossible to have a hardware test setup for every feature of every PIC.

Some companies solve the rapid release issues by creating beta and production releases. in theory, the production releases come out less often and have been more fully tested, while the beta releases have only passed unit testing, and not full integration testing. the problem here is that CCS does not even do a good job of unit testing. There have been several bugs fixed in CCS 5 over the last year of so where the bug was reported as something like, "fixed an issue introduced with V5.xxx", where xxx was just released a couple of days ago.

Overall, I need to really trust a compiler. When I have a hard to find bug, I need to now that it is my code, not the compiler that had an issue. Many moons ago (in the previous century), when I wrote tens of thousands of lines of code under a Borland C++ compiler running under OS2, I did find a bug in the compiler generated code. I spent over a week looking for it in my code (it was a large complex system and the bug intermittently caused a crash in seemingly random places). Working with what you know is a buggy product makes that process much more difficult. You need to be able to trust your tools - especially with a compiler.

   The CCS compiler, from version 5.037 onwards, the PcdWiz.exe for PIC24 not work,
   giving error when running.   :o

CCS 5.042

Link fixed .. forgive my mistake.

Thank you very much but I think you uploaded CCS 5.040 again, instead of 5.042.

The error continues

You're right .. it's fixed.

link dead

Try this link...

Link mega pcwhdupd+PcdWiz+CCSUniversalKeygen  ;)

Copy and paste the whole link, not just the underscored bit.

Link and Software are OK  :D

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.043

Recent changes include:
5.043  Forward referencing a 'rom' data item with & in an initializer is now accepted
5.043  The default fuse settings have changed back to the way they were in older compilers
5.043  Fixed a type conversion problem between float and int in some relational expressions on a dsPIC
5.043  The address used for & on large "rom" structures when passed to a  built in function on PIC24 is fixed
5.043  setup_wdt() in newer 12 bit parts no longer glitches the pull-ups
5.043  A number of updates have been made for the new EV chips


Updated:  PIC16F1784
Updated:  PIC16F1786
Updated:  PIC16F1787
Updated:  PIC16F1788
Updated:  PIC16F1789

Last version:

CCS 5.043

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.044

Recent changes include:
5.044  Fixed a bug in PCD in subtraction of 32 bit numbers in complex expresions involving the -> operator
5.044  A warning in string.h is now gone
5.044  Corrected a formatting issue in %W (%LU, %LD should not have been affected)
5.044  A file signing issue has been resolved


Updated:  PIC16F648A
Updated:  PIC18F65J94

Version 5.044

New version in five minutes...  :P

5.045 Another version and some more fixes from CCS

 5.045  #locate now issues a warning if you locate a variable on top of another
 5.045  A PIC24 problem with the < and > operators on floats with interrupts is fixed
 5.045  A problem with multiple compilation units and some static variables not being zeroed is fixed
 5.045  A warning in string.h has now been eliminated
 5.045  A bug allocating multiple odd sized rom structures in PIC24 is fixed


Updated:  PIC12F1571
Updated:  PIC12F1572
New:      PIC16F1574
New:      PIC16F1575
New:      PIC16F1578
New:      PIC16F1579
New:      PIC16F1764
New:      PIC16F1765
New:      PIC16F1768
New:      PIC16F1769

Version 5.045

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.046

Recent changes include:
5.046  Fixed an problem with -> where the target was a bit field of another structure on PCM parts
5.046  An IDE issue with error files kept outside the project directory is fixed
5.046  A wrong checksum in "#ID checksum" when using #fill_rom is fixed
5.046  A PIC24 problem with oversized printf widths on %LU and %LD is fixed
5.046  Support for auto clock tuning is added for chips that have this feature
5.046  A #USE RS232 bug is fixed when buffers larger than 256 are specified


Updated:  PIC16F1614
Updated:  PIC16F1615
Updated:  PIC16F1618
Updated:  PIC16F1619

CCS 5.046
Last version.. again..  :P

------------------------------------------------------------------------------------------------
                      CUSTOM COMPUTER SERVICES, INC.
------------------------------------------------------------------------------------------------

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.047

Recent changes include:
5.047  A bug converting some floating point numbers just below zero to an integer is fixed.
5.047  A bug with 32 bit enum's is fixed
5.047  A problem with the 1705 comparator is fixed
5.047  IDE mouse-over improved for structures and ROM variables


New:      PIC16C99
Updated:  PIC16F1503

5.047

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.048

Recent changes include:
5.048  Compiler now does type checking on EXTERNs
5.048  A compiler IDE hang problem with some complex structures is fixed

Version 5.048

CURRENT SOFTWARE VERSIONS

 Version 5.049
 
 
RECENT CHANGES

 5.049  Added support for the new and different 24 bit GS chips and the 16F183xx chips
 5.049  A problem with PIC24 function pointers inside a structure in large memory spaces is fixed
 5.049  Debugger issue with some floating point numbers is fixed
 5.049  Fixed a bug involving signed ints in a switch statement
 5.049  An inline assembly error when using an indirect goto is fixed
 5.049  Debugger now shows a full 32 bit enum as it should

Updated:  PIC12F1840
Updated:  PIC12LF1840T39A
Updated:  PIC12LF1840T48A
Updated:  PIC16F1619
New:      PIC16F18313
New:      PIC16F18323
New:      PIC16F18324
New:      PIC16F18325
New:      PIC16F18344
New:      PIC16F18345
Updated:  PIC18F85J94

Can anyone share the link for 5.049?

Last version: 5.049

CURRENT SOFTWARE VERSIONS

Version 5.050
 
RECENT CHANGES

 5.050  Support for the new 4x chips is in
 5.050  An incorrect warning concerning enum assignments is removed
 5.050  A linker bug that sometimes combined global variables with the same name is fixed
 5.050  Added USB and TCP/IP wizards for 24 bit parts
 5.050  Fixed a bug in #USE PWM for parts with more than 6 remappable OC pins
 5.050  Added a PLL_WAIT option to #use delay to wait for the PLL to start up
 5.050  Fixed a bug in tx_buffer_available() where the wrong count was returned
 5.050  Fixed a bug when negative number were used with %W on 24 bit parts
 5.050  Added a feature to use OSCTUNE on 24 bit parts to get the requested clock speed


Updated:  PIC16F1705
Updated:  PIC16F1782
Updated:  PIC16F1783

 :-\  last version...

CURRENT SOFTWARE VERSIONS

Version 5.051
 
RECENT CHANGES
A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.051

Recent changes include:
5.051  A linker bug affecting multiple compilation unit builds is fixed
5.051  A segmentation fault for some Linux compiles is fixed
5.051  An optimization error involving << with mixed byte and dword operands is fixed
5.051  Fixed a syntax error with spi_write4() and spi_read4() functions for 24 bit parts
5.051  Fixed a syntax error with #pin_select for some PIC18 devices
5.051  Fixed a bug when #opt compress is used on some programs
5.051  Fixed an issue with #use pwm and MCP1911x devices
5.051  The 24 bit Wizard now has a MODBUS configuration page


Updated:  PIC16F1503

------------------------------------------------------------------------------------------------

Finally... new last versión...    ::)   5.051

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.052

Recent changes include:
5.052  Variable length argument functions now allow a single parameter
5.052  A bug with some 16 bit additions done in a call to spi_write() has been fixed
5.052  A problem with the bit order in lcd_symbol() when used with 16 bit segments is fixed


Updated:  PIC16F505
Updated:  PIC16F1829
Updated:  PIC18F25K80
Updated:  PIC18F26K80
Updated:  PIC18F45K80
Updated:  PIC18F46K80
Updated:  PIC18F65K80
Updated:  PIC18F65J94
Updated:  PIC18F66K80
Updated:  PIC18F66J94
Updated:  PIC18F66J99
Updated:  PIC18F67J94
Updated:  PIC18F85J94
Updated:  PIC18F86J94
Updated:  PIC18F86J99
Updated:  PIC18F87J94
Updated:  PIC18F95J94
Updated:  PIC18F96J94
Updated:  PIC18F96J99
Updated:  PIC18F97J94
Updated:  PIC16F1773
Updated:  PIC16F1776

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 5.052 <- should be 5.053?

Recent changes include:
5.053  A corrupted device database in the V5.052 release is fixed

Why you don't just give the official changelog URL link instead of posting such stupid informative posts?
http://www.ccsinfo.com/devices.php?page=versioninfo

New year, new version... 5.053

NEW VERSION OUT -  Version 5.054

http://www.ccsinfo.com/devices.php?page=versioninfo (http://www.ccsinfo.com/devices.php?page=versioninfo)

NEW VERSION OUT -  Version 5.055

http://www.ccsinfo.com/devices.php?page=versioninfo (http://www.ccsinfo.com/devices.php?page=versioninfo)

New Version out 5.056

http://www.ccsinfo.com/devices.php?page=versioninfo (http://www.ccsinfo.com/devices.php?page=versioninfo)

Version 5.056  ;)

anyone got a link that doesnt require login/signup/generalaccount rubbish

same last file in mega, 5.056

you do run the risk of being muted for these useless posts.

I also want ( need) the update, but pickit2 has a wrath.

I always wait for a kind soul to oblige

I have no power in this topic, but as the old man says, "I hate such posts".
I also know anyone who uses software knows when there is an update, There no need to advertise such updates.

I find these posts as to the status of the software useful. What isn't useful are the multiple posts saying it isn't useful.
Ooops I may have just added to the useless chatter about useless posts.
 Hope I don't get muted for a useless post commenting on useless posts

New Version out 5.057

http://www.ccsinfo.com/devices.php?page=versioninfo (http://www.ccsinfo.com/devices.php?page=versioninfo)

 :-X :-X ;D

CCSC PCWHD New version out 5.058

http://www.ccsinfo.com/devices.php?page=versioninfo

 5.058  A debugger problem with some 24 bit parts is fixed.
 5.058  Some device database problems with certain parts are fixed
 5.058  Some warning problems are cleaned up
 5.058  New RS232_BUFFER_ERRORS variable for use when using buffered RS232
 5.058  Second ADC module now fully supported for the 16F18855
 5.058  #use pwm and setup_vref() functions fixed for some chips

@pickit2

get yer gun out !!!

did you miss the post #154 ?

Version 5.058  .... enjoy ;)

Version 5.059  :o

Version 5.061

Versión 5.062.

Version 5.063

last version again...


Fixed... Sorry guys...

Best regards sincerely, but in the archive is stored version 5.063.
... OK, now is fixed!

The new link above is for version 5.064!!!

For me, the version 5.063  has a number of bugs, in projects that already compiled in previous versions, this release happen several problems, which has been fixed in the new version.
At least that was tested so far...

Version 5.065  ;)

Version 5.066

Version 5.069

Version 5.070

Version 5.071

Version 5.072

it looks like v 5073 has some problems, so 5074 should be along real soon  ;D

New bugs update...  :D

bugs Versión 5.073

hi
any expectation about 074 availability here at sonsivri
best regards
juan

Has anyone the 5.075 version?

There is no version 5.075, still version 5.074.

http://www.ccsinfo.com/devices.php?page=versioninfo

Perhaps GabGol got the version from dream.

Version 5.074  ;)

Version 5.075   ;D

Version 5.076

man... 8 pages of v5.0xx... amazing indeed... I am looking at the first page's date, this is when I was newly married :D
since then I and this compiler got ***e.d up :D

Same here, but I was two and a half years earlier on the wife-husband thing

 ;D

Version 5.077   :P

 ;D This time, CCS released the next one (5.078) too quickly after 77. On change log they use word "some" ... No good signs.
Let see ...

Version 5.078  ;D

The above link is working. Found one more link for 5.078

Many updates.

Could anyone explain, how do I view log update for the lastest version?

http://www.ccsinfo.com/devices.php?page=versioninfo

Hi CCS C 5.xxx users,

Can someone suggest which version is stable?

Regards

they are all stable.

choose the  latest one v5.078

Version 5.079   :D

Hi, I'm searching for the CCS compiler v5.054...can anyone help me ?  thanks in advance

v5.054 seems not to have been linked.
It seem not to be even if looking for.
Though it is regrettable....

I am waiting for a v5.080. :)

lol
GabGol was warned to start posting and that was his post.

Version 5.0.80

hmm...
5.082 went out without 5.081 going out.

5.081 did go out, so it looks like you are just asking for the latest 5.082 since '81 wasnt posted here.

Are you sure that v5.081 has not left?
Merry Christmas!

Zero point one 0.01 updates are often pulled due to errors.
there are a few members in here on a mute as all their posts are asking for a 0,01
update to be patched, without testing if original patch was still working.

@pickit2

The CCS updates are full installation installs, NOT patch updates.
They only require the licence crg files.

The poster from my point of view was asking for a new set of install files.

I would like them also, usually because they include bug fixes, and new micro support.

I never ask for newer updates because that is begging, and verbotten on this site.

If a poster wants to supply thats fine, and there are also many thanks to the person who does the post.

Quick question:
Is the 45 days Demo on the vendor's website always the latest version?

Note: I just read that it is limited in examples and chips supported... :( but I would like to know the answer to that question anyways.

@ kreutz:  Why you don't ask the vendor? Actually only they should know. Also this question is kind of off-topic. If you need anything particular, find the appropriate discussion and ask. Believe this place is not exactly here.

@kreutz : You can check here,
hxxp://www.ccsinfo.com/downloads.php#utilities

At the moment, latest is v5.082

AFAIK the thread's title is "CCS 5.xxx".  Here we are supposed to discuss CCS 5.xxx issues and all questions are on topic. This thread is not to just download attachments.

..nightmare.. again.

V5.083 had gone out before v5.082 was published.
(In this forum)

Though I think that I use CCS-C easily
How about you?

Versión 5.082  ;D

since CCS is on 5.084, its a little out of date

On the web I found the 5.083 version, Old_but_Alive if you want the latest version you can connect on this link: http://www.ccsinfo.com/downloads.php
Regards

Someone has the new version, it is 5.085 the last one, and it fixes problems of 5.083 and 5.084.
Thank you! ;D

Please update the link if possible..
As the links posted on this page are not working
It would be great to get a working link....

Thanks

You was warned to start posting. not to start begging.

Did you miss my post, just above yours?

Version : 5.083

mega.nz or Mediafire link, please. At the above page, it says "These files are not available until tomorrow, because the owner has reached the daily traffic limit."

Version: 5.083 (For MediaFire)

no new updates since may , latest is 5.087 whats happening ?

I know F all

Just read the newsletter from CCS about v5.088 and I see the CCS programmers have been busy!

In May 2019, CCS added this functionality:
Tech Note: New i2c functions for the CCS C Compiler!
Tech Note: The CCS C Compiler now supports Dual Core Processors!

Then a few days ago, CCS added this functionality:
Tech Note: New Message based SPI functions in the CCS C Compiler!
Tech Note: New Advanced RFID driver in the CCS C Compiler!
Tech Note: New Graphic LCD functions in the CCS C Compiler!

They must have hired some new programmers. I haven't seen such a flurry of new features for quite a while from CCS. I hope they have been thorough in their debugging and testing!

Version 5.088  :D

Looks like their developers have been busy again  :D

5.089  #rom crc16 problem affecting some programs is fixed
 5.089  An optimization bug affecting K42 parts is fixed
 5.089  Fixed an issue with setting break points in the debugger on some Enhanced 16 devices
 5.089  Fixed an issue with reading and writing eeprom memory with the debugger on the PIC16F183xx family
 5.089  Updated i2c_read() function so for 1 param it figures out if it is stream or ACK.
 5.089  Added a new i2c_write_slave() function so slaves can push data to the master in an ISR without waiting
 5.089  Added MAX_BAUD option to HW #use spi() to make the baud rate <= instead of as close as possible

New version again! Looks like 5.089 had a lot of issues that has been resolved.

A new release of the CCS C compiler for PICmicro(r) microcontrollers has been released. The new version is: 5.090

Recent changes include:
5.090  An optimization bug affecting most PIC18 parts and the baseline PIC16 parts is fixed
5.090  Added a debugger for the PIC16F177x family
5.090  Improved error detection for when an incorrect stream identifier is passed to I2C functions

Updated:  PIC16F1773
Updated:  PIC16F1776
Updated:  PIC16F1777
Updated:  PIC16F1778
Updated:  PIC16F1779
Updated:  PIC16F18857

So I do have a request: Can anyone upload to Mega? Please...

Version 5.090 :D

5.090  An optimization bug affecting most PIC18 parts and the baseline PIC16 parts is fixed
5.090  Added a debugger for the PIC16F177x family
5.090  Improved error detection for when an incorrect stream identifier is passed to I2C functions

Updated:  PIC16F1773
Updated:  PIC16F1776
Updated:  PIC16F1777
Updated:  PIC16F1778
Updated:  PIC16F1779
Updated:  PIC16F18857

CCS seem very busy these days  :P

not as busy as Micro$oft  :D

Version 5.091  ;D

Small Christmas gift :D
Version 5.092

Version 5.093  :D

Version 5.094 please

Version 5.094  ;D
Enjoy!

THere is always something new with CCS.

thank you, what about 5.095 , could you share this version?

Well what about 5.095 ?
we are not a library or an online order service.
Your post in forum.

so whats your mean, I didnt tell you or anyone else a inconvenient thing, he is a friend from the forum and I just asked to him , its rather normal.

And what to what Value to the Forum is such posts.?

Your Total Post Count is Now 3.

Version 5.095

Version 5.095 isn't available anymore, could you please reupload it? TIA!

Version 5.095 isn't available anymore, could you please reupload it?

here you go

Version 5.097
Enjoy  ;)

Version 5.099  ;D
Happy New Year to everybody!

Version 5.100  :o
CCS it's updating so fast! Enjoy  ;D

Version 5.101   ;D

can someone please upload the old licenses or the keygen please?

Keygen link :

All my browsers are reporting errors due to virus, anyone experiencing the same?

Why did you write to this thread?
Do you get a warning when you look at this thread?

My browser gives no warning.

It is not the thread, it is the last file from last link posted, so be very careful if you disable the antivirus.

Browsers often do. It doesn't look that bad, in fact it looks positively benign compared to many:

https://www.virustotal.com/gui/file/dc5a9ea080a78da4d14aaab6bfecb5d5d0fbfc3f8aef187638f29961e429708c/detection

Regardless, always run such things in a sandbox and copy out the key/file. Standard practice... like condoms and, these days, masks.

Version 5.103  ;D

Hi, thanks for updates, I've just a question, no problem when update already installed program, but if I install ex-novo, PIC-C continually asks update options, is there a method to ovid this?
-
Thanks
Max

Go to the PIC-C installation directory and delete the file named ccsdownload.exe - no more annoying requests.

Version 5.104  :D

CCS Newsletter June/2021

https://www.ccsinfo.com/pdfs/June-2021-Newsletter.pdf

 (previous one,  Aug/2020)
https://www.ccsinfo.com/pdfs/August-2020-Newsletter.pdf

Here is all the docs about CCS

https://www.ccsinfo.com/pdfs/ (https://www.ccsinfo.com/pdfs/)

Best regards.

Version 5.105  8)

Recently, I needed new registry files, I had a lot of trouble finding files that weren't viruses or other kinds of tricks, I finally found one that actually worked or didn't have an expired link.

The link is an old medicine, but it still works on CCS version 5 105, which the friend above shared.

Version 5.106  8)

Hello, apparently version 5.106 has problems with the dsPIC33 family, this is corrected in version 5.107

Version 5.107  ;D

Version 5.108  ;)

The file has a virus.. could you check it?

"The file has a virus.. could you check it?"
Clean with Panda

virustotal says 0

no virus detected by Windows10 Defender

no detection for Symantec

X!

Windows 10 defender..  

I downloaded it again and now there is no warning. Is rare.

No detect using Kaspersky.

THX

Pls conquerertr , use the THANK YOU button, it works better i think.

:-D

X!

A Mute works better

User is in Deep Sleep Mode.

Version 5.109  8)

Version 5.110  8)

Version 5.112

Version 5.113

Version 5.114

In this version  the key generator been not changed?

SCG-PCWHD-keygen working this ver.

Version 5.114 has problems with the use of the SPI module, apparently with the most recent PICs, for example with the PIC18F16Q41, I hope that problem will be solved with version 5.115

The release notes for 5.115 mention a couple changes relating to SPI, but I don't know if that covers your specific issue.

 5.115  Fixed some header file defines for PIC16F180xx family.
 5.115  Fixed the PCD #use rs232() when using the transmit buffer to not lose some characters.
 5.115  Fixed an issue with setup_vref() function for PIC18F67J11 family.
 5.115  Updated #use spi() for PIC18F45K50 family so the alternate HW DO pin can be used with it.
 5.115  Updated how #use spi() sets up the SPI baud rate when using HW SSP peripheral on some PIC16/18 parts.
 5.115  #opt compress now excludes functions with #asm as-is.

Version 5.115  8)

Version 5.116  8)

I kindly ask to someone upload again the SCG-PCWHD-keygen which is not exist anywhere.
I checked the forum I found some links but they are already dead.

Thanks
Ero

SCG-PCWHD-keygen-105

Thank you but I can not load that one which is full trojan inside.

ero

Tested with Norton 360, file is good

How to use the keygen?

Kaspersky finds nothing!

open keygen
input Name    <username>
input Company      <anything>
select where the 4 licence *.crg files will generated
keygen will generate the 4 codes & close

Just wondering if anything has changed in 116 version since in XP it says not valid x32 application.
 i did have a look at their website but cant find info on it

thnax in advance

i am answering my question on this one, the installer seems to be changed and not installing on xp but working on 7 i copied installed files to xp and software doesnt complain.

i have compiled some tiny program files and those seems to work in proteus simulation.


/sphinx

p.s. perhaps time to upgrade  to w7 from xp.

The new version v5.117 is now available, for those of us who had problems with the SPI of the new PIC18... it seems that this version will solve it!

Can you put the link? Or maybe cjack? Please!  8)

The v5.117 release looks like the usual... fix one problem and bury it in a bunch of minor changes. lol From their newsletter:

Recent changes include:
5.117  IDE COMPILER > CLEAN function now deletes .hex files.  .ccspjt files are are NOT deleted
5.117  Improved RTOS error message added when a task is not defined.
5.117  Updated Debugger not showing RAM for parts with more than 64K RAM.
5.117  Fixed the USE RS232 receive_buffer= option when used with over 4K RAM.
5.117  Fixed spi_read() function to properly wait on newer PIC 18 devices when a parameter is passed to it to clock out.
5.117  Updated i2c_slaveaddr() function to update all slave address registers for newer PIC18 devices.
5.117  #pin_select  now accepts PORTF pins on the dsPIC33CK1024MP710 family.
5.117  All CN pins are now available for PIC24FJ64GB106, PIC24FJ64GB108 and PIC24FJ64GB110 devices.
5.117  Updated PCD Wizard TCP/IP to fix an issue with displaying web pages on some parts.

New:      PIC16F17154
New:      PIC16F17155
New:      PIC16F17156
New:      PIC16F17174
New:      PIC16F17175
New:      PIC16F17176
New:      PIC16F18154
New:      PIC16F18155
New:      PIC16F18156
New:      PIC16F18174
New:      PIC16F18175
New:      PIC16F18176
Updated:  PIC24FJ64GB106
Updated:  PIC24FJ64GB108
Updated:  PIC24FJ64GB110