In the posts above, you have "INCLUDE 16F877A.INC"
Do you actually have that in the program? MCS/PBP already take care of that for you.
Doesn't sound like a bad idea...clean it all out... While your at it, spend the $25 and upgrade to PBP 2.50A.I think I shall have to strip it all off the computer and reload again.
Here's the way I do a fresh reload. In my mind, I start from the PIC itself, and work my way backward, to the PBP source code itself...
1) Load the programmer software/hardware/firmware. Test it out, make sure it recognizes and handles the programmer the way it needs to handle it.
2) Load the latest version of MPLAB with any patches that need to be in there. Ensure that MPLAB can compile, and puts any result HEX files where you can find them.
3) Load PBP and any patches that need to be applied. Try it out, compile a file, assemble it (whether you do it, or you set up PBP to let MPLAB do it, either way)
4) Load MCS, connect it to PBP, connect it to MPASM.
5) Try it all out.
And don't load all of this into your "My Documents" folder. There seem to be the occassional 'long path' issues. It seems to work best for me if I put PBP in the root dir of C:, and MPLAB and MCS in their normal 'program files' folder.





Bookmarks