Help Getting Inchworm to Debug. - Electronic Circuits Projects Diagrams Free

ravix · 28th February 2007, 10:45 PM

So I finally got my inchworm hooked up to a PIC and at first everything went well. I built the circuit around the PIC and I am able to read/program it perfectly. However, after duplicating the Hello World program from blueroom's PDF, I didn't get any action on the LED. I tried to debug the PIC and now I am getting errors/lockups in the program, but ONLY in debug mode.

Specifically, the MBLAB says: "ICDWarn0015: Program memory has changed since last program operation? Continue with Debug operation?" when I try to step through the program.

Does anyone know why this occurs?

I'm sooo close!

-Eric

**3v0** · 28th February 2007, 11:07 PM

Are you sure you did not see an error in the OUTPUT window about not being able to enter the debug mode. If so the most common problem in a bad config value or a problem with connecting the osc.

Did you use one of the processors on the INCHWORM hello world poster ? That is to say what PIC are you using ?

ravix · 1st March 2007, 12:49 AM

I'm sorry I forgot to mention which PIC I am using. I am using the PIC16F88, with the config set to use in the internal oscillator. Although there is no schematic on the poster for my PIC (only the firefly, which uses the same one) I was able to determine how to hookup the PIC from the data sheet and the other diagrams.

I am definitely able to enter the debug mode, the output window looks as follows:

Quote:

Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
Target Device PIC16F88 found, revision = Rev 0x8
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready

Do I need to add anything to the circuit to enable debug mode?

edit: AH! I started changing some configuration options, based on the template Microchip provides, and I got the error you specified:

Quote:

MPLAB ICD 2 Ready
ICDWarn0015: Program memory has changed since last program operation? Continue with Debug operation?
Running Target
ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information.
ICD0069: Debug: Unable to run target
MPLAB ICD 2 Ready

Any ideas now?

Pommie · 1st March 2007, 01:28 AM

The first error is normally cause by pressing a key while the asm window has focus. This changes the asm file and causes the error. Recompile/assemble to fix it.
The second error has various causes - debug turned off - master clear turned off - reserved location being used (SFR and program space). Have you got a nop at location zero as required with some chips.

Mike.

blueroomelectronics · 1st March 2007, 01:32 AM

From MPLAB

Debugger / ICD2

Debugger / Settings / Program / Automatically program after sucessful build (make sure it's checked)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Title	Starter	Forum	Replies	Latest
More inchworm help needed	Andy1845c	Micro Controllers	24	6th March 2007 01:40 AM
Configuration Bits (Nigel's tutorials and Inchworm)	lpinkai	Micro Controllers	7	23rd January 2007 06:39 PM
Unable to connect to Inchworm	Hedos	Micro Controllers	15	23rd December 2006 04:26 PM
Inchworm built: Next step	Hedos	Micro Controllers	3	18th December 2006 12:30 AM
BS2p and GSM modem together. Help!!! :roll:	ice-egoz	Micro Controllers	0	20th July 2004 07:38 AM

28th February 2007, 10:45 PM	(permalink)
ravix	Help Getting Inchworm to Debug. So I finally got my inchworm hooked up to a PIC and at first everything went well. I built the circuit around the PIC and I am able to read/program it perfectly. However, after duplicating the Hello World program from blueroom's PDF, I didn't get any action on the LED. I tried to debug the PIC and now I am getting errors/lockups in the program, but ONLY in debug mode. Specifically, the MBLAB says: "ICDWarn0015: Program memory has changed since last program operation? Continue with Debug operation?" when I try to step through the program. Does anyone know why this occurs? I'm sooo close! -Eric

28th February 2007, 11:07 PM	(permalink)
3v0	Are you sure you did not see an error in the OUTPUT window about not being able to enter the debug mode. If so the most common problem in a bad config value or a problem with connecting the osc. Did you use one of the processors on the INCHWORM hello world poster ? That is to say what PIC are you using ?

1st March 2007, 01:28 AM	(permalink)
Pommie	The first error is normally cause by pressing a key while the asm window has focus. This changes the asm file and causes the error. Recompile/assemble to fix it. The second error has various causes - debug turned off - master clear turned off - reserved location being used (SFR and program space). Have you got a nop at location zero as required with some chips. Mike.

1st March 2007, 01:32 AM	(permalink)
blueroomelectronics	From MPLAB Debugger / ICD2 Debugger / Settings / Program / Automatically program after sucessful build (make sure it's checked) __________________ Bill Smart Kits build Smart People http://www.blueroomelectronics.com