• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 493 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.

Original question:

CCS/MSP430FR5969: Printf causes a breakpoint

CCS/MSP430FR5969: MSP430FR5969

user6139757
Prodigy 10 points
Part Number: MSP430FR5969

Tool/software: Code Composer Studio

Hi,

I am connecting a FSR sensor from ADC to my self-develop board, which using MSP430FR5969 processor.

Recently, I want to use printf function in a while loop to print the value in my console so that I can test my sensor.

However, the printf function always halt in trgmsg.c file line 122, which requires me to keep pushing resume button.

I am wondering if this a common problem for CCS? When I used the same method in a built-in "hello world" project it works perfectly.

Is there any solution to this problem?

BTW, I am using CCS V8.2.0

This is my first time posting question. If there is anything i need to provide, please let me know.

Thank you in advance.

  • 0
    TI__Guru**** 171034 points

    Hi,

    Both the original thread above and the one below seem to tie this issue to a device configuration issue. 

    https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/412403 

    I will notify the MSP430 device experts to provide any additional insights about this. 

    Hope this helps,

    Rafael

     

  • 0
    TI__Mastermind 29075 points

    Hello,

    I'm not sure of the best solution here.  Is the Printf() working as expected otherwise?  If it works in another project, then it could be somehow related to the project settings.  

    While debugging, you can go to view-> breakpoints and should be able to see all the current breakpoints.  If there is one here, you should be able to disable it.  

    Another option would be to run in "Free run" mode, which skips all breakpoints.  

    Please test these suggestions and let me know if this work for you.  

    Thanks,

    JD