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 support@ccsinfo.com

Compiler command line v5.098 problem?
Goto page Previous  1, 2
 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
Ttelmah



Joined: 11 Mar 2010
Posts: 19195

View user's profile Send private message

PostPosted: Thu Jan 07, 2021 2:18 am     Reply with quote

OK. It fixes this problem, and also the PCD one I was seeing (I suspect this
was the one with PASS_STRINGS referred to in the notes). However it
has a new oddity. It's not allowing ADC bit number selection properly (on
PIC33's at least). Select ADC=10, and it gives:
Quote:

>>> Warning 227 "C:\Program Files\PICC\testmplab\test\TOC\mainconf.h" Line 4(9,15): Feature not supported ADC does not have that many bits 0<10
temtronic



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

View user's profile Send private message

PostPosted: Thu Jan 07, 2021 6:35 am     Reply with quote

Curious....
I have to ask, since you've been using a specific PIC for years, why did you upgrade the compiler ? Was there a certain issue or 'bug' that needed to be fixed ?
Yes, I understand if you use 'new' PICs you need the 'new' compiler.

I use the 46k22/26k22 for ALL my project or products so I haven't upgraded the compiler in years yet we see here NEW problems when the compiler has had 'bugs' fixed. A '[spam]'s box'...fix one, two new bugs, fix one of them 3 more......sigh

Guess I'm gettng old, but I like the 'if it ain't broke- no need to fix it' philosophy.
just curious.....
Jay
Ttelmah



Joined: 11 Mar 2010
Posts: 19195

View user's profile Send private message

PostPosted: Thu Jan 07, 2021 6:50 am     Reply with quote

I upgrade, because I hope for fixes to some of the issues with the current
compiler. I have about three different things where I have to implement
'bodges' for compiler problems. Now twenty versions ago, that was nearly three times as many....
The compilers generally do get better with each version, but unfortunately
sometimes new problems appear.
I always keep 'current best' installed, and every known working code
has recorded what compiler is used, and this is saved with it. Otherwise
you risk problems if you have to recompile. Sad
hmmpic



Joined: 09 Mar 2010
Posts: 314
Location: Denmark

View user's profile Send private message

PostPosted: Thu Jan 07, 2021 12:34 pm     Reply with quote

My comments as a user.
I have used 5.066 for years, for me the best version, some small bug but they can be handled in the code.
6 month ago i made an license renew (pcwhd) to 5.094. Then all my problem start, and i have spend many hours solving the problem, then 5.095, and now 5.099.
I have posted a lot of bug report to CCS and suggested them to do beta channel for testing to prevent not release bad software, but they don't want it.
They prefer to do like @temtronic wrote, every release is beta release there mostly are bug closing for the previous beta release.
One more problem is the bad release notes, they only put some of the changes not all. We have no chance to know if the next release will be better or worse, this is not nice at all.
So for me, my latest license renew for 6 month ago was until now just a bad choices.
That said, if finding a well working version, for me 5.066 then stick to that version, and enjoy the compiler:-)
Ttelmah



Joined: 11 Mar 2010
Posts: 19195

View user's profile Send private message

PostPosted: Fri Jan 08, 2021 1:12 am     Reply with quote

I agree wholeheartedly, and in fact have campaigned many times here for
people to not unnecessarily upgrade.
However when you are dealing with using 'power' features on many new
chips at the same time (my current project is using 5*PIC33's, 2*PIC24,
and 3 relatively new PIC18's), this is when compiler issues will be 'at their
worst'. I actually want to use a lot of the newer peripherals on these.
The latest issue CCS have again said will be fixed in the next release.
Historically, CCS seemed to have a library of 'test' code that they ran. So
once an issue was found it tended not to reappear in following versions.
However possibly because Covid has limited their ability to actually do
the testing, the last few versions seem to have had more problems than
has typically been the case in recent years.
5.074, was a favourite for me for quite a while.
esbelektronik



Joined: 13 Dec 2018
Posts: 23

View user's profile Send private message

5.099 problem!
PostPosted: Sat Jan 16, 2021 1:26 pm     Reply with quote

I am having similar issue at 5.099. When I compile the program I compiled before in 5.098, it gives a warning that there is not enough ram. I regretted upgrading. What should I do to load the previous version or how do I compile it in 5.098 to the compiler?
_________________
^ ^
(q p) ESB
( V )
L L
PCM programmer



Joined: 06 Sep 2003
Posts: 21708

View user's profile Send private message

Re: 5.099 problem!
PostPosted: Sat Jan 16, 2021 1:44 pm     Reply with quote

esbelektronik wrote:

What should I do to load the previous version ?

Request it from CCS.
http://www.ccsinfo.com/request-old-compiler.php

In the future, save the versions that you download. Rename the install
file with a version number.
temtronic



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

View user's profile Send private message

PostPosted: Sat Jan 16, 2021 2:24 pm     Reply with quote

Interesting... I was asked to do a survey for CCS and the one thing I asked was that 'updates' would load into unique folders and that I could have a program use a specific version of the compiler. I'd like a 'default' option ( probably the version I'm happy with) as well as a 'trial or test' version. I know you can kinda do that now through MPLAB(just 2 options), but it's the folder 'labelling' that'd be nice to reflect the version with a pulldown selection ?
Ttelmah



Joined: 11 Mar 2010
Posts: 19195

View user's profile Send private message

PostPosted: Sun Jan 17, 2021 8:01 am     Reply with quote

Yes. As you know I like having multiple versions available. The existing
compiler does have a 'nominal' 'use an older version' ability, but parts of
this do not seem to genuinely reflect the actual behaviour of the older
compiler.
I always disable the ccsupdate program, because I want my compiler
to be the one I 'know'.
esbelektronik



Joined: 13 Dec 2018
Posts: 23

View user's profile Send private message

PostPosted: Sun Jan 17, 2021 1:20 pm     Reply with quote

You can add and remove the versions you want among the add / remove programs options. I removed 5.099 from there and the problem was fixed. But when compiled in version 5.098, it is interesting that when it says Memory usage: ROM = 74% RAM = 59% - 62%, it gives a warning that there is not enough memory space in 5.099 version. My processor is 16f19197, I wonder if something about the new processors was forgotten in the compiler?
_________________
^ ^
(q p) ESB
( V )
L L
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion All times are GMT - 6 Hours
Goto page Previous  1, 2
Page 2 of 2

 
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