Continue to Site

Welcome to

Welcome to our site! is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

[SOLVED] Error in Programming PIC18F4550 with the K150 PIC programmer

Not open for further replies.


Junior Member level 3
Oct 14, 2010
Reaction score
Trophy points
Ahmedabad, India
Activity points
Hello everyone,

I got K150 PIC programmer. The programmer successfully programs PIC16F877A microcontroller.
But when comes to PIC18F4520 and PIC18F4550 controller, it gives error in verifying the flash at 0x0000 location.

The programmer is supposed to support these two controllers and I follows every steps which are written in its user manual. But till I cannot program any of F4520 or F4550 controller.

Now I wonder if K150 can program "PIC18F" series or not?

Please help me out of this.

Seek for the solution of this.

Thanking you all.

Now I wonder if K150 can program "PIC18F" series or not?

According to the Kitsrus site, not many.

Reference: Pic and Atmel Programmers and Microcontrollers Kits
Here is a list of the PICs the software & firmware of diypack25 supports for K149 and K150. K128 and K182 are flash programmers and support only those PICs with an 'F' in the partnumber:

12C508 16C65A 16C77 16F76 16F877
12C508A 16C65B 16C710 16F77 16F877A
12C509 16C66 16C711 16F737 18F242
12C509A 16C66A 16C712 16F747 18F248
12C671 16C67 16C716 16F767 18F252
12C672 16C620 16C745 16F777 18F258
12CE673 16C620A 16C765 16F83 18F442
12CE674 16C621 16C773 16F84 18F448
12F62916C621A 16C774 16F84A 18F452
12F675 16C622 16C83 16F87 18F458
16C505 16C622A 16C84 16F88 18F1220
16C554 16C71 16F627 16F818 18F1320
16C558 16C71A 16F627A 16F819 18F2220
16C61 16C72 16F628 16F870 18F2320
16C62 16C72A 16F628A 16F871 18F4220
16C62A 16C73 16F630 16F872 18F4320
16C62B 16C73A 16F648A 16F873 16C63
16C73B 16F676 16F873A
Added from diypack23:
16C63A 16C74 16F684 16F874 16F5x
16C64 16C74A 16F688 16F874A 10Fxxx
18F6525 6621 8525 8621
(all beta) 16C64A 16C74B 16F73 16F876
16C65 16C76 16F74 16F876A
Added diypack25 12F683

Support for 16F88 added in diypack22 on. Note 10K resistor needs to be added between pins 9 & 10
of Programming sock

Neither the PIC18F4520 nor PIC18F4550 appear to be listed.


There are several 'unofficial' software upgrades to the K150 which do support the 18F4450. Do a search for "DIYPack25ep" or "micropro26" to see if you can find them.


Do a search for "DIYPack25ep" or "micropro26" to see if you can find them.

Acting on the tip from Brian, thanks Brian, I managed to find the following company's website which seems to have taken over upgrades and support for many of the Kitsrus kits, including the K150. They have the DIYPack25ep update package which includes a firmware upgrade for the K150 and their own programming application which also supports the K150 and both the PIC18F4520 and PIC18F4550.

Micropro Windows software for PIC programmers K128 and K149F

While I was unable to run their app within Windows 7, no matter the compatibility settings, I was able to run the app under a Windows XP VM and confirm its support for the K150, PIC18F4520 and PIC18F4550. You may want to review the included README and their website for any required hardware mods for the K150.


I'm not sure what the issue with Win7 might be, on my computer with Windows I stuck to XP, it's expensive upgrading to stand still :|. There is a 'gotcha' with the new Micropro software, it only allows COM ports up to COM9 and it has a cap on the number of __CONFIG words it can handle. The device (.cid) file is easy to edit to add new devices but it isn't possible to expand to allow more __CONFIG words, if you add them they are ignored. It limits it's ability to ISCP later devices but the 'EP' version of the file is certainly better than the original one. I tend to use it for 10F and 12F devices and use Pickits for everything else.


I suspect the compatibility issue is directly related to the method the application is accessing the serial port, as these methods varied widely from one programming language platform to another under Windows XP and many stretched bounds of acceptable practices, with little regard for other applications or the OS.

I'm not sure what the issue with Win7 might be, on my computer with Windows I stuck to XP, it's expensive upgrading to stand still :|.

To the contrary, clinging to outdated equipment with very limited use and having to rely on its legacy application is certainly not moving forward, but standing still. :grin:

Not all us of can run the required applications on a system with a Pentium 90, 512MB of RAM and a 1GB hard drive, these applications require a system which exceeds the 3.5GB of RAM and the two processor limitations of Windows XP Pro, and a more stable OS.

I'm running a Dell T7500 with Dual QuadCore 3.47Ghz Xeons, 48GB of 1333MHz DDR3 ECC RAM, SCA RAID 5 drive system, therefore installing Windows XP so a few legacy apps can be ran in the host OS rather than a Windows XP VM, is really not an option. One of the system's main tasks is to run simulations which can easily consume more than a few gigabytes of memory. Besides, the legacy apps run just fine in a Windows XP VM and I have enough legacy systems laying around to run legacy apps if the need should arise.


Thanks Brian and BigDog.

Actually I am running the latest version of microbrn software in my PC because I bought this programmer in 2011 and the last update of its software made at 2007 so I just need to re-flash 16F628 controller in programmer with latest hex file and try again.
But as of now, I don't have the new PIC16F628 controller so I cannot upgrade the hex file.
But I will upgrade it and let both of you know.


I have a room full of computers, dedicated to various tasks but all normally run Linux. Some are dual boot to XP for 'legacy' applications, I use Windows so little it isn't worth my while 'upgrading'. The system I use for programming isn't quite up to your standard, a 3.4GHz i7 with 6Gb of 1333MHz RAM and SSD for storage but it plods along quite nicely!
I find "Crossover" lets me run most Windows apps in Linux if necessary. The 3.5Gb RAM limit in 32-bit XP doesn't cause any problems with the kind of programs I use but it's nice to know it's all there when running the 64-bit Linux.

Back to the original issue - the COM9 limit seems to be built into the Micropro software. I have an alternative "made in China" board that looks almost identical to the K150 but is USB powered and has it's own VPP generator circuit. It IS compatible with higher COM port numbers but the software isn't compatible with Micropro and is horrendous to operate. The instructions and some of the screen text is in Mandarin!


Hey :-D

The problem is resolved by upgrading the hex file.

Thank you very much guys. I am now capable to Program both of that controllers by upgrading the hex file of 16F628A controller on the board.

Thanks for guiding me to the right way. I can now proceed further in PIC18F devices.


Not open for further replies.

Part and Inventory Search

Welcome to