ok, I think Ive gotten everything coded correctly and such, I have 2 different programmers, the pikit2 and the k150 programmers, and got both programming on linux and from within gEdit. here's the code to add in to qedit's external tools for the k150:
I was tired and just copied tetsujin's python programmer software to the main bin dir using "sudo cp *.* /usr/local/bin" from within the programmer's folder, then I could call it as a normal program by just typing picpro.py. here's the link for those people that use the K150 also:#!/bin/sh
pic="16f628a"
wine c:/pbp/pbpw -e -s -ac:/Program Files/Microchip/MPASM Suite/MPASMWIN -p$pic $GEDIT_CURRENT_DOCUMENT_NAME
var=$GEDIT_CURRENT_DOCUMENT_NAME
var2=${var%???}
outasm=$var2"ASM"
wine c:/Program\ Files/Microchip/MPASM\ Suite/mpasmwin /q /e /l $outasm
outhex=${var2}"HEX"
picpro.py -p /dev/ttyUSB0 --pic_type=$pic -i $outhex
also, for some reason, when the programmer is waiting for the chip inside qEdit, it shows a warning inside the shell output box, but everything works fine, just ignore it and put your chip in, and it'll work fine.
http://sourceforge.net/projects/tets...rogrammer/0.2/
then I added pickit2 by installing the official pk2cmd from microchip's site, and did this mod to the system:
http://gatemaze.blogspot.com/2009/06...er-ubuntu.html
This allows you to run pickit2 as a normal user, which is what we want.
And added this code to the external tools dialog in qEdit:
add the existing post's code into it as "Compile PBP code" and you'll be able to use qEdit as a full ide with built in compiling and direct downloading of the code/hex from within the text editor.#!/bin/sh
pic="16f628a"
wine c:/pbp/pbpw -e -s -ac:/Program Files/Microchip/MPASM Suite/MPASMWIN -p$pic $GEDIT_CURRENT_DOCUMENT_NAME
var=$GEDIT_CURRENT_DOCUMENT_NAME
var2=${var%???}
outasm=$var2"ASM"
wine c:/Program\ Files/Microchip/MPASM\ Suite/mpasmwin /q /e /l $outasm
outhex=${var2}"HEX"
pk2cmd -P$pic -F$outhex -M -R
Bookmarks