Post by thread:[PIC]:Wisp628, some (minor ?) problems.

Hi all. Yes, maybe I'd better send these questions directly to Wouter van Ooijen, but I thought that maybe there are some "out there" that have built and uses Wouter's Wisp628 PIC programmer. Anyway, here is my story... I'v built my copy of Wisp628 (from the design on the web page and with a home made PCB made in Eagle). It looks as it's starting up, the LED on pin-6 on the DB15 flashes twice on power up. The "WISP PORT COM1 TERM 1200" works and characters are returned, *but* not exactly those typed. I'v tried to see any pattern with help from a ASCII table, such as any 7/8 bit or par y/n errors, but couldn't. When trying "WISP GO B84A-1", with a PICF84A on a breadboard according to the description on Wouter's web page, it says : c:\Program\xwisp> wisp go b84a-1 wisptool 4.07 (1) hardware Wisp682 1.00 (2) <timestamp> (00127460) fatal: comm timeout on receive : check.... (3) (1) comes from the PC tool, right ? (2) comes from the Wisp682 programming hardware, right ? (3) comes aprox half a second after (2) If I re-execute the GO command, I only get (1) and (3), it seems as the Wisp682 is stuck in some software loop. After power off/on, I get the #(2) message again. The same thing if I execute a TERM command before the GO, it seems as it's stuck in the TERM routine. When I execute a second TERM command, I get the last ESC character from the last TERM command, so it seems to me at least. I'v also tried the TALK command, and characters A-F (both lower and upper case) are retured in upper case, but typing "G" hangs the programmer with the LED on pin-6 on. Power cycling get's it going again. Well, that's it ! The PC hardware is OK. I used the same COM port to program the F682 for the Wisp682 using the PIC card from Elektor as published earlier this year. Built for the F84A, but the F682 programmed and verifyed just OK using IC-prog version 1.04C. Best Regards Jan-Erik Svderholm. Jan-Erik Svderholm S:t Anna Data tel : +46 121 42161 mob : +46 70 5241690 -- http://www.piclist.com hint: To leave the PICList spam_OUTpiclist-unsubscribe-requestTakeThisOuTmitvma.mit.edu

