• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 1499 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/MSP430F6736: Problem to use "getVersion( )" os MSP430ware

Haroldo Amaral
Expert 1105 points

Part Number: MSP430F6736

Tool/software: Code Composer Studio

Hi,

Inside the driverlib of a device there is a folder "inc" and inside it the file "version.h". Apparently the "#define getVersion()" return the current version of the driverlib, but there is some troubles:
- It's necessary to include the path of "/inc" folder by hand
- When I tried to use "getVersion( )" I received an error about wrong octal notation. To correct it is necessary to remove the left zero in the BUILD define.

Why not facilitate the access to this "function"?

Why not change algo the defines with version number to hexadecimal notation? With this is possible to easily read the version in the expression tab just changin the format to hexadecimal.

  • 0
    TI__Guru**** 220787 points
    Hi Haroldo,

    For what reason do you need access to the DriverLib version? It is not intended to be used by the application which is why the correct path is not already included. getVersion() produces an unsigned long (uint32_t) data type and the correct variable should be assigned accordingly to avoid any errors.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Expert 1105 points

    I think that is a simple way to verify the version or identify inside a firmware version.

    The variable was correctly assigned to the type, the problem appears to be inside the file, in the definition.

        

    Literals started with zero "0" denotes an octal number, and here is the problem. If you try to use "getVersion( )" in the current version of driver lib (2.80.00.01) there is no problem during the build, but if you try with the version "2.21.00.08", there is a problem because "08" (build version) it's not a possible octal number.

    Using the hexadecimal notation will solve this problem and enable an easy assesment of the value in the Expression tab.

  • 0 in reply to Haroldo Amaral
    TI__Guru**** 220787 points
    I will notify the DriverLib software designer of this issue so that it may be addressed in future releases.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Expert 1105 points
    Thanks Ryan.

    Regards,

**Attention** This is a public forum