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

Version 4 Comments
Goto page Previous  1, 2, 3 ... 15, 16, 17, 18, 19  Next
 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
Jim Hearne



Joined: 22 Dec 2003
Posts: 109
Location: West Sussex, UK

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

That didn't last long, they've broken it again !
PostPosted: Wed May 16, 2007 9:35 am     Reply with quote

After fixing the memset bug in version 4.033 things were looking good.
Except i upgraded to 4.037 today and my large project using the 18lf6722 now resets when i go down several menu levels.
If i disable the WDT then it crashs and randomly changes the state of the outputs on all ports !
Tried 4.034 and thats the same.
Back to 4.033 and all works, identical source, just running the different compiler versions.

So,

    4.020 All works !
    4.032 Memset bug corrupts variables.
    4.033 All works !
    4.034 Crashs/(causes WDT restart)
    4.037 As 4.034


So back to 4.033, that didn't stay fixed long did it !

Jim
Jim Hearne



Joined: 22 Dec 2003
Posts: 109
Location: West Sussex, UK

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

PostPosted: Wed May 16, 2007 11:04 am     Reply with quote

Hmm, i bet my problems with >4.033 (see message above) are to do with the changed operation of CONST in 4.034
My code is about 50% const's of fonts for a graphic LCD.

The readme says:

Quote:

The CCS compilers traditionaly used the C keyword CONST to locate data in program memory.
ANSI uses this keyword to specify a read only data item. The version 4 compiler has a
new method of storing data in program memory for chips that allow program memory to be read.
These three storage modes may be set directly using one of the following qualifiers:
ROMI Traditional CCS method to store in ROM optimized for access from indexed arrays.
ROM New method to save data in ROM optimized for when the user needs pointers to the data
_READONLY Marks the data item as read only, defaults to RAM (like ANSI wants)

By default the CONST keyword is the same as ROMI. The CONST behavior may be changed with
any of the following:
#device CONST=READ_ONLY
#device CONST=ROM
#device CONST=ROMI

Examples:
char rom commands[] = {"put|get|status|shutdown"};
int32 add32( long _readonly * a; long _readonly * b );
char const hex[16] = "0123456789ABCDEF";
char rom * list[] = {"red","green","blue"};


I tried #device CONST=ROMI which should be the default and as expected the problem was the same.
I tried #device CONST=ROM and just get 100 "not enough ram for all variables" errors. Does this new method use more ram ?, anybody have more details on it ?

Thanks,

Jim
Horkesleys
Guest







CCS Version 4.039
PostPosted: Tue May 29, 2007 9:10 am     Reply with quote

Hi,

I have recently loaded 4.039 and I am having problems when I enable the debugger.

The debugger and target worked fine on a previous version of the compiler.

It takes me though some target checking process, even if select no.

I have to switch of the target and reload the debugger.

Any comments?
Jim Hearne



Joined: 22 Dec 2003
Posts: 109
Location: West Sussex, UK

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

PostPosted: Tue May 29, 2007 10:48 am     Reply with quote

The debugger seems ok here with V4.3039 on a 18lf6722

But whatever was making my menu code crash with versions 4.034 to 4.037 (didn't try 4.038) has been magically fixed.
And they've fixed the files window which they broke in V4.033 (would only display the main source file).

Jim
inservi



Joined: 13 May 2007
Posts: 128

View user's profile Send private message

problem with PCWH V4.040 and the ICD-U40 2.14 rev #99
PostPosted: Sat Jun 09, 2007 3:51 am     Reply with quote

Hello,

I work with XP pro sp2.

With version 4.039, ICD-U40 worked perfectly as well with “PCWH” than with “ICD program interfaces”.
When I installed PCWH V4.040, the first time that I test “ICD interfaces program” that worked well.
After that, I charged PCWH V4.040, launched a compilation, and then, I launched ICD (from the menu of PCWH ide).

Since this moment, the USB connection is stop to worked ( when launch ICD, the dialog box for serial connection appear).
It is then the same problem from “ICD program interfaces” and from PCWH ide.

The only manner that I found to fix the problem is to reinstall PCWH V4.039 and the driver of usb ICD-U40. I make with this test 3 times.


For summarize, the USB driver is corrupted after the first usage of ICD-U40 with PCWH 4.040.

CCS must absolutely improve its debugging process !

Thank-you.

dro.
_________________
in médio virtus
EdWaugh



Joined: 07 Dec 2004
Posts: 127
Location: Southampton, UK

View user's profile Send private message

Version 4.042
PostPosted: Thu Jul 05, 2007 6:33 am     Reply with quote

Hi all,

Just an update on my experiences with v4.042. I still find it to be very buggy. Using multiple compilation units seems to break quite a lot of stuff including the second RS232 stream. I am getting problems sharing functions that are passed pointers between compilation units and stuff with constant strings seems broken including using printf("%s",string);.

Has anyone had any better luck? These problems pretty much make the compiler useless as far as I am concerned and I'm considering trying to get a refund for the updated licenses I just bought. The support system is a bit rubbish and a lot of the responses I get are rude, shortly followed by silence when it becomes apparent I have found a bug and am not a moron.

Maybe its time to move to a more ANSI compiler like HiTech?

cheers

ed
Guest








discouraged by the continued reports of bugs ...
PostPosted: Thu Jul 05, 2007 8:10 pm     Reply with quote

Hello all,

I have been content using 3.249 for some time, but have also been a bit chagrined that I might be missing something by not jumping in and trying 4.xxxx.

Well, I see that the Gods have smiled on me by resisting to take the plunge. It appears that after nearly a year, ver4 still enjoys some level of beta status, while many of the forums do not share in such joy.

I think I will stick with 3.249. I really have come to enjoy the many features of the compiler, but can't see sticking with this. If I need to upgrade, it will actually be to use the pic24's or 33's, and well, I have no confidence that the PCD compiler will not be beta for a year henceforth as well.

I may also be looking at HTech when I am forced to upgrade.
PCM programmer



Joined: 06 Sep 2003
Posts: 21708

View user's profile Send private message

PostPosted: Thu Jul 05, 2007 8:18 pm     Reply with quote

What does "multiple compilation units" mean ? Does that mean using
the linker in the vs. 4.xxx IDE, or does that mean using multiple #include
files ?
EdWaugh



Joined: 07 Dec 2004
Posts: 127
Location: Southampton, UK

View user's profile Send private message

mcu
PostPosted: Fri Jul 06, 2007 3:12 am     Reply with quote

multiple compilation units is what CCS are calling using a linker. I was hoping the changes would allow me to write code in a more portable style but it just doesn't work at the moment.
abraxas
Guest







Murder or suicide
PostPosted: Mon Jul 23, 2007 7:17 am     Reply with quote

I've downloaded the 4.045. 4.044 everything normal, ( the term normal in ccs means that you think that everything is going like you want)

4.045---> A-D is not functionnal ?...


Come on, I'm working for a business who has sevral product to program maintaint ( over 40)....

Just tired to wast my time over your compiler poor poor poor qualituy

How are you able to introduce so much bugs, you might want to think about hiring a new dev team
Billy
Guest







PCD Demo
PostPosted: Fri Jul 27, 2007 4:25 am     Reply with quote

According to the website the new PCD compiler is ready so I clicked on their link to download the demo version - except it isn't, its just the old demo for the pic16 and 18 compiler . . .

There seems to be a theme developing here - a complete inability to manage development projects. Perhaps its time to start firing people at CCS.

Also, when will the editor start working properly! How hard can it be to write a text editor. The current version seems to have big problems with mouse clicks and the ends of lines so I end up having to navigate around with the arrow keys.
lewiseley



Joined: 30 Oct 2003
Posts: 24
Location: skegness

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

PostPosted: Fri Jul 27, 2007 6:55 am     Reply with quote

that happened to me too, then when i re read the mail they sent it said

A full 30-day PCD demo will be available after July 27, 2007 at ccsinfo.com!

and it was the 26th, so i wait for the 28th.
airjack



Joined: 02 Mar 2007
Posts: 2

View user's profile Send private message

PostPosted: Wed Sep 05, 2007 9:50 pm     Reply with quote

The Ver 4.054 not work again !!
It seems same problem back .
I'll suggest keep 4.053 .
AEC
Guest







Ver 4.056
PostPosted: Thu Sep 13, 2007 2:45 pm     Reply with quote

Anybody check 4.056 to see if it's cleaned up?
inservi



Joined: 13 May 2007
Posts: 128

View user's profile Send private message

PostPosted: Fri Sep 14, 2007 2:00 am     Reply with quote

Hello,

I just carry out a fast test with ICD U40 and the debuger, it seems to work well. I did not have a problem with V4.055 the preceding one, except the debugger which was planted.

I think that, when V4 will be reliable, this compiler will be a great tool!

Best regards,

dro.
_________________
in médio virtus
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, 3 ... 15, 16, 17, 18, 19  Next
Page 16 of 19

 
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