Searching \ for '[PIC] PICkit 2 will get better soon' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: 'PICkit 2 will get better soon'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] PICkit 2 will get better soon'
2005\11\21@195117 by Chen Xiao Fan

face
flavicon
face
The next revision of PICkit 2 firmware will support
the 18F USB chips as well quite some popular 16F and
18F chips. It is scheduled to be released by end of
this year.

With the next firmware, PICkit 2 will be truly a
hobbyists' programmer. It supports most popular
under-40pin (read: DIP version available) modern
Flash PICs.

Together with Wisp628 (using xwisp2 1.8.1), I think
these two programmers are worth a try if you want to
try a new PIC programmers. Wisp628 is easier to be
built by oneself. PICkit 2 (US$35+shipment) is good if
you want to buy a ready-made programmer.

If one wants to deal with dsPICs, then Olin's EasyProg
seems to be the way to go now. It is a pity that
no alternative host software has been developed
for EasyProg under Linux. PICkit 2 and Wisp628 work
under Linux.

If one wants to have a debugger, MPLAB ICD2 (original
or clones) is the only relatively cheap solutions.
Microchip has not opened the protocol of ICD2 so it
is not working under Linux.

Regards,
Xiaofan

Existing chip support of PICKit 2 V1 firmware:
PIC10F200/202/204/206/220/222
PIC12F508/509/510
PIC16F54/57/59/505/506

PIC12F629/635/675/683
PIC16F630/636/676
PIC16F684/688/689/690/785
PIC16F913/914/916/917/946

New 16F support to be added by next release:
PIC16F627A/628A/648A
16F73/74/76/77
16F818/819
16F873A/874A/876A/877A

18F devices to be added by next release:
DS39592:
PIC18F1220/1320/2220/2320/4220/4320
DS39622:
PIC18F2221/2321/2410/2420/2455/2480/2510/2520/
PIC18F2525/2580/2585/2610/2620/2680
PIC18F4221/4321/4410/4420/4455/4480/4510/4520/
PIC18F4525/4580/4585/4610/4620/4680

2005\11\21@210735 by Mike Young

picon face
I notice the 18Fx550 missing from the list. They will be missed.

----- Original Message -----
From: "Chen Xiao Fan" <spam_OUTxiaofanTakeThisOuTspamsg.pepperl-fuchs.com>
To: "Microcontroller Discussion List - Public. (E-mail)" <.....piclistKILLspamspam@spam@mit.edu>
Sent: Monday, November 21, 2005 6:51 PM
Subject: [PIC] PICkit 2 will get better soon


> The next revision of PICkit 2 firmware will support
> the 18F USB chips as well quite some popular 16F and
> 18F chips. It is scheduled to be released by end of
...
{Quote hidden}

2005\11\21@212729 by Chen Xiao Fan

face
flavicon
face
Oops, I forget to put 18F2550/4550 there. They will be
supported. It is a bit troublesome since I can not
copy/paste from the DS39622E directly with Adobe
Acrobat Reader 6.

The 18F support should be:
18F devices to be added by next firmware release:
DS39592:
PIC18F1220/1320/2220/2320/4220/4320
DS39622:
PIC18F2221/2321/2410/2420/2455/2480/2510/2520/
PIC18F2525/*2550*/2580/2585/2610/2620/2680
PIC18F4221/4321/4410/4420/4455/4480/4510/4520/
PIC18F4525/*4550*/4580/4585/4610/4620/4680

Regards,
Xiaofan

-----Original Message-----
From: piclist-bouncesspamKILLspammit.edu
Sent: Tuesday, November 22, 2005 10:08 AM
To: Microcontroller discussion list - Public.
Subject: Re: [PIC] PICkit 2 will get better soon

I notice the 18Fx550 missing from the list.
They will be missed.

Mike Young

2005\11\22@073435 by olin piclist

face picon face
Chen Xiao Fan wrote:
> If one wants to deal with dsPICs, then Olin's EasyProg
> seems to be the way to go now. It is a pity that
> no alternative host software has been developed
> for EasyProg under Linux.

The protocol is open and my Windows source is also available.  Some people
here had expressed interest in creating Linux versions a few months ago, but
I haven't heard anything in a while.  Has anyone tried running my Windows
executables on a Windows emulator on Linux?  My stuff doesn't cheat and uses
normal Windows calls, so this should work in theory.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products

2005\11\22@191502 by Chen Xiao Fan

face
flavicon
face

>Olin wrote:
>
>The protocol is open and my Windows source is also available.  Some people
>here had expressed interest in creating Linux versions a few months ago,
but
>I haven't heard anything in a while.  Has anyone tried running my Windows
>executables on a Windows emulator on Linux?  My stuff doesn't cheat and
uses
>normal Windows calls, so this should work in theory.

