3.119 disables global interrupts

nilsener · Guest

Dear,

3.119 and 18F452

I have updated from 3.110 to 3.119 and after that my program fails. I have determined that something disables the global interrrupt a few seconds after power up the PIC. After introducing an additional enable_interrupts(GLOBAL); into the main loop everything seems to work fine, but this is not acceptable because it is unknows how often the global interrupt will be disabled from 3.119. In worst case the global interrupt will be disabled immediately after the enable_interrupts(GLOBAL); directive.
I have checked this with different projects and always the same problem.
Has anyone seen this before ?

Code in general:

enable_interrupts(GLOBAL);
enable_interrupts(INT_RDA); enable_interrupts(INT_EXT); enable_interrupts(INT_TIMER1);
enable_interrupts(INT_TIMER3);

main()
{
while(1)
{
enable_interrupts(GLOBAL); // prog fails without this directive
...
...
code
...
...
}

regards nilsener
___________________________
This message was ported from CCS's old forum
Original Post ID: 8323

Mark · Joined: 07 Sep 2003 Posts: 2838 Location: Atlanta, GA

Are you using an ICE2000 or an actual chip. I have as well as others here experienced this problem with the ICE. The actual chip works fine. I believe the problem is in the ICE module. This problem happens to me with both the CCS compiler and the Microchip C18 compiler.

Regards,
Mark

:=Dear,
:=
:=3.119 and 18F452
:=
:=I have updated from 3.110 to 3.119 and after that my program fails. I have determined that something disables the global interrrupt a few seconds after power up the PIC. After introducing an additional enable_interrupts(GLOBAL); into the main loop everything seems to work fine, but this is not acceptable because it is unknows how often the global interrupt will be disabled from 3.119. In worst case the global interrupt will be disabled immediately after the enable_interrupts(GLOBAL); directive.
:=I have checked this with different projects and always the same problem.
:=Has anyone seen this before ?
:=
:=Code in general:
:=
:=enable_interrupts(GLOBAL);
:=enable_interrupts(INT_RDA); enable_interrupts(INT_EXT); enable_interrupts(INT_TIMER1);
:=enable_interrupts(INT_TIMER3);
:=
:=main()
:={
:=while(1)
:={
:=enable_interrupts(GLOBAL); // prog fails without this directive
:=...
:=...
:=code
:=...
:=...
:=}
:=
:=regards nilsener
___________________________
This message was ported from CCS's old forum
Original Post ID: 8325

nilsener · Guest

Dear Mark,

thanks for your response,

I use MPLAB 5.70.00. and ICD2
I am not sure what ICE2000 is ? a chip ? If you mean that newer chips of 18F452 are working, perhaps do you know the datecode of those chips ?

:=Are you using an ICE2000 or an actual chip. I have as well as others here experienced this problem with the ICE. The actual chip works fine. I believe the problem is in the ICE module. This problem happens to me with both the CCS compiler and the Microchip C18 compiler.
:=
:=Regards,
:=Mark
:=
:=:=Dear,
:=:=
:=:=3.119 and 18F452
:=:=
:=:=I have updated from 3.110 to 3.119 and after that my program fails. I have determined that something disables the global interrrupt a few seconds after power up the PIC. After introducing an additional enable_interrupts(GLOBAL); into the main loop everything seems to work fine, but this is not acceptable because it is unknows how often the global interrupt will be disabled from 3.119. In worst case the global interrupt will be disabled immediately after the enable_interrupts(GLOBAL); directive.
:=:=I have checked this with different projects and always the same problem.
:=:=Has anyone seen this before ?
:=:=
:=:=Code in general:
:=:=
:=:=enable_interrupts(GLOBAL);
:=:=enable_interrupts(INT_RDA); enable_interrupts(INT_EXT); enable_interrupts(INT_TIMER1);
:=:=enable_interrupts(INT_TIMER3);
:=:=
:=:=main()
:=:={
:=:=while(1)
:=:={
:=:=enable_interrupts(GLOBAL); // prog fails without this directive
:=:=...
:=:=...
:=:=code
:=:=...
:=:=...
:=:=}
:=:=
:=:=regards nilsener
___________________________
This message was ported from CCS's old forum
Original Post ID: 8328

Mark · Joined: 07 Sep 2003 Posts: 2838 Location: Atlanta, GA

ICE is In-Circuit-Emulator. I know there are some differences is how the emulator and the actual chip handle interrupts. There is errata on the interrupt handling for the PIC18's. According to Microchip support, the emulator module was built base on the orginal documentation in the datasheet. The PIC18's were built based on the errata. I know have have some early engineering samples that do not work. They no longer verify correctly (if my memory is correct). The latest chips I have all seem to work fine. The code on the chips that I am currently using is 0231JGF.

:=Dear Mark,
:=
:=thanks for your response,
:=
:=I use MPLAB 5.70.00. and ICD2
:=I am not sure what ICE2000 is ? a chip ? If you mean that newer chips of 18F452 are working, perhaps do you know the datecode of those chips ?
:=
:=:=Are you using an ICE2000 or an actual chip. I have as well as others here experienced this problem with the ICE. The actual chip works fine. I believe the problem is in the ICE module. This problem happens to me with both the CCS compiler and the Microchip C18 compiler.
:=:=
:=:=Regards,
:=:=Mark
:=:=
:=:=:=Dear,
:=:=:=
:=:=:=3.119 and 18F452
:=:=:=
:=:=:=I have updated from 3.110 to 3.119 and after that my program fails. I have determined that something disables the global interrrupt a few seconds after power up the PIC. After introducing an additional enable_interrupts(GLOBAL); into the main loop everything seems to work fine, but this is not acceptable because it is unknows how often the global interrupt will be disabled from 3.119. In worst case the global interrupt will be disabled immediately after the enable_interrupts(GLOBAL); directive.
:=:=:=I have checked this with different projects and always the same problem.
:=:=:=Has anyone seen this before ?
:=:=:=
:=:=:=Code in general:
:=:=:=
:=:=:=enable_interrupts(GLOBAL);
:=:=:=enable_interrupts(INT_RDA); enable_interrupts(INT_EXT); enable_interrupts(INT_TIMER1);
:=:=:=enable_interrupts(INT_TIMER3);
:=:=:=
:=:=:=main()
:=:=:={
:=:=:=while(1)
:=:=:={
:=:=:=enable_interrupts(GLOBAL); // prog fails without this directive
:=:=:=...
:=:=:=...
:=:=:=code
:=:=:=...
:=:=:=...
:=:=:=}
:=:=:=
:=:=:=regards nilsener
___________________________
This message was ported from CCS's old forum
Original Post ID: 8330

Ned Konz · Guest

:=Dear,
:=
:=3.119 and 18F452
:=
:=I have updated from 3.110 to 3.119 and after that my program fails. I have determined that something disables the global interrrupt a few seconds after power up the PIC. After introducing an additional enable_interrupts(GLOBAL); into the main loop everything seems to work fine, but this is not acceptable because it is unknows how often the global interrupt will be disabled from 3.119. In worst case the global interrupt will be disabled immediately after the enable_interrupts(GLOBAL); directive.
:=I have checked this with different projects and always the same problem.
:=Has anyone seen this before ?

Yes, I see it when changing from 3.116 to 3.118.
I haven't gotten around to tracking it down, and probably won't, as I've moved to the Microchip C18 compiler.
This was the last straw for me.
___________________________
This message was ported from CCS's old forum
Original Post ID: 8357

Regan · Guest

I had a similar problem to Mark while using the RICE17A emulator. I kept finding that interrupts would be disabled.
I put the following command at the beginning of my main() routine and everything has been smooth sailing since then.

#define RCON 0xFD0
main()
{
bit_clear(RCON,7); // clear IPEN bit
etc...

This disables interrupt priority management and puts the processor into PIC16C compatability mode with respect to interrupts. Unless you have specifically coded some high-priority interrupts, this may do the trick.

regards,

Regan.
___________________________
This message was ported from CCS's old forum
Original Post ID: 8367