• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 79 subscribers
  • Views 1923 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/MSP430FR5969: MSP-EXP430FR5969 Launchpad "Out of Box Demo" not working in CSS Ver 7.0.0.00043.

James Kirkley
Prodigy 70 points
Part Number: MSP430FR5969
Other Parts Discussed in Thread: MSP-EXP430FR5969, MSP430WARE

Tool/software: Code Composer Studio

I purchased two MSP-EXP430FR5969 Launchpad Boards from Digikey. I tried the "Out of Box" demo that came pre-load from the factory.
I'm using Windows 7 to run the GUI portion of the Demo. Each board worked fine in both "realtime logging" and "loging to FRAM"...and "playing back the FRAM" in the GUI.

So both the Launchpad Boards worked fine with the "factory loaded Out of Box Demo".

Then I loaded CCS Ver 7.0.0.00043, and compiled the source code for the "Out of Box Demo". I went into debug mode and re-flashed both boards.
Before the flashing could occur, each Launchpad Board required an automatic Firmware update...which went fine. After the firmware update, each Board seemed to flash the "newly compiled Out of Box Demo firmware image" fine.

I shutdown CCS and unplugged USB from the board and then re-plugged in USB and started the GUI portion of the Demo. 

The GUI is now only working in the Realtime mode. When logging to FRAM...the logging piece seems to be working correctly. At least the green LED is blinking every 5 seconds, which supposedly denotes the logging to FRAM. But the playback from FRAM is not working.

Each board is exhibiting the exact same behavior. This leads me to believe that the problem lies in the Demo Source Code, and not the flashing process or GUI program itself. Everything was working fine with the original factory loaded Demo.

I did get a warning message #10420-D during compilation: "FRAM device usage: clearing PM5CTL0.LOCKLPM5 bit at start-up".

It Recommended: Insert the following line of code at the beginning of the project:

" // Disable the GPIO power-on default high-impedance mode to activate
 // previously configured port settings
 PM5CTL0 &= ~LOCKLPM5;"

I inserted these tree lines as the first lines of the "int main(void)" function.
It got rid of the warning message...but the playback of FRAM is still broken.

I'm coming over to the MSP430 from using Atmel with the Atmel Visual Studio and Visual Micro Studio

I'm specifically looking for a "very low power solution" that the FRAM chips provide.

Any help would be greatly appreciated.

  • 0
    TI__Genius 15370 points
    Hi James,

    I've tested this out and I'm able to replicate the issue you're experiencing. For now I don't have a workaround for you but I will work with our CCS team to solve this issue and keep you updated. Thanks for bringing this to our attention.

    Best regards,
    Caleb Overbay
  • 0
    Prodigy 70 points
    Wow...I am very impressed with the quick turnaround on this.
    That gives me good confidence that I wasn't doing anything wrong on my part.

    Another clue is, I noticed in the GUI, that anytime the board connects to the COM port, a black frame line appears in the window.
    When trying to dump the FRAM, the black frame unexpectedly disappears.
    Maybe this means that the COM port is suddenly dropping it's connection?
  • 0 in reply to James Kirkley
    TI__Genius 15370 points
    Hi James,

    Thanks for the updated information. I think this is just an issue with the GUI and/or the out-of-box demo code. I don't expect it to hinder any other development you'd like to do with the board. Please let us know if you experience any other issues with example code or the board. Again, I'll be sure to keep you updated on the status of this.

    Best regards,
    Caleb Overbay
  • 0
    TI__Genius 9220 points

    Hi James,

    This is actually a known bug with the OOB source code... Please refer to this post for the fix to the current version of the source code: https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/478405/1733830#1733830

    I'll make sure to escalate this bug and fix it in our next MSP430Ware update.

    Thanks for evaluating MSP430!
    Eric C

  • 0 in reply to Eric Chen
    Prodigy 70 points
    I applied the fixes to the source code lines in question.

    It amounted to increasing delay times from 500000 to 900000 in a number of lines of code in the "main.c" and "FRAMLogMode.c" source files.

    After the changes were made...everything works fine.
    Thanks for your incredibly speedy help!!!

    Jim Kirkley.
  • 0 in reply to Eric Chen
    Prodigy 70 points

    Hi Eric,

    I think I found another thing to fix in your next MSP430Ware update. In the main.c file...lines 84-85 of the code is supposed to be clearing an interrupt flag on P1.1 which is connected to Button S2 on the board.

    The comment on line 84 is correct, but the code is passing GPIO_PIN0 as the pin number. Unless I'm confused, I think it should be passing GPIO_PIN1.

    GPIO_PIN0 is actually driving LED2.

**Attention** This is a public forum