That is not an error: some bits are fixed at 1, so you cannot change them to 0; see the datasheet.
If you observe the picture with all bits, the difference between 3F3A and 2F0A are bits 4,5,12.
PicKit considers them 0, OP does not change them compared to what it reads (1).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I have a strange error programming PIC16F876. (opgui v0.9.1) . I load my .hex file with 2F0A config word:
When I write, I have this error:
The same forcing config word: (2F0A)
But, when I read with PicKit2:
The config word, is OK (2F0A)
I go back to read with opgui:
and read 3F3A [0x2007]
¿ some ideas ?
Last edit: Anonymous 2015-12-09
That is not an error: some bits are fixed at 1, so you cannot change them to 0; see the datasheet.
If you observe the picture with all bits, the difference between 3F3A and 2F0A are bits 4,5,12.
PicKit considers them 0, OP does not change them compared to what it reads (1).
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
OK!!! thanks Alberto . Mistery resolved!!.
I was scratching my head about this.
Greetings.
Last edit: Anonymous 2015-12-10