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.

MSP430F6746: MSPWare changes in pmm.c(HAL_PMM.c)

Part Number: MSP430F6746
Other Parts Discussed in Thread: MSPWARE, MSP430WARE

Hi,

My customer has a question for MSPWare change in pmm.c(HAL_PMM.c).

The customer has been using MSP430Ware version 2.0.12 (12/15/2010).
Now they are planning to develop new product and found pmm.c and HAL_PMM.c are different in the latest MSPWare version 3.80.14.01.
https://dev.ti.com/tirex/explore/node?node=AL2TddKgbiS0Iyx8RrhcKg__IOGqZri__LATEST

Please see below page#5 (yellow parts).
pmm.pdf
He wants to know reason of the changes and wonders whether he should update his software.

Questions:
Q1) What is the reason of the changes?
I found below comments in release notes "Revision History" section. Is this the case?
https://dev.ti.com/tirex/explore/node?node=ABJipQf4YI2Pe1XjKgHMSA__IOGqZri__LATEST

2.80.00.01
Bugzilla issue(15684) fixed - PMM correctly waits until both SVM high and low sides are settled

Thanks and regards,
Koichiro Tashiro

  • Hello Koichiro,

    For new product development, yes,  it is recommended to use the latest release as it contains updates and bug fixes or errata workarounds.  For their existing project, if they have not seen any issues with the PMM, then it is not likely to be a problem to continue with older version.  It really depends on how many products they have in the field and for how long of time.

    I did checkthe F6746 errata and there is one PMM errata #15 that can affect this device.  Have the customer review the workaround.  There is a driverlib function in the workaround description that they can temporarily add to their project, make the function call and it will tell them if PMM15 is relevant to their device and version of driverlib.

  • Hi Dennis,

    Thanks for your reply. I checked your answer, but I am not sure I understood it correctly.

    For new product development, yes,  it is recommended to use the latest release as it contains updates and bug fixes or errata workarounds.  For their existing project, if they have not seen any issues with the PMM, then it is not likely to be a problem to continue with older version.  It really depends on how many products they have in the field and for how long of time.

    I understood above is just a generic answer, not specific to the pmm.c changes customer is asking, correct?
    If so, could you provide "Bugzilla issue(15684)" information?

    I did checkthe F6746 errata and there is one PMM errata #15 that can affect this device.  Have the customer review the workaround.  There is a driverlib function in the workaround description that they can temporarily add to their project, make the function call and it will tell them if PMM15 is relevant to their device and version of driverlib.


    Above answer seems nothing related to the pmm.c changes, correct?

    Thanks and regards,
    Koichiro Tashiro

  • Hi Koichiro,

    I'll have to get help on this.

  • Hello Koichiro,

    We won't be able to tell you exact changes for the differences between versions the customer is comparing are too far apart. We only have kept previous version from MSP430Ware 3.80.0.0.0 release (2017) to the latest. 

    We no longer use bugzilla as a bug tracking software, so we won't be able to get information from there either. I do know we have made periodic updates to DriverLib around the PMM module to account for emerging scenarios and erratas across device families.

    The recommendation is to use the latest version of driverlib and MSP430Ware for new projects. Also keep in mind  relevant errata docs as they will point to the most up to date workaround information. 

  • Hi Jace,

    I see. Thanks.

    Thanks and regards,
    Koichiro Tashiro

**Attention** This is a public forum