|
That's an interesting problem you have - I had a similar experience with 12F629 where the chip behaved properly if all my timing was using PAUSE but failed to reprogram when using the NAP in my code... Finally I ended up using the extended temperature version of the device (12F629E/P instead of the I/P) and haven't had any problems since!
I had to use NAP to keep power consumption low - do you have a similar situation?
-warrier
|
no nap, no pause. thats my whole code, just a good old fashion for next loop
|
i tried to erase it again. The epic says that erase sucessfull or something even if there is no chip in there, so i don know how well I can trust it. anyways. I tried to run it and it was deffenatly erased. the board does nothing now. and it still doesnt reprogram.
|
ok so I found the problem.... its sleep. i think i need more.
apperently pics dont like 12 V on an input pin......
sorry to all 54 people who wasted their time reading this and to warrier and mr.e answering me.
Is there anyway this thread can be deleted to stop any more of my embarrassment?
-scorp
|
hehe bah don't be shy, you can't imagine how many time it happen to everybody here one day or another. I'm sure you'll not redo the same error two times
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
Actually you need a pat on your back! You solved a problem by yourself that we couldn't visualize just by reading your code - it's the best way to learn and don't be embarrassed. When dealing with peripherals sometimes it is a good thing to make sure one has a reasonable configurations - chips usually fail through hardware issues - but software often gets carries the blame....
-warrier
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks