I am having some issues programing a PIC18F67K22 using a PICKIT3.
Programing will work fine until the program grows and passes memory location 14000, at witch point I will get the following error.
"Address: 14001 Expected Value: b3 Received Value: 0"
Removing a function from the program (can be any function) until the program is smaller the 14000 and it will program fine.
I have tried;
1. MPLABX 5.20, 5.35 and 3.40.
2. PIC at 3.3v and 5V, both from external power and from the PICKIT.
3. 2 Different PICs (Both PIC18F67K22).
Only thing I cant test is a different PICKIT as I only have one..
 
I am guessing hardware is ok as it will program fine when the program is small.
Nothing else is currently connected to the board.
 
Is there anything I can try to get around this? What is so special about memory location 14000 anyway. i cant see anything in the datasheet that matches up to this boundary.
 
Thanks 

If you want to.  Your choice.
 
I can try your errant HEX with PICKitPlus and a PICKit3 programmer here.  I just need the hex.
 
This is not a plug but a true offer of help.  The root cause could be identified by this offer.

I just tried a HEX hex.  Stats are Program Memory: 63908/65536 words (97.52%)   RAM: 24/3862 bytes (0.62%)   OSC: INTIO2, 64Mhz (Internal oscillator)   Chip: 18F67K22 The PROGMEM is therefore from 0x0000 to x0x1F2AC contiguous in memory. 
 
So, what is your CONFIG? Do you have a write protect set? 

Anobium
I just tried a HEX hex.  Stats are Program Memory: 63908/65536 words (97.52%)   RAM: 24/3862 bytes (0.62%)   OSC: INTIO2, 64Mhz (Internal oscillator)   Chip: 18F67K22 The PROGMEM is therefore from 0x0000 to x0x1F2AC contiguous in memory. 
 
So, what is your CONFIG? Do you have a write protect set? 

Programming typically involves erasing (including the protection bits), programming, verifying, and then activating the protection bits.
 
@OP: Daniel in this link seems to have the same issue as you:  https://www.microchip.com/forums/m1130750.aspx
 

Hi Anobium,
 
I will take you up on the offer. HEX can be found here - https://1drv.ms/u/s!AjN1dYoUGyAvh64iclNqhBXwExUh9Q?e=oFtMKb
 
Thanks
 

Thanks 1and0.
I had a look at the post but there is not really much helpful information there, just banter about PICKIT3 not supporting new pics. The 18F67K22 is not new and I cant see why support would be dropped.
 
 

markdem
Thanks 1and0.
I had a look at the post but there is not really much helpful information there, just banter about PICKIT3 not supporting new pics. The 18F67K22 is not new and I cant see why support would be dropped.

Did you read post#4 and post#6 in that thread?
 

This is most likely a bug in the tools or in PICkit3. Most likely something introduced lately. 3 years ago, I used PIC18F67K22 for testing programming speed, and PICkit3 could program the full chip (but not EEPROM) without problems in 34 sec.
 
I would suggest contacting Microchip support - perhaps they can fix it.
 
If nothing else helps, you can buy one of our NSDSP programmers. It is not integrated with MPLAB X, but it can program your HEX file without problems:
 

NSPROG 141 (C) 2015-2020 Northern Software Inc. All Rights Reserved.
The HEX file contains the following blocks:
   0x00000000-0x00000006: 6 bytes
   0x00000008-0x0000fffe: 65526 bytes
   0x00010000-0x00014674: 18036 bytes
   0x00300000-0x0030000e: 14 bytes
Target device is PIC18F67K22.
Connected to NSDSP100000000 Version 0103.
Ranges to be programmed:
   code   0x00000000-0x00014680: 653 rows
   config 0x00300000-0x0030000e: 7 words
Communications with target device established at 6000kHz.
Programming ... Done
Operation complete. Time elapsed 2.246s.

 
Found an interesting thing (silicon bug perhaps) when working with your file - your file has MCLRE disabled and there must be impossible to program it with LVP, but the file programmed just fine effectively locking out my LVP mode. I had to use HVP extension to bring the chip back with HVP mode.
 
 

I did.
I tried MPLab 5.20, did not make a difference. 
I will try 5.05 later on today. 

Your hex works here.  See the https://1drv.ms/u/s!Ase-P...uQWbTVUJS-HuQ?e=gwYm5D
 
As one of the developers of the PICKitPlus software.  I do know.  There was a low level with these specific chips that Microchip had had failed to resolve in the PICKit range of software.  We resolved this issue within our new software.  
 
So, I would try the latest version of MPLAB-IPE or upgrade to PICKitPlus (this would retain your existing programming hardware).