Either method works, however, placing your CONFIGs in your code lets you debug issues better. If something doesn't work, and the problem lies with your CONFIG settings you set up a program time (with the pop-up window), how would you know??
Either method works, however, placing your CONFIGs in your code lets you debug issues better. If something doesn't work, and the problem lies with your CONFIG settings you set up a program time (with the pop-up window), how would you know??
Thanks - good wisdom!
However, I'm not familiar with setting up a program time (with the pop-up window)
When you go to program, the Programmer window pops up. Under View/Configuration you can view your CONFIG options similarly to MPLABX. There are quite a few neat features in the header tabs. You ought to play with it and get to know your tool. Charles walked me through it several years ago.
Thanks!
I'm familiar with the MPLAB config editor.
I guess because that was there I never thought much to look the the Pickit2 options.
But perhaps you're referring to the ME programmer.
I haven't used that since I had to let go of my PC with a serial port.
I thought I would try out the Pickit2 and that seemed to be working fine.
But just last week it died on me.
So I may end up getting one of the newer ME Labs units
Thanks!
I have an old Pickit2 I haven't used in years. I also have a Pickit3 that I haven't used in about a year. I usually use either the Pickit4 or ICD4, depending on the board. I have the ME Labs U2 Programmer that I use often when breadboarding. Lastly, I have the inexpensive Snap, which I bought only to verify it worked on circuits I sent to my partner (who also has one). If cheap is a priority, you might look into the Snap:
It programs anything Microchip sells, but
- It cannot power the project
- It requires LVP for programming
I was successful at doing this.
Thanks everyone for your kind help! :-]
Bookmarks