Searching \ for '[PIC]: test cases for PIC programmers' 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/devprogs.htm?key=programmer
Search entire site for: 'test cases for PIC programmers'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: test cases for PIC programmers'
2007\07\18@162000 by wouter van ooijen

face picon face
What do you (Olin, other PIC programmer creators) use as test cases for
you programmers?

For users of programmers: if you are interested in the speed (or
slowness..) of a programmer, which cases are interesting:
- with or without verify
- with or without eeprom (eeprom is IME seldom used, and programs quite
slow)
- with or without ID values (do you ever use those?)
- small programs, or chips filled up to their limit

I can't take measures of all variations, so my choice would be to pick a
small program (blink a LED, no ID values, no eeprom), and a fully filled
PIC. Disadvantage of a small program is that everyone will have his own
idea about what it should be. A fully filled PIC is better defined.

If anyone is interested: I use an asm file that can be configured to
blink a LED on (at this moment) 89 different PICs (12, 14 and 16-bit
cores). It can be configured fill the whole PIC: code, eeprom, and ID.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu



2007\07\18@163419 by Xiaofan Chen

face picon face
On 7/18/07, wouter van ooijen <spam_OUTwouterTakeThisOuTspamvoti.nl> wrote:
> What do you (Olin, other PIC programmer creators) use as test cases for
> you programmers?

Olin provides many test cases in his programming environment.
(C:\embedinc\examples\pic_prog if you installed it in the default location).

> For users of programmers: if you are interested in the speed (or
> slowness..) of a programmer, which cases are interesting:
> - with or without verify

With.

> - with or without eeprom (eeprom is IME seldom used, and
> programs quite slow)

Probably without.

> - with or without ID values (do you ever use those?)

With. Config words need to be programmed anyway. So I think
skipping the ID words does not save much time.

> - small programs, or chips filled up to their limit
>

To the limit. Or maybe a half-filled program.

Regards,
Xiaofan

2007\07\18@173458 by olin piclist

face picon face
wouter van ooijen wrote:
> What do you (Olin, other PIC programmer creators) use as test cases
> for you programmers?

I have a PIC programmer tester that tests individual capabilities of a PIC
programmer.  This is intended to verify the hardware is working correctly.
Then I have a suite of HEX files for spot checking things and regression
tests.  These HEX files are included with the PIC programmer software.  They
are in the EXAMPLES > PIC_PROG directory within the software installation
directory.  You can install all the PIC programmer software from
http://www.embedinc.com/picprg/sw.htm or get just the HEX files at
http://www.embedinc.com/picprg/hex.zip.

> For users of programmers: if you are interested in the speed (or
> slowness..) of a programmer, which cases are interesting:
> - small programs, or chips filled up to their limit
> - with or without eeprom (eeprom is IME seldom used, and programs
> quite slow)

Trying to simulate a short "real" program is meaningless because you can't
relate that to what your program does.  Instead I create two HEX files, one
full and one empty.  The empty one has everything set to the erased value,
although all locations are specified in the HEX file.  The full one sets all
useable program memory, EEPROM, and user ID locations to randomly generated
values, and may have a few selected config bits set to other than the erased
state.  These files never enable code protection or the like because then
you couldn't examine memory after programming.

These two cases represent the extremes, so gives users a solid outer bounds
on what they will get.  The full HEX file uses random values to defeat any
kind of compression or optimization.  Basically the spread gives you the
range of small to large program.  You can then decide how far into the range
your case is.

> - with or without verify

All my programmers perform 2 verify passes, one at each Vdd limit, by
default.

> - with or without ID values (do you ever use those?)

I have never used them in my own projects, but the full case HEX files
include random values for all user ID locations.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.

2007\07\18@175723 by Mark Rages

face picon face
On 7/18/07, wouter van ooijen <.....wouterKILLspamspam@spam@voti.nl> wrote:
> What do you (Olin, other PIC programmer creators) use as test cases for
> you programmers?
>

For pyk, I made a short script to generate random hex files for
program, eeprom, and config memory.  I believe the program is included
in the distribution.  It is called make_random_hex.py.  Run it with no
arguments for usage instructions.
--
Mark Rages, Engineer
Midwest Telecine LLC
markragesspamKILLspammidwesttelecine.com

2007\07\18@195600 by Xiaofan Chen

face picon face
On 7/18/07, Mark Rages <.....markragesKILLspamspam.....gmail.com> wrote:
>
> For pyk, I made a short script to generate random hex files for
> program, eeprom, and config memory.  I believe the program is included
> in the distribution.  It is called make_random_hex.py.  Run it with no
> arguments for usage instructions.
>

Hello Mark,

By the way, what is the official location for pyk? pickit-devel google
group is not a very good place to search for pyk download.

The following two locations do not have pyk for download.
http://vivara.net/software/ (seem to be offline now)
http://code.google.com/p/pyk/

Regards,
Xiaofan

2007\07\18@214459 by Herbert Graf

flavicon
face
On Wed, 2007-07-18 at 22:19 +0200, wouter van ooijen wrote:
> For users of programmers: if you are interested in the speed (or
> slowness..) of a programmer, which cases are interesting:
> - with or without verify

I only program with verify. Considering all the possible areas for
problems, leaving out a verify is IMHO not worth it.

> - with or without eeprom (eeprom is IME seldom used, and programs quite
> slow)

Without, I've only used the PIC's EEPROM once.

> - with or without ID values (do you ever use those?)

Without, never used them.

> - small programs, or chips filled up to their limit

Both. Why cause the user to wait to program the whole PIC if they're
only using 100 words of program space. At the same time, how long it
takes to program a full PIC is equally as important.

TTYL

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