gnupic: [gnupic] Unable to program pic


Previous by date: 5 Jan 2006 09:30:34 +0000 Re: [gnupic] gpsim installation problem, S W Collier
Next by date: 5 Jan 2006 09:30:34 +0000 KTechlab 0.3 Released, David Saxton
Previous in thread: 5 Jan 2006 09:30:34 +0000 [gnupic] Unable to program pic, Mikael Wämundson
Next in thread: 5 Jan 2006 09:30:34 +0000 Re: [gnupic] Unable to program pic, Mark Rages

Subject: RE: [gnupic] Unable to program pic
From: "Chen Xiao Fan" ####@####.####
Date: 5 Jan 2006 09:30:34 +0000
Message-Id: <7D4AB72251D4D949AB2732ABEABDA54F12FF8F@PFSG-MX1.ap.p-f.biz>

Have you tried out Mark's Python based pyk? It is much better 
than usb_pickit. It works under Linux and Windows but it may
work under Mac OS X as well. You need to have Python/SWIG
installed other than libusb.

You can also try Microchip's Mac OS X application for PICkit 1.
It is not based on libusb.

Regards,
Xiaofan

> -----Original Message-----
> From: Mikael Wämundson ####@####.####
> Sent: Wednesday, January 04, 2006 12:34 AM
> 
> I'm using the PICKit 1 with a OS X system. When programming in  
> assembler and using gpasm to compile the files I can program my chip  
> (16f684) using usb_pickit. But I'm now trying to program in C using  
> picc-lite. I can compile a hex-file, but when I'm trying to flash it  
> over to my pic (using usb_pickit) the chip is left un-touched. I get  
> no error message when flashing the pic, but when I use usb_pickit -- 
> extract and then gpdasm to check what's on the chip, it is empty? Is  
> it something wrong with the hex-file I try to flash? Suggestions?
> /Mikael

> 

Previous by date: 5 Jan 2006 09:30:34 +0000 Re: [gnupic] gpsim installation problem, S W Collier
Next by date: 5 Jan 2006 09:30:34 +0000 KTechlab 0.3 Released, David Saxton
Previous in thread: 5 Jan 2006 09:30:34 +0000 [gnupic] Unable to program pic, Mikael Wämundson
Next in thread: 5 Jan 2006 09:30:34 +0000 Re: [gnupic] Unable to program pic, Mark Rages


Powered by ezmlm-browse 0.20.