Hello guys,
I want to thank=B4s here again, everyone who gave me information and tips
about the problem I was having.=20
Using the information and suggestions I received, I ended up finding the
problem.
To not make this text too long, I mean that the cause was really the lack o=
f
initialization of some positions in RAM.
The fact that RAM stays with the pattern after turning off the power for
some long time has left me really confused.
I use interruption with the timer0 for multiplex three 7 segment displays
that show the direction in degrees of the pointing of an antenna.
The problem was that I enabled the interrupt before having the value to sho=
w
already ready.=20
I have a table with several "retlw" that returns me the segments I need to
turn on to show the numbers.
When the interruption took effect, the value was not yet established and
instead of matching the "retlw" ended up going to a program address with
unpredictable results ... I learned a lot from this error ... Fortunately
everything is working as it should and without bug I may have noticed.
Many thanks to everyone who gave their suggestions on how to find out what
was going on.=20
Certainly this list is invaluable, and I hope one day I can give some help
as well.
Just to complement ...=20
As I was given the suggestion, at the beginning of the program I did a
routine that wrote 0x00 in all RAM and the problem disappeared.=20
Then I tried with 0xFF and locked ...=20
>From this point I could know that the problem was the lack of initializati=
on
of some RAM position.=20
As my table would have to be index between 0x00 and 0x0F I finally
understood what was happening and I was able to correct it.
Thank you for all guys that send me some suggestion, and apologize my
English since my first language are Portuguese...
Marcus - PP5MS
=20


--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.