Debug point failure

[meiermat]

Hello.  I found this exact problem in the CodeWarrior for Coldfire forum, but I can't follow the solution becuase my project options are quite different.

I'm using CodeWarrior 10.1.0 with the PE Micro Multilink and an S08DZ60.  The project is written in assembly, with no C support.  When I go to debug the project, I get the following message:

"Error stopping at main.

Reason:  Target request failed:  Failed to set breakpoint.

Continue?"

I have the options Yes or No.  Hitting no naturally aborts the process.  However, hitting yes proceeds to load the target board with the software and enter debugging mode, and everything runs fine after that.

Since this isn't hindering my ability to write and debug software, this isn't a pressing issue.  It's more an annoyance, but I'd like to solve the problem mostly because it's been nagging me and I haven't been able to find a solution.

Thanks,

Matt

[CrasyCat]

Hello

Did you check if you have debug information generated for your project source files?

The box Strip Symbolic Information  should not be checked in S08 Linker > Output project settings panel.

The option -NoDebugInfo should not be specified in the Other Flags edit box inside of the S08 Compiler > General panel.

You may also want to check the All options list box in the S08 Compiler Panel. The option -NoDebugInfo should not be specified there.

CrasyCat

[meiermat]

Maybe I'm just looking in the wrong places.  Where do I find the S08 Linker and Compiler panels?  I'm looking under the Project menu, and going to Properties.  Under that panel I get the following sidebar:

Resource

Builders

C/C++ Build

C/C++ General

Linked Resources

Processor Expert

Project References

Refactoring History

Resource Filters

Run/Debug Settings

C/C++ Build brings up a menu, which gives me a settings item, but there's no Linker or Compiler options.  Also, why would there be any compiler or linker information for this project?  As it is, I'm confused as to why there are C/C++ options.

Thanks,

Matt

[J2MEJediMaster]

Open the Settings item. This presents a view with a vast array of tools settings, including those for the compiler and linker.

---Tom

[meiermat]

Here's the array of options for the Settings item, under the Tool Settings tab.

Messages

Host

General

Disassembler

--Output

--Input

HCS08 Assembler

--Input

--Language

----Compatibility Modes

--Output

----Configure Listing File

--Code Generation

--General

Burner

--General

--Output

----Configure S-Records

--Input

Still nothing about the compiler or linker.  I looked through all the items, and don't see any options for -no debug info.

I also see tabs for Build Steps, Build Artifact, Binary Parsers, Error Parsers, and Build Tool Versions, but they're pretty bare.

Maybe I'm in the wrong set of menus?

Matt

[J2MEJediMaster]

It took a while for me to recall that you are using a pure assembly language program. Not only that, but from experiments I conducted in making an assembly project with the New Project wizard, you have made an absolute assembly language program, right?

When I make an absolute assembly language project, I get a build configuration layout similar to yours. There's no compiler or linker items because absolute assembly does not use a compiler or linker. So you cannot generate debug information through those choices, because they are simply not there.

Having said that, now look under the Language item. There should be a sub-item termed Code Generation. When you select that, check the option Absolute debug information to assembly source file. I think that should get you what you need.

---Tom

[meiermat]

Yes, it's absolute assembly.  In part, it's just because this is how I've always done it, and I'm comfortable doing so.  Barring some quirks when starting a new project in the new CodeWarrior, it's been very reliable.

I suspected the linker and compiler options should be absent, since neither is used, but it puzzled me that there were C and C++ options, so I just went with it.

I tried checking that box, but it didn't fix the problem.

Yes, there's a directive "ABSENTRY _Startup"

It was added when we created the project.  I didn't even notice it until now.  It didn't show up in my older projects for the HCS08, but we're still pretty new to both CodeWarrior 10.1 and this newer S08.  After doing some research, it looks like that directive needs to be there for the debugger to know where to start operation.

[bigmac]

Hello Matt,

This may be totally off the track, but did you place an ABSENTRY directive within your ASM file?  This affects debugging operations only.

Regards,

Mac