Please note that E2E has undergone a major upgrade. Before logging in, please clear ALL your browser's cache and cookies.

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/MSP430FR6989: MSP430FR6989

Part Number: MSP430FR6989

Tool/software: Code Composer Studio

Happy New Years TI Team,

I have a small issue I would like to get some guidance. I'm using the MSP430FR6989 LaunchPad development kit.  I am completing the MSP430 Workshop tutorial Booklet which is very good. The workshop does not mention the FR6989, I suspect the device was not released at the time of writing this workshop. Nevertheless things are going very well - for the workshop I have been following the flow for the FR5969.

Presently I am completing Chapter 5 "Interrupts", actually on the last page of this chapter where there is an optional LAB called Lab 5b on page 5-53.

This lab requires a download from the TI Resource Explorer. The download is actually a CCS project IMPORT called "wdt_a_ex2_intervalACLK".  This example uses WDT as a standard timer for causing an internal INTERRUPT.

I wish to complete this Optional Lab 5b but TI Resource Explorer does not seem to have this EXAMPLE PROJECT as defined in the workbook.

My question, is this EXAMPLE PROJECT LAB 5b for MSP430 Workshop done only for the FR5969 and not the FR6989?

If so, I would appreciate if anyone can point out the location for the FR6989 and this lab.


  • I found a project by this name over in the Driverlib examples. It includes a .lnk file for the FR5969, but it sounds as though you know how to deal with that.

    If you've installed MSP430Ware, it's in:


  • Thanks for the help.

    I was able to locate the "wdt_a" as you explained. I was able to run the design and BUILD/DEBUG. One thing I did not like was the way the "lnk" was handled as you mentioned, as it was set for the FR5989 and I'm using the FR6989.

    For completeness I want to place the proper lnk file FR6989 into the design, so I actually cut-&-pasted a lnk file from another project where the lnk file was defined for the FR6989 device. Not sure if Cut-&-Paste was appropriate flow, but its what I did.

    When I went back to build the design again, the CCS stopped and advised that the proper lnk file was not there, the CCS stopped gave an option to IGNORE this fault, I selected IGNORE and the design did build properly all the wall through DEBUG.

    I am not comfortable with this flow as I know CCS gave me an out, I think there is another and proper way to update this lnk file. Can you give me a hint on the proper procedure for making sure the proper lnk file is n the design?



  • I rarely change the .lnk file, so I usually let CCS manage it. This is a check-box at "Build Settings->CCS General->Manage the project configuration automatically". If you check that and then set the MCU "Variant" two lines above, it will set the .lnk file and other options for you. (The debugger will probably prompt you (first time) about switching variants, but then it will build you a targetConfig and not ask again.)

    This will deal with memory layout and device-register locations, but won't (can't) audit pin usage. I haven't checked, but from what you said earlier there aren't many differences there.

  • Hey Thomas,

    As Bruce said, I think your issue is that the project is set to FR5989 and you pointed it to a FR6989 linker file.  Updating the project settings to the MSP430FR6989 should fix this error for you, and it should link the correct header files for this device.  

    You are correct, I don't believe the FR6989 is included in the workshop currently.  We have it in our backlog to possibly update this workshop or even integrate the workshop into TI Resource Explorer directly.  



  • OK Bruce and JD,

    I think I have a grip on this now. I was able to open the Project Build Setting Menu and did locate the "CHECK BOX" for "Managing the project's target Configuration automatically. I was also able to select the proper device on my target eval board.

    I will have to remember to go through these steps when I bring in another project from the TI Resource Explorer Environment when the design was not originally designed for the device on my target board.

    This is good information - Thanks