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.

MSP430 PMBus Device Support

Other Parts Discussed in Thread: TPS53679, MSP430F5308

Hi team,

We are looking to use the MSP430 in a PMBus application with the TPS53679. From the PMBus Library's User Guide, it says that we have support for the MSP430G2xx3 and MSP430FR5xx_6xx devices and I see that for these families we have examples in our resource explorer. Are these the only families that we can use with this library? 

We are interested in having a devices with 2 I2C ports and looking at potentially using the MSP430F5308. Are there any considerations we would have to take when looking at this device or other devices?

If need be, can we use the PMBus library with the software I2C ports as well?

Regards,

Akash Patel

  • Hi Akash,

    From Section 5.1 of the User's Guide: "The code examples and PMBus library can be implemented in different derivatives of the same family with little effort, and they can be migrated to other MSP430™ devices with the same I2C interface with some considerations such as pin usage, memory and timeout-timer availability."

    There is also SLAA386 for reference: www.ti.com/.../slaa386a.pdf

    So my suggestion is to take the MSP430G2xx3 USCI PMBus example and port it to the MSP430F5308. There are no additional considerations required so long as you have the available I2C bus and alert/control pins, I imagine a bit-bang I2C solution is possible as well but the additional communication layer has not been developed in the PMBus library and should be avoided in favor of using a (e)USCI module.

    Regards,
    Ryan

  • Hi Ryan,

    I just wanted to point out a bug that we found in our use of the PMBus Library. If you could pass that over to the appropriate team, that would be helpful.

    In the pmbus.c file, line 45 reads:

    #define PMB_BLOCK_READ                              0x40
    

    This should actually be:

    #define PMB_BLOCK_READ                              0x04
    

    Regards,

    Akash Patel

  • Hi Akash,

    Thank you for bringing this to our attention, I have submitted a bug request so that this issue is investigated and addressed.

    Regards,
    Ryan

**Attention** This is a public forum