Velleman K8048 PIC programmer

[FredProd]

I've tried that! Still doesn't work...

[Tomi Engdahl]

I canät say for sure what is wrong in your system.

With a correct cable (direct 9 pin RS-232 cable all pins connected), righ tpower supply and Windows 2000 computer (AMD 1.4 GHz CPU) I got the system working pretty easily.

Check that you have this cable and power supply also right.

[FredProd]

I've got correct voltage and cable...
I've got the newest software, even tried other software...

I'm running Windows XP SP2 on AMD Athlon 2400+ (2Ghz)

[HWguru]

Product: K8048
Manufacturer: Velleman
Product type: Electronics kit / PIC Programmer
Product web page: http://www.velleman.be/common/product.a ... &id=350903
Manufacturer home page: http://www.velleman.be/

Velleman has also a ready made module product based on this.
The VM111 is the same product as this kit but ready to be soldered (no need to solder it together by you).

For example the web store at http://store.qkits.com/moreinfo.cfm/VM111 sells this ready made programmer at $64.95

[Lyvyux]

The problem shold be the T3 witch should be 557 not 547 !

[janhol]

i have the same problem.
can't find the k8048 either,
T3 is the correct one. 557, led flashes, when in program mode and LD8 is on too.
anybody any ideas ?

[Vince]

Same problem here...

[parkington]

same with my 8048 too... LD8 is on permantely when in program mode, and the progpic2 software says there is no 8048 attached... T3 is correct.

any ideas anyone?

[parkington]

actually.. i suspect the problem is down to Windows XP or the supplied software - if I attach the K8048 to my FreeBSD server and use http://dev.kewl.org/k8048/Doc/#toc to program it, it works perfectly. I have now also installed FreeBSD on the same computer I had problems with earlier and it works fine there too... so it has to be something windows is doing, or progpic2.exe does...

any ideas anyone?

[Guest]

hi i'm catacocol

i'm form mexico and i just want to say this is a really good web.

[Kasper]

I am relatively happy beginner with this K8048 programmer. Unluckily it looks like the board sometimes burns 12F675 chips. I first succeeded to program the chip several times, then suddenly the programmer gui says that it cannot get the chipid. Same happened to another unit after first programming. I don't think I misused the system (pulling chip out with power on, etc.).

[David (Belgium)]

I've got exactly the same problem with 12F675. I tried with the 5 pieces I had in my stock, and they all became inaccessible for any other action from ProgPic2 : no read, no write, no erase.

The supplied 16F627 worked ok: I programmed it a dozen times without any problem.

However, with a 12F675, it's a one-shot ! I've got a program with parameters to adjust in the EEPROM, but no way ! Once programmed, there's no more access.

What's weird is that the config-word was changed, apparently by the ProgPic2 software: I entered 3F8C in my program, and that is the value that appeared in the ProgPic2 screen, but whenI made a readback, the value was read as 118C. This activates Code and data protection, which I didn't ask.

And from this time on, no more access to the chip. It runs its program, but I can nor alter neither read anything from it : no code, no data. And what's worse is that even the bulk erase doesn't work since the Dev-Id can not be read anymore, and ProgPic2 disables all its functions.

Any ideas ?

[unlucky]

I also have the same problem with 16F676. Config word won't always set properly.
There's no activity in the chip even if the code (and the config word) is read back and verified to be ok.

My application is a temp logger by Niklas Langmaack and what comes to hardware everything should be ok. Actually two different pcb's are tested.

Any ideas?

Thanks!

[Guest]

I think my problem is solved!
Temp logger application is now running ok and no errors in programming.
I already programmed several 16F676's with no problem.

Problem was caused by combination of two things:
1. For some reason there was following lines in temp logger asm code:
org 0x03FF
goto init

These had to be removed from the code because this goto command overrides/conflicts with factory set RETLW command in location 3FF.
This RETLW returns factory set calibration value (in w-register) when application is CALLing it (as is done in this temp logger).

2. Velleman K8048 and progpic2 software tried to program this 3FF location (according to HEX-file) but I believe that a bit more sophisticated programmers will not do this (even if told in HEX-file).

So these things together caused a lot of write failures (mostly in config word & eprom area).

If application is time sensitive (like this temp logger's RS-232 interface) the factory set calibration value must be used (moved to osccal-register).

Factory set calibration value can be read from blank chip using progpic2's readback-function. Calibration value can be seen in address 07FE. This should be 34xx where 34 is RETLW command and xx is calibration value which is used for correcting error of PIC's internal RC-oscillator.

The lucky one from Finland

[david]

I had fun building this kit, but compiled programs just wont transfer to the 16F627 chips I am using. All I get is No Device ID received. As far as I can tell, my assembly was okay. In prog mode LED9 flashes, and when attempting writes LED8 flashes, then goes out when error message displayed, and then stays on when error message accepted.