I'm happy no announce that my native Wisp port to
Windows (port done on W2K), is now running.
The major problems (apart from the HD crash :-) ) was that
I'm a non-C-expert, and I was mixing up UCHAR with PUCHAR
and when to use and when *not* to use the "&" character
in parameter passing to functions...
Anyway, I have been testing with a 18F1320 which runs
just fine. Tested with both my old home built Wisp and an
"original" ready built Wisp from Wouter I got today.
Tested using a standard COM port and using USB-RS232
I've made an agreement with Rob Hamerling, that I'll
host the Windows port for the time beeing on my web site,
I'll put it up tomorrow, I'll let you know. I will provide
the EXE and a full source kit for those interested. I have
just some minor tidying up of the code to do.
So, now it's a single 130Kb EXE and a 14Kb CFG (with the
PIC part specifics), instead of the 40Mb Python install
with close to 3000 files :-) :-) And (on my system) it runs
in about half the time.
Since someone asked off-list...
No, there is *no* GUI.
At the moment... :-)
Example of flashing one of Wouters example programs
for the Dwarfs (DN003.HEX):
C:\>xwisp2 port 3 go dn003
XWisp2 version 1.3.03 (Mar 22 2004, LCC)
File DN003.Hex loaded and Intel Hex format conforming
Total of program and data memory: 110 bytes
Programmer Wisp628, firmware version 1.09
Detected target: 18F1320 rev 02 ('07C2')
Transferring image to 18F1320 via Wisp628
Transferring program OK!
Verifying program OK!
Transferring data OK!
Verifying data OK!
Transferring ID OK!
Verifying ID OK!
Transferring fuses OK!
Verifying fuses OK!
Write-Verify terminated successfully in 1.11 seconds
Putting target in run mode
XWisp2 terminated successfully in 2.88 seconds
I feel here that I must say that the "port" wasn't from the
Python version, but from the port Rob Hamerling did
to OS/2, and it was already written in C. My task was to
add conditionaly compiled code for the Windows API
specific parts. Mainly low level serial port handling. 95%
of the code is still Robs original C code. And half of my time
was spent reading "msdn.microsoft.com"... :-)
> That s great news!
I had also thought that, if someone else had done it :-) :-)
Well actualy, I *do* think that also.
And about a GUI. Anoter way would be to write it as a
"system tray" task. So you could point on the Wisp-icon
in the "tray", right click and select "Go" from the pull-up-menu.
Or "Select File", "Select Port" or whatever. But the command
line version/interface will of course still be there.
And, at last, *this* port was to support a specific project,
I've no idea what will happen in the future...
Recently someone mentioned that MPLAB calls an external program when it
uses some specific mircochip programmer (picmaster pro?). The command
line interface of that program is documented. Now replace that
executable by a suitable ZPL executable :)
Wouter van Ooijen wrote :
> > And about a GUI.
> Recently someone mentioned that MPLAB calls an external
> program when it uses some specific mircochip programmer
> (picmaster pro?). The command line interface of that program
> is documented. Now replace that executable by a suitable
> ZPL executable :)