What about spaces in the C program itself--could that be an issue that could effect the hex output when building.

White spaces between C variables, parentheses or operators are not limited. In hex files are white spaces not allowed. You can open hex file in text editor and and see if there is white spaces inside strings (do not save the hex file from text editor, it may corrupt the file).

I tried both the PIC16f627a and PIC16f628a, I mean, once in a while-maybe two times they were programmed successfully.

This is very strange behavior and points probably to inconsistent connecitions between the PIC, programmer and/or computer USB port. Check the power settings for PicKit, if you use external power for the PIC then you cannot feed power fron PicKit.

If you want, i can upload whole project folder i created on my Linux machine with MPLAB X 6.20. You must unzip it to your MPLAB X projects folder.

 

I don't know if the makefile will help but let me include it.

White spaces between C variables, parentheses or operators are not limited. In hex files are white spaces not allowed. You can open hex file in text editor and and see if there is white spaces inside strings (do not save the hex file from text editor, it may corrupt the file).


This is very strange behavior and points probably to inconsistent connecitions between the PIC, programmer and/or computer USB port. Check the power settings for PicKit, if you use external power for the PIC then you cannot feed power fron PicKit.

If you want, i can upload whole project folder i created on my Linux machine with MPLAB X 6.20. You must unzip it to your MPLAB X projects folder.

Thank you but I rather you don't send your project folder. There are no spaces in the hex file viewed with the text editor.

 

Connections from PicKit to PIC are very long, the PicKit3 is sensitive to long connections, try to connect these jumper wires directly to PicKit connector without this flat cable.

Project configuration data for Make is in file nbproject/configurations.xml

 

Way too much going on with that breadboard... I cannot tell what wires go where. Also, many breadboards have a break in the power buss strips at the mid point. Unless you jumper them, you may have power on only half of the breadboard. Try programming with just the pickit, the chip and nothing else. See the pin hookup for the 627/628 at:
https://www.allelcoelec.com/blog/Co...cRPyScmSrVid0Jn1_hDJRNMGNhBE1fyiMi00ykgOoNEx1

 

Ribbon cables are notorious for generating cross-talk.

 

I am able to program the device now. I removed the ribbon cable, but all connections are the same. I still used external power. I changed the timing to 500ms blink on the program and it works and also the original 1000ms blink works also. Thanks to everyone who had the patience with me. I guess my ICs are OK. I wanted to upload an mp4 video of the blinking LED but can't attach one.
Consider this if you may: I reasoned that the force of gravity of love is upside down like fire before I programmed the device. Maybe this realization helped.

 

Did you notice that once a photo was posted the problem was identified and resolved?

 

Did you notice that once a photo was posted the problem was identified and resolved?

Thank you Mr chips for mentioning crosstalk of ribbon cables. You must be referring to my photo of the breadboard. I imagined that crosstalk may have been the problem as I'm sure you believe. Humorous. https://www.dropbox.com/scl/fi/akh8...ey=m9r7yzeuuhyjbn4ej1yr4ri99&st=8llcsx3z&dl=0 Both of the Pickit3 from eBay and Amazon works.