Exact match. Not showing close matches.
'[PIC] Re: Bizarre Nop Behavior - Reporting Back'
I've had more strange results best given as good news and bad
news (for me)
Good news. The code works fine.
Bad news. I don't know why (or why it didn't before).
I tried the various suggestions that were made, including the one
below, and nothing seemed to help. There were interrupts involved
and turning them on or off still sent the code into neverland. In
frustration I took copies of the code to my office to work on and
all the versions worked fine. Interrupts, label or $-1 jump, PORTA, 4
pin, nops, no nops - all ok. My home machine is 433 MHz running
Win 98 and MPLAB 7.1; my office machine runs Win200 and the
MPLAB 7.1 taken off the same CD, using the same programmer,
and running the code on the same chip, on the same breadboard.
Doesn't make sense to me. This weekend I will take the
code off the office machine, bring everything home, reprogram the
chip, and see if it runs.
>Funny... Do you have any interrupts running? Specifically interrupts
>that might be using T0CKl (which is linked to PORTA,4)? These could
>interrupt your code, and by the time they return (if they return)
>PORTA might have changed state. Note that PORTA,4 is an exceedingly
>odd port on the 16F84... You might want to try if the problem also
>occurs on PORTA,3...
Thanks for all the suggestions, they will be helpful to me in debugging
More... (looser matching)
- Last day of these posts
- In 2005
, 2006 only
- New search...