it's maybe too late here... time to sleep i gues BUT yep in fact code is suppose to work.. But as i see few time, you asked about OSCCAL... maybe your chip lost his OSCCAL value. May you put a midpoint value, let's say $80 and tell us what's happening now. maybe you can program this value with your programmer without changing anything in the code.
but i never try to remove OSCCAL in PB to see what's happening.... maybe will work anyway... i know it make no sense but....
what about if you remove assembly code at the begining for OSCCAL setting ??
what about if you try a simple blink program on all outputs... is it working or not. case not OSCCAL or fried chip is the cause... or suppply line under the minimum
Last edited by mister_e; - 6th December 2004 at 05:17.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks