CW10 can't find my .ttf file; won't flash image to board

[dhlocker]

- Right-click on my hello_Thor-1_2 project->Debug As->3 CodeWarrior Download

- select intflash_d.elf in the C Local Application window [Qualifier is m68k be - /hello_Thor-1_2/Int Flash Debug/intflash_d.elf) and click OK

- build verifies that all binaries are up to date, then I get a CodeWarrior Alert window with the message:

======8<-------------

Unable to find target task "hello_Thor-1_2_mcf52259_Int_Flash" in the current workspace

------------>8=======

The only file matching that pattern is the TargetTaskFramework file
./mqx/examples/hello/cw10/hello_Thor-1_2/hello_Thor-1_2_mcf52259_Int_Flash.ttf

which fits my discovery that the download hasn't worked

======8<-------------

Clicking No (do you want to continue) aborts the debugging with a window 'Launching hello_Thor-1_2_Int_Flash_Debug_PEBDM' has encountered a problem.

Unable to find the target task "hello_Thor-1_2_mcf52259_Int_Flash" in the current workspace.

------------>8=======

I haven't been able to find a place to specify the path to that file (closest seems to be in the Debug Configuration->Arguments->Working directory which is the default ${workspace_loc:hello_Thor_1-2}

That file is NOT in the current workspace because it is in the project's space (I imported the project without copying the project into the workspace.)

Suggestions?

Donald.

[madifazio]

Well, this is pretty old, but I think it's a good place to share my experiences.

Double-click the file
./mqx/examples/hello/cw10/hello_Thor-1_2/hello_Thor-1_2_mcf52259_Int_Flash.ttf
will create the task that the debugger is looking for.

The secret is that the task generated matches the name specified in the project options.

Project Properties-> Run / Debug Settings-> Select configuration and Edit-> Debugger->Execute Task (at very bottom)

If the task matches the previously generated, you should have no problem in launchingthe debugger.

Greetings

[dhlocker]

Thank you, Marcos.

I also discovered that TaskName field in the xml element <TargetTask> in the .ttf file has to have the name as the .ttf file (but without the .ttf extension) and that the TaskProjectName field in the <TargetTask> element has to match the project for which the Target Task is destined.  This doesn't happen automatically when CodeWarrior "copies" a project to a new project.  There are a huge number of places where various references are not properly re-referenced, though the files are copied.

My current practice is to set up all the debug configuration settings, change to the debug perspective, and import the appropriate Target Task (e.g. MCF52259.xml)  I was just working on this again on Monday.

Donald.

[dhlocker]

Forgot to mention that if I don't abandon the debug session, CW does find the .cfg and .mem files and successfully attaches to the board and can start and manipulate the processor.  The image there doesn't match the one in CW, so I can't really debug, but the rest of the business seems to function.

TIA,

Donald.

[dhlocker · Accepted solution]

Well, that was fun.

I had to import the task into the current debug perspective.