bump ^^
I suspect it may be due to a conflict in the config word.
In your PicProg settings on the screenshot above, you have “Write Config.Word” checked and the HEX for the options you are writing is 3FFF.
The options are different in the code you are writing: (cl2-025.hex)
__CONFIG _CP_OFF & _WDT_OFF & _PWRTE_ON & _INTRC_OSC_NOCLKOUT & _LVP_OFF & _BODEN_ON & _MCLRE_OFF
…which I ‘THINK’ should be 3F50…
So, which takes precedence? The settings in PicProg, or the options in the code?
I don’t know, so I can’t answer that one.
What I would do, is disable the “Write Config.Word” and just use the options in the code you are writing.
All this assumes your board IS now working correctly…Have you gone through the demo files with the supplied 627 PIC?
HTH,
Mickster.
Thanks for that, it works perfectly now. Woo! Mickster, i thought velleman staff are supposed to patrol these boards? Why did it take so long for a reply, only for it to be a normal end user. Granted you solved all my problems, and i love you for it, this is ore of a dig at velleman, surely they should have replied a long time ago…?
Ah well, all is working now, thanks mickster, i owe ya one!
dragon
Note from Velleman: The main purpose of this board is to allow people to help eachother out, to share experiences, give hints, etc… We simply do not have the means to dig into everybodies individual problem. Most common problems are answered. Btw, thanks Mickster for your continued interest and support.
Glad it worked out for you dragon.
A note to everyone:
As stated by VEL417, this forum cannot cover every possible and theoretical problem that may occur with their VM111 or K8048 kit…the kit especially, as there are so many things that can go wrong during the build.
Also, Velleman have no control over the code flashed to the PIC’s and therefore cannot provide support for user’s programs.
However, I think there is a possible solution to prevent future frustrations…
It would be wonderful if someone at Velleman, or another user with more spare time than I have, could collate all the common problems and solutions into one post, then Velleman could make it into a ‘Sticky’ which user’s having problems could be directed to…sort-of like this:
COMMON PROBLEMS AND SOLUTIONS.
- Are you using an adequate power supply - unregulated 12v required
- Does LD7 light up?
- Does LD9 flash when SW5 in Run position?
- Does LD9 flash & LD8 light up when SW5 in Prog position?
- Do VR1 or VR2 get hot? Are they in the correct positions?
VR1=78L12, VR2=78L05 - Are there any solder-bridges on the PCB? Check CAREFULLY.
- Does the pre-loaded demo program work when SW5 is in Run position?
- Are you using a real COM port?
- Does PicProg communicate with the hardware?
- Is the COM cable wired correctly?
- Is T3 ‘C557B’ ?
- Are the black bands on the diodes aligned with the thick end on the silkscreen?
- Are your Config Word settings in PicProg correct?
- Are your Config Word settings in your code correct?
- Are you using EITHER #12 OR #13, not both?
etc.
etc.
At the foot of the ‘Sticky’, it should be requested that the whole list is worked through and the conditions fully met, before requesting further assistance. This may alleviate the same questions being raised again and again.
N.B. Some sections may not be applicable to VM111
If the ‘Sticky’ was labelled “New Members Please Start HERE”, or something similar, it may be more helpful than having to trawl though past posts.
HTH,
Mickster.
I agree with making that list available from an official velleman troubleshooting faq for the k8048. I’ve been having the same issues (exactly as Dragon2309) with no resolution so far. I will try the config word thing tonight.
I have had some hardware issues surrounding diodes as well. I installed them at the correct orientation, but ended up having to replace two entirely as they were showing no directional bias at all. Maybe I got a bunch of bad diodes.The zener is working perfectly however.
I only bought this kit because the k8055 has worked well for me. (though even with that kit one of the darlington arrays was non-functional)
I would hate to have to give up on this board, but it’s been about 9 or 10 hours of frustration, and soon it will seem worth it to go for a board that can handle the 18fs, the wider 16f877s and the narrow small chips as well with the ZIF socket. I’ve seen some pretty nice looking parallel port programmers.
I suppose ICSP can answer some of the limitations… but only if the board starts working on the socketed ones first.
I finally got it working. As a note, never have two pics in at the same time.
One would think the jumpers would activate on the pic they select, but it’s not the case. if two pics are present, there is no way you will read or write properly.
^^
That’s actually quite a good point mikey.
Although the silkscreen says “Use X1 only for one socket at the same time.”, it doesn’t stipulate that other PIC’s have to be removed in order for the selected PIC to be successfully programmed.
However, once you get more familiar with PIC’s from differing families, you will recognise that the slight differences between each of the RISC instructions, per family, can create confusion…
I am not able to pin down the exact PIC family and instruction set right now, but I can sort-of recall problems where BODEN & BOREN (Brown Out Detection Enable & Brown Out Reset Enable) can cause problems when they get mixed up in the Config Word of your code, where a particular family is concerned, to use just one example.
Maybe 627/8 & 627/8A?
You need to look at the applicable datasheet for the PIC you are using and adapt any differences in the instruction set, to suit your code.
HTH,
Mickster.
P.S. From looking at the jumpers, the tracks on the lower side of the PCB are all interlinked to X1, apart from the 8P socket.
Q. Is X1’s sole purpose on the board to enable a PIC program to run, or does it play any part in the Programming process?
Maybe one of the VEL’s can answer this…