• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 493 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/EK-TM4C1294XL: I2C needs a setting GPIO at application programming level?

Takano
Expert 1345 points

Part Number: EK-TM4C1294XL

Tool/software: Code Composer Studio

HI All,

I have a question about I2C which needs a setting GPIO at application programming level.

Manual of Microcontoller explains that I2C needs setting up GPIO something.

I expect that peripheral library supports such the setting, and ordinary programmer does not need to do for it.

If I2C really needs GPIO setting at application programming level, then which document describes about the setting?

Best Regards,

Takano

  • 0
    Guru 117855 points

    Candidate I2C "pins" appear across multiple MCU Ports - do they not?    And - while (some) few pins "default" to I2C (or UART, or SPI) most do not.

    Thus - as a general rule - would it not be wise to follow the "normal/customary" Peripheral Set-Up procedure?   (to properly enable your chosen I2C Port/Pins)

    • Enable that Port containing your desired I2C candidate pins
    • "Pin-Type()" those pins as I2C
    • "Pin-Configure()" those (same) pins as I2C

    It is firm's (and my) belief that those pins (defaulting) into I2C (from power up) may escape (some) of the above - yet that is extremely risky - and sure to "cause disaster" when you (later) seek to "Re-Use" your I2C code via (another - non-default to I2C) Port.

    Proper (full) set-up of Peripherals is the best guarantee of project success and (especially) re-usability...