I tested all of these today.
Programmer worked 100% with all of them.
16F1572
!6F15323
16F15324
16F15344
16F18855 (WITH 0.11.0 OPGUI when write give a strane error fronm ox0800 adres, but the program is write OK in MCu, and work properly. Today I try With 0.11.2 opgui and evriting is ok .
I tested all of these today.
Programmer worked 100% with all of them.
16F1572
!6F15323
16F15324
16F15344
16F18855 (WITH 0.11.0 OPGUI when write give a strane error fronm ox0800 adres, but the program is write OK in MCu, and work properly. Today I try With 0.11.2 opgui and evriting is ok .
Thanks for sharing.
EEPROM on 16F188xx presently cannot be written correctly; I will relase a fixed version soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-06-22
hi,
the reason is that there is an error about missing parentheses in the 'Write16F18xxx' function (progP16.c, line 6005), so the DIA-DCI never will be written.
by the way, the 'Write18FKx' and 'Read18FKx' functions has the same error (progP18.c, lilne 1734 and 2106), and there is an uninitialized value problem too (with 'x' value line 2557).
hope I helped,
Attila
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually the problem was in the algorithm itself (or rather the interpretation of programming specs); it was corrected in 0.11.3 after a full verification on a device.
I don't see problems with line 6005:
int useDCI=options&0x10==0?1:0;
Regarding issues in progP18.c I will fix them, thanks for reporting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-07-01
hi,
the problem is the operator precedence:
1: 0x10==0 -> always false
2: options&false -> always false
3: useDCI will be always 0.
these issues found the gcc compiler, when I added to the CFLAGS: '-Wall -Wextra -Wpedantic' and removed '-w'.
there are many warnings also, but they are not so critical, except for some variable array overwrite issue, but I have no dealt with them yet (all DisplayCODEXXX functions and progP16.c, line 686 - 't' array size maybe less than the source in the sprintf function. I think the correct way is using the snprintf, because it can not overwrite the target, if 'n' is the target size).
hope I helped
Attila
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Right, indeed it works as you describe.
Fortunately there are no consequences, as DCI info is entirely optional.
But still worth correcting, as the other issues.
It's good to see somebody looking at the code once in a while.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
16F77
16F76
16F73
Thanks for your contribution. I will mark them as verified.
Just to confirm,
I tested all of these today.
Programmer worked 100% with all of them.
16F1572
!6F15323
16F15324
16F15344
16F18855 (WITH 0.11.0 OPGUI when write give a strane error fronm ox0800 adres, but the program is write OK in MCu, and work properly. Today I try With 0.11.2 opgui and evriting is ok .
Just to confirm,
I tested all of these today.
Programmer worked 100% with all of them.
16F1572
!6F15323
16F15324
16F15344
16F18855 (WITH 0.11.0 OPGUI when write give a strane error fronm ox0800 adres, but the program is write OK in MCu, and work properly. Today I try With 0.11.2 opgui and evriting is ok .
Thanks for sharing.
EEPROM on 16F188xx presently cannot be written correctly; I will relase a fixed version soon.
hi,
the reason is that there is an error about missing parentheses in the 'Write16F18xxx' function (progP16.c, line 6005), so the DIA-DCI never will be written.
by the way, the 'Write18FKx' and 'Read18FKx' functions has the same error (progP18.c, lilne 1734 and 2106), and there is an uninitialized value problem too (with 'x' value line 2557).
hope I helped,
Attila
Actually the problem was in the algorithm itself (or rather the interpretation of programming specs); it was corrected in 0.11.3 after a full verification on a device.
I don't see problems with line 6005:
int useDCI=options&0x10==0?1:0;
Regarding issues in progP18.c I will fix them, thanks for reporting.
hi,
the problem is the operator precedence:
1: 0x10==0 -> always false
2: options&false -> always false
3: useDCI will be always 0.
these issues found the gcc compiler, when I added to the CFLAGS: '-Wall -Wextra -Wpedantic' and removed '-w'.
there are many warnings also, but they are not so critical, except for some variable array overwrite issue, but I have no dealt with them yet (all DisplayCODEXXX functions and progP16.c, line 686 - 't' array size maybe less than the source in the sprintf function. I think the correct way is using the snprintf, because it can not overwrite the target, if 'n' is the target size).
hope I helped
Attila
Right, indeed it works as you describe.
Fortunately there are no consequences, as DCI info is entirely optional.
But still worth correcting, as the other issues.
It's good to see somebody looking at the code once in a while.