Originally Posted by modifyit
I repeat...
<<If your code is evolving, you really should keep MCLR as a reset. The last programming action will be to flip the config fuse for the MCLR pin to become an input.>>
Originally Posted by modifyit
I repeat...
<<If your code is evolving, you really should keep MCLR as a reset. The last programming action will be to flip the config fuse for the MCLR pin to become an input.>>
Let's try that again...
If your code is evolving, you really should keep MCLR as a reset. The last programming action will be to flip the config fuse for the MCLR pin to become an input.
Ahh that could make some sense then...If the last thing the programer does is flip the MCLR to being an input, that is why it could be crashing the MELABS programmer and corrupting the chip, but the chip's program seems to run fine.
I will try using the MCLR as a reset and see what happens.
Thanks again
Making the MCLR a reset did the trick. Thanks to all for your thoughts
Bookmarks