Try 'WISP VERBOSE LOG X GO ...', this will show a lot of logging which is also written to file X. This might give a clue where the communication goes wrong. OK, that gave the following output : 23:03:08.74 (00188740) init port 01 at 03F8 baudrate 19200 start 23:03:08.74 (00188740) init port end 23:03:09.17 (00189170) line break start 23:03:09.50 (00189500) line break end 23:03:09.50 (00189500) wake up device 0000 23:03:09.50 (00189500) send [0] 30 23:03:09.61 (00189610) send [0] 30 23:03:09.72 (00189720) send [0] 30 23:03:09.83 (00189830) send [0] 30 23:03:09.94 (00189940) send [h] 68 23:03:10.05 (00190050) send [0] 30 23:03:10.16 (00190160) send [0] 30 23:03:10.27 (00190270) send [0] 30 23:03:10.38 (00190380) send [0] 30 23:03:10.49 (00190490) clear receive 23:03:10.60 (00190600) receive [0] 30 23:03:10.71 (00190710) clear receive end 23:03:10.71 (00190710) send [v] 76 23:03:10.82 (00190820) clear receive 23:03:10.93 (00190930) receive [V] 56 23:03:11.04 (00191040) clear receive end 23:03:11.04 (00191040) start waitsendchar 23:03:11.04 (00191040) fast clear receive 23:03:11.04 (00191040) clear receive end 23:03:11.04 (00191040) send [q] 71 23:03:11.04 (00191040) sending done 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [Q] 51 23:03:11.04 (00191040) receiving done 23:03:11.04 (00191040) fast clear receive 23:03:11.04 (00191040) clear receive end 23:03:11.04 (00191040) send <next> 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) done <next> 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [1] 31 23:03:11.04 (00191040) done <receive> 23:03:11.04 (00191040) send <next> 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) done <next> 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [.] 2E 23:03:11.04 (00191040) done <receive> 23:03:11.04 (00191040) send <next> 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) done <next> 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [0] 30 23:03:11.04 (00191040) done <receive> 23:03:11.04 (00191040) send <next> 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) done <next> 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [0] 30 23:03:11.04 (00191040) done <receive> 23:03:11.04 (00191040) device request 0000 response 1.00 23:03:11.04 (00191040) start waitsendchar 23:03:11.04 (00191040) fast clear receive 23:03:11.04 (00191040) clear receive end 23:03:11.04 (00191040) send [t] 74 23:03:11.04 (00191040) sending done 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [T] 54 23:03:11.04 (00191040) receiving done 23:03:11.04 (00191040) fast clear receive 23:03:11.04 (00191040) clear receive end 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive hex [20] 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [W] 57 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [i] 69 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [s] 73 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [p] 70 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) wait for char 23:03:11.04 (00191040) receive [6] 36 23:03:11.04 (00191040) send [n] 6E 23:03:11.04 (00191040) wait for char 23:03:11.10 (00191100) receive [2] 32 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive [8] 38 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive hex [20] 23:03:11.10 (00191100) start waitsendchar 23:03:11.10 (00191100) fast clear receive 23:03:11.10 (00191100) clear receive end 23:03:11.10 (00191100) send [v] 76 23:03:11.10 (00191100) sending done 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive [V] 56 23:03:11.10 (00191100) receiving done 23:03:11.10 (00191100) fast clear receive 23:03:11.10 (00191100) clear receive end 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive hex [20] 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive [1] 31 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive [.] 2E 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive [0] 30 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive [0] 30 23:03:11.10 (00191100) send [n] 6E 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive hex [20] 23:03:11.10 (00191100) start waitsendchar 23:03:11.10 (00191100) fast clear receive 23:03:11.10 (00191100) clear receive end 23:03:11.10 (00191100) send [0] 30 23:03:11.10 (00191100) sending done 23:03:11.10 (00191100) wait for char 23:03:11.10 (00191100) receive [0] 30 23:03:11.10 (00191100) receiving done 23:03:11.10 (00191100) start waitsendchar 23:03:11.10 (00191100) fast clear receive 23:03:11.10 (00191100) clear receive end 23:03:11.10 (00191100) send [0] 30 23:03:11.10 (00191100) sending done 23:03:11.10 (00191100) wait for char 23:03:11.15 (00191150) receive [0] 30 23:03:11.15 (00191150) receiving done 23:03:11.15 (00191150) start waitsendchar 23:03:11.15 (00191150) fast clear receive 23:03:11.15 (00191150) clear receive end 23:03:11.15 (00191150) send [f] 66 23:03:11.15 (00191150) sending done 23:03:11.15 (00191150) wait for char 23:03:11.15 (00191150) receive [F] 46 23:03:11.15 (00191150) receiving done 23:03:11.15 (00191150) start waitsendchar 23:03:11.15 (00191150) fast clear receive 23:03:11.15 (00191150) clear receive end 23:03:11.15 (00191150) send [x] 78 23:03:11.15 (00191150) sending done 23:03:11.15 (00191150) wait for char 23:03:12.20 (00192200) fatal: communication timeout on receive : check the power and the serial line to the WISP hardware and retry Jan-Erik Svderholm S:t Anna Data tel : +46 121 42161 mob : +46 70 5241690 -- http://www.piclist.com hint: To leave the PICList .....piclist-unsubscribe-requestKILLspam@spam@mitvma.mit.edu

>> 23:03:11.15 (00191150) send [x] 78 >> 23:03:11.15 (00191150) sending done >> 23:03:11.15 (00191150) wait for char >> 23:03:12.20 (00192200) fatal: communication timeout on >> receive : check the power and the serial line to >> the WISP hardware and retry > >The programmer does not answer on the X (go to programming mode) >command. That definitely looks like a hardware problem. Check your >hardware, especially around the charge pump (caps/diodes) and the >transistor. Well well, I found a short between the line for programing power (after the charge pump) and one of the Xtal pins ! I supose that as soon as the charge pump started, the osc stopped... Now I get the follwing when trying to program a 16F84A : C:\Program\XWisp>wisp target 16f84a go example\b84a-1 wisptool 4.07 hardware Wisp628 1.00 target specified as 16f84a Target appears to be a 23:24:04.22 (01444220) fatal: Target does not match command line Hm... Jan-Erik. -- http://www.piclist.com hint: To leave the PICList piclist-unsubscribe-requestKILLspammitvma.mit.edu

Jan-Erik Soderholm <.....jan-erik.soderholmKILLspam.....telia.com> wrote : > Now I get the follwing when trying to program a 16F84A : > > C:\Program\XWisp>wisp target 16f84a go example\b84a-1 > wisptool 4.07 > hardware Wisp628 1.00 > target specified as 16f84a > Target appears to be a > > 23:24:04.22 (01444220) fatal: Target does not match command line > I now also tried a F628 and got the following : C:\Program\XWisp>wisp go example\b628-1 wisptool 4.07 hardware Wisp628 1.00 target auto-detect ... target is a 16f628 rev 00 patch end patch program fuses a=0000 d=FFFF 23:41:21.87 (02481870) fatal: send [w] 01110111 expected [w] 01110111 received [?] 00111111 : check the connection to the target and retry C:\Program\XWisp> Jan-Erik. -- http://www.piclist.com hint: To leave the PICList EraseMEpiclist-unsubscribe-requestspam_OUTTakeThisOuTmitvma.mit.edu

