• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 233 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DLPC350: How to enable and configure FW 4.1 I2C_BUSY_GPIO feature correctly

Anders Guldahl
Intellectual 385 points
Part Number: DLPC350

We are trying to use the new I2C busy gpio feature of firmware 4.1, but cannot get any activity on the selected gpio pin. Is this the correct way to enable it in the INI-file before building our firmware or do we need to do something different?

PERIPHERALS.I2CBUSYGPIO_ENABLE 0x01 ;
PERIPHERALS.I2CBUSYGPIO_SELECT 0x0D ;

Our assumption is that this should enable the i2c busy gpio feature and map it to gpio 13 (0x0D)?

  • 0
    TI__Mastermind 28005 points

    Anders,

    What platform are you doing this on? Are you on an EVM, or a custom board? 

    Regards,

    Philippe Dollo

  • 0 in reply to Philippe Dollo
    Intellectual 385 points

    We are using a custom board. Do you have a working configuration ini file we can compare with? maybe gpio 13 doesn't work?

  • 0 in reply to Anders Guldahl
    TI__Mastermind 28005 points

    Anders,

    Let me verify with the team and get you a response ASAP.

    Regards,

    Philippe Dollo

  • 0 in reply to Philippe Dollo
    TI__Genius 10925 points

    Hi Anders, 

    Kindly note the following about the I2CBUSYGPIO Pin:

    A GPIO Pin can be configured to act as a I 2C Busy Pin, which will be raised to indicate that the controller is busy processing an I2C Command. Two parameters in the Default.ini configuration file is used to control this functionality. "PERIPHERALS.I2CBUSYGPIO_ENABLE" is used to enable/disable the I 2C Busy Pin functionality, while the "PERIPHERALS.I2CBUSYGPIO_ENABLE" parameter is used to select a particular GPIO pin for this functionality. Valid GPIO numbers for this parameter are : 14,15, 20, 21, 25, 27, 28, 29, 33, 34, 35, 36.

    Kindly also note the following: 

    1. I 2C Busy Pin is only available with DLPC350 FW v4.1.0+ and LightCrafter 4500 EVM GUI v4.0+.

    2. I 2C Busy Pin configuration cannot be changed through any command. The related parameters in the INI needs to be set properly and the INI needs to be attached with the FW using the GUI Firmware Build Tool to make any changes to this configuration.

    Thanks & Regards,

    Hirak.

  • 0 in reply to Hirak Biswas
    Intellectual 385 points

    Hi again Hirak,

    As I mentioned, we are using the INI-file to configure this, see first post for exact entry in ini-file. We are using fw 4.2.0 and building with GUI 4.0.0.  No activity on the configured GPIO.

    One additional question, is this feature reliant on also updating the bootloader? (We always upgrade units with "skip-bootloader" checked, since this is the only way it is safe for power-loss during update etc. )

    -Anders

  • 0 in reply to Anders Guldahl
    TI__Genius 10925 points

    Hi Anders,

    The "skip bootloader update" should not affect this setting. In your first post I can see you have selected GPIO13, which is not in the supported GPIO list. Kindly use a GPIO from the provided list and try again.

    Thanks & Regards,

    Hirak