When running in debug, the program hangs on those two steps. So, I comment them out. Then in the release version, I have to uncomment them. Unfortunately, I sometimes forget to do that.
Just use a delay? It does not take long to stabilise, so you can add a hard-coded delay in the start of your code. If you do not already have one it is also a good practice having a delay to allow PSU voltages etc to stabilise after turn on.
I could change the code. But of course, that is what I am currently doing.
Register injection at a specific program counter sounded like the right term for what I wanted to do with the stimulus worksheet You can access OSCCON in the dialog. It would be so easy if all you had to do was indicate which bit to flip at that location, like: bsf OSCCON, 2. I'll give it a fresh look today.
It may not be a valid assumption, but if Mike K8LH doesn't use a stimulus for that step, then I am assuming that OSCCON,2 (HTS) cannot be set by the user.
In fact, this little change compiles, but still doesn't skip:
It may not be a valid assumption, but if Mike K8LH doesn't use a stimulus for that step, then I am assuming that OSCCON,2 (HTS) cannot be set by the user.