Question about Inchworm+ - Page 3 - Electronic Circuits Projects Diagrams Free

3rd October 2007, 09:36 PM

Nope it still diddnt work...

What else to do?

**3v0** · 3rd October 2007, 10:15 PM

I googled and found some info but it only seems to apply to
Microsoft Windows XP Embedded SP2

But it goes like this:

Quote:

Device Manager

When you open the COM port properties in Device Manager, and then click Advanced on the Port Settings tab, you may receive the following error message:
You must have write privileges in the registry for this device in order to modify the devices advanced settings.
This behavior occurs because there are three missing registry subkeys from the following registry key:
HKEY_LOCAL_MACHINE\system\currentcontrolset\enum\a cpi\pnp0501\2
The missing keys are:

RxFIFO
TxFIFO
ForceFifoEnable

If you choose to mess with the registry be sure to back it up first.

Will do a bit more checking to see if I can find this for HOME or PRO. Which are you using ?

**3v0** · 3rd October 2007, 10:18 PM

This seems like a better bet:

"Group Policy" editor.

Quote:

Try it this way:
Go to Start\Run: Type in: gpedit.msc

This will open GP editor.. in the left pane, look in User Configuration \ Administrative Templates \ System\...

In the right pane, look for the key "Prevent access to registry editing tools"

Make sure it's set to "Not Configured"
(If you need to alter it, double click the key and select the appropriate setting).

If this doesn't work, then I suggest you post a HijackThis log in the "Applications and Security" forum so one of the guys there to see what the problem might be regarding possible malware etc.

Good luck....

Edit: Just tried the above on my machine...if I enable the key, I get exactly the same "Registry editing has been disabled by your administrator" message when trying to run regedit. Set it to "Not Configured" ...and bingo..regedit works ok.
(I use XP Pro by the way)..

4th October 2007, 12:54 AM

no, It still isnt working...

WHY!!!

I cant even open gpedit.msc...

4th October 2007, 12:59 AM

It Works On My Other Computer!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!

**3v0** · 4th October 2007, 01:06 AM

Quote:

Originally Posted by Quan

no, It still isnt working...

WHY!!!

I cant even open gpedit.msc...

Why do you expect it to work you still have not fixed the problem with XP??

OK I followed the instructions. You run gpedit.msc
That is you cllick on run from the start menu then type in gpedit.msc
Not sure how how tried to open it. Maybe you got it right but could not tell from your post.

I see that you are having better luck on another computer. Chances are you will hit another snag. Just be cool about it... please

If you choose to go on to be an engineer or scientist you will run into things that do not work on a daily (some times seems hourly) basis. The drama just eats up time and raises the blood pressue.

4th October 2007, 01:13 AM

My other computer has about 1 gig of total software and no internet, so it is a perfect canidate for C programming

I am going to program upstairs, because I have had way better chances upstairs.

4th October 2007, 02:00 AM

Ok I have everything working, but I am recieving this error over and over:

Code:

Clean: Deleting intermediary and output files.
Clean: Deleted file "C:\Documents and Settings\user\My Documents\MPLABIDE\Hello World.asm.mcs".
Clean: Done.
Executing: "C:\Program Files\Microchip\MPASM Suite\MPAsmWin.exe" /q /p16F628A "Hello World.asm" /l"Hello World.lst" /e"Hello World.err"
Error[105]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 3 : Cannot open file (Include File "p 16F628A.inc" not found)
Error[111]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 4 : Missing symbol
Error[113]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 6 : Symbol not previously defined (STATUS)
Error[113]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 6 : Symbol not previously defined (RP0)
Error[113]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 8 : Symbol not previously defined (OPTION_REG)
Error[113]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 10 : Symbol not previously defined (TRISB)
Error[113]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 11 : Symbol not previously defined (STATUS)
Error[113]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 11 : Symbol not previously defined (RP0)
Error[113]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 12 : Symbol not previously defined (PORTB)
Error[173]   C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 15 : Source file path exceeds 62 characters (C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM)
Halting build on first failure as requested.
BUILD FAILED: Wed Oct 03 21:56:05 2007

What should I do?

4th October 2007, 02:20 AM

Well, I made good progress today...

1. Hooked up my HP laserjet 4 that I got for free (they have 3 others that I can have)

2. Connected Inchworm+ up to my other computer

3. Disabled FIFO buffers

4. Other little tasks.

Cant wait until tomorrow to see where I get

**3v0** · 4th October 2007, 02:55 AM

Line by line

