How to program M52223EVB using Multi-Link with CW10 (and MQX3.6)

[mykepredko]

Hi Folks,

I'm having problems with not being able to program code into a M52223EVB using the Multi-Link connection.  I'm using the release version of CW10 and the latest MQX build. 

When I try to program an application using "Flash File to Target" (even just an empty project for Debug), I get the message:

Initializing remote connection ...

Performing target initialization ...

Error: Connect Failed.

Can't connect. Can't load GDI dll - System error:The specified module could not be found.

. (ColdFire GDI Protocol Adapter)

Error: command failed

This seems to indicate that CW is not attempting to access the correct programmer hardware.  I have spoken to my FAE and he got the response:

"To solve this issue the launch configuration needs to be reconfigured by opening the LCD (launch config dialog) and choosing again the connection. This action will reset the previous settings."

I have tried to find the "LCD" and haven't had any luck in getting the connection back. 

Could somebody please outline the steps I should take to a) find the LCD and b) selecting the correct programmer?

Thanx - this is really appreciated,

myke

[J2MEJediMaster]

1) After CW 10 launches, select your project in the CodeWarrior Projects view.

2) Choose Run > Debug Configurations.

     A Debug Configurations window appears. On the left is a list of items under CodeWarrior Download.

    These items are launch configurations, which store the settings information required for a run or debug

     session. On the right of this window is the configuration settings area.

3) On the left, click on the item (launch config) that matches your project name.

4) On the right, click on the Debug tab.

    The settings area now displays debugger settings. There is an area further down that displays Debugger

    Options and has more tabs.

5) Click on the Connection tab under the Debugger Options and see if the Multilink probe is selected in the

    Connection option. If not, click and select it from the drop-down menu.

---Tom

[mykepredko]

Hi Tom,

Thank you - that was a big help.  The code seems to be downloaded into the EVB now (messages indicating success AND the LEDs on the EVB are flashing).  "printf" seems to be working in the different tasks :^) and my code for accessing the LEDs isn't :^(

Just as a follow up, when I start "Debug" (F11), I get a "CodeWarrior Alert" dialog box with the message "Unable to find target task "Blink4_mcf52223_Int_Flash" in the current workspace.  Do you want to skip this task and continue launching?"  If I say "Yes", then things seem to run okay (after a few moments the debugger seems to come up and when I hit "continue", my program starts). 

If I say "No", I get a "Problems Occured" dialog box with the message "'Launching Blink4_m52223evb_Int_Flash_Debug_PEDBM' has encountered a problem.  Unable to find target task "Blink4_mcf52223_Int_Flash" in the current workspace."  The debugger doesn't start up after this. 

Shouldn't it be looking for "Blink4_m52223evb_Int_Flash_Debug_PEBDM" (which has been downloaded into the evb) and not "Blink4_mcf52223_Int_Flash"? 

The good news is I'm off to the races. 

Thanx for the quick reply,

myke

[statrix]

Hi,

Same problem here. I think is some path issue, caused by non english default "Program files" folder, but i guess this is 

not your case right?

Did you solve it?

Thanks!!

[mykepredko · Accepted solution]

Hiya,

I can't really comment as to whether or not it is the same problem without seeing exactly what you are getting but I do have a bit of a (sloppy) work around to the problem:

1.  After I successfully build the ap with MQX, I then click on "Run"->"Debug Configurations".

2.  I then click on the "<Appname>_<board>_Int_Flash_Debug_PEBDM" on the left side to highlight it. 

3.  Next, click on the "Debugger" tab

4.  Click on the "Download" (under "Debugger") and deselect the "Execute Tasks" (this will avoid the message when you start up the debugger.

5.  Next click on the "Connection" (under "Debugger")  and select a different "Connection:" (the one I get initially, which is correct, is "P&E ColdFire V234 Multilink\Cyclone Max") and then click on "Apply". 

6.  Change the "Connection:" to the original (correct) setting and then click on "Apply". 

7.  You can close the "Debug Configurations" dialog box and you should be able to program and debug without any problems. 

For some reason, CW does not properly recognize the debugger link.  To get it working, you have to change it to something else, then change it back. 

Let me know if this fixes your problem.

myke 

[statrix]

Finally the solution!! 

The point is that when you add the target task from double clicking the *.ttf file (as it is shown in the "FSL_MQX_Getting_Started.pdf"  the debugger can't find it (at least as it had happened to some of us). 

And that is because the debugger searches for a .xml file!!.

So, the target task to add is the "generic" one for your derivative located at ..\MCU\bin\plugins\support\target task\flash programmer\coldifre  as it is shown in the "Targeting_Microcontrollers.pdf". 

Now the "funny" fact is that the .TTF file is also an XML file almost identical to the generic one. 

It would be interesting if someone from freescale can explain us is happening this.

[mykepredko]

I'm glad I could help. 

It is a known problem (I got my solution from my FAE (thanx Derrick!)) but the initial solution, as described earlier in this forum thread really isn't helpful until you've worked with CW10 for a while.  After getting it written up to me, I wrote out the instructions I posted previously. 

I'm hoping that the problem will be fixed in the next version of CW10 and this extra playing around isn't necessary. 

Good luck with your application!

myke