PIC16F1619 Error HEXFile

[Speed64]

Translated with Google, sorry

hello
I've created a new blank project.
PIC16F1619 processor, 32MHz original settings by the compiler.
I compiled it.
The compiler issues an error.
When you load the hex file this text is displayed.
I load the hex file with the software for PICkit 3 / ICD 3
PIC16F16- 13,14,15,18 result in the same error.
who can please help.

"program MyProject

' Declarations section

main:
' Main program
end.
"
"The line checksum on line 4 of the hex file is incorrect; the hex file appears to have been corrupted.

:06000E00E23E871F1F3F26"Loaded hex file is invalid.

HEXFile

:020000000328D3
:020006000328CD
:020000040001F9
:06000E00E23E871F1F3F26
:00000001FF

[petar.timotijevic]

Hi,

The problem lies in the fact that the new PIC16 have three rather than two configuration words. Problem is located in a compilers.

Development team is already informed about that.

Thank you for your patience and I apologize for the inconvenience.


Best regards,
Peter

[Speed64]

Thank you for your quick response

[petar.timotijevic]

Hi,

No problem, development team already working on this.


Best regards,
Peter

[ronanagh]

Same as me. I have same problem for PIC16F1613 on EasyPICv7. Error Message is "Error at line 4 checksum error". After read above post, Did MikroElekronika solve this error problem? I change to PIC16F1705, and it is working prefect. Let me know about above error problem for PIC16F1613.

Regards
Ronan

[petar.timotijevic]

Hi,

Same as me. I have same problem for PIC16F1613 on EasyPICv7. Error Message is "Error at line 4 checksum error". After read above post, Did MikroElekronika solve this error problem? I change to PIC16F1705, and it is working prefect. Let me know about above error problem for PIC16F1613.

Yes, solution for this will be included in next compiler update.

Thank you for your patience and I apologize for the inconvenience.


Best regards,
Peter

[john_hauton]

Hi, before I start trying to program some pic16f1619 chips, has the above problem been resolved?
Thank you
john

[biljana.nedeljkovic]

Hello,

this problem has been solved in the latest version of the compiler.

Kind regards,
Biljana