|
The following information only concerns PiKdev for KDE 3.5.x and must be considered as obsolete
You need the following softwares :
- KDE 3.5.x or newer
- Qt 3.x
-
gputils v0.11.x or newer (gpasm is part of gputils)
- The following support must be present within your system :
ppdev, parport, parport_pc.
Of course, you also need the dev packages wich contain the headers files
of KDE and Qt libraries if you plan to build pikdev from source code.
Pikdev's build from source can be done in a traditionnal way, using a ./configure
script and a Makefile (see below).
However, more and more people have trouble with the
autotools suite, so I have decided to provide a simpler and more reliable way to build/install
the application (see the next section).
The build_pikdev and install_pikdev scripts (since V1.2.1)
The build_pikdev script build the pikdev and pkp applications from source code. The install_pikdev script install all the needed stuff at the proper location.
These scripts are (designed to be) very stupid : they will not try to guess anything about your system,
so they must be manually configured. However, I expect they will be simple to understand and maintain
for most users. They are pre-configured for DEBIAN distributions, under KDE3 or KDE4 and work perfectly
in these situations.
- Build
- Unpack the pikdev tarball
- Go to the src sub directory
- Edit the build_pikdev script (the script contains explanations about what must be configured)
- Type ./build_pikdev
- After a successful build, please send me informations about your configuration (distro, versions, etc.). I will update the script accordingly,
so future users will be happy to get an easy to use script.
- Please note that a non-installed pikdev will not work properly.
- Installation
- Edit the install_pikdev script (configuration of target directories)
- su root
- Type ./install_pikdev
- Return to user mode (exit)
- After a successful install, send me the configuration you have used
Pikdev in a KDE4.x environment
First of all: pikdev works perfectly under KDE4.x.
You just need to install the KDE 3.5.x and Qt 3.x libs.
Depending on the distribution you use, the name of the needed packages may vary. Here are
the names of these packages for a DEBIAN unstable (sid), if you just need to run pikdev.
- Qt 3.5.x : libqt3-mt (libraries)
- KDE 3.xx : kdelibs4-dev (libraries and headers)
If you plan to build from source (recommended) you also need :
- Qt 3.5.x : qt3-dev-tools (various utilities, such as moc)
and libqt3-headers (headers)
To install pkp (the command line version of the PiKdev programming engine),
you just need a gcc 3.x or 4.x C++ compiler (see installation instructions below).
pkp does not use any KDE or Qt libraries/headers.
Installation of Microchip's pk2cmd tool for picKit2
Many people have trouble to get a working pk2cmd. Here are my advices to install pk2cmd properly.
- Verify that the libusb and libusb-dev are installed in your system (the actual name of the needed packages may vary from one distro to another)
- Get pk2cmd V1.20.0 (or higher) source code from Microchip's website
- Unpack the archive
- Goto the created directory
- Build the application with make linux (no ./configure needed .. NICE ! )
- Become root with su
- Install with make linux install (please do not try to bypass this step)
- Return to user mode with exit
- Make sure that your PATH environment variable contains /usr/share/pk2.
If you use bash, you must add the following at the end of the .bashrc AND .bash_profile files : export PATH=$PATH:/usr/share/pk2
- Before trying to use your pickit2 programmer from pikdev, try to use it from command line interpreter:
pk2cmd -P
Programmer's LED should quickly flash, and pk2cmd should issue a Auto-Detect: No known part found. message. If this is not the case, the pikdev's picKit2 support will not work.
Parallel port
PiKdev uses the parallel port in user mode (/dev/parport device).
The parport devices are automatically detected since version 0.3.4.
If this device is not present in your filesystem, you can easily
create it with the mknode command (with root privileges):
(Note: /dev/parportN is a character device whose
major number is 99 and minor number is N)
mknod /dev/parport0 c 99 0 (first parallel port)
mknod /dev/parport1 c 99 1 (eventually, second parallel port)
Moreover, be sure that the device is RW enabled:
chmod a+rw /dev/parport0
The previous informations are obsolete for most modern Linux distro (parport device is now automagically created)
Finally, you must have the ppdev support.
This is necessary for using parallel ports in user mode.
This support can be compiled into the linux kernel, or loaded as modules
(depending on your system, you might have to update /etc/modprobe.preload
or /etc/modules).
Installation as root from tarball:
- Unpack the tarball:
tar xzvf pikdev-[VERSION].tar.gz
- Enter the PiKdev directory:
cd pikdev-[VERSION]
- Configure the software: (prefix is mandatory)
./configure --prefix=[DISTRIB-SPECIFIC-PREFIX]
If the kde-config script is available in your system, you can directly use it to set the correcty prefix :
./configure --prefix=`kde-config --expandvars --prefix`
- Compilation:
make
- Become root:
su
Password: [root password]
- Installation:
make install
- Return to user mode:
exit
Note: The following DISTRIB-SPECIFIC-PREFIXs seem to be correct :
- Mandrake 9.x,10.x : /usr
- Red Hat 8.x, 9.x : /usr
- Suse 8.x : /opt/kde3
- Debian : /usr
Another solution to obtain the correct prefix is to use the
kde-config command:
kde-config --expandvars --prefix
will report the correct distribution specific prefix.
and
kde-config --expandvars --path data
will report the correct distribution specific location for .rc files.
CAUTION
You might have to use an installation prefix which is not mentionned in the
previous list. Please send me informations if this is the case.
If this prefix is not consistant with the way your distribution uses KDE,
PiKdev will not find the files pikdev-main.rc and pikdev-prg.rc
and will not be able to construct its graphical interface (No menu, no icon!).
In this case, just copy these files in your home directory or use the good
prefix, or use the installation method exposed below.
Before changing the installation prefix, do not forget to uninstall PiKdev
to keep your system clean.
make uninstall (with root privileges)
Installation of pkp
The installation of pkp is totally independant from the PiKdev installation.
To compile pkp :
- Unpack the tarball:
tar xzvf pikdev-[VERSION].tar.gz
- Enter the source directory:
cd pikdev-[VERSION]/pikdev
- Compile pkp and the programming engine : (you might have to edit Makefile.pkp before this)
make -f Makefile.pkp
- Installation:
su
Password: [root password]
make -f Makefile.pkp install
- Return to user mode:
exit
pkp uses two (hidden) configuration files :
- .pkprc : This files contains pins affection for your hardware.
I don't provide any .pkprc file because pkp creates
this file if it doesn't exist.
You can move this file to your home directory, so it will be seen by pkp from any subdirectory.
.pkprc is very simple and only contains informations about pins and port device name.
Please edit this file to fit your hardware configuration. Here is the default .pkprc config file :
# parallel port device
# (use /dev/parports/x if your system is devfs based)
port=/dev/parport0
# pins assignation :
# negative value means inverted signal
# the following values are correct for
# classic D. Tait's hardware
type=parallel
vpp=-5
vdd=-4
clock=3
datao=2
datai=10
.pkpdefaults : This file only contains the name of the current pic device and the name of the current
hex file. This file is created by pkp in the current directory, so each project may have its own default parameters.
Feel free to
send reports about (successful or not)
installations.
|