• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 654 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.

TI PinMux version 4.0.858 (Cloud) does not enable peripherals correctly?

Don Carlson2
Intellectual 410 points
Other Parts Discussed in Thread: TM4C1294NCPDT

I am using the TM4C1294NCPDT processor.  The TI PinMux only supports this part on the cloud version.

When configuring GPIO, USB, I2C, and ADC peripherals, I noticed the pinout.c file that is generated that there is only MAP_SysCtlPeripheralEnable() calls for the GPIO ports, and NO calls to enable the USB, I2C, and ADC?

Am I somehow missing a configuration setting on the PinMux cloud tool, or is the tool not working correctly??

For example, I see correct calls to configure the I2C5 pins correctly:

//
// Configure the GPIO Pin Mux for PB4
// for I2C5SCL
//
MAP_GPIOPinConfigure(GPIO_PB4_I2C5SCL);
MAP_GPIOPinTypeI2CSCL(GPIO_PORTB_BASE, GPIO_PIN_4);

//
// Configure the GPIO Pin Mux for PB5
// for I2C5SDA
//
MAP_GPIOPinConfigure(GPIO_PB5_I2C5SDA);
MAP_GPIOPinTypeI2C(GPIO_PORTB_BASE, GPIO_PIN_5);

But there is no call to enable the I2C peripheral? Expected to see:

MAP_SysCtlPeripheralEnable(SYSCTL_PERIPH_I2C5);

Any clues?

Thanks,
Don ...

  • 0
    Intellectual 410 points
    Also noticed the PinMux cloud utility does not correctly use the AHB port definitions. On the TM4C1294NCPDT, GPIO PortA through PortJ should be defined using the AHB base and definitions. Example:
    //
    // Configure the GPIO Pin Mux for PJ0
    // for GPIO_PJ0
    //
    MAP_GPIOPinTypeGPIOInput(GPIO_PORTJ_BASE, GPIO_PIN_0);

    Should be:
    //
    // Configure the GPIO Pin Mux for PJ0
    // for GPIO_PJ0
    //
    MAP_GPIOPinTypeGPIOInput(GPIO_PORTJ_AHB_BASE, GPIO_PIN_0);

    Anyone else having the same issues?

    Don ...
  • 0
    TI__Guru**** 244400 points
    Hello Don,

    Pin Configuration does not require the peripheral to be enabled. The Pin Mux configuration is completely handled in the GPIO Peripheral hence you will not see any peripheral being enabled. This has to be done by the application code.

    Regards
    Amit
  • 0 in reply to Don Carlson2
    TI__Guru**** 244400 points
    Hello Don,

    Glad that you have reported this. On the TM4C129 the APB address aperture is still enabled so that a migratory path to complete removal can be done on the TM4C129x. Having said that it can be fixed in the next release of the tool (which I believe is soon)

    Also the following post shall provide more information on the TI Pin Mux Tool Updates being planned for TM4C12x devices

    e2e.ti.com/.../451208

    Regards
    Amit