Instruction stepping went away

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Instruction stepping went away

1,963 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by jdurand on Wed Jun 13 22:53:58 MST 2012
I used to be able to use instruction stepping, but now it's grayed out.  I can single step code just fine, I can view the disassembly, i just can't get back to where I can step through the disassembly.

Using LPCXpresso v4.2.3 on Ubuntu Precise.

Problem shows up with an LPC1113 board I designed and is now in production, using Red Probe+.

Also shows up on LPC-Link card for LPC1769 using the built-in probe.
0 Kudos
Reply
4 Replies

1,869 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by researchinnovation on Fri Jun 15 23:48:59 MST 2012
[B][SIZE=3]Hi...!!! [/SIZE]
[/B]

Is this helping you...!!!

[B]
[/B]

[B]
[/B]

[B]Displaying assembly instructions when debugging[/B]

It  is sometimes useful to be able to view the actual assembly instructions  of your application when you are debugging. This can often assist in  understanding the behavior you see as the application executes.
One way to do this is to change into "Instruction Stepping Mode". To do this click on the "[B]i->[/B]" icon in the Debug view.
[IMG]http://support.code-red-tech.com/CodeRedWiki/DebugViewAsm?action=AttachFile&do=get&target=istep.png[...
This  changes debug behavior such that you will now step by processor  instructions, rather than source lines. It will also cause the  Disassembly view to be added to your current perspective, which will  display instructions around the current program counter.
If you click the "[B]i->[/B]" icon again to return to source stepping mode, the Disassembly view will continue to be displayed.
Alternatively the menu [B]Window->Show view->Other->Debug->Disassembly[/B] will cause the Disassembly view to be displayed (without changing the current stepping mode).
DebugViewAsm  (last edited 2010-09-30 07:54:00 by CrSupportAb)
0 Kudos
Reply

1,869 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by jdurand on Thu Jun 14 09:43:56 MST 2012
Hmmmm, that picture was reduced to useless.  I'll try a Zip of the picture.
0 Kudos
Reply

1,869 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by jdurand on Thu Jun 14 09:41:06 MST 2012
I found the problem, sort of...

The proper thread was selected but it wasn't working.  If I pick another thread and come back, THEN it works.

The screen shot is before I pick anther and then come back.
0 Kudos
Reply

1,869 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Jun 14 02:15:02 MST 2012
I presume that you mean the "i->" icon is greyed out within the Debug view's tool bar?

http://support.code-red-tech.com/CodeRedWiki/DebugViewAsm

Normally the only time this will happen is if you have selected an entry in the main part of the Debug view that is not part of the call stack.  In the Debug view you will see something like the following...

<AppName> Debug [C/C++ MCU Application]
 - MCU GDB Debugger....
    - Thread [1] ....
       - [I]<current func name>[/I]
       - [I]<caller func1>[/I]
       - [I]<caller func2>[/I]
           :
       - main...
    - arm-none-eabi-gdb...
    - <Location of AXF>


Make sure you select the "Thread" line or one of the functions under it. The "i->" icon should then be active.

If this doesn't solve the problem for you, then please provide more details of what you are actually seeing (and potentially a screenshot).

Regards,
CodeRedSupport
0 Kudos
Reply