Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#182 The pic14 port, automatically creates the -DpicXXX

closed-fixed
Borut Ražem
None
5
2012-06-02
2012-06-01
Molnár Károly
No

The pic14 port, automatically creates the -DpicXXX definition. Now I write the libio directory and this definition needed to distinguish the PIC types. The adc is almost complete. Then comes the usart and i2c. As my time permits.

Discussion

1 2 > >> (Page 1 of 2)
  • Creates the -DpicXXX definition.

     
    Attachments
  • Borut Ražem
    Borut Ražem
    2012-06-01

    Sdcc already generates -D__SDCC_PROCESSOR="XXX", for example -D__SDCC_PROCESSOR="16f842". Isn't this enough to distinguish the PIC type?

    Borut

     
  • Borut Ražem
    Borut Ražem
    2012-06-01

    • assigned_to: nobody --> borutr
    • status: open --> pending-works-for-me
     
  • Raphael Neider
    Raphael Neider
    2012-06-01

    ... and if it is not, please use -D__picXXX. Philipp only recently worked towards replacing all compiler-generated defines to the standard-compliant form with two leading underscores. I am not sure, but it might even need to be -D__PICXXX (uppercase?).
    However, if other tools such as mplab to emit -DpicXXX I would like to know about it and withdraw my plea.

     
    • status: pending-works-for-me --> open-works-for-me
     
  • Therefore must that the pic16fam.h to function. This pic18fam.h is modeled on. I upload to the pic16fam.h.

     
  •  
    Attachments
  • Borut Ražem
    Borut Ražem
    2012-06-01

    * This file is has been generated using ./pic16fam-h-gen.pl .

    What about the pic16fam-h-gen.pl script? Do you intend to submit it?

    Borut

     
  • Anyway the -D__picXXX also good.

    Originally I wanted to send along with libio. Here it is.

     
  •  
    Attachments
1 2 > >> (Page 1 of 2)