D
DesignElect
- Jan 1, 1970
- 0
Hello,
I'll try to explain what's happening as simply as possible:
I've designed a fairly simple circuit based around a PIC12F629.
It is configured as follows;
GP0=digital O/P
GP1=Analogue comparator input (Comparator mode 04h)
GP2=Digital O/P
GP3=digital I/P
GP4=digital I/P
GP5=digital I/P
Internal voltage reference set to low voltage 01. Fed internally to CIN+.
All Interrupts disabled, Internal oscillator, internal MCLR, pull-ups enabled
on I/Ps except GP3.
What happens is that the circuit works fine, but only when GP3 is pulled low.
When it goes high, it appears to generate a reset, fairly regularly, but mostly
at a point in the program just following reading the comparator status bit.
(ie, the program re-starts). I have ran the program on the simulator and it
goes fine. (It's not supported by my emulator)
Has anyone come across this problem before? I am starting to think that there
is a problem with this chip.... or does anyone know if it's possible that a
problem with the programmer could cause something like this.
Many thanks for any help,
Peter
I'll try to explain what's happening as simply as possible:
I've designed a fairly simple circuit based around a PIC12F629.
It is configured as follows;
GP0=digital O/P
GP1=Analogue comparator input (Comparator mode 04h)
GP2=Digital O/P
GP3=digital I/P
GP4=digital I/P
GP5=digital I/P
Internal voltage reference set to low voltage 01. Fed internally to CIN+.
All Interrupts disabled, Internal oscillator, internal MCLR, pull-ups enabled
on I/Ps except GP3.
What happens is that the circuit works fine, but only when GP3 is pulled low.
When it goes high, it appears to generate a reset, fairly regularly, but mostly
at a point in the program just following reading the comparator status bit.
(ie, the program re-starts). I have ran the program on the simulator and it
goes fine. (It's not supported by my emulator)
Has anyone come across this problem before? I am starting to think that there
is a problem with this chip.... or does anyone know if it's possible that a
problem with the programmer could cause something like this.
Many thanks for any help,
Peter