PP06 Homepage KDE GUI Front end for programmer |
The linux software is still at an early stage. I don't use it regularly. This information is subject to change, and applies at V1.09. I am using SuSe 8.1, 2.4.19, Asus L3 P4M-1700 laptop.
The console version is PPLIN. It is built using the free Borland Kylix3 C Builder. All versions use the same sources, platform specific code is in separate files.
I directly write to the printer port at /dev/ports. PPLIN needs to have permissions to be able to do this. You need to know that your ports are at the correct address
As we write straight to /dev/port, there is no protection or interlocking. PPLIN will write straight through the printer drivers, and vice versa. Its up to you to prevent clashes over the port. This is important for a multi users system.
Currently (v1.09) the linux version will not read DOS (CRLF) files. If you get a warning message like "Not a hex code", then you need to convert the file to unix line terminators using DOS2UNIX. try dos2unix -n infile.hex outfile.hex .
KPicProg is a simple GUI front end. I recommend that you use it to get going, and get an idea of pplin's capabilities. However you will save your self a whole lot of time by making shell scripts to program specific devices/projects directly
Launch it from the console. All output will be displayed on the console, so you need to be able to see it!
If you want to launch it from an icon or short cut, then you want to give it a terminal to show its output on. Try: konsole -T Pic Programmer -e kpicprog
It uses the Kaptain console scripting engine. You need the kaptain package (V0.6 on) and it will use konqueror to display html help pages.
To develp the kpicprog script use the -V --test options to just display the command lines rather than executeing them. eg kpicprog -V --test
You will probably want to change the script to set the default values you want to use, or make custom versions of it for specific projects.
In particular watch the Block CP option. This masks out the CP bits. The intention is to prevent them being set when using the windowed Eprom (-JW) parts. Because these bits are buried (non-eraseable), inadvertantly setting the CP bit effectively destroys the part. If you aren't going to use -JW parts, then you can remove this option from the script
C Compiler: B.Lo.C... coming soon
Linux Assembler: GPASM is several times faster than Microchips excrably slow MPASM. Very compatible with MPASM, except for a couple of silent bugs.