About 12F1822

[Anonymous]

First, thanks for making OP an Open Source Project, and since it is FULL open, including the USB stack, I think it is a nice project.
Second, the hardware design looks simple, clean and easy, which is also nice.

I am testing OP with a 18F2550 with 20MHz crystal and it seems to work OK.
Recompiled the firmware from source.

[12F1822]
It seems that there is a typographic error (perhaps only a typo) that leads the OP GUI to display it as a 16F device (16F1822)...

[Reading the device flash memory...]
Using the OPGUI and trying the memory reading and saving the result to a file seems to create unusual file...

Compare the 3 listing below:
READING FROM OP-GUI

Reading code ... completed
Reading CONFIG area ... completed
Reading EEPROM ... completed
ID0: 0x3FFF ID1: 0x3FFF
ID2: 0x3FFF ID3: 0x3FFF
DevID: 0x2708
16F1822 rev8
Configuration word 1: 0x3FE4
Configuration word 2: 0x1EFF
Calibration word 1: 0x28B9
Calibration word 2: 0x0D85

Code memory:
0000: 2801 2FFD 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 
07A0: 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 3FFF 0020 018C 
07B0: 0023 018C 0021 018C 0819 3987 3870 0099 30FC 0599 0020 150C 3001 00F0 3000 00F1 
07C0: 27C9 0020 110C 3001 00F0 3000 00F1 27C9 2FBA 01F4 01F5 0871 0275 1D03 2FD1 0870 
07D0: 0274 1803 0008 01F6 01F7 0877 3A80 00F2 3080 0272 1D03 2FDE 3064 0276 1803 2FF8 
07E0: 301A 00F3 30F8 00F2 0BF2 2FE4 0BF3 2FE4 0000 3001 07F6 3000 3DF7 0877 3A80 00F2 
07F0: 3080 0272 1D03 2FF6 3064 0276 1C03 2FE0 3001 07F4 3000 3DF5 2FCB 107E 0020 2FAE 

SAVED FILE (OP GUI)

Open Programmer Reading Resulting File Saved
---------------
:020000040000FA
:040000000108FD0FE7
:100F5000FF0FFF0FFF0FFF0FFF0FFF0F20008C0190
:100F600023008C0121008C01190887097008990061
:100F7000FC00990520000C050100F0000000F100C4
:100F8000C90720000C010100F0000000F100C907B2
:100F9000BA0FF401F50171087502030DD10F700845
:100FA000740203080800F601F7017708800AF200CE
:100FB00080007202030DDE0F640076020308F80F52
:100FC0001A00F300F800F200F20BE40FF30BE40F49
:100FD00000000100F6070000F70D7708800AF20014
:100FE00080007202030DF60F64007602030CE00F1E
:100FF0000100F4070000F50DCB0F7E002000AE0FBE
:020000040001F9
...

PICKIT2 (pk2cmd) Reading

PICKIT2 Reading
---------------
:020000040000FA
:100000000128FD2FFF3FFF3FFF3FFF3FFF3FFF3F27
:100F5000FF3FFF3FFF3FFF3FFF3FFF3F20008C0170
:100F600023008C0121008C01190887397038990001
:100F7000FC30990520000C150130F0000030F10024
:100F8000C92720000C110130F0000030F100C92702
:100F9000BA2FF401F50171087502031DD12F7008F5
:100FA000740203180800F601F7017708803AF2008E
:100FB00080307202031DDE2F643076020318F82F92
:100FC0001A30F300F830F200F20BE42FF30BE42FA9
:100FD00000000130F6070030F73D7708803AF20054
:100FE00080307202031DF62F64307602031CE02F5E
:100FF0000130F4070030F53DCB2F7E102000AE2FDE
:020000040001F9
...

I am using a Debian Stretch with pk2cmd compiled from sources, also checked with Microchip PICKIT2 Windows Application, which is the same as pk2cmd...

The OP-GUI is the latest, compiled from sources...

Thanks,
Valter
PS. I have another question but I will put it into another post...

[Alberto Maccioni]

I don's see this 16F1822 ...
You found a bug related to file saving: a 12F1xxx is incorrectly considered a 12 bit device so all locations are trimmed.
Easy fix: after reading choose any 16F device then save.
Will be fixed in next version.

[Anonymous]

Alberto, thanks for the reply.
I will be using/testing OP, if I encounter more issues I will report to you...

Valter