It is about to remove files from any previous build
Clean: Deleting intermediary and output files.
Clean: Deleted file "C:\Documents and Settings\user\My Documents\MPLABIDE\Hello World.asm.mcs".
Clean: Done.
It is about to assemble "Hello World.asm"
for the p16F628A
the list file is "Hello World.lst"
errors go to file "Hello World.err"

Executing: "C:\Program Files\Microchip\MPASM Suite\MPAsmWin.exe" /q /p16F628A "Hello World.asm" /l"Hello World.lst" /e"Hello World.err"

It failed because it could not find the include file "p 16F628A.inc"
Error[105] C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 3 : Cannot open file (Include File "p 16F628A.inc" not found)

From Bill's Poster the 16F628A code

Code:

;*** WDT reset toggles RB0
  list p=16F628A
  include <p16F628A.inc>
  __CONFIG 0x3F34

Good bet you have
include <p 16F628A.inc>

You need to pay close attention.

Computers do EXACTLY what you tell them.
If you screw up by one space they crap out.

4th October 2007, 11:16 AM

I did have that!

I fixed the code and it WORKS!

I just gotta create a shorter directory and IT IS ALIVE!!!

**3v0** · 4th October 2007, 11:38 AM

That allows it to build.

Does it program and blink the LED ?

**Krumlink** · 4th October 2007, 09:49 PM

No, I keep getting the error that it doesnt have a valid target Device.

Sorry about blowing up, it appeared that the problem was human error

**Krumlink** · 4th October 2007, 10:15 PM

Here is my code:

Code:

;*** WDT reset toggles RB0
  list p=16F628A
  include <p16F628A.inc>
  __CONFIG 0x3F34
	org			0
	bsf			STATUS, RP0
	movlw		b'00001110'
	movwf		OPTION_REG
	movlw		b'11111110'
	movwf		TRISB
	bcf			STATUS, RP0
	xorwf		PORTB, f
	sleep
	end

And the MPLAB history of what I have done

Code:

Connecting to MPLAB ICD 2
ICD0019: Communications: Failed to open port: (Windows::GetLastError() = 0x2, 'The system cannot find the file specified.
')
ICD0021: Unable to connect with MPLAB ICD 2
MPLAB ICD 2 Ready
ICDWarn0034: Please ensure that your system's serial FIFO buffers are disabled.
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0020: Invalid target device id (expected=0x83, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0020: Invalid target device id (expected=0x83, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0x7)
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x1683, Val Read = 0x0)
ICD0275: Programming failed.
MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0020: Invalid target device id (expected=0x83, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0054: MPLAB IDE has lost communications with the MPLAB ICD 2. Would you like to attempt to reconnect?
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0020: Invalid target device id (expected=0x83, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
ICD0082: Failed MPLAB ICD 2 operation
ICD0275: Programming failed.
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0x7)
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x1683, Val Read = 0x0)
ICD0275: Programming failed.
MPLAB ICD 2 Ready
Reading...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
ICDWarn0038: When using auto-calculate write range, reads cover the entire memory range. Do you wish to continue?
...EEPROM
...Program Memory (0x0 - 0x7FF)
.. Config Memory
...User ID Memory
...Read Succeeded
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming EEPROM Memory
...Programming Program Memory (0x0 - 0x7FF)
...Programming User IDs
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
...EEPROM
...User ID Memory
...Verify Succeeded
Programming Configuration Bits
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
.. Config Memory
Verifying configuration memory...
...Verify Succeeded
...Programming succeeded
04-Oct-2007, 17:18:01

MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming EEPROM Memory
...Programming Program Memory (0x0 - 0x7FF)
...Programming User IDs
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
...EEPROM
...User ID Memory
...Verify Succeeded
Programming Configuration Bits
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
.. Config Memory
Verifying configuration memory...
...Verify Succeeded
...Programming succeeded
04-Oct-2007, 17:25:49

MPLAB ICD 2 Ready
Reading...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
ICDWarn0038: When using auto-calculate write range, reads cover the entire memory range. Do you wish to continue?
...EEPROM
...Program Memory (0x0 - 0x7FF)
.. Config Memory
...User ID Memory
...Read Succeeded
MPLAB ICD 2 Ready
Reading...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...EEPROM
...Read Succeeded
MPLAB ICD 2 Ready
Blank Checking...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x3FFF, Val Read = 0x0)
...Device not blank
MPLAB ICD 2 Ready
Erasing Target Device...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Erase Succeeded
MPLAB ICD 2 Ready
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x1683, Val Read = 0x0)
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming EEPROM Memory
...Programming Program Memory (0x0 - 0x7)
...Programming User IDs
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x1683, Val Read = 0x0)
ICD0275: Programming failed.
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming EEPROM Memory
...Programming Program Memory (0x0 - 0x7)
...Programming User IDs
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x1683, Val Read = 0x0)
ICD0275: Programming failed.
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming EEPROM Memory
...Programming Program Memory (0x0 - 0x7)
...Programming User IDs
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 0x1683, Val Read = 0x0)
ICD0275: Programming failed.
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming EEPROM Memory
...Programming Program Memory (0x0 - 0x7)
...Programming User IDs
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
ICD0200: Operation Aborted (Warning 51).
ICD0275: Programming failed.
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make sure that the target device is connected and properly powered. Select "OK" to continue, or "CANCEL" to abort the operation
ICD0200: Operation Aborted (Warning 51).

Hoped that helps

**3v0** · 4th October 2007, 11:51 PM

Quote:

ICDWarn0020: Invalid target device id (expected=0x83, read=0x0)

This msg is telling you that the ICD2 is not able to read the target chips device ID. It is a show stopper.

You will not be able to program the chip till you get that fixed.

The problem is either the way you have the ICD2 hooked to the target or
the Inchworm itself. Most often it is the first. What are you doing for a
programming cable since you had a broken connector in your kit?

We need to see your schematic.
If you are using the schematic from Bill's poster you should tripple
check each and every connection. Use a Ohm meter,

Till you get a device ID other then zero the code does not matter.

EDIT:

Quote:

Sorry about blowing up, it appeared that the problem was human error

Perhaps an actual apology to the people you barked at would be in order?

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

Similar Threads
Thread	Thread Starter	Forum	Replies	Latest
Capacitor Charge/Discharge question	ThermalRunaway	General Electronics Chat	25	12th August 2008 04:48 PM
Basic Transmission question	CamNuge	General Electronics Chat	2	8th March 2006 10:08 PM
High speed data logging question	cubdh23	Micro Controllers	3	19th August 2004 11:54 AM
Data Logging question with high speed!!!!	cubdh23	General Electronics Chat	4	16th August 2004 06:33 PM
PBX question	waqar	Electronic Projects Design/Ideas/Reviews	0	30th March 2003 06:21 PM

3rd October 2007, 09:36 PM	(permalink)
Quan	Nope it still diddnt work... What else to do?

4th October 2007, 12:54 AM	(permalink)
Quan	no, It still isnt working... WHY!!! I cant even open gpedit.msc...

4th October 2007, 12:59 AM	(permalink)
Quan	It Works On My Other Computer!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!

4th October 2007, 01:13 AM	(permalink)
Quan	My other computer has about 1 gig of total software and no internet, so it is a perfect canidate for C programming I am going to program upstairs, because I have had way better chances upstairs.

4th October 2007, 02:20 AM	(permalink)
Quan	Well, I made good progress today... 1. Hooked up my HP laserjet 4 that I got for free (they have 3 others that I can have) 2. Connected Inchworm+ up to my other computer 3. Disabled FIFO buffers 4. Other little tasks. Cant wait until tomorrow to see where I get

4th October 2007, 02:55 AM	(permalink)
3v0	Line by line It is about to remove files from any previous build Clean: Deleting intermediary and output files. Clean: Deleted file "C:\Documents and Settings\user\My Documents\MPLABIDE\Hello World.asm.mcs". Clean: Done. It is about to assemble "Hello World.asm" for the p16F628A the list file is "Hello World.lst" errors go to file "Hello World.err" Executing: "C:\Program Files\Microchip\MPASM Suite\MPAsmWin.exe" /q /p16F628A "Hello World.asm" /l"Hello World.lst" /e"Hello World.err" It failed because it could not find the include file "p 16F628A.inc" Error[105] C:\DOCUMENTS AND SETTINGS\USER\MY DOCUMENTS\MPLABIDE\HELLO WORLD.ASM 3 : Cannot open file (Include File "p 16F628A.inc" not found) From Bill's Poster the 16F628A code Code: ;* WDT reset toggles RB0 list p=16F628A include <p16F628A.inc> __CONFIG 0x3F34 Good bet you have include <p 16F628A.inc> You need to pay close** attention. Computers do EXACTLY what you tell them. If you screw up by one space they crap out.

4th October 2007, 11:16 AM	(permalink)
Quan	I did have that! I fixed the code and it WORKS! I just gotta create a shorter directory and IT IS ALIVE!!!

4th October 2007, 11:38 AM	(permalink)
3v0	That allows it to build. Does it program and blink the LED ?

4th October 2007, 09:49 PM	(permalink)
Krumlink	No, I keep getting the error that it doesnt have a valid target Device. Sorry about blowing up, it appeared that the problem was human error __________________ MechTronics World of Warcraft is a disease