F886 & pgm

[Bruce]

Hmm. That is an interesting problem.

Try this. Save the file you're compiling in your 2.60 directory with one name, and save
a 2nd copy of the same file in your 2.46 directory with a different name.

Compile the one with 2.60. Open it with your MeLabs programmer software, and click on
the C radio button. You should see a screen with config settings like the one I have
attached.

Now open the file in your 2.46 directory, and repeat. Are config settings the same?

[MOUNTAIN747]

I’ve tried ANSELH=$00 with the same results. In fact BOR was also Enabled along with a few other items. It did set internal osc at 8Mhz with clockout at 2Mhz.

I used the code file on different computers. One with 2.60 and the other with 2.46. And yes I clicked the C radio button to take a look at the Configs.

I think I’ll try reloading 2.60 on the computer to see if there are any changes in results.

[Bruce]

If you're doing this on two different PCs, it may be that you just have different settings for the MeLabs programmer. Make sure you have Options >> Update Configuration From File checked on the 2.60 machine. That sounds like the problem.

You previously programmed it with LVP_ON, and it's not updating config settings.

[MOUNTAIN747]

Bruce,
I've checked both computers. Both computers were set to "Update Configuration from file". 2.46 Config default option was set to LVP_off. 2.60 was set to LVP_on. I changed that setting and recompiled with the same results, LVP is NOT turning off on 2.60.

[MOUNTAIN747]

I got it. I was not saving the new default setting on 2.60. There is still the issue of why the file was not recognized when default setting on the programer was set to "Update Configuration from file". However 2.60 is now turning off LVP as it should, but only because the default LVP was changed.

I learned a lot about PBP defaults and LVP. I also was unaware that I could have a digital out put with an analog input (ANSELH), at least that what I got out of reading the datasheet on ANSELH.
Thank you all for your assistance.

[Bruce]

Here's a really quick/easy way to find out if it's the compiler or a different setting in your
programmer software.

Compile it on your 2.60 machine. Transfer the .HEX file to your 2.46 machine.

Open the .HEX file & program & test the PIC.

[MOUNTAIN747]

Thanks Bruce, I'll give it a try.