Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2207 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.

Two debug message --TI MSP430 USB1/MSP430(Suspended-HW Breakpoint)

LEE YULIN
Prodigy 220 points
Other Parts Discussed in Thread: MSP-EXP430F5529LP

Dear all:

I using CCSv6.0 to program sample code to LDC1000 inductive sensing  IC EVM board via MSP-EXP430F5529LP.

When i build it then debug the project, it's shows two message,the picture as below:

(1)main() at main.c:39 0x004420

(2)_c_int00_noexit() at boot_special.c:102 0x004416(the entry point was reached)

How can i solve this two problem?

thank you.

Best regard,

Thanks.

  • 0
    TI__Guru**** 437671 points

    Hello,

    LEE YULIN said:

    When i build it then debug the project, it's shows two message,the picture as below:

    (1)main() at main.c:39 0x004420

    (2)_c_int00_noexit() at boot_special.c:102 0x004416(the entry point was reached)

    These two messages are not errors. This is your call stack. The call stack is integrated into the Debug view.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 220 points
    Hi, Ki-Soo:

    So i can ignore this two messages , right?
    Is this programming procedure correct?

    Best regard,

    Thanks.
  • 0 in reply to LEE YULIN
    TI__Guru**** 437671 points
    Yes this is correct behavior. It is just debug information.

    You don't have to necessarily ignore the messages. The call stack is a useful debug tool to get the function call history. I'm sure you will find that information useful in the future.

    Thanks
    ki