• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 82 subscribers
  • Views 1111 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.

_c_int00_noexit:

James Bunger
Prodigy 170 points
Other Parts Discussed in Thread: MSP430F4152, MSP430G2231, MSP430G2553

I am using Code Composer Studio version 5.2.1 and am trying to marry parts of two projects onto a MSP430F4152.  One is in C and the other assembler.  Each works on its own.  In the combined project, I want to start in C and call the assember code, allowing the compiler to set up the stack and heep. 

Starting with the C code, the debugger always stops at main.  Adding a void ASSEMBLER_CODE (void) call and the assembly code causes the debugger to get hung up around  _c_int00_noexit: and never gets to the call to main.  This is true even for simple assembler programs consisting of several NOPs and a RET.  SLAA140 does not provide any advice in this direction.

I am guessing there is a Project Property that is not set correctly but cannot seem to find it. 

Thank you.

James

  • 0
    Intellectual 385 points

    Hi James,

    I am really not an expert but I think the debugger always stops at main when you launch it.

    The c_int00 I learned is a function which initializes c on the controller. I got a problem using a

    512 bytes buffer on a MSP430G2231 which has only 128 bytes of RAM, so it was way to big

    and all the code after the buffer was put to nowhere, and I also got hung up at c_int00 which

    jumped back to main.

    But another problem could be an interrupt without isr or something that resets the controller.

  • 0
    Prodigy 10 points

    Hi James,

    Did you solve the problem yet?

    I got the similar problem.  Every time I started debug session, I always got _c_int00_noexit and did not get to main.

    The problem has been solved.

    Please go to pulldown menu click Project-> Properties, select Debug from the left side. then select Auto Run and Launch Options from middle. Now you can see Auto Run Options from right side. The first line is Run to symbol, which is Main.  You only need to check On a program load or restart.  Click OK to finish. It is very simple, isn't it?

    --Jay--

  • 0 in reply to Jay Kung
    Guru 25210 points

    Jay Kung said:
    It is very simple, isn't it?

    I think the OP's (James') problem was quite a bit different. His issue looks to be not handling the C calling convention correctly in the asm code, thus messing up the stack frame on return and jumping into the weeds.

  • 0 in reply to Jay Kung
    Prodigy 30 points

    I am sorry jay. This didnt work for me. i am using the Launchpad with an  MSP430G2553 on it.  i have the same problem as indicated by James. I tried your suggestion but it didnt make any difference. I dont understand why CCS needs boot.c abd pre-init.c in debug mode. Any more suggestions? I am still stuck and i will keep trying out stuff.

**Attention** This is a public forum