Searching \ for 'PIC16C67 Strange Behavior?' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/microchip/devices.htm?key=16C
Search entire site for: 'PIC16C67 Strange Behavior?'.

Truncated match.
PICList Thread
'PIC16C67 Strange Behavior?'
1999\03\29@102301 by Steven Kosmerchock

flavicon
face
Friends,
I am working with a PIC16C67/JW and finally got it
working. Problem; it only works when the JW part isn't
covered. I program an OTP and it still flakes out. Any
suggestions and possible solutions?? Thanks in advance!

Best regards,
Steven


Steven Kosmerchock
Engineering Technician/Student
CELWAVE
Phoenix  Arizona   USA
Email:  spam_OUTsteve.kosmerchockTakeThisOuTspamcelwave.com
http://www.geocities.com/researchtriangle/lab/6584

1999\03\29@103009 by Tjaart van der Walt

flavicon
face
Steven Kosmerchock wrote:
>
> Friends,
> I am working with a PIC16C67/JW and finally got it
> working. Problem; it only works when the JW part isn't
> covered. I program an OTP and it still flakes out. Any
> suggestions and possible solutions?? Thanks in advance!
>
> Best regards,
> Steven

The light coming into the window resets the RAM to 255 in the JW.
You need to insert a initializing routine into your code.

--
Friendly Regards          /"\
                         \ /
Tjaart van der Walt        X  ASCII RIBBON CAMPAIGN
.....tjaartKILLspamspam@spam@wasp.co.za  / \ AGAINST HTML MAIL
|--------------------------------------------------|
|                WASP International                |
|R&D Engineer : GSM peripheral services development|
|--------------------------------------------------|
| Mobile : tjaartspamKILLspamsms.wasp.co.za  (160 text chars) |
|     http://www.wasp.co.za/~tjaart/index.html     |
|Voice: +27-(0)11-622-8686  Fax: +27-(0)11-622-8973|
|          WGS-84 : 26¡10.52'S 28¡06.19'E          |
|--------------------------------------------------|

1999\03\29@235623 by Tjaart van der Walt

flavicon
face
Gerhard Fiedler wrote:
>
> At 08:49 03/29/99 -0700, Steven Kosmerchock wrote:
> >Tjaart,
> >
> >>>The light coming into the window resets the RAM to 255 in the JW.
> >>>You need to insert a initializing routine into your code.
> >
> >I am not sure what you mean by an "initializing routine".
> >I used the <PIC16C67.INC> file, is that what you mean?
> >If so, it still doesn't seem to work. I still have MUCH to
> >learn..................
>
> tjaart is talking about the ram contents. your chip's ram may get reset (by
> the light) when the window is open, and it for sure doesn't, when it is
> closed. so it looks as if you might be using a ram location that has not
> been initialized (ie. written to before you use its content).

It is good practise to put some 'standard' routine in all
your programs to make sure the RAM is in a known state before
your program starts chugging away.

As soon as you've got this figured out, you can go one step further.
On startup, you check to see if the PIC was started up from scratch,
or because of a watchdog reset. If you don't want your little program
to start from scratch if a watchdog reset occured, you can initialise
the RAM differently for a watchdog reset.

****warning****
If you didn't understand the previous paragraph, don't worry about it
now. You will get there soon enough....

--
Friendly Regards          /"\
                         \ /
Tjaart van der Walt        X  ASCII RIBBON CAMPAIGN
.....tjaartKILLspamspam.....wasp.co.za  / \ AGAINST HTML MAIL
|--------------------------------------------------|
|                WASP International                |
|R&D Engineer : GSM peripheral services development|
|--------------------------------------------------|
| Mobile : EraseMEtjaartspam_OUTspamTakeThisOuTsms.wasp.co.za  (160 text chars) |
|     http://www.wasp.co.za/~tjaart/index.html     |
|Voice: +27-(0)11-622-8686  Fax: +27-(0)11-622-8973|
|          WGS-84 : 26¡10.52'S 28¡06.19'E          |
|--------------------------------------------------|

1999\03\30@002116 by Dave VanHorn

flavicon
face
>It is good practise to put some 'standard' routine in all
>your programs to make sure the RAM is in a known state before
>your program starts chugging away.



Indeed,  My SOP is to init all ram with zeroes, then fill all buffers
with 1,2,3 (ie: buffer1 all = 1 etc) which aids in debugging, so I can
see where the buffers are.
Finally, all ram variables are initted to some rational value
depending on the application.

I do this init this way, hoping that if I ever am scatterbrained
enough to use uninitialized ram, either it will work, because the
value I set it to happens to be right, or it will crash 100% of the
time, and I will fix it. Either way, I win :)

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