Welcome
Username or Email:

Password:


Missing Code




[ ]
[ ]
Online
  • Guests: 28
  • Members: 0
  • Newest Member: omjtest
  • Most ever online: 396
    Guests: 396, Members: 0 on 12 Jan : 12:51
Members Birthdays:
No birthdays today

Next birthdays
05/04 Matthew T. (35)
05/04 Amrit Deshmukh (60)
05/05 Alexandre (32)
Contact
If you need assistance, please send an email to forum at 4hv dot org. To ensure your email is not marked as spam, please include the phrase "4hv help" in the subject line. You can also find assistance via IRC, at irc.shadowworld.net, room #hvcomm.
Support 4hv.org!
Donate:
4hv.org is hosted on a dedicated server. Unfortunately, this server costs and we rely on the help of site members to keep 4hv.org running. Please consider donating. We will place your name on the thanks list and you'll be helping to keep 4hv.org alive and free for everyone. Members whose names appear in red bold have donated recently. Green bold denotes those who have recently donated to keep the server carbon neutral.


Special Thanks To:
  • Aaron Holmes
  • Aaron Wheeler
  • Adam Horden
  • Alan Scrimgeour
  • Andre
  • Andrew Haynes
  • Anonymous000
  • asabase
  • Austin Weil
  • barney
  • Barry
  • Bert Hickman
  • Bill Kukowski
  • Blitzorn
  • Brandon Paradelas
  • Bruce Bowling
  • BubeeMike
  • Byong Park
  • Cesiumsponge
  • Chris F.
  • Chris Hooper
  • Corey Worthington
  • Derek Woodroffe
  • Dalus
  • Dan Strother
  • Daniel Davis
  • Daniel Uhrenholt
  • datasheetarchive
  • Dave Billington
  • Dave Marshall
  • David F.
  • Dennis Rogers
  • drelectrix
  • Dr. John Gudenas
  • Dr. Spark
  • E.TexasTesla
  • eastvoltresearch
  • Eirik Taylor
  • Erik Dyakov
  • Erlend^SE
  • Finn Hammer
  • Firebug24k
  • GalliumMan
  • Gary Peterson
  • George Slade
  • GhostNull
  • Gordon Mcknight
  • Graham Armitage
  • Grant
  • GreySoul
  • Henry H
  • IamSmooth
  • In memory of Leo Powning
  • Jacob Cash
  • James Howells
  • James Pawson
  • Jeff Greenfield
  • Jeff Thomas
  • Jesse Frost
  • Jim Mitchell
  • jlr134
  • Joe Mastroianni
  • John Forcina
  • John Oberg
  • John Willcutt
  • Jon Newcomb
  • klugesmith
  • Leslie Wright
  • Lutz Hoffman
  • Mads Barnkob
  • Martin King
  • Mats Karlsson
  • Matt Gibson
  • Matthew Guidry
  • mbd
  • Michael D'Angelo
  • Mikkel
  • mileswaldron
  • mister_rf
  • Neil Foster
  • Nick de Smith
  • Nick Soroka
  • nicklenorp
  • Nik
  • Norman Stanley
  • Patrick Coleman
  • Paul Brodie
  • Paul Jordan
  • Paul Montgomery
  • Ped
  • Peter Krogen
  • Peter Terren
  • PhilGood
  • Richard Feldman
  • Robert Bush
  • Royce Bailey
  • Scott Fusare
  • Scott Newman
  • smiffy
  • Stella
  • Steven Busic
  • Steve Conner
  • Steve Jones
  • Steve Ward
  • Sulaiman
  • Thomas Coyle
  • Thomas A. Wallace
  • Thomas W
  • Timo
  • Torch
  • Ulf Jonsson
  • vasil
  • Vaxian
  • vladi mazzilli
  • wastehl
  • Weston
  • William Kim
  • William N.
  • William Stehl
  • Wesley Venis
The aforementioned have contributed financially to the continuing triumph of 4hv.org. They are deserving of my most heartfelt thanks.
Forums
4hv.org :: Forums :: Computer Science
« Previous topic | Next topic »   

JDM programmer not working?

1 2 
Move Thread LAN_403
dan
Sun Aug 13 2006, 01:47AM Print
dan Registered Member #223 Joined: Mon Feb 20 2006, 06:42PM
Location: Ottawa, Ontario, Canada
Posts: 125
I seen the pic newb thread and I thought I would give pics a try. I built the 'JDM' programmer on solderless breadboard but for some reason every programming software I have tried doesn't detect it. With winpic it gives the error:
"Couldn't find "devices\PIC16F684.dev", please borrow/copy from MPLAB !
Failed read back of DATA line (HIGH) !
WARNING: Could not initialize programmer !"
Others simply say couldn't find programmer. I triple checked all the wiring and all the components seem to check out. however instead of the speced transistors I had to use NTE replacement parts NTE123ap which is supposed to be able to replace the BC547B. The same is true for the four 1N4148 diodes so I used NTE519's. all the diodes have a measured .7v drop and I tested the transistors by switching a LED with them and they seem to work. The zeners and capacitors also check out. There doesn't seem to be too much information on debugging these programmers. Probably because they are so simple. I was thinking it was a software problem but I have tested the programmer on two different computers and I get the same error. One was running Windows 95 the other XP.

Any idea's of what I could be doing wrong?
Back to top
Carbon_Rod
Sun Aug 13 2006, 02:25AM
Carbon_Rod Registered Member #65 Joined: Thu Feb 09 2006, 06:43AM
Location:
Posts: 1155
May help:
Link2