I tried last time and the programmer portion was not working (pic_read
and pic_prog) under Wine. The fact I was using a Wisp628 with EasyISP
should not matter but I am not 100% sure about this. Anyway xwsip2
Windows was also not working under Wine (back at that time there was
no xwisp2 under Linux). So honest stuffs using Win32 API are not working
under Wine. ;-(

It is reported that IC-Prog (using a kernel driver to direct write to
the port) works under Wine using JDM programmer.

It is also a bit strange that complex stuff like IE6 and others can
work under Wine without much problems. Anyway, Wine is getting better
and better so one day they may be able to solve the problem.

By the way, some parts of the EmbedInc programming environment
like prepic work under Wine.

Regards,
Xiaofan

2005\11\23@073136 by olin piclist

face picon face
Chen Xiao Fan wrote:
> I tried last time and the programmer portion was not working (pic_read
> and pic_prog) under Wine.

What exactly do you mean by "not working"?  Did it just hang?  Emit an error
message?  Something else?

> By the way, some parts of the EmbedInc programming environment
> like prepic work under Wine.

The main difference between PIC_PROG and PREPIC in this case is probably
that PREPIC doesn't try to do any external I/O.  PREPIC just does some file
I/O which I imagine is more likely to work correctly on an emulator.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products

2005\11\23@083544 by Xiaofan Chen

face picon face
On 11/23/05, Olin Lathrop <.....olin_piclistKILLspamspam.....embedinc.com> wrote:
> Chen Xiao Fan wrote:
> > I tried last time and the programmer portion was not working (pic_read
> > and pic_prog) under Wine.
>
> What exactly do you mean by "not working"?  Did it just hang?  Emit an error
> message?  Something else?

It can not find the programmer. The error message under Wine DOS window
is as following.

"C:\embedinc\com>pic_read -SIO 1 -hex read.hex
fixme:comm:GetCommProperties (0x44 0x7789ed50 )
fixme:comm:SetupComm insize 2048 outsize 2048 unimplemented stub
No response was received from the programmer.  The programmer may
be powered off or not connected to COM1.
Error occurred on attempt to open a new use of the PICPRG library.
*** Program aborted on error. ***"

Similar error message for xwisp2w.

"C:\xwisp2181>xwisp2w port 1 read test.hex
fixme:ntdll:FILE_AsyncReadService unexpected status 00000000
xwisp2 version 1.8.01 for Windows (Oct 24 2005, Open Watcom C 1.30)
SendReceiveSlow read timeout, 0 bytes received
Failed to activate Wbus device
xwisp2 failed after 0.84 seconds, rc 23!"

Therefore I think Wine's serial support is not so good.

Regards,
Xiaofan

2005\11\23@085249 by olin piclist

face picon face
Xiaofan Chen wrote:
> "C:\embedinc\com>pic_read -SIO 1 -hex read.hex
> fixme:comm:GetCommProperties (0x44 0x7789ed50 )
> fixme:comm:SetupComm insize 2048 outsize 2048 unimplemented stub
>
> ...
>
> Therefore I think Wine's serial support is not so good.

Yeah, it's a good clue when it says "fix me".

I'm a bit surprised that it's complaining about a call to GetCommProperties,
since that's pretty main stream.  The SetupComm call is a bit more unusual
in that I specifically try to set the input and output buffers to at least
2K bytes.  This isn't actually required by the PICPRG software, but is done
deep down in the serial line support of my OS interface layer.  A while back
I had problems on some systems that decided to provide only very small
serial buffers.  I then changed my low level Windows interface to always
request 2Kbytes.  There is a way for Windows to tell the app to stick it,
and my software can handle that.  That would sound like an easy expedient
for Wine.  It can use a fixed size and just refuse requests to change it.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products

2005\11\23@091611 by Xiaofan Chen

face picon face
Not so sure if this is related but Wine's pipe support is also broken.
The following is the error message from MPLAB IDE 7.21 under Wine.

Clean: Deleting intermediary and output files.
Clean: Done.
Executing: "C:\MCC18\bin\mcc18.exe" -p=18F4550 "main.c"
-fo="C:\MCHP~3R5\fw\Boot\_output\main.o" /i"C:\MCHPFSUSB\fw\Boot" -scs


File or path is not found
Thread would not exit normall
y.
Could not read language tool output from pipe.
(0)
BUILD FAILED: Wed Nov 23 22:05:23 2005

Regards,
Xiaofan

2005\11\23@094354 by Xiaofan Chen

face picon face
On 11/23/05, Olin Lathrop <EraseMEolin_piclistspam_OUTspamTakeThisOuTembedinc.com> wrote:
{Quote hidden}

I am interested to get pic_read and pic_prog work under Linux with
Wine. Therefore I googled a bit and it is said that latest Wine is better.
Then I just upgraded to the latest Wine version. It seems the serial support
is now much better. At least it find the Wisp628 and device ID with
xwisp2w. I guess it might work after some tweaking. This may not
be of much use since xwisp2 works natively under Linux. Still this
can be a good start for porting pic_read and pic_prog to work under
Wine even it still failed to find the programmer now. At least the
warning messages are gone.

Accoding to the README file of xwisp2w, Jan-Erik Soderholm
write the Windows code.

Regards,
Xiaofan

C:\xwisp2181>xwisp2w baud 9600 com1 erase
xwisp2 version 1.8.01 for Windows (Oct 24 2005, Open Watcom C 1.30)
Programmer Wisp628, firmware version 1.10
Detected target: 18F252 revision 04 (ID=0404)
SendReceiveFast read timeout, received 0 of 5
xwisp2 failed after 15.58 seconds, rc 21!

C:\embedinc\com>pic_read -sio 1 -hex test.hex
No response was received from the programmer.  The programmer may be powered
off or not connected to COM1.
Error occurred on attempt to open a new use of the PICPRG library.
*** Program aborted on error. ***

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...