Why IAR reports "can not run to main", or "failed to set a breakpoint on main"?

allankliu

During my developing ez430-RF2500. I tried to evaluate in simulator mode, the debugger reports:

"The stack plug-in failed to set a breakpoint on "main". The stack window will not able to display stack contents. You can change this setting in the Tools>Options dialog box. "

Sometimes it reports "can not run to main", also related to stack plug-in.

I re-create some small projects from scratch. Some projects reports same warnings, the others don't.

I have no idea about this warning. Does anyone know the root cause?

BTW, I am using IAR Workbench Kickstart for MSP430 V5.4.

Allan

over 13 years ago

0 M over 13 years ago

TI__Genius 13620 points

In the project options, in the Linker section, Output tab, make sure you have selected "Debug information for C-SPY"

0 allankliu over 13 years ago in reply to M

Intellectual 310 points

Thanks for your reply.

Now I remember I have enabled "Other" format for "intel extended", because it is supported by Proteus, which is used during my driver development w/o hardware. When I switch back, the warning disappeared.

Yours sincerely

Allan K Liu

0 karan patel1 over 12 years ago in reply to M

Expert 1085 points

i have same problem .i selected debug information option as you shown in above window still i got same problem "stack plud-in failed to set a breakpoint on "main",stack window is not able to view stack contents"

0 Ilkin Tacan over 12 years ago in reply to karan patel1

Prodigy 10 points

you must add d43 file not a43

0 rachit choudhary over 8 years ago in reply to Ilkin Tacan

Prodigy 70 points

I have added this file as well above solutions, still i am facing the same issue.

Sub-1 GHz

Sub-1 GHz forum

Why IAR reports "can not run to main", or "failed to set a breakpoint on main"?