Were your self-tests passing in mplab?


On 10/2/06, Rolf <learr@rogers.com> wrote:
>
> Shawn Wilton wrote:
> > No, the pins don't have any load on them.
> >
> > I followed peoples advice to pull the PIC from the board and actually
> put
> > the ICD in-circuit.  Put some wires on the SMD pads and now I am
> currently
> > trying to get the ICD debugger to work.  But it just gives me this
> output:
> >
> > Connecting to MPLAB ICD 2
> > ...Connected
> > Setting Vdd source to MPLAB ICD 2
> > Target Device PIC12F675 found, revision = Rev 0x2
> > ICDWarn0044:  Target has an invalid calibration memory value (0x0).
> > Continue?
> > ...Reading ICD Product ID
> > Running ICD Self Test
> > ...Passed
> > MPLAB ICD 2 Ready
> > Programming Target...
> > ICDWarn0044:  Target has an invalid calibration memory value (0x0).
> > Continue?
> > ...Validating configuration fields
> > Connecting to debug executive
> > Entering Debug Mode
> > ...Programming GOTO 0x00 command
> > ICD0083: Debug:  Unable to enter debug mode.  Please double click this
> > message for more information.
> > MPLAB ICD 2 Ready
> > Resetting Target
> > Entering Debug Mode
> > ...Programming GOTO 0x00 command
> > Resetting Target
> > MPLAB ICD 2 Ready
> > MPLAB ICD 2 Ready
> > Entering Debug Mode
> > ...Programming GOTO 0x00 command
> >
> >
> > All the self-tests pass.  I have this connected to the circuit.  I have
> > tried both with and w/o the target board powered and have also tried w/o
> the
> > debug header connected to the board.  I would think that even if the
> target
> > board were not connected, I would still be able to launch in to the
> debugger
> > and watch my code execute on the attached pic12f675 header board.
> >
> > Any help or ideas, as always, appreciated.
> >
> >
> Hi Shawn.... others.
>
> I have been doing battle with my ICD2 for the last couple of days as
> well. I have been having intermittent problems, sometimes it works fine
> for a few hours, then, it begins failing with one type of error (unable
> to switch mode=TM, also unable to identify processor) or some such
> message, it does that for a  few hours, then it does a message stack
> very similar to your's, Shawn, with the ICDWawn0044, the ICD0083, and
> sometimes the ICD0053 thrown in too.
>
> I tracked mine back to the RJ11 connector in the ICD2. If I push the
> ICSP cable hard in to the ICD2, it works, but if I tug gently on it so
> it rests against the RJ11 retaining clip, it stops working. I think the
> actual RJ11 socket is not "springy" enough, or something. But, you can
> push the cable in until it clicks, then push it that extra millimeter
> more..... works for me.
>
> For the record, I don't have an oscilloscope, and I tracked this back by
> putting LED's on the ICSP lines, and figures out that Vpp was not being
> driven properly.... and playing with the cable caused the Vpp to go
> high. ICSP works find while driving LED's off *each* line through 330Ohm
> resistance....
>
> This may or may not be your problem.
>
> Rolf
>
>
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>



-- 

Shawn Wilton (b9 Systems)
http://b9Systems.com  <- New web page
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist