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.

CCS4.1.1.00014 Debuger "Disable interrupts while stepping" and stability

Other Parts Discussed in Thread: MSP430F123

Hi!

Why the menu item "Disable interrupts while stepping " is disabled permanently in context menu (CCS v4.1.1.00014 )? Of course I can switch GIE flag every time manually, but this feature was convenient for use. 

 

The problem appeared when I installed automatic update to CCS v4.1.1.00014 Core edition couple day back. I have instaled just a MSP430 development tools.

The debuger is working worse than before (V4.1.0.02003). It stop's responding frequently.   Now I am working with MSP430F123 device using  MSP-FET430UIF v1.4a, but problems persist on eZ430-F2013 as well.  OS is winxp pro SP3.

The error log:

2335.CCS41114.log

 

Regards

 

 

  • Hello,

    I also see the issue with that option is no longer accessible. I have filed bug number SDSCM00035402 for the issue.

    Could you describe in more detail the issue where it stops responding? Does it hang and never come back (and you have to kill in task manager)? Does it crash?

    Thanks

    ki

     

  • Hello,

    Thank you! I wasn't sure - may be it is moved somewhere else.

    From user point of view: If I have pushed a RUN button - it comes disabled (gray), but HALT button is not activated (still gray) - the trouble is here.

    After that there can be several ways to go out: - sometime RESET CPU button help's me, if not - TERMINATE ALL button. It can help and after reloading debuger all works again. Sometime it is waiting long time to terminate- if I disconnect a JTAG interface it performs termination of debugger. If it is not working I have to kill CCS by Task Manager. Actually often I can solve a debugger problem without restarting CCS. As I have used CCS v4.1.0 more than month, and v4.1.1. just few days.  I can not specify - was all cases mentioned before for v4.1.1. as well.  Definitely there is some problem by breakpoints with conditions, let say "break at address when a = 15" but I have to tray reproduce it.  

     

    Regards,

     

    Juris

     

     

     

     

     

  • Juris, 

    Do you see the issues on a F2013? I ask this because I have access to that device, so I can try to reproduce the issue. If you have a test case also (project), that would be very helpful

    Thanks

    ki

  • Hello,

    Regarding the "Disable interrupts while stepping", I was also surprised to find a greyed option. But in fact, this option was multiplied in three : while running, while source-stepping and while assembly-stepping !

    You'll find it in two places :

    - remanent setting :in the project's "Debug Properties ..." => Generic Debugger Options, the three "Disable interrupts" options are the very bottom of the options list

    - temporary setting in a debug session : the menu "Tools => Debugger Options => Generic Debugger Options" is the same as above, but open in a new tab; scroll to the bottom to see the three options ...

    Have fun !

    Philippe