Menu

18f252.dat and others

bed
2017-08-30
2024-04-18
  • bed

    bed - 2017-08-30

    I'm a bit unsure, but I/O=0 seems not correct, isn't it?

    'GCBASIC/GCGB Chip Data File
    'Chip: 18F252
    'Generated 10/12/2016
    'Format last revised: 14/11/2009
    
    [ChipData]
    Prog=16384
    EEPROM=0
    RAM=1536
    I/O=0
    ADC=5
    MaxMHz=40
    IntOsc=0
    Pins=28
    Family=16
    PSP=0
    MaxAddress=4095
    

    to be precise:

    grep 'I/O=0' 1*.dat
    18f242.dat:I/O=0
    18f2439.dat:I/O=0
    18f248.dat:I/O=0
    18f252.dat:I/O=0
    18f2539.dat:I/O=0
    18f258.dat:I/O=0
    18f442.dat:I/O=0
    18f4439.dat:I/O=0
    18f448.dat:I/O=0
    18f452.dat:I/O=0
    18f4539.dat:I/O=0
    18f458.dat:I/O=0
    18f6525.dat:I/O=0
    18f6620.dat:I/O=0
    18f6621.dat:I/O=0
    18f8525.dat:I/O=0
    18f8620.dat:I/O=0
    18f8621.dat:I/O=0
    18f8720.dat:I/O=0
    

    And if this is no Error, what does I/O=0 mean?

     

    Last edit: bed 2017-08-30
  • Anobium

    Anobium - 2017-08-30

    Well this is a find. Now you have found it... This needs to be fixed I guess.

    We have have 28 chips definition files with some data missing for the IO parameter. These are:

    See last paragraph below on how to get these chips supported.

    PIC12F520
    PIC16CR926
    PIC16F19197
    PIC18F242
    PIC18F2439
    PIC18F248
    PIC18F252
    PIC18F2539
    PIC18F258
    PIC18F442
    PIC18F4439
    PIC18F448
    PIC18F452
    PIC18F4539
    PIC18F458
    PIC18LF46j53
    PIC18F6525
    PIC18F6620
    PIC18F6621
    PIC18F66J99
    PIC18F8525
    PIC18F8620
    PIC18F8621
    PIC18F86J99
    PIC18F8720
    PIC18F96J72
    PIC18F96J99
    PIC18F97J72
    

    I need some to capture the data and complete the spreadsheet. The missing data is not a lot. I have shown the missing data below. Just need someone to update the spreadsheet and we can get these chips operational... another option is to hack the .dat file but these chips are not support until we get these dat files re-issued. I have checked... these files have been like this for years....

     

    Last edit: Anobium 2017-08-30
  • bed

    bed - 2017-08-30

    How to capture? From microchip website or from the chips itself, sorry no native english speaker

     
    • Anobium

      Anobium - 2017-08-30

      Try using MAPS from the Microchip website. There is an XLS you can download. Does this have this data that is missing?

      If yes... then yipee.

      If not, datasheets unless someone else knows a better method.

       
      • Peter

        Peter - 2017-09-01

        I can have a look to see if the data is in the MCC xml files.
        I suspect those chips don't have an xml file.

         
  • bed

    bed - 2017-08-30

    Ok, I do it, I think today or tomorrow, one day more is not critically.
    I come back with results. Where can I the actual xls sheet?

     
  • bed

    bed - 2017-08-30

    Ok, have downloaded the whole thing from microchip and sorting it out, first few not found, could it be thats the chips are very old or seldom?
    one PIC18F2420 in between was found 35 I/O so the table is a good first try. Looking deeper tomorrow it's to hot in Germany (one of 25 Days of Summer in the whole Season ...)

     
  • bed

    bed - 2017-08-31

    So, except of PIC16F19197 no Chip was found in the whole in one list of microchip
    often there are a 0 extended, bu never the exact name
    Look at table 2

     
  • Anobium

    Anobium - 2017-08-31

    Note that the following are not supported until we have sufficient information to create a valid .dat file.

    PIC12F520
    PIC16CR926
    PIC16F19197
    PIC18F242
    PIC18F2439
    PIC18F248
    PIC18F252
    PIC18F2539
    PIC18F258
    PIC18F442
    PIC18F4439
    PIC18F448
    PIC18F452
    PIC18F4539
    PIC18F458
    PIC18LF46j53
    PIC18F6525
    PIC18F6620
    PIC18F6621
    PIC18F66J99
    PIC18F8525
    PIC18F8620
    PIC18F8621
    PIC18F86J99
    PIC18F8720
    PIC18F96J72
    PIC18F96J99
    PIC18F97J72
    

    I have tried to create a valid .dat for the PIC16F19197 and there is insufficient data in the source file from Microchip to enable this. So, PIC16F19197 is also in the not fully supported list.

     

    Last edit: Anobium 2017-08-31
  • kent_twt4

    kent_twt4 - 2017-08-31

    Also add AVR Attiny102 and Attiny104 to not supported list?

     
    • Anobium

      Anobium - 2017-08-31

      @Hugh. Why are these not supported?

       
      • Anobium

        Anobium - 2017-09-01

        I have asked Microchip for produce claritification. They should be able tell us.

         
  • Anobium

    Anobium - 2017-09-02

    Attached are some resources direct from Microchip and a URL to enable us to create a dat file for the chips.

    These resources will populate the missing data in our configuration tooling.

     
  • Anobium

    Anobium - 2017-09-07

    And, after a long discussion with Microchip support they have formally responded.

    "I spoke to the divisions and they indicated that the ones below are not released.
    PIC12F520 PIC18F66J99 PIC18F86J99 PIC18F96J72 PIC18F96J99 PIC18F97J72

    Many of these devices are very old and legacy.
    PIC16CR926 PIC16F19197 PIC18F242 PIC18F2439 PIC18F248 PIC18F252 PIC18F2539 PIC18F258 PIC18F442 PIC18F4439 PIC18F448 PIC18F452 PIC18F4539 PIC18F458 PIC18LF46j53 PIC18F6525 PIC18F6620 PIC18F6621 PIC18F8525 PIC18F8620 PIC18F8621 PIC18F8720 PIC16F19197"

     
  • Anobium

    Anobium - 2024-04-18

    The 18F24xx & 18F44xx chips are now corrected and operational.

    See build 1381.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.