good luck,
Back to top
Wolfram
Sun Aug 13 2006, 02:47AM
Wolfram Registered Member #33 Joined: Sat Feb 04 2006, 01:31PM
Location: Norway
Posts: 971
That modification is fine if you want to reprogram PICs that are set to internal oscillator and no MCLR, for everything else the standard circuit is fine.

Have you tried with WinPic800? (not the same as WinPic) Link2
Back to top
dan
Sun Aug 13 2006, 03:27AM
dan Registered Member #223 Joined: Mon Feb 20 2006, 06:42PM
Location: Ottawa, Ontario, Canada
Posts: 125
Well I tried winpic800 and still no luck. This may be a dumb question but does a pic need to be connected in order for the programmer to be detected by the software. I have tried using an adapter and connecting a 16F684 to the programmer but still no luck. Its as if the programmer is not even there according to the software.(yes I checked the cable) I don't really want to risk blowing a pic until I know this thing is going to work. I'm suspecting it is a hardware problem but I still haven't located it. It's most likely the transistors. Even though they are marked as replacement parts for the BC547B they might not be exact an substitute. I'll probably abandon the JDM because I cannot find the BC547B at my local electronic store. The RCD programmer seems promising as it supports two of the pics I want to program (12F675 and the 16F684) although not the 16F877a :(
Back to top
...
Sun Aug 13 2006, 08:12AM
... Registered Member #56 Joined: Thu Feb 09 2006, 05:02AM
Location: Southern Califorina, USA
Posts: 2445
Yes the pic needs to be connected for the programmer to be detected.

I don't think the transistors are critical, but having enough voltage on the serial port is. Put a meter on the mclr pin and the vdd pin of the pic and see if the voltages are correct (while programming)

Good luck!
Back to top
Wolfram
Sun Aug 13 2006, 02:16PM
Wolfram Registered Member #33 Joined: Sat Feb 04 2006, 01:31PM
Location: Norway
Posts: 971
The transistors are not critical at all, any standard small signal transistor is gonna work, like 2N3904, 2N2222 etc...
Back to top
dan
Sun Aug 13 2006, 05:25PM
dan Registered Member #223 Joined: Mon Feb 20 2006, 06:42PM
Location: Ottawa, Ontario, Canada
Posts: 125
Apparenly there isn't enough programming voltage. I only measure ~10v on MCLR while programming. I guess I'm going to need a programmer with an external power supply. Thanks for the help.
Back to top
Bjørn
Sun Aug 13 2006, 05:36PM
Bjørn Registered Member #27 Joined: Fri Feb 03 2006, 02:20AM
Location: Hyperborea
Posts: 2058
Most if not all FLASH based PICs don't use the programming voltage directly, they have their own voltage generators. They only require the programming voltage to be a few volts above the supply voltage. The different datasheets have all the information.
Back to top
rupidust
Sun Aug 13 2006, 07:29PM
rupidust Banned
Registered Member #110 Joined: Fri Feb 10 2006, 12:23AM
Location: Banned City
Posts: 85
10v is marginal yet sufficient. I just attached a potentiometer to the Vpp output of my ICD2 programmer. I knew Vpp could go down to 10.5v, but I was surprised to see that after tweeking the pot down to 9.4v my 16F648A still programmed just fine repeatedly.

If voltage is not an issue then it may be signal or port access. If you have a scope, no, use a scope to view the signal. See if the MCLR line is rippling, fluctuating, or pulsating. MCLR should drop to near 0v, toggle to Vpp (12v nominal) a few times, and remain at Vpp without disruption then toggle a few times at the end. Rippling will cause errors and represents a lack of driving current, current leakage, and driving voltage from lower power RS232 Usart chips in todays PCs. Fluctuating, like elongating triangular waves, will cause errors and represents serious timing delays due to loads exceeding the RS232 I/O lines. Pulsating, like signal a HIGH for a second then signal oscillating like RS232 data signals, represents a possible driver issue on the PC side. Next is to monitor both Data and Clock lines. Their should be signal on both those lines during programming. If no signal is seen, back track to the com port lines which control Data and Clock. If the port lines have no signal, remove all loads from these lines. If problem still persist, its a com port driver access issue. If the RS232 interface is from a USB cable converter, this is very likely. Also, XP requires driver acces from these programs to access the RS232 com ports. Some of the programs require a third party com port privilege access driver to be seperatly installed after app installation.

There has been alot of issues with the JDM and its varients. Fed up myself, I broke down and got a PIC-ICD2 USB/RS232.
Back to top
Part Scavenger
Sun Aug 13 2006, 11:13PM
Part Scavenger Registered Member #79 Joined: Thu Feb 09 2006, 11:35AM
Location: Arkansas
Posts: 673
Try a different computer. I can't get any of my programmers to work on my upstairs computer or my laptop.
Back to top
1 2 

Moderator(s): Chris Russell, Noelle, Alex, Tesladownunder, Dave Marshall, Dave Billington, Bjørn, Steve Conner, Wolfram, Kizmo, Mads Barnkob

Go to:

Powered by e107 Forum System
 
Legal Information
This site is powered by e107, which is released under the GNU GPL License. All work on this site, except where otherwise noted, is licensed under a Creative Commons Attribution-ShareAlike 2.5 License. By submitting any information to this site, you agree that anything submitted will be so licensed. Please read our Disclaimer and Policies page for information on your rights and responsibilities regarding this site.