• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 904 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/RF430FRL152HEVM: CCS + MSP-FET + MSPDebugStack -- how to actually program the device?

Jason Kim31
Prodigy 80 points
Part Number: RF430FRL152HEVM
Other Parts Discussed in Thread: MSP-FET, RF430FRL152H, UNIFLASH

Tool/software: Code Composer Studio

Hi, after stumbling about with CCS ( Version: 7.1.0.00015 ) and the firmware for it ()  and various docs for MSP-FET as well as for MSPDebugStack, I am still stumbling about trying to find out HOW to actually use the MSP-FET (via CCS on Win10) to program the RF430FRL152HEVM.

After tweaking the various project settings in CCS, I believe I managed to successfully build in CCS the SensorHub and  NFC Projects for the RF430FRL152H under the (default)  Debug Profile

Apologies for this n00b question, but in all seriousness, this *seems* to be a lack in the documentation. For example, on page 6 (sec 2.3.2) of salu607.pdf, it clearly says I can debug/program the device using MSP-FET (and from the pic and the obvious cables and where they get plugged in, I can see that MSP-FET lights up sold green and that the MSP Application USART1 and MSP Debug Interface has come up on device manager on my win10 CCS box.)...

Okay. but whats the next step?? Do I need to do anything with the MSPDebugStack package? (I assume not, because I found the same MSP430.dll on both the CCS install dir as well as on the default msp430.dll_developer_package_rev_3_09_002_015.zip ???)

Thank you.

  • 0
    TI__Guru*** 135355 points

    Hello Jason,

    Which Compiler Version are you using for the project? This can be seen under Project Properties -> General -> Main tab (look on the bottom half of the tab under Advanced Settings)

  • 0 in reply to Ralph Jacobi
    Prodigy 80 points
    Hi. It has selections for TI v16.9.2.LTS, TIvv16.9.1.LTS and TI v(4.4.5). I set it to the first (which, I assume is the latest one that came after the suggested "upgrade" which happend right after CCS install just yesterday)
  • 0 in reply to Jason Kim31
    Prodigy 80 points
    Err, when I clicked on "Connection/Identify" on the same main tab, it tells me that the MSP-FET needs firmware upgrade.. its doing something now... I suppose that's good...
  • 0 in reply to Jason Kim31
    TI__Guru*** 135355 points
    Hi Jason,

    While the LTS compilers are the newest, our project is older so they don't always play nice with them. Please try the TI v(4.4.5) Compiler and see if that helps.
  • 0 in reply to Ralph Jacobi
    Prodigy 80 points
    Sorry, I think there is a disconnect here.

    If the MSP-FET is plugged in, is the transfer of the compiled binary to the board automatic? How do I just "program the device?"

    Is debugging with the MSP-FET as simple as just starting a debug session from the CCS gui?

    Strangely enough, in the project properties tab, the available compiler versions are 16.9.2 and 16.9.1. The older one has disappeared (!) Perhaps it was set originally in the project, but was overridden by CCS?

    Where do I find, and how do I install the older compiler toolchain?

    Thank you!
  • 0 in reply to Jason Kim31
    TI__Expert 7820 points
    There are two ways to program RF430FRL152HEVM. One is through CCS (and it should work with the latest compiler, in fact the project is using one if the latest compilers). Through CCS you have the option to modify the source code obviously.

    To program through CCS (it seems as if you may be having difficulty here) is simply click on the "green bug" button. This should compile and then program the RF430FRL152HEVM. Once it compiles it then programs and it will halt at the first instruction. If you do not need to debug the project, I would recommend to stop the debug session by clicking on the red button. Then you can power-cycle the EVM and it will operate according to the project programmed.

    There is another way as well. You could use UniFlash. This simply programs the device with one of the binaries in the "Debug" folder. It is simpler and more reliable but with no debug capability.