Hi. I think this message got lost (or never sent, I'm not sure)... Jan-Erik. {Quote hidden}>> 23:03:11.15 (00191150) send [x] 78 >> 23:03:11.15 (00191150) sending done >> 23:03:11.15 (00191150) wait for char >> 23:03:12.20 (00192200) fatal: communication timeout on >> receive : check the power and the serial line to >> the WISP hardware and retry > >The programmer does not answer on the X (go to programming mode) >command. That definitely looks like a hardware problem. Check your >hardware, especially around the charge pump (caps/diodes) and the >transistor. Well well, I found a short between the line for programing power (after the charge pump) and one of the Xtal pins ! I supose that as soon as the charge pump started, the osc stopped... Now I get the follwing when trying to program a 16F84A : C:\Program\XWisp>wisp target 16f84a go example\b84a-1 wisptool 4.07 hardware Wisp628 1.00 target specified as 16f84a Target appears to be a 23:24:04.22 (01444220) fatal: Target does not match command line Hm... Jan-Erik. -- http://www.piclist.com hint: To leave the PICList piclist-unsubscribe-requestspam_OUTmitvma.mit.edu

>4. Did you connect the transistor OK? The 2N has a pinout that differs >from the BC's that are more common in europe. I only had aprox 8.5 V. The BC547B had it's E and C reversed (of course, as you sad :-) ). Now, with the BC turned 180 degrees, my F628 does the "blink-the-LED" tune !! Now I could turn to my main 16F870 based project !! May I at last also thank you for your very fine support, Wouter ! Jan-Erik. -- http://www.piclist.com hint: To leave the PICList @spam@piclist-unsubscribe-requestKILLspammitvma.mit.edu

Hi again... Well, a few days ago my Wisp628 worked and I programmed a F628 without any problems. Now, after a few changes to the PC hardware, I can't get it working again. Maybe not exactly a PIC problem, but I'm sure there many out there who understands PC hardware. I'v changed PC hardware, from a Compaq Deskpro (166 Mhz) to a "no-name", A-open based AMD-K6 450 Mhz system. Same OS as before (plain Win98). Problem : can't get any communication to the wisp hardware to work. The command "wisp port x term 1200" returns any character typed at the keyboard, no matter the "port x" setting or even if the cable to the wisp628 is connected or not !! If I connect my Elektor PICee card, and start IC-prog, I can use the "Hardware check" funtion in IC prog to toggle the "Data out", "Clock" and "MCLR" lines as verifyed by the LED's on the Elektor card. I have also used COM1 as serial console on my Alpha OpenVMS system with no problem, so I don't *think* I'm having any problem with my PC hardware. "wisp verbose port 1 term 1200" gives the following output : 21:38:42.24 (02322240) init port 01 at 03F8 baudrate 1200 start 21:38:42.24 (02322240) init port end 21:38:42.24 (02322240) receive hex [1B] 21:38:43.29 (02323290) send [A] 41 21:38:43.29 (02323290) receive [A] 41 21:38:43.45 (02323450) send [A] 41 21:38:43.45 (02323450) receive [A] 41 21:38:43.56 (02323560) send [A] 41 21:38:43.56 (02323560) receive [A] 41 21:38:44.06 (02324060) send [ ] 1B 21:38:44.06 (02324060) receive hex [1B] 21:38:44.17 (02324170) send [ ] 1B Using "...port 2..." gives the same output, just with "...init port 02..." instead. When running these tests, COM1 was "open", and COM2 was connected to the wisp628. But it doesn't matter if the wisp628 is connected or not, I get the same output anyway. I'v also reinstalled wisp629 and the two Phyton install kits. How can wisp get any input when there is nothing connected ? Jan-Erik Svderholm S:t Anna Data tel : +46 121 42161 mob : +46 70 5241690 -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email KILLspamlistservKILLspammitvma.mit.edu with SET PICList DIGEST in the body

OK. I'v now got Xwisp to program my 16F870. The LED blinks... For some reason I had to change to COM2 from COM1, I got "Access denied" on COM1. Don't know why right now. (I had missunderstod your docs, I thought Xwisp just was a "frontend" to wisp.exe, and using Xwisp shouldn't make any difference regarding the port access. Well, it seems I was wrong...) And yes, I used Reflection (a windows application) to access my OpenVMS systems on the COM1 port yesterday. IC-prog is at least a windows prog, and probably uses the WinAPI calls to access the port(s)... Anyway, I'll stick with XWisp for the time beeing ! And, as I sad last time, many thanks for your support ! Jan-Erik Svderholm S:t Anna Data tel : +46 121 42161 mob : +46 70 5241690 -- http://www.piclist.com hint: To leave the PICList RemoveMEpiclist-unsubscribe-requestTakeThisOuTmitvma.mit.edu