Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 16 subscribers
  • Views 1459 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/RF430FRL152H: Debugging 152H SensorHub example with CCS 6.2.0 and MSP-FET

Ken Ward
Intellectual 345 points
Part Number: RF430FRL152H
Other Parts Discussed in Thread: MSP-FET, TRF7970A

Tool/software: Code Composer Studio

CCS 6.2.0, MSP-FET, RF430FRL152H SensorHub example project.

Example project is modified to query LIS3MDL magnetometer X, Y, Z axes instead of SensorHub BoosterPack sensors.  After my modified project builds and the Debug session is started, CCS indicates programming complete:

MSP430: There were 280 (code) and 51 (data) bytes written to FLASH/FRAM. The expected RAM usage is 0 (uninitialized data + stack) bytes.
MSP430: AutoRun: Target not run as the symbol "main" is not defined

and waits for a Run command, at the Reset_ISR()

This is when I halt then disconnect the debugger, then after reset, my modified SensorHub example app responds to the TRF7970A GUI commands.  Thanks to Alex for helping me get that working!

However none of my breakpoints inside the app are being honored, after hitting the Run icon. I must be doing something basic wrong. Any hints?

Thank you for looking at this post!

  • 0
    TI__Guru**** 173310 points

    Ken,

    I believe the experts in the device forum who are more familiar with this device and the SensorHub project will be able to assist better with this, so I will move this thread to the NFC/RFID forum.

  • 0
    TI__Expert 7820 points
    Sorry did not understand your question fully. From the previous thread:

    "Looking for a hint on how to get the debugger to run, so I can debug the I2C code in the SensorHub example project. No breakpoints are getting hit, even for very basic operations. Is the lack of a "main" symbol an issue? Could it be a compiler version or optimization level? I'm using 15.12.3.LTS in place of 4.4.5

    Am successfully using the MSP-FET for programming the 152H, now would like to use it to debug the code.

    Thank you for looking at this post!"

    Response:

    To debug with the SensorHub (or even the "Default") project, the ROM code needs to be told to maintain the JTAG connection. The risk is that the ROM code references the same pins (or switches on the EVM) for its settings as the JTAG connection uses. So if it is told to maintain JTAG, then it will still read the P1.7-P1.4 pins, but they will be set by the JTAG protocol. The only significant pin, is P1.7 the master I2C/SPI setting. Since it multiplexes with the JTAG TMS it will usually be low, it will select the master option.

    So what needs to be done to have debug access, is these steps:
    1. Load the SensorHub (or the Default) project
    2. After it loads and is halted, open the Memory Browser.
    3. Find the address: 0xF87D
    4. Write to it: 0x39 - 8-bits only
    5. Then resume debugging
    6. Any breakpoints in CCS will now work.