On 3/16/07, alan smith wrote: > Client calls.....your new board doesnt work...few of the outputs aren't on. > > *sigh* ....its the same board....smaller.....etc..... > > hello client...let me see....hmmm...your right, the two outputs are not being turned on...oh...its B6 and B7. Lets reburn the code to it. Hooks up the pickit....same thing. Board works fine except those two outputs. > > Lets power the board this time. Wierdness...pickit doesn't like it.....wont find the target.... > > OK...here...lets use my ICD2. Rewire the connector for the pickit pinout.....hey it works! > > > OK, so group.....does the pickit2 leave B6 and B7 in some unknown state? I havent tried it myself with my pickit...havent even unwrapped it actually....purchased in case I needed to support this client. Actually the pickit programmed board didnt even cycle code in the normal run mode, but ran ok in the test mode cept for these two outputs. > The PICkit 2 leaves those in a high-impedance state as long as the power is on. Do you have Vdd_TGT connected on the PICkit ICSP connector? If not, you need to have the PICkit's target power "on" while the target is running. So the PICkit's Vdd_TGT must be up while the target circuit is running, even if the circuit supplies its own power. See emitter-followers Q2,3,5 in the PICkit 2 schematic. Note that the target's power can be allowed to "backflow" into the PICkit to take care of this. Regards, Mark markrages@gmail -- Most of the time, for most of the world, no matter how hard people work at it, nothing of any significance happens. -- Weinberg's Law -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist