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. 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. I think this takes care of 3.3V problem. I don't know if my program actually got programmed but it doesn't seem to work. Here I just want RB3 to go High. Originally this was going to be an led blinker, but I just want to see if it works. #include main() { //static bit b = 0; int i; TRISB = 0x00; // PortB output for (i=0; ;i++) { if (i % 10 == 0) { RB3 = 1; } } } I also use RC oscillator. I have 10K connected to CLKIN and the other end is connected to 39pf capacitor and 5V, the capacitor is connected to the ground. Pretty standard RC osc. When I measure voltage on CLK out, it's always 0V. Also RB3 is always 0 volts. So I don't know if the pic was actually programmed. What is going on? 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. 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 >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