CodeWarrior 5.9 debugging with multilink: unable to put breakpoints on executed instructions.

[eugenia_suarez]

I have the following piece of code for coldfire V2 MCF52258:

According CW tutorial, dashes at left column tell us where we can set a breakpoint. As it can be seen, a low red point is tried to be put at instruction. You can think that it means that this code will not be executed as it has no dashes at left. 

IsolatedSetsBidir() is a function that will be executed under ETH arriving order. 

When I run this command script it should start to execute the code inside this function. tInteH3_IsolatedSetsBidir is a function that only will be called and executed if this commands launches IsolatedSetBidir(). So, if I can' t put a breakpoint here, this thing makes me think that it will not be executed. 

Actually, when I debug the execution thread doesn't stop where the breakpoint -at picture- is (when Ethernet command is received). But if I also have put a breakpoint inside tInteH3_IsolatedSetsBidir... "voila" it stops here. So, thread must be entering to IsolatedSetBidir(). It is no other way to call tInteH3_IsolatedSetsBidir.

I don't know why is it happening. Why I can not put a breakpoint in a place that is obviously executed? Is it a bug? 

Regards.

[TomE]

It may be a code optimisation problem. Can you build it with a lower level and see id that helps?

Can you open an assembly (or disassembly) window and set breakpoints in there instead? That may show you why your source breakpoints aren't working.

Tom

[Hui_Ma]

Hi,

Sorry for the later reply.

For the CodeWarrior V5.9 was quite old IDE version, there with very few support resource for this version IDE.

We recommend customer to update CodeWarrior software to CodeWarrior for MCUs (Eclipse IDE).

Thank you for the attention.

best regards,

Mike

[eugenia_suarez]

I know it would be the best. 

But actually it must need a good planning to do that because doing it will imply more changes than only put the project in a new IDE. The version of some used libraries are not compliant with newest CW versions. We are using an RTOS version that affect to great part of project code. So, this IDE jumping will be also done chosing a new MCU and facing new PCB electronic design. 

By the way we still debugging this project in order to look for because it is running in manufactured equipments for ten years. Some times we must to analyze application behaviour under concrete conditions. 

Thank you for the suggestion.

Regards.

[Hui_Ma]

Sorry for the later reply.

We don't have support resource for CodeWarrior for ColdFire V5.9 IDE software so far.

Quite sorry for that.

Mike