Hi Alberto,
I have a 16F18857, not going to use it now but, just as curiosity I tried it, and it works!
Well:
I did a little blink-led (RC4) to test and it WORKS...
1) reading the memory seems to go OK.
2) writing OK, BUT COMPLAIN about config verify/timeout...
Attached here are 5 files:
a) messages when programming - txt
b) messages when reading - txt
c) original .hex
d) op readed .hex
e) about the little firmware - txt
Right now I am more interested in 18xx, 15xx, 183xx families but I am sending this infos so that it may serve to help the project/you.
Here is a fragment of the "errors" message (full text on attached files):
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-02-14
Alberto, I am not so sure but, it seems that the 188XX family DOES NOT have DIA (device information area) and also NOT HAVE DCI (device configuration information)...
Perhaps, OP is trying to use the 184XX family Programming Specifications...
Regards,
Valter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Right, it's an hybrid chip: 8 bit commands but no DIA-DCI. I had missed that.
Will fix it in the next version; anyways those areas are read only for information.
I see that the config word is written correctly but there's a timeout at write time, so the error.
Is it always doing that? Can you check once more with a different CONFIG3?
Also can you write all configs just for a trial?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-02-14
Hello Alberto...
Not sure if this is what you ask...
The previous example has 3 configs words,
this new one has all 5 configs words... SAME BEHAVIOR... WORKS!
4 files attached: 5-config.hex, programming-messages, reading-messages and read-saved-file...
anything else, just ask, if it easy like this one, it is my pleasure to help...
Valter
Hi Alberto,
I have a 16F18857, not going to use it now but, just as curiosity I tried it, and it works!
Well:
I did a little blink-led (RC4) to test and it WORKS...
1) reading the memory seems to go OK.
2) writing OK, BUT COMPLAIN about config verify/timeout...
Attached here are 5 files:
a) messages when programming - txt
b) messages when reading - txt
c) original .hex
d) op readed .hex
e) about the little firmware - txt
Right now I am more interested in 18xx, 15xx, 183xx families but I am sending this infos so that it may serve to help the project/you.
Here is a fragment of the "errors" message (full text on attached files):
Regards,
Valter
Alberto, I am not so sure but, it seems that the 188XX family DOES NOT have DIA (device information area) and also NOT HAVE DCI (device configuration information)...
Perhaps, OP is trying to use the 184XX family Programming Specifications...
Regards,
Valter
Right, it's an hybrid chip: 8 bit commands but no DIA-DCI. I had missed that.
Will fix it in the next version; anyways those areas are read only for information.
I see that the config word is written correctly but there's a timeout at write time, so the error.
Is it always doing that? Can you check once more with a different CONFIG3?
Also can you write all configs just for a trial?
Hello Alberto...
Not sure if this is what you ask...
The previous example has 3 configs words,
this new one has all 5 configs words... SAME BEHAVIOR... WORKS!
4 files attached: 5-config.hex, programming-messages, reading-messages and read-saved-file...
anything else, just ask, if it easy like this one, it is my pleasure to help...
Valter
Just one more thing, the log file of a write.
(Options -> log activity)
Hi.
This is the log for the 5 config .hex "above"...
Just to clarify: the log file is for the "xc8_16F18857_second.X.production.hex" that has all the 5 configs set...
Valter
Perfect, thanks.
It's just a short communication delay ... my fault.
Will fix it