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.

MSP430FR2433: MSP430FR2xx_4xxDriver_Li b_Users_Guide-2_91_03_00.pdf

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

I am complaining about the documentation. 

1. Please put the name of the document on the first page. This document says "User's Guide". Which users guide? How about something like "MSP430FR2xx_4xx Drivers Lib Users Guide" I may have multiple users guides open when I am working on something I am not familiar with. 

2. The issue that caused me to come here:

I want to create a new project for the MSP430FR2433 that uses the MSP430FR2xx_4xx Driver Library for my IAR compiler. 

So I look at the table of contents and I think I am in luck. There is a Chapter 5 "How to create a new IAR project that uses Driverlib" 

First paragraph is:
"It is recommended to get started with an Empty Driverlib Project. Browse to the empty project in
your device’s family. This is available in the driverlib instal folder\00_emptyProject"

The fact that nobody noticed that "instal" was spelled wrong and no space between "folder" and "\00_emptyProject" should have been the clue that nobody checked this document. 

First off what is the "install folder"? I installed in "F:\ti" according to the installer when I installed it, but after searching the directory I see you meant (in my case) "F:\ti\msp\MSPWare_3_80_02_10\driverslib\examples\MSP430FR2xx_4xx\00_emptyProject\IAR"

Could they have meant "examples folder" and not "install folder"? That is still wrong, but closer. 

So I find it then what? End of chapter! Those were only three sentences in the whole chapter. 

This just told me that in the case I want to do a new project that uses the driverlib with the IAR compiler the project will be put in the examples directory of the of the library and it will only work the first time. Really?

Don't you think you should have a solution that works more than one time and that lets me put the new project in whatever directory I want? 

Let me see if Chapter 6 is any better...

Kip

  • Chapter 6 is a little better but I still think it may have some errors and omissions.

    So I created a new project where I wanted it to be.

    And started following the instructions.

    So I created a group called driverlib.

    Then it says "Now click Add files and browse through driverlib folder and add all source files of the family the
    device belongs to." If I had not been through the exercise before where I had to hunt down the empty project I would not have a clue what that meant.

    I believe they wanted me to go to (in my case) "F:\ti\msp\MSP430Ware_3_80_02_10\driverlib\driverlib\MSP430FR2xx_4xx" sort the directory by type, and select all the files that ended in ".c". At least that is what I did. I do not think it meant source files to include ".h" files but normally I think of ".h" files as part of my source code.

    Then it says "Add another group via ”Add Group” and add inc folder. Add all files in the same driverlib family inc
    folder." I think that means to go to the same directory and select all of the ".h" files.

    Then it shows another window titled "Options for node "NewIarPrj"" But has no instructions.

    Then it says "Click ”Finish” and start developing with driver library in your project." The window clearly says "OK" not "Finish". But it did not tell you what you were supposed to do.

    What I believe they wanted us to do was to click on the "..." button, and add a new directory for include files and go to the same directory that the .c and .h files were in.

    That tells the compiler to look in that directory for .h files. Which we already put in the project in the step above. The advantage of this is that it also lets it find the subdirectories "inc" and "rom_headers". So I think the second group I made was redundant.

    Kip
  • Hello Kip,

    Thank you for your post and feedback. I will definitely pass it along to our software team involved with DriverLib.

    Regards,

    James

    MSP Customer Applications
  • I am finding more as I go. Do I post what I find here or is there somewhere else I should post to? Some of the newer documentation says where to post errors to. This one does not.
  • Hello Kipton,

    The best place to post feedback about our documentation is using the "Submit Documentation Feedback" link in the bottom of our newer documents. Even though some of our older documents may not have this link, you can still use this link from another document, then change the document number (see highlighted screenshot below) to that of the older document, and then submit your feedback.

    Obviously, if you're referring to an old version with a newer version available, check the newest version for any changes before submitting feedback in case the gap has already (hopefully) been addressed. I hope this helps!

    Regards,

    James

    MSP Customer Applications

**Attention** This is a public forum