ePanorama.net

All about electronics

Skip to content

Velleman K8048 PIC programmer

Post a reply


Enter the code exactly as it appears. All letters are case insensitive, there is no zero.
Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Velleman K8048 PIC programmer

Re: Velleman K8048 . Device ID not found

Post by mharrisb on Fri Aug 04, 2006 1:24 pm

ledjorge wrote:
Paul wrote:Hello, I am having problems getting my pcs to work with this unit.
I have the correct cable and power supply.
Works ok on pc at work , but at home I get Device ID not found after I click any of the options to read / write to the k8048 unit.
The software old and new finds the unit but does not see the pics.
Any help would be nice. Thankyou


Hi. I have the same problem. The programmer work OK with PC Desktop, but in my Laptop, appear the message: ""K8048 not found at COM1".... I don't know but may be beacuse of the voltage levels....

Please, if you find the solution, write me... please!!!

Thanks,


Jorge
Gent, Belgium


Hi all,

I am new on this forum. I recently got my velleman however i was having the same problem (i-e. when trying to read and write I would get a "No Device ID Received" error) however just to calm your nerves I can assure you that theres nothing wrong with the pic or the product itself. I am currently unsure of what I did to make it work. However I can tell you that If you mess around with some of the settings under Control Panel > System > Device Manager > Ports > [Your COM]
If you experiment with different IRQs, Changing Com port names from the Advanced Tab and the I/o Range you will find the configuration that works for you.

Hope this helps. I will try experimenting some more to see if I can pin-point the problem.

Cheers

Re: Velleman K8048 . Device ID not found

Post by ledjorge on Wed Jul 19, 2006 7:15 pm

Paul wrote:Hello, I am having problems getting my pcs to work with this unit.
I have the correct cable and power supply.
Works ok on pc at work , but at home I get Device ID not found after I click any of the options to read / write to the k8048 unit.
The software old and new finds the unit but does not see the pics.
Any help would be nice. Thankyou


Hi. I have the same problem. The programmer work OK with PC Desktop, but in my Laptop, appear the message: ""K8048 not found at COM1".... I don't know but may be beacuse of the voltage levels....

Please, if you find the solution, write me... please!!!

Thanks,


Jorge
Gent, Belgium

K8048 problem fixed

Post by libratigger on Tue Jul 18, 2006 4:16 pm

Problem solved..... In attempting to fix the previous problem I'd used the delay transistor suggested in a post on CNCzone, last post

