Chip configs
Posted: Wed Aug 31, 2016 12:13 pm
Apologies for what is most probably a dumb question but I'm getting really confused and frustrated.
When I develop projects I build in steps. When a step is successful I baseline it and move onto the next piece of functionality building the project in stages. What I’ve noticed is occasionally when I revert back to a known working baseline the previously successful baseline no longer functions correctly.
It’s almost as if I changed the chips character/fuses but when reverting, the chips not returned to its same state as it was.
To try and prove my point, I substituted a brand new (18F44K22) and burnt a previously successful baseline and it worked as expected. I then burnt the next unsuccessful baseline which of course failed again. I then reverted and the previously working version is now failing.
Does this make any sense and is there a way or returning a chip back to the same state as a new device. I’ve tried but apart from substituting a new chip I can’t seem to find a way to “go backwards” when this happens. It seems to affect the higher end devices more than the simpler varieties.
Many thanks
When I develop projects I build in steps. When a step is successful I baseline it and move onto the next piece of functionality building the project in stages. What I’ve noticed is occasionally when I revert back to a known working baseline the previously successful baseline no longer functions correctly.
It’s almost as if I changed the chips character/fuses but when reverting, the chips not returned to its same state as it was.
To try and prove my point, I substituted a brand new (18F44K22) and burnt a previously successful baseline and it worked as expected. I then burnt the next unsuccessful baseline which of course failed again. I then reverted and the previously working version is now failing.
Does this make any sense and is there a way or returning a chip back to the same state as a new device. I’ve tried but apart from substituting a new chip I can’t seem to find a way to “go backwards” when this happens. It seems to affect the higher end devices more than the simpler varieties.
Many thanks