--===============0664734343==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by pch.mit.edu id l58NRt0w012031

It turns out mplab auto range of program memory to program got it wrong

debugger/settings/program/program memory start-end
"Allow ICD 2 to select memories and ranges" got it wrong!
end was short, had to manual adjust.
Ray


On Fri, 8 Jun 2007 10:13:46 -0400, Ray Newman wrote:
>=A0Bill,
>=A0I always use external MCLR, just for debugging.
>=A0It looks like defective AC162053 from feedback I am getting from
>=A0microchip. Thanks, Ray
>
>
>=A0On Fri, 08 Jun 2007 09:20:57 -0400, William Bross wrote:
>
>>=A0Hi Ray,
>>=A0I don't have access to any of my headers or notes right now but I
>>=A0do =A0have a question for you. =A0Are you using the MCLR line as I/O
>>=A0or as =A0MCLR? =A0I seem to recall that it needs to be MCLR and
>>=A0pulled up when =A0using the ICD-2. =A0I'll check into it further
>>=A0tonight but I'm getting =A0slammed at work right now.
>>
>>=A0Bill
>>
>>=A0Ray Newman wrote:
>>
>>>=A0Hard time getting debugger to execute code from reset instead
>>>=A0of =A0just stepping through it. reinitialize every thing I can
>>>=A0thing of =A0and it finally executes code up to about 0x11A then
>>>=A0it reverts =A0back to just stepping through program like it was
>>>=A0just nops. =A0(mplab 7.6)
>>>
>>>=A0Using pic's since 1990 mostly small chips
>>>=A0have two icd-2 swapped, no effect.
>>>=A01st time using header/pic16f627a
>>>=A0but used icd-2 with pic16f913 and others with no problem. =A0Did
>>>=A0tie RA1 to ground in target board.
>>>
>>>=A0HELP!
>>>=A0Ray





--===============0664734343==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--===============0664734343==--