(http://www.cnczone.com/forums/archive/i ... 11701.html)

The added electronics was just enough to drop the VPP to just below 5V and for it not to run properly. Incidentally, the 628s ran OK with the kit in PROG mode when the RESET (SW6) button was pressed.

k8048 and LEDs

Post by libratigger on Tue Jul 18, 2006 10:04 am

Hi everyone. I've been here on the quiet trying to get my kit working.... transistor mix up, the eventual discovery.

Having now got my K8048 kit up and running after a couple of teething problems I've noticed a problem especially when more than one LED is lit at one time using the provided DEMO2.ASM program. I wonder if anyone else has experienced this?

The demo2.asm program just doesn't work right when the EFFECT_3 loop is selected. A few leds light up then it goes back to the EFFECT_4 loop. If only one LED at a time is lit then it all works perfectly with any combination or sequence, but as soon as more than one is lit it just misbehaves.

For example at the moment I have EFFECT_3 as

EFFECT_3 BTFSC PORTA, SW3
GOTO EFFECT_3
E3 MOVLW B'00000110'
MOVWF PORTB
CALL DELAY_ROUTINE
MOVLW B'00011000'
MOVWF PORTB
CALL DELAY_ROUTINE
GOTO E3

What happens here is I get a double flash from the B'00000110' and a single flash from B'00011000'.

Another query.... should the 16F627 be interchangeable with the 16F628? Should they do the same with identical programs? I'm finding that they're not. With the demo2.asm program the 628 hardly responds to switches being pressed (and this is the same for 2 different 628 chips). A different LED might flicker, but the kit just goes back to what it was doing before the button was pressed. Both the 627 and 628 are 04/P

Thanks for any assistance.

Andy

K8048 problems

Post by Tomi Engdahl on Tue Mar 28, 2006 1:26 pm

As I in the original preview pointed out, I had some problems with the mode switch on my kit. It did not work reliably first, but using some contact spray solved the problem. I had my problems in turnign the PIC to running mode. If I had soldered that switch on the other way on the circuit board I woudl have had serious programmign problems I think...
If you have problems in reliable protection, make sure that your switch on the board works reliably as it should.
That's just my tip.

K8048 ID problems

Post by james_hernon on Tue Mar 28, 2006 12:36 pm

The problem with the ID can sometimes be resolved by having the SWITCH in the right position, it has to be in the PROG and not standby or RUN...

I was getting an ID error when trying to READ A TEST PROGRAMMED PIC16F627-04/P and when I put the SW5 switch into PROGR. Pulling it down towards you, the software was able to read the PIC.

I hope this helps.

Thanks
James Hernon

K8048 cable

Post by Tomi Engdahl on Wed Feb 22, 2006 3:07 pm

I found that a 9-pin Male to Female passthrough cable did the job. It's using a fair number of the pins, not just RX/TX/GND like so many serial apps often do. So, specifically: make a cable with pin 1 -> pin 1, pin 2 -> pin 2, etc. for all 9 pins, and you should be good to go.


That's what I have used with my kit. I have used for example RS-232 cable made from "flat cable" and IDC type 9 pin connectors that can be crimped to it. I made straight through cable and it worked well. I have also used the circuit with a commercial 9 pin D connector RS-232 extension cable.

I'm also using a slightly low power supply (a lot closer to 12v than 15v) without problems.


If you use lower voltage than specified on the kit, the microcontroller once programmed should run without problems. Anyway it is powered through 5V regulator. The lower than listed voltage can affect the programming reliabity. If you use lower than specified power supply voltage, then this causes the PIC programming voltage drop somewhat below the specified voltage... this can cause programming to fail or be unreliable.

Oh, and do yourself a BIG favour. As soon as the board works, go to www.microchip.com and download the MPLAB IDE software. It has a built-in assembler and can simulate many devices this board can program.


I can also recommend to do this. I have done that.

If you want to program PICs using C programming language, then take a look at the free PICC-Lite compiler that allows you to write software for many PIC microcontrollers usign C programming language. More information on that can be found at http://www.htsoft.com/products/PICClite.php

Re: Velleman K8048 PIC programmer

Post by rmilne on Fri Feb 17, 2006 10:05 pm

Dunno if this will help anyone, but there seems to be no reference as to what kind of serial cable is needed. I found that a 9-pin Male to Female passthrough cable did the job. It's using a fair number of the pins, not just RX/TX/GND like so many serial apps often do. So, specifically: make a cable with pin 1 -> pin 1, pin 2 -> pin 2, etc. for all 9 pins, and you should be good to go. Once I had the right cable installed, my board worked right away. I compiled the two sample apps that come with the board, and installed and ran them no problem on the 16F627 that came with my kit. I'm also using a slightly low power supply (a lot closer to 12v than 15v) without problems.

Oh, and do yourself a BIG favour. As soon as the board works, go to www.microchip.com and download the MPLAB IDE software. It has a built-in assembler and can simulate many devices this board can program. It even has a software logic analyzer in the simulation, and can fake incoming data on the input pins and so many other useful features like watch windows, etc. WONDERFUL! and free!!! Just use your existing K8048 programmer software to upload your hex file when you want to try your code on the real device.

Post by Guest on Thu Feb 16, 2006 6:01 pm

grrr I cant get it to work either.
No Device ID recieved, and a similar error message comes up when I use the new software.

velleman K8048

Post by david on Mon Jan 30, 2006 3:26 pm

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.

Post by Guest on Thu Jan 05, 2006 11:55 am

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 :)

Post by unlucky on Fri Dec 30, 2005 8:32 am

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!

K8048 and 16F675

Post by David (Belgium) on Mon Dec 26, 2005 10:04 am

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 ?

K8048 with 12F675

Post by Kasper on Fri Dec 16, 2005 10:34 am

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.).

Post by Guest on Mon Dec 12, 2005 3:28 am

hi i'm catacocol

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

Top

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
phpBB SEO
cron