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.

TMS320F280039C: PMBus multiple slave address support

Part Number: TMS320F280039C
Other Parts Discussed in Thread: SYSCONFIG

Hi Champ,

I am asking for my customer.

As the PMBus module has to two modes, PMBus mode and I2C mode. It is known that PMBus mode could have multiple slave address support.

(1). Does the PMBus over I2C also hw support multiple slave address ? From sysconfig GUI, after checking the enable I2C mode checkbox, if the device is configured as target mode in PMBus device mode, it is grayed out for the masked addresses displayed in binary. May I reconfirm that ? 

(2). Continue to 1st question, if not, any sw workaround to achieve multiple slave address in I2C mode ?

(3). The PMBus example we have now (located at libraries\communications\PMBus), it is included a library (F28003x_PMBus_Communications_Stack_Over_I2C.lib) and be called in the example (pmbus_stack_over_i2c_project) , do we have a plan to disclose it, and for customer could direct control of underlying registers of PMBus ?

Thanks and regards,

Johnny

  • Hello Johnny,

    It will take some time for me to look into this question, I will try to get back to you by the middle of next week just to see if I can find some answers on my own first.

    Best regards,

    Omer Amir

  • (1). Does the PMBus over I2C also hw support multiple slave address ? From sysconfig GUI, after checking the enable I2C mode checkbox, if the device is configured as target mode in PMBus device mode, it is grayed out for the masked addresses displayed in binary. May I reconfirm that ? 

    If you're talking about PMBus over I2C, then this is a requirement of the I2C peripheral which doesn't supports multiple addresses when it is a target. If you're talking about using the PMBus as an I2C, then the same requirement for I2C still stands (the target address mask is not used within the PMBus initialization when configured in I2C mode).

    (2). Continue to 1st question, if not, any sw workaround to achieve multiple slave address in I2C mode ?

    No, we do not currently have a software workaround for this.

    (3). The PMBus example we have now (located at libraries\communications\PMBus), it is included a library (F28003x_PMBus_Communications_Stack_Over_I2C.lib) and be called in the example (pmbus_stack_over_i2c_project) , do we have a plan to disclose it, and for customer could direct control of underlying registers of PMBus ?

    This example uses the existing I2C peripheral to implement PMBus, it is not an example which utilizes the actual PMBus peripheral. We currently don't have any examples using the driverlib for PMBus to create an example, but I believe there is a plan to create the PMBus examples. I'm not sure what the timeline is on this, although I wouldn't expect it until later next year at the earliest.

  • Dear Omer,

    "...If you're talking about using the PMBus as an I2C, then the same requirement for I2C still stands (the target address mask is not used within the PMBus initialization when configured in I2C mode)."

    May I confirm again?

    You mean F28003x PMBus module supports target multi-address-mask in PMBus mode, but it CANNOT support target multi-address-mask in I2C mode.

    Is my understanding correct?

  • You mean F28003x PMBus module supports target multi-address-mask in PMBus mode, but it CANNOT support target multi-address-mask in I2C mode.

    Is my understanding correct?

    Yes, that is my understanding of this peripheral.