Searching \ for '16C57' 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=16C
Search entire site for: '16C57'.

Truncated match.
PICList Thread
'16C57'
1996\09\19@203421 by Stuart Allman

flavicon
face
Whenever I read the program memory of my 16C57, every location is 004
(after erasing).  Does this mean that the PIC is shot?  I've been using it
for quite a few weeks now, without any difficulty, but now it refuses to
work.  The circuit and programming setup hasn't changed since the PIC
worked this morning.

Stuart Allman
spam_OUTstudioTakeThisOuTspamhalcyon.com

1996\09\19@205119 by Rob Diederichs

flavicon
face
At 05:24 PM 9/19/96 -0700, you wrote:
>Whenever I read the program memory of my 16C57, every location is 004
>(after erasing).  Does this mean that the PIC is shot?  I've been using it
>for quite a few weeks now, without any difficulty, but now it refuses to
>work.  The circuit and programming setup hasn't changed since the PIC
>worked this morning.
>
>Stuart Allman
>.....studioKILLspamspam@spam@halcyon.com
>

Most likely...  I do most of my delevoping on the 16C57/JW and I usally run
about 8 of them.  I couldn't tell you exactly how many programmings each
have taken before they failed, but I am having to chuck one or two every
couple of months.

While on the topic of 16C57.....   Are there any security concerns with the
OTP devices like the 16C57?  Or was the discussion here limited to the
eeprom products?

Rob Diederichs
Computalog Drilling Services L.T.D.
Edmonton, Alberta
Canada
rob.diederichsspamKILLspamcomputalog.com

1996\09\19@210823 by Robert Lunn

flavicon
face
>Are there any security concerns with the
>OTP devices like the 16C57?  Or was the discussion here limited to the
>eeprom products?
>
>Rob Diederichs

       Well, the discussion covered a lot of quite general issues
       related to the idea of hardware protection of software.

       The eeprom chips just bring the discussion into focus by
       being known for their ease of cracking.

       The OTP parts do not suffer the particular problems of the
       eeprom parts.

       Others have, however, made the comment they believe the 'C5x
       parts are easier to crack than the 'C8x parts!

       Use your best professional judgement ;)

___Bob (tm, except Scandinavia)

1996\09\20@001421 by fastfwd

face
flavicon
face
Stuart Allman <.....PICLISTKILLspamspam.....MITVMA.MIT.EDU> wrote:

> Whenever I read the program memory of my 16C57, every location is
> 004 (after erasing).  Does this mean that the PIC is shot?  I've
> been using it for quite a few weeks now, without any difficulty, but
> now it refuses to work.  The circuit and programming setup hasn't
> changed since the PIC worked this morning.

Stuart:

It sounds like a problem with the programmer (not you... the EPROM
programmer) rather than the PIC.  Do you have other 16C57s whose
programming behavior you can observe?

-Andy

Andrew Warren - EraseMEfastfwdspam_OUTspamTakeThisOuTix.netcom.com
Fast Forward Engineering, Vista, California
http://www.geocities.com/SiliconValley/2499

1996\09\20@003440 by John Payson

picon face
> Whenever I read the program memory of my 16C57, every location is 004
> (after erasing).  Does this mean that the PIC is shot?  I've been using it
> for quite a few weeks now, without any difficulty, but now it refuses to
> work.  The circuit and programming setup hasn't changed since the PIC
> worked this morning.

Hmm... most likely your programmer is not attaching to all the pins of the
device properly, or maybe is not applying VPP?

1996\09\20@044529 by mike

flavicon
picon face
In message  <2.2.16.19960920110620.38cf12ce@huey> PICLISTspamspam_OUTMITVMA.MIT.EDU writes:
{Quote hidden}

I'd like to know how the C84 and the C5x devices are cracked so that I
can use my professional judgement. My last project is expect to sell
4000 a month. I would not like the manufacturer to cut me out of the
supply loop by simply having the pics programmed elasewhere.


Anyone care to enlighten me on the tricks that are used?


Regards,



Mike

1996\09\20@055721 by Bill Madden

flavicon
face
Stuart Allman wrote:
>
> Whenever I read the program memory of my 16C57, every location is 004
> (after erasing).  Does this mean that the PIC is shot?  I've been using it
> for quite a few weeks now, without any difficulty, but now it refuses to

<snip>

A couple of days ago John Barrowman of Parallax informed me that the
latest PIC windowed devices being shipped by Microchip incorporate
a code protect fuse that is NOT erasable. Perhaps this is your problem?

               Bill

1996\09\21@221121 by Jim Robertson

flavicon
face
At 04:47 AM 9/20/96 -0700, you wrote:
>Stuart Allman wrote:
>>
>> Whenever I read the program memory of my 16C57, every location is 004
>> (after erasing).  Does this mean that the PIC is shot?  I've been using it
>> for quite a few weeks now, without any difficulty, but now it refuses to
>
><snip>
>
>A couple of days ago John Barrowman of Parallax informed me that the
>latest PIC windowed devices being shipped by Microchip incorporate
>a code protect fuse that is NOT erasable. Perhaps this is your problem?
>
>                Bill
>
This doesn't apply to and of the 16C5x series, even if it did you would read
00F
not 004. Personally, I think your 16C57 is stuffed.

Jim

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