Searching \ for 'Checking for corrupt program' 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/index.htm?key=checking+corrupt
Search entire site for: 'Checking for corrupt program'.

Truncated match.
PICList Thread
'Checking for corrupt program'
1997\03\13@022505 by Ruben Jnsson

flavicon
face
Is there any simple way to check if the program in a PIC
(16C57) is corrupt?

Since the program memory can't be read by the program
itself it's impossible to check it with a checksum. Is there
any other way?

I could put RETLW XX at several locations, where XX is a
known constant, and then call these locations to see if I get
the expected value in return but this doesn't check the
entire program.

------------------------------------
Ruben Joensson
AB Liros Elektronik
Box 9124
200 39 Malmoe
Sweden
Tel +46 40 14 20 80
Mail: spam_OUTrubenTakeThisOuTspamsbbs.se
------------------------------------

1997\03\13@061729 by Ruben Jnsson

flavicon
face
Is there any simple way to check if the program in a PIC
(16C57) is corrupt?

Since the program memory can't be read by the program
itself it's impossible to check it with a checksum. Is there
any other way?

I could put RETLW XX at several locations, where XX is a
known constant, and then call these locations to see if I get
the expected value in return but this doesn't check the
entire program.
------------------------------------
Ruben Joensson
AB Liros Elektronik
Box 9124
200 39 Malmoe
Sweden
Tel +46 40 14 20 80
Mail: .....rubenKILLspamspam@spam@sbbs.se
------------------------------------

1997\03\13@162604 by TONY NIXON 54964

flavicon
picon face
The only ways I can think of, is to verify the code on the chip with
the HEX file that it was programmed with, using the programmers
'verify' command.

If the chip is code protected, you should read back the program
contents after you have programmed it and save it to a file. The data
in this file can be used to verify the software in code protected chips.

Regards

Tony


Just when I thought I knew it all,
I learned that I didn't.

1997\03\14@023111 by Ruben Jnsson

flavicon
face
I want to verify the program at runtime every time
it is powered up.

Som aplications regarding human safety requires that
the processor checks itself for a corrupt program,
checks that every used instruction is working ok and
checks that every used ram register is working before
it can go on with it's safety part of the program.

The instruction- and ram-checking is ok but since
I can't read the memory with the instructions
(Harvard Architecture) I can't do any checksum
test.

{Quote hidden}

------------------------------------
Ruben Joensson
AB Liros Elektronik
Box 9124
200 39 Malmoe
Sweden
Tel +46 40 14 20 80
Mail: rubenspamKILLspamsbbs.se
------------------------------------

1997\03\14@162914 by Norm Cramer

flavicon
face
I am familure with this requirement but hadn't thought about how to do it
on a PIC.  Maybe you could throw another PIC at the problem.  The second
PIC reads the first PIC's ROM and does the check sum.  If needed, the first
PIC could also check the 2nd PIC's code.  Kind of a round about way of
doing it but it might work.  The 2nd PIC might be the cheapest approach.

Norm

At 08:19 AM 3/14/97 +0000, you wrote:
{Quote hidden}

1997\03\16@234437 by tjaart

flavicon
face
Norm Cramer wrote:
{Quote hidden}

Why not use a 17CXX ?

--
Friendly Regards

Tjaart van der Walt
.....tjaartKILLspamspam.....wasp.co.za
_____________________________________________________________
| Another sun-deprived R&D Engineer slaving away in a dungeon |
|             WASP International  http://wasp.co.za           |
|             GSM and GPS value-added applications            |
|  Voice : +27-(0)11-622-8686   |   Fax : +27-(0)11-622-8686  |
|_____________________________________________________________|

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