I cannot connect to the Tower MCF5441X from CodeWarrior 10.
I dont understand why I cant talk to the processor board to download the program and debug.
Did not have this problem with older CodeWarrior and the MCF522xxEVB.
I'm borrowing the thred, hope it's ok! I have exactly the same problem..
I opened an Example project in CodeWarrior10 and it builds ok. But when I should debug it cant connect to target.
Error message: "An error occured while connecting to the interface hardware or target specified in the Launch Configuration Dialog...
Dropdown list: "USB Multilink - USB Port"
Dropdown list: "(No Device Available)"
I've looked at the USB connection settings under "debug configuration/mcf51cn128_demo - MCF51CN128_INTERNAL_FLASH - PnE USB BDM/Debugger/Connection" And there I use:
Connection Protocol: GDI
Physical connection: P&E Coldfire V1 Multilink\Cyclone Pro
Interface: USB HCS08/HCS12/CFV1 Multilink - USB Port
Port: Here is nothing to choose, just blank!
When I connected the USB-cable to the computer it installed the drivers as it should, so that should not be the problem.. But what could be?
I found some interesting info in this thread that might solve the problem! To summon it up: The firmware could be old and not compatible with CW10. To find out, follow this guide.
I just find out that I had a firmware that's too old (and I've got my tower kit last week!) using that guide, so I'm just about to update..
After firmware update I can connect to board as long as i start a new project. The provided projects or MQX labs still doesn't work. So now it has to be a settings issue i think.
I did update the firmware on the target. It went smooth.
Now I do connect, but get an error that says that it cant set program counter to initial startup line.
I am using OSBDM.
Hmmm.. I think I've got that one as well. Are you creating a new project or opening an existing example or MQX lab?
Try to create a new project and check Processor Expert and follow the code expert tutorial (found under help menu) and change the LED port pin to PTE3, wich is LED1 on the board. That worked for me. I've still not got any existing example to work with debugging.
I started a thread in another forum for the tower system wich I think you could find and read some of the tips I've got. Perhaps it will help you. Don't think I'm allowd to link to other forums though.
You are allowed to post links to other forums. People have done this before and no one got their knuckles rapped. I am all for posting links to other forums if they help solve the problem.
Ok - I now have the MCF52259evb working with CW10. It works great can compile mqx and single-step examples and also view TAD windows.
I notice that the evb has P&E Micro chip for bdm. My connection protocol is GDI and my connection is P&E ColdFire V234 Multilink\Cyclone Max and the interface is USB.
So I will stick with this setup until we can get the MCF5441X ironed out - could not get it to operate/debug with CW10.
Thanks for reading.
Ok, great! What were the problem, was it just the old driver? Can´t you get it to work with OSBDM?
I still can't debugg any exampels or labs, either MQX or just from CW10. Really annoying!
Just my own new created projects.
Hey StRob I didnt get it working with the tower yet just got it working with the MCF52259 evaluation board.
I did download the new MQX patch for the MCF54418 tower. I will test the tower again shortly.
OK - have looked at the tower MCF54418 with the new twr-mcf54418 MQX patch.
In the readme it states the following:
5.2 OSBDM debugging
The OSBDM debugging connection does not work correctly at the time of this release. The issue was identified as a problem of OSBDM firmware and debugger support and will be fixed in future release of CodeWarrior tool. The MQX 3.6.2 MCF54418 patch was tested using PE Micro debugging interface.
I believe this means that the osbdm is not working currently.
Maybe someone from freescale will concur and let us know when this might be fixed ?
Or if we should purchase a PE Cyclone MAX.
I have found both the Tower and the debugger to be very picky about USB cable quality and length. I got many of the same errors about the debugger not being available or connecting and then running off into the weeds while debugging. the solution has been to use short USB cables for both the debugger interface and the power to the tower. Interestingly the most troublesome has been the power cable.
I still lose connection to the debugger every time I power cycle the PC, but that fixes by un/replugging the debugger.
Retrieving data ...