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

Bug? Fast interrupts incompatible with option noclear?
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
prwatCCS



Joined: 10 Dec 2003
Posts: 67
Location: West Sussex, UK

View user's profile Send private message

PostPosted: Tue May 11, 2004 2:21 am     Reply with quote

further to my last post, I do not have 3.187 to try it with.

I cannot see anything obvious in the devices file (using device editor) which switches this on or off - what have I missed ?
_________________
Peter Willis
Development Director
Howard Eaton Lighting Ltd UK
ckielstra



Joined: 18 Mar 2004
Posts: 3680
Location: The Netherlands

View user's profile Send private message

PostPosted: Tue May 11, 2004 6:12 am     Reply with quote

Congratulations! You have found another bug in v3.190!

I do have v3.190 here, but never tried it because several people reported errors in it and the features changed from v3.187 are not important to me.

Just to prove you are right I installed v3.190, and guess what, now my RETFIE 1 changed into an RETFIE 0 too!!!!

So in the change from 3.187 to 3.188 this functionality has broken. Even when this is due to some new (undocumented) options you would suspect the compiler to be backwards compatible.

Please report this to CCS so they can fix it in the next release.
prwatCCS



Joined: 10 Dec 2003
Posts: 67
Location: West Sussex, UK

View user's profile Send private message

PostPosted: Tue May 11, 2004 7:39 am     Reply with quote

I have posted it to CCS (twice) - once as a query and once as a bug report after the various posts here.

I have even had a response Shocked
Quote:

This message is a reply to CCS e-mail id: 4E2298

The FAST ISR should always use "RETFIE 1" however there is a bug in 3.190 that
prevents this. This will be fixed in the next release.


> Is there a way of telling the FAST interrupt handler to return with a
> RETFIE 1 rather than RETFIE 0 ?
>
> Obviously, my interim workaround is (for a Timer2 Fast irq)
> Code:
>
> #int_TIMER2 FAST
> TIMER2_isr()
> {
>
> .....
>
> CLEAR_INTERRUPT(INT_TIMER2);
> #asm
> RETFIE 1
> #endasm
> }
>
> I am proposing to rely on the processors ability (for the 18Fxx2) to
> context save and restore W and STATUS, which is why I want the RETFIE 1.
>
> Earlier posts to the CCS use forum suggested that use of the keyword FAST
> would result in the RETFIE 1 but in my .lst file it is RETFIE 0, hence the
> apparent need for my workaround.
>


Remember this problem is also observed in 3.188 as far as I can tell.

you have been warned Very Happy
_________________
Peter Willis
Development Director
Howard Eaton Lighting Ltd UK
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