ECIO with a PIC18F2525

[mackrackit]

I never trusted the programmer menu. The sure way is to set the configs in code space.
If you use PBP3 the documentation is included with the program. If using PBP2.6 or lower then take a look at this http://www.picbasic.co.uk/forum/showthread.php?t=543

The other nice about setting the configs in code space is the code is complete, you do not have to remember what the settings were as they are always there.

[Szczepaniec]

I never trusted the programmer menu. The sure way is to set the configs in code space.
If you use PBP3 the documentation is included with the program. If using PBP2.6 or lower then take a look at this http://www.picbasic.co.uk/forum/showthread.php?t=543

The other nice about setting the configs in code space is the code is complete, you do not have to remember what the settings were as they are always there.

I guess I will join the crowd that doesn't trust the programmer menu. I wonder how many other projects I have scrapped in frustration over the same or similar issue?

[Darrel Taylor]

Check the options menu in meProg.

If you have "Reread File before Programming" and "Update Configuration from file" checked, any changes you make in the configuration dropdowns will not have an affect.
It will only use the configurations contained in the .hex file.

If you want to change them manually, uncheck one or both of those options.
If you do a read from the chip, the configuration window will show you exactly which settings were programmed.

There is no reason not to trust the dropdowns.