I just create it from scratch for a long time ago,
using long and hard way when i start creating my IDE.

I think this piece of information will be useful for every available
PIC Compiler in this earth.

For this, i may give it to use just with JAL or pJAL only, to make
this compiler
beat some compiler that need $$$$, to get the information.

The information is created to per PIC basis, where this will be easier
to maintain.

I think DIPPinDef is useful to generate any kind of aliases or PIC
informations.

For now i got only 297 pieces of PIC informations.

Regards,
Mohammad Hafiz Othman

On May 20, 1:52 pm, Sebastien Lelong <[email protected]>
wrote:
> Hi Mohammad,
>
> This is interesting! I've extracted information about pins, like those in
> your "DIPPinDef" section, parsing datasheets. I could cross these with yours
> to double check (my parsing assumes a lot of things).
>
> Can you tell us how did you produce this data? Did you use a script, what
> source of information, ... ?
>
> Cheers,
> Seb
>
> 2009/5/20 MhzO <[email protected]>
>
>
>
>
>
> > Inside the zip file DatasheetCollect.zip contains PIC MCU External
> > Device Informations that I write.
>
> > I just put PIC10 and PIC12 first. If you have comments please do so
> > before I send PIC16 and PIC18.
>
> > I hope with this information i gave you all, you could upgrade the JAL
> > Library.
>
> > The definitions would state the pins, only for DIP.
>
> > Example for PIC10F200.DEX
>
> > Part=PIC10F200        ---> Part Name
> > PDF=41239D            ---> PDF Datasheet
> > Type=Flash            ---> Part Type
> > CoreSize=12           ---> core size in bit
> > MaxSpeed=4000000      ---> Max speed in Hz
> > ADCResolution=0       ---> Adc resolution in bit, 0 means no ADC
> > available.
> > AnalogComparator=0    ---> Comparator Available Number
> > PWM=0                 ---> PWM or CCP Available Number
> > Timer=TMR0            ---> Timer Available?
> > USART=0               ---> USART Available?
> > SPI=0                 ---> Support Serial Peripheral Interface?
> > I2CSlave=0            ---> Support I2C Slave?
> > I2CMaster=0           ---> Support I2C Master?
> > USB1_1=0              ---> Is USB 1.1 available?
> > CaptureCompare=0      ---> Capture
> > ParallelSlavePort=0   ---> PSP
> > BrownoutReset=0       ---> Brownout reset support
> > InternalOSC=4000000   ---> internal Oscillator available
> > InternalOSCOnly=1     ---> indicates is InternalOSCOnly available
> > SelfProgramming=0
> > ICSP=1                ---> In-Circuit Serial Programming
> > FlashAlternate=0      ---> Alternative flash could be used
> > DIPPinDef=            ---> pin aliases.
> > {
> >     1, NC,
> >     2, VDD,
> >     3, GP2/T0CKI/FOSC4,
> >     4, GP1/ICSPCLK,
> >     5, GP0/ICSPDAT,
> >     6, NC,
> >     7, VSS,
> >     8, GP3/_MCLR/VPP,
> > }
>
> > Notes=25mA source/sink per I/O
>
> > NC means Not Connected,
> > An underscore before variables (_) , indicates "not" or "active low",
> > eg :_MCLR
> > An asterisk (*) after variables means an alternative pin. VSS or VDD
> > alternative pins may not have asterisk on them.
>
> > Sorry for my bad English. English is not my first language, as I came
> > from Malaysia.
>
> > Regards,
> > Mohammad Hafiz Othman
>
> --
> Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to