gnupic@linuxhacker.org

gnupic@linuxhacker.org


Subject: Re: Nearly done picp 18F252/452 & similar parts
From: Alexandre Pereira Nunes
Date: Fri, 19 Sep 2003 14:32:24 -0300

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Dattalo wrote:

>On Wed, 17 Sep 2003, Alexandre Pereira Nunes wrote:
>
>  
>
>>Hi,
>>
>>Our tests with the 18F support on picp seems to be almost done, no know 
>>problems exists on this area.
>>    
>>
>
>This sounds really great! Do you know when you might be releasing this 
>code?
>
>Regards,
>Scott
>
>  
>

What about now ?

Available at: http://www.alexnunes.brturbo.com/picp-20030919-01-all.diff.gz.
There's a Makefile patch that I hope no one will need at:  
http://www.alexnunes.brturbo.com/picp-20030919-01-Makefile.diff.gz.


But I'm releasing it as an experimental, beta-quality release, since 
I've made some changes in order to support older pics again (It was 
broken), and I only did some naive tests in order to make sure it was 
working as expected.

There are two patches, the one ending with '-all' is the required stuff. 
The -Makefile patch is only to revert some changes I've made to the 
Makefile, and will probably be of interest only to non-linux users, in 
the case the Makefile supplied on the first patch fails for some reason. 
This will revert to picp-0.5d Makefile,  in this case make sure that the 
original picp's Makefile works for you before complaining to me

The patch ending in -all is against picp-0.5d unmodified sources, you'll 
need to get it first.

Uncompress both the picp sources and the patch file, then enther the 
picp sources directory, and type:

patch --verbose -p1 </where/is/picp-20030919-01-all.diff

then a 'make' should do the trick.

You'll need to have the patch tool. I guess it's on diffutils package, 
for most distributions.

Adjust "/where/is" accordingly to place where the uncompressed patch 
file is

If for some reason, anyone cannot use patch, please drop me an email, 
I'll be glad send the modified picp as a tarball.

For now, there are some know bugs:

- - Writing ID Locations for anything other than 18f252/18f452 is probably 
broken.
- - Writing Configuration bits or ID Locations from the command line (via 
- -wc and -wi parameters, respectively) is probably broken. It should work 
from the hex file, except for the bug spooted above;

And some Caveats:

- - Support for other parts than 18F252, 18F452 and 16F628 was not 
empirically tested during tests;
- - Support for other 18Fxxx/xxxx parts is not tested. Support for 18Fxx20 
parts is experimental, intended to ICSP only. There's only one 
definition, 18F6520. The other 18F parts may require some tuning.

TODO list:

- - Verify after programming and before wirting configuration bits;
- - Write to EEPROM data area;
- - Some other things I can't remember of right now

Feedback is appreciated, for both working and non-working scenarios.

To file a bug report, mail-me with the session logged using the new 
parameter -d twice (i.e., for ./picp /dev/ttyS0 18F252 -wp, use ./picp 
/dev/ttyS0 18F252 -d -d -wp ...). '-d' stands for 'debug'. Also provide 
as much data as you can.

I only have here the 18F252, 18F452, 16F628 and 12F629 parts for testing.

In that case, you can log the failing operation with the -d -d scheme 
above, and mail me along with an mplab session log doing the same 
operation on the same part. I take these on windblowz by using this 
software:  http://www.sysinternals.com/ntw2k/freeware/portmon.shtml

(Note that there are two download links for portmon, one for windows 
nt/2000/xp, other for windows 9x. One kind will probably not work on 
another).


* Since this is not a definitive patch, I would ask people to not 
distribute it as if it was an otherwise release patch (In particular, 
some folks at some linux distributions like to release testing stuff as 
if it were a stable release, confusing the users and messing the package 
maintainers) *.

This patch will not be considered stable until there are lots of testing 
involved. So please help testing


Thank you all,

Alexandre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/az2tc/q4llewz9oRAkXUAJ43qf2tT33nUdtVDkEpHEPV6P8vhACdF2vq
715IS/yOGh/7n857/HXX2QE=
=RM30
-----END PGP SIGNATURE-----


gnupic@linuxhacker.org