On Tue, Mar 18, 2003 at 04:04:54PM -0500, Konstantin Klitenik wrote: > I just built a QandD programmer. Since the port is 3.3V, I just used > transistors, where the port pin is connected to the base. Through a base resistor I hope? > I just inverted > the pin in FPP, so when the pin is high, it opens up the transistor and > grounds RB(X), otherwise it's 5V. The +5 is through a pullup resistor I hope. > I think this takes care of 3.3V problem. Maybe. What happened when you attempted to program. Just to be clear: You have base resistors, pullups and transistors for each of Vpp (MCLR), CLK (RB6), and DATA (RB7). You then tested each line from the debug/test section. You then loaded a program and the programmer software indicated that it loaded? Right? > I don't know if my program actually got programmed but it doesn't seem to > work. Well you're stuck at this level of testing until you are sure. > [Program deleted for brevity.] > I'm just beginning with > microcontrollers and it's frustrating. I don't have a 74HCT53, I have > 74LS244N, i think that's also a flip flop. It's a buffer. And LS parts don't really solve the 3.3V/5V issue anyway because it has TTL inputs and outputs. > Can I use that. Also, I don't > have 16f628, i only have 16f84. I'd really like to get this QandD > programmer working. Help?....??? Thanks You're on the right track using the transistors as level shifters. The reason I use HCT parts is because it handles all of the issues of the transistors without inversion, resistors, and pullups. Since I pretty sure the level shifting is your problem, you may want to invest some time and energy getting an HCT573 (or similar) instead of banging your head in the direction you're currently headed. But as Olin loves to point out, this is an instance of TANSTAAFL: There Ain't No Such Thing As A Free Lunch. Programmers such as the PicStart+, the Warp-13, and the Wisp628 cost money because the designers spend a lot of sweat and blood making sure that their hardware works in tough environments. The cost of systems like the Basic Stamp and the OOPic are high for the same reason. The cost of using low end programmers is patience. I've added some autodetection and debugging features to picprg2.3d to assist in the process of getting the programmer going. It'll tell you what it reads during autodetect. All ones (3fff) or all zeros are a clear indication that everything isn't working correctly. So it's decision time. If you just want to program microcontrollers, you may want to consider buying a programmer. However if like many of us hobbyists where your time is much less valuable than your cash, then take a deep breath and solve the problem of getting the actual programming hardware and software working in concert, and leave the microcontroller programming to a time where the programmer is stable. BAJ > > > >From: Byron A Jeff > >Reply-To: pic microcontroller discussion list > >To: PICLIST@MITVMA.MIT.EDU > >Subject: Re: [PIC]: PARPIC AND TAIT's FPP programmer > >Date: Tue, 18 Mar 2003 15:01:10 -0500 > > > >On Tue, Mar 18, 2003 at 02:14:55PM -0500, Konstantin Klitenik wrote: > > > Well, I built PARPIC, and i've tested everything with a multimeter. > > > >Good. > > > > > All the > > > connections are fine. The voltage on the parallel port is 3.3V but I > >heard > > > people built and used PARPIC successfully. > > > >I took a look at the schematic. This is definitely your problem. > > > >Others who were successful were probably using a 5V parallel port. > > > > > When I try to use WinIcProg, it > > > doesn't detect the port. When the autodetect is on, it says "port: > >none." > > > It seems like it is something with the software. I've done all the test > > > things in FPP and all the settings are fine. > > > >But it doesn't matter. It's a hardware problem. I'm getting my info from > >http://members.optushome.com.au/donmck/dtait/icp84.html > > > >I know for a fact that David's PARPIC was designed at a time when almost > >every PC was 5V. So the parallel port was 5V too. But the world has > >changed. > > > > > > > Although I don't understand > > > the point of D3 in the PARPIC schematic, it's not in the parpic setting > >in > > > the FPP. Anyway, does anyone else know what could be wrong? I have > > > giveio.sys installed. > > > >It's not software. Your parallel port's interaction with the PIC is doing > >you > >in. > > > >Humor me. Spend an extra few minutes and build a THVP here: > > > >http://www.finitesite.com/d3jsys/proghvp.html > > > >It specifically addresses your problem parallel port. Then try again. I'll > >bet that you'll have better luck. > > > >Remember to keep the cable short. > > > >BAJ > > > > > >From: Byron A Jeff > > > >Reply-To: pic microcontroller discussion list > > > >To: PICLIST@MITVMA.MIT.EDU > > > >Subject: Re: [PIC]: PARPIC AND TAIT's FPP programmer > > > >Date: Tue, 18 Mar 2003 11:51:17 -0500 > > > > > > > >On Tue, Mar 18, 2003 at 10:52:01AM -0500, Konstantin Klitenik wrote: > > > > > I've used define/test and all the pins are configured correctly. I > >have > > > > > also tried to use picprg and it doesn't detect the programmer. I've > > > >been > > > > > trying to figure out what's wrong for hours and I'm getting > >frustrated. > > > >I > > > > > tried building a QandD and there isn't much you can get wrong there, > >but > > > >it > > > > > still doesn't work. > > > > > > > >OK. Here's the next phase. You need a voltmeter for it. > > > > > > > >Redo your define/text mode. But this time record the actual low and > >high > > > >voltages for each pin on the socket. > > > > > > > >Here's the theory (sight unseen): Your parallel port outputs a 3.3V > >high > > > >signal. High enough for TTL printers, not high enough for programming > >PICs. > > > > > > > >Further details about the situation on the TLVP page: > > > > > > > >http://www.finitesite.com/d3jsys > > > > > > > >BAJ > > > > > > > > > > > > > > > > > > > > >From: Byron A Jeff > > > > > >Reply-To: pic microcontroller discussion list > > > > > > > >To: PICLIST@MITVMA.MIT.EDU > > > > > >Subject: Re: [PIC]: PARPIC AND TAIT's FPP programmer > > > > > >Date: Tue, 18 Mar 2003 10:25:43 -0500 > > > > > > > > > > > >On Tue, Mar 18, 2003 at 02:14:10AM -0500, Konstantin Klitenik > >wrote: > > > > > > > I think the problem is that FPP doesn't even recognize anything > >on > > > > > >Parallel > > > > > > > port. I checked everything again. I made the cable less then 2 > > > >feet. > > > > > > > > > > > >Good. That eliminates one variable. > > > > > > > > > > > > > The > > > > > > > way the error comes up, it doesn't even try to program. As soon > >as > > > >I > > > > > >press > > > > > > > program it says "Failed to program code!" > > > > > > > > > > > >This isn't a really useful error message unfortunately. About 12 > > > >different > > > > > >items have to be perfect for the programmer to work. > > > > > > > > > > > > > All the settings are fine. > > > > > > > > > > > >Are you sure? Have you actually used the test mode to wiggle each > >line > > > >and > > > > > >verify that it's the correct pin on the programming socket. Any of > >a > > > > > >misconfig, > > > > > >miswire, or wrong polarity on any of the programming lines will > >cause > > > >the > > > > > >programmer to fail. > > > > > > > > > > > >Trust me, it's worth taking the 30 minutes required to test each > >line > > > >from > > > > > >config to socket. You won't be sorry. > > > > > > > > > > > > > I set > > > > > > > the pic to 16f84 which is what I have and chose parpic as the > > > >hardware. > > > > > > > > > > > >That isn't sufficient for initial testing. You still need to verify > > > >that > > > > > >each line is configured and wired properly. This can only be done > >by > > > >actual > > > > > >testing in test mode. > > > > > > > > > > > >This failure mode in FPP is one reason why I put chip autodetect in > >my > > > > > >latest > > > > > >version of picprg. If it doesn't autodetect, then you don't even > >bother > > > >to > > > > > >try to program. > > > > > > > > > > > >Verify everything. I can almost promise you that you have a > >misconfig > > > >or > > > > > >miswire somewhere in your setup. > > > > > > > > > > > >BAJ > > > > > > > > > > > >-- > > > > > >http://www.piclist.com hint: PICList Posts must start with ONE > >topic: > > > > > >[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: > >->Ads > > > > > > > > > > > > > > > _________________________________________________________________ > > > > > Tired of spam? Get advanced junk mail protection with MSN 8. > > > > > http://join.msn.com/?page=features/junkmail > > > > > > > > > > -- > > > > > http://www.piclist.com hint: PICList Posts must start with ONE > >topic: > > > > > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: > >->Ads > > > > > > > >-- > > > >http://www.piclist.com hint: PICList Posts must start with ONE topic: > > > >[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads > > > > > > > > > _________________________________________________________________ > > > Protect your PC - get McAfee.com VirusScan Online > > > http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 > > > > > > -- > > > http://www.piclist.com hint: PICList Posts must start with ONE topic: > > > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads > > > >-- > >http://www.piclist.com hint: PICList Posts must start with ONE topic: > >[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads > > > _________________________________________________________________ > Help STOP SPAM with the new MSN 8 and get 2 months FREE* > http://join.msn.com/?page=features/junkmail > > -- > http://www.piclist.com hint: PICList Posts must start with ONE topic: > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads