A little closer look and the new PK2DeviceFile.dat does indeed supply the correct config mask. My bad, talking off the top of my head there.
The difference I saw without further investigation was the "programmed" config after burning the hex. The IPE and PK2 GUI have different ways of reporting this. The IPE would follow the data sheet in reading "unimplemented" config bits as "1", while the PK2 reports them as "0" which leads to the exact difference that I saw.
The program memories look exactly the same whether burned by the IPE or the new PK2 device file. Checksum is the same for the imported hex. The blinky led program works exactly the same.
So in conclusion, I feel the new device file for the PK2 PIC12f1571 & 1572 is good to go. Will report back if I run into any problems.
On Tuesday, June 7, 2016 12:28 PM, William Roth <williamroth@users.sf.net> wrote:
Atached is modified device file with some corrections to Ver 1.63.48. This should work with 12F1571/72. They should now be in family renamed to USB-Min III. I changed the version to 1.63.50 and added my initials to comments to keep it distinct from other versions.
The config bit masks for 1571/1572 have been corrected to match the data sheet. When the GUI opens and before memory is read the configs should read 0EFB & 3703. After reading memory the configs should reflect the actual settings.
Let me know if this works.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
William, thanks so much. Looks like I am up to date with all the latest and greatest devices.
The hex file operations for the PIC12f1571 look just fine.
The new bit mask doesn't seem to address the CONFIG2 !LPBOREN. The datasheet says 3F03 which means the low power brown out reset is disabled. With 3703 bit mask it is enabled, is that what we want to do? In the PK2 configurator they mistakenly show bit 11 as unimplemented?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As far as my research goes, this last PK2 device file correctly supports the most 8-bit chips. It is based upon 1.63.48 as originally published by "gert" and 1.63.46 as published by "Scasis-Dougey".
I made some corrections so that certain addded chips would work correctly (12F157x and 16F178x). Of these, I have personally tested 16F1788/89.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes and no. The 12F1612 and 16F16xx devices were added in Ver 1.63.48. However the person who added them was not very familar with PICs at the time, and did not consider that these chips have 3 config words, whereas all other Midrange chips have either 1 or 2. This mean that the the existing scripts will only read/write CONFIG1 & CONFG2 ... CONFIG3 will always be at it default settings. This means that the watchdog timer cannot be configured.
I would recommend only using PK3 and MPLABx IPE with these chips until I or someone else can figure out how to add scripts that can read and write three 14-bit config words.
William
Last edit: William Roth 2016-06-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have removed the posted files as I found some more problems, While lots of new chips were added in 1.63.148 vs 1.63.46, these additions messed up support for other devices. Any version after 1.63.46 seems to have a corrupted data structure. This should be sorted out in the next week or so.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looks like it inhereted the config masks for the 16F144x which will be incorreect
The correct config masks fior 12F1571 should be ....
ConfigMask 0 0x0EFB
ConfigMask 1 0x3F03
Adding a part is not as simple as some make it out to be. :)
Last edit: William Roth 2016-06-07
A little closer look and the new PK2DeviceFile.dat does indeed supply the correct config mask. My bad, talking off the top of my head there.
The difference I saw without further investigation was the "programmed" config after burning the hex. The IPE and PK2 GUI have different ways of reporting this. The IPE would follow the data sheet in reading "unimplemented" config bits as "1", while the PK2 reports them as "0" which leads to the exact difference that I saw.
The program memories look exactly the same whether burned by the IPE or the new PK2 device file. Checksum is the same for the imported hex. The blinky led program works exactly the same.
So in conclusion, I feel the new device file for the PK2 PIC12f1571 & 1572 is good to go. Will report back if I run into any problems.
Looks like the config masks in the devicefile are incorrect. For 12F1571 they should be:Config 0 0x0EFB
Config 1 0x3F03
Hit Count help pleaseSent from sourceforge.net because you indicated interest in https://sourceforge.net/p/gcbasic/discussion/629990/To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Kent,
Atached is modified device file with some corrections to Ver 1.63.48. This should work with 12F1571/72. They should now be in family renamed to USB-Min III. I changed the version to 1.63.50 and added my initials to comments to keep it distinct from other versions.
The config bit masks for 1571/1572 have been corrected to match the data sheet. When the GUI opens and before memory is read the configs should read 0EFB & 3703. After reading memory the configs should reflect the actual settings.
Let me know if this works.
William, thanks so much. Looks like I am up to date with all the latest and greatest devices.
The hex file operations for the PIC12f1571 look just fine.
The new bit mask doesn't seem to address the CONFIG2 !LPBOREN. The datasheet says 3F03 which means the low power brown out reset is disabled. With 3703 bit mask it is enabled, is that what we want to do? In the PK2 configurator they mistakenly show bit 11 as unimplemented?
Kent.
3F03 is what is called for in the Programming Specs, This enables the bit as "implemented".
I had that in my notes but typed in a 7 instead of an F.
Please delete the previous file and use this instead
There we go. Thanks!
Kent
Kent,
As far as my research goes, this last PK2 device file correctly supports the most 8-bit chips. It is based upon 1.63.48 as originally published by "gert" and 1.63.46 as published by "Scasis-Dougey".
I made some corrections so that certain addded chips would work correctly (12F157x and 16F178x). Of these, I have personally tested 16F1788/89.
Hello again William. will this new .dat file look at the 12F1612 device also?
@Keith
Yes and no. The 12F1612 and 16F16xx devices were added in Ver 1.63.48. However the person who added them was not very familar with PICs at the time, and did not consider that these chips have 3 config words, whereas all other Midrange chips have either 1 or 2. This mean that the the existing scripts will only read/write CONFIG1 & CONFG2 ... CONFIG3 will always be at it default settings. This means that the watchdog timer cannot be configured.
I would recommend only using PK3 and MPLABx IPE with these chips until I or someone else can figure out how to add scripts that can read and write three 14-bit config words.
William
Last edit: William Roth 2016-06-09
I have removed the posted files as I found some more problems, While lots of new chips were added in 1.63.148 vs 1.63.46, these additions messed up support for other devices. Any version after 1.63.46 seems to have a corrupted data structure. This should be sorted out in the next week or so.