From e7d76e189ef558244ef414244d288645f998125b Mon Sep 17 00:00:00 2001 From: scottlivingston Date: Sat, 22 May 2010 02:36:54 +0000 Subject: [PATCH] Updated contents of PIC app readme file. git-svn-id: https://svn.code.sf.net/p/goodfet/code/trunk@548 12e2690d-a6be-4b82-a7b7-67c4a43b65c8 --- firmware/apps/pic/README.txt | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/firmware/apps/pic/README.txt b/firmware/apps/pic/README.txt index ee0ace1..9182d54 100644 --- a/firmware/apps/pic/README.txt +++ b/firmware/apps/pic/README.txt @@ -1,15 +1,18 @@ PIC programmer -March, April 2010. +March-May 2010. -Scott Livingston +Scott Livingston -Currently targeted at dsPIC33F/PIC24H chip family and tested on +Currently targeted at 16-bit PIC chip families (i.e., PIC24F, +dsPIC30F, PIC24H, dsPIC33F) and tested on dsPIC33FJ128GP710, dsPIC33FJ128GP708, PIC24HJ12GP201. +Expansion in the 8-bit and 32-bit directions is in the works. + For the 14-pin GoodFET port (size 2x7), the pinout is 3 -> PGD @@ -44,8 +47,7 @@ $ ./goodfet.pic devid Much more documentation is needed for the programmer and is -forthcoming along with more common tools (e.g. verify programming -results). For now, here are some quick examples. To bulk erase program +forthcoming. For now, here are some quick examples. To bulk erase program memory (this is necessary before programming), $ ./goodfet.pic erase @@ -54,8 +56,12 @@ Then to program the device with a code file, foo.hex, $ ./goodfet.pic program foo.hex +To verify programming results, + +$ ./goodfet.pic verify foo.hex -A quick visual check of results might be a dump of the first few +Please note that only addresses in given hex file are verified. A +quick visual check of results might be a dump of the first few instruction words. $ ./goodfet.pic - 0x200 0x220 pretty -- 2.20.1