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.

MSP430FR5962: About Libraries available for MSP430

Genius 5350 points
Part Number: MSP430FR5962

Hi experts,

Q1:Is there any errata information on standard functions that are not specifically mentioned in the TI compiler user's manual?
Standard functions are functions that are only described as "supported," such as C99. We need information on potential bugs that are not listed in the above documents.

Q2:When implementing software (when using libraries including standard functions), what method should be used to determine if the function or library to be implemented can be used?
I understand that I need to check at least the following documents:
Device user's guide, datasheets, and errata. Compiler and assembly language user's guides
We also need information on the above to eliminate potential bugs, etc. by not using functions that cannot be used (or are not supported) in the first place.

Please point out if my explanation is insufficient.

Best regards,
O.H

  • 1. About your first problem, it is not about driverlib. It is about the TI complier. Sorry, as I know, there is no Errata for the complier. Can you tell me why you have this concern? If you have any concern about the complier, I think you can choose GCC complier, which is open source. Or you can choose the complier supported by IAR. 

    2. All the functions of the driverlib is tested by TI. Besides, the driverlib is open source You can see the register level code that how it operated. I think you can read the driverlib API guide and refer to our code examples to build your software. If you meet any problem, you can refer to the register value to see whether the register setting is as expected.

  • Hi Eason,

    Thank you for you reply.

    As I answered in another thread, there is a specification that TI compilers have a different definition of epoch when using the localtime() function, and some compiler versions may not have this information. If no information is available, this is a potential problem. It is a difficult situation to use MSP430 if there is such a potential problem in the functions and libraries used for future MSP430 development.

    I understand that "C99 is supported" means that it can be used with MSP430 without any problem, but is this understanding incorrect in the first place?
    It would be helpful to know TI's stance on the use of standard C libraries and functions such as C99.

    Best regards,
    O.H

  • localtime() is operating system dependent and makes no sense at all in an embedded application like those the MSP430 is intended for. On Unix/Linux it works because there is an OS that provides that service.

  • Sorry, as I know, there is no Errata for the complier.

    If you go to MSP430 code generation tools - compiler there are link to the release notes for each compiler version, and the release notes have a list of Known Defects.

    As I answered in another thread, there is a specification that TI compilers have a different definition of epoch when using the localtime() function, and some compiler versions may not have this information.

    There is defect Document that the epoch can be changed from 1900 to 1970 by defining the preprocessor symbol __TI_TIME_USES_64 (EXT_EP-10174) which is reported as fixed in MSP430_21.6.0.LTS

  • Hi,

    Thank you for your reply. I understand what you are saying, but our customers are actually running it in their applications. Since localtime() is not supposed to be used with MSP430, but is listed as "C99 supported", I was wondering how I can use it in our development.

    Best regards,
    O.H

  • Hi,

    Thank you for your reply. I had missed that information and will refer you to it as well.

    Best regards,
    O.H

**Attention** This is a public forum