I am trying to use the K8048 kit, but it appears every time I try to write any code it tells me No Device ID received. I feel I have followed the instructions.
Can anyone tells me what this means? Jumpers are installed SW5 is in run
Peter
Can you check this post?
[url]K8048 Programming a Pic]
[quote=“VEL982”]Can you check this post?
[url]K8048 Programming a Pic][/quote]
Already checked before posting. The software recognises the board fine, justr getting that error
What pic are you using? It is possible that the internal oscillator is running?
I am using the PIC16F628-04/P
“Jumpers are installed SW5 is in run”
–> SW5 must be in the “PROG” possition ! when reading or writing to any MCU.
-Check also that your input voltage to the K8048 board is min. 15V
-Did you have already used the included PIC ? (PIC16F627)
I get the same problem with the PIC16F627 chip. supplied with the kit. Board is detected [gives ‘K8048 detected’ message on port selection]; Jumpers on, voltage checked, ‘Prog’ switch on etc. Attempting to ‘Write’ gives ‘No Device ID Received!’ message. Attempting to see Data Window gives same error ‘No Device ID Received!’.
With alternate chip PIC1684a-20/P gives a different error:
Write Error @ 0000
Wrote: 2812
REad: 3FFF
Spent a day assembling the board, no mods, checked connections etc etc.
I’d be very grateful for advice!
One more detail: Jumpers on or off produces same result.
Same problem = same possible solutions.
If everithing is OK (Voltage,cable,hardware,…) is maybe your serial port not 100% compatible. USB converters are not supported.
We can always check your card if you send it to us (via your dealer).
The error message while using a F84 is different because this controller doesn’t have an ID code. (old die)
[quote=“VEL456”]Same problem = same possible solutions.
If everithing is OK (Voltage,cable,hardware,…) is maybe your serial port not 100% compatible. USB converters are not supported.
We can always check your card if you send it to us (via your dealer).
The error message while using a F84 is different because this controller doesn’t have an ID code. (old die)[/quote]
I’d appreciate any advice you can give before we go to the major step of sending internationally…
-Voltage tests ok
-cable is new and works with other devices.
-I’m using a traditional serial cable, not a USB converter.
Clarifications:
a) in your previous posts, it is not clear whether the jumpers must be in place for correct functioning- clarify please [in my case the error is there either way]
b) please clarify the following message:
‘The error message while using a F84 is different because this controller doesn’t have an ID code. (old die)’–I’m afraid I don’t understand the short-form references. Does the error message experienced with the alternate PIC1684a-20/P [brand new, not programmed] shed any light on what might be happening? No programming at all has happened yet.
thanks
The jumpers are only for connecting the ‘test’ XTAL, and haven’t any relation with reading or writing to the PIC.
The C/F 84 als an old design (1994-95) and haven’t any device ID.
I have experienced this problem and solved it last night.
n my oscilloscope I noticed that the programming voltage that is on Pin 4 dropped out during programming.
If your program is designed to produce outputs on the PGD output pin then this will corrupt the rreading of the PIC ID.
I lifted one end of R13, this prevents the PC from driving T3 and clamping the programming voltage.
This solved my problem and was able to reprogramm my PIC that I was unable to read the Device ID for the last week.
Hope this helps.
Derek
I have been using a VM111 for about a year. Most of the time it is OK but occasionally I get the No Device ID Received message.
I’ve got it again - and this time it seems permanent!
I’ve tried 7 or 8 16F627s - but none return the ID. Some are new and all were perfect a couple of days ago.
The programming voltage is unchanged (about 15V). Same PSU as I have used for a year.
Connecting a 'scope I can see a burst of clock pulses every time I ‘write’ however the PGD (data line) seems permanently high - with a slight ripple that corresponds to the clock burst. I would have expected a rail to rail binary signal.
While in programming mode the chip appears to be running the programme - is this to be expected?. I am not sure I have noticed this happen before. The internal RC oscillator could well be running as the programme I am downloading is configured to use it. In the past I have generally used the internal RC oscillator and it has caused no problems when programming.
I haven’t ried lifting R13 yet - it seems a rather extreme measure when I know that the problem has, in the past, corrected itself spontaneously.
Any advice welcomed
Hi Denis
My program was the same, using rc Oscillator and not using the MCLR option - This allows the program to run freely and if there are outputs turning on this can corrupt the data trying to be read back.
I first had to delete the program then consider reprogramming the chip.
By doing the Mod I mentioned it allowed me to get to do a memory clear.
There is also another program that Vellerman offer for Download called PicProg2006.exe, this has an option for the programmer board we use - and it also allows you to get passed the No Device ID message. Again I would go for Erase Pic - Erase all option first.
On the comment about not seeing the data change - are you absolutely sure you have the program voltage there on the PIC?
Hope you can sort it out - I have not lost a PIC 16F627/8 yet and I seem to have locked access a few times, but have always recovered them.
Regards
Derek
I have the same problems.
I cant write to pic
I tried all, still doesnt work!
Matej
Dear colleagues, it’s natural to raise the question of a design flaw. Sure seems like a lot of us are experiencing this same vexing malfunction. Is it us, or is it the kit?
Philip Beesley pbeesley@uwaterloo.ca
Hi all,
I just bought a VM111 last week, and i’m getting the same error since then. I’ve tryied to program the PIC16F627 that came with the board, and also several PIC16F84A, using the serial cable included in the VM111. I always have the 3FFF read error with the F84 or a message saying that the switch should be in PROG mode, or there are not PIC on the board or something… when using the F627.
I’m quite dissapointed, it seems that no one from Velleman is trying to help us with this problem anymore, they do not answer our questions since last December, am i wrong?
Please, if someone have any clue let us know.
By the way, just in case it can be part of the problem, the COM port on my desktop is configured as follows:
bits per second: 9600
data bits: 8
parity: none
stop bits: 1
flow control: none
I’m translating this from spanish, i hope you can understand these parameters. Flow control can be none, Xon/Xoff or hardware.
Because our PIC programmers doesn’t use RS232 protocol, these settings doesn’t matter. The port must just be UART 16550 Compatible.
How come it worked fine before this?
So, long story short, the solution is to short D7?