In message "Bill Kuncicky" wrote: > I tried doing "xwisp.py verbose go tut2_1" as suggested, and it gets a lot > further. The "verbose" command puts out a lot of information, but > eventually puts out: > > Send_Expect( "3D18w") > . . . (followed by some trackback information) . . . > _main_.Wbus_Protocol_Error: send=' 3D18w' received=' 3D18?' > > Then it quits. What that's saying is, "I tried to write 3D18 into the PIC's program memory, but when I went back to verify it I saw something different." Check that: - Your power supply is outputting between 4.5 and 5.5V and is stable - You've connected all the wires up correctly - Red to +5V - Black to GND - Yellow to /MCLR - Blue to RB7 - Green to RB6 - The PIC is getting power - The PIC isn't faulty - MCLR isn't shorted to either rail - MCLR is pulled up to Vcc via a 1 to 10k resistor It sounds like you might have swapped over the PGD and PGC lines. The WISP628 is getting power (otherwise it wouldn't have responded to the WBUS requests) but it's unable to program the PIC. That means the problem is somewhere between the target device and the WISP. On second thoughts.. it's reading the device ID OK, so the PIC might be code protected. Get Vcc up to 5V, then issue an erase command followed by a blank check. I'm not sure if the Wisp can do a blank-check, but it should be able to do a Bulk Erase, which will wipe out the code protection and any code that's already on the PIC. -- Phil. | Kitsune: Acorn RiscPC SA202 64M+6G ViewFinder philpem@dsl.pipex.com | Cheetah: Athlon64 3200+ A8VDeluxeV2 512M+100G http://www.philpem.me.uk/ | Tiger: Toshiba SatPro4600 Celeron700 256M+40G -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist