Search found 110 matches

Thanks for your answer

Get rid of using the high priority bit.
...
So try with this not enabled.

OK, I remove it, and Warning 225 "cms.c" Line 754(1,1): Interrupt level changed EX ...

Does anybody knows the details of #INT_EXT ?

I use it in my project.
I need to monitor a 4/20mA loop.
The signal applied to my PIC18F2550 is like series of squares 2 times a second
Each serie is ...

Does anybody knows the details of #INT_EXT ?

I use it in my project.
I need to monitor a 4/20mA loop
The signal applied to my PIC18F2550 is like series of squares 2 times a second
Each serie is ...

Thanks to all of you
I inserted a PIC18F2520 which is 16k and it runs (with V4)

Very Happy

as soon I have time, I try with V5

But first, finish the project and deliver to customer

Have a go ...

I compiled my project in 2013 with V4 version and it worked
As customer asks for changes, we have made pcb changes and need to adapt software for it..
So, when I have tried to compile with these mod ...

To answer your earlier question, the version is shown at
the top of the .LST file. If it has a "d" on the end of the
version it is a demo...

i.e. CCS PCM C Compiler, Version 5.032d
...

1) buy the real compiler from CCS. That way you will NOT have a 'memory' problem.

Jay

OK

The problem is that I bought a full version to CCS, and received the package with book and CD lice ...

Sorry
I don't understand
I use the same version V4 I always used bought to CCS, and my pch.crg is dated 07/01/2013

How can I see that I have a demo version and not a full version, and why would I ...

Thanks for your help Ttelmah and Temtronic
I now can compile when I have suppressed all my JBus fuctions !
(but I need them)
Anyway, when I modify my code somewhere else, I get the error again.

...

However I must also go back to PCM_programmer's question about whether you are using a bootloader?. The error being reported, appears to show the compiler behaving as if it is being excluded from so ...

OK, going back to your original post, if v4.xyz worked WHY bother upgrading to v5.abc ? Obviously v4 was suitable for your PIC, perhaps you can explain why you upgraded?

Really I am a bit lost
...

You can almost certainly get V5 to actually fit the code, if it did go in with V4, by compiling with the option (near the top of your source file):

#OPT compress

OK thanks Ttelmah
I put ...

And if I clearly empty this function (mark inside as /* ... */) another one appears :

*** Error 71 "cms.c" Line 1119(1,2): Out of ROM, A segment or the program is too large ...

The function which seems too large for it is the following (it is the one the error 71 mentions)

In my mind, it is not very long, and not so easy to split off
Why the V5.061 makes code larger than ...

With the newer version there have been udpates and fixes causing the assembly code size to increase just enough to not fit within the banking limitiations.

Aïe Aïe Aïe

Do you mean the code ca ...