Classic codewarrior 7.1.1, Windows 7 64-bit, and PEMICRO debugger are not compatible

[mikegr]

All,

I am recently responsible for maintaining a codebase with a coldfire V2 target (MCF52277) that includes MQX RTOS 3.0.1.  This codebase will compile under codewarrior 7.1.1.  I would like to use the existing tool chain (codewarrior 7.1.1 and PEmicro Coldfire Multilink debugger, USB-ML-CFE) to compile, debug, and build the firmware.  I have a Windows 7 64-bit machine and have been unsuccessful at using the PEmicro debugger with Codewarrior.  I tried the following two methods and both failed.  Do you have any suggestions?

Method #1

I followed the freescale recommended procedure to install classic codewarrior 7.1.1 on a 64 bit machine (see instructions here  http://cache.freescale.com/files/soft_dev_tools/doc/app.../AN3936.pdf ).  I installed Windows Virtual PC and Windows XP mode.  I installed codewarrior 7.1 in the windows XP virtual machine.  This allowed me to compile my code.  I plug in the pemicro debugger to the USB port and my Windows 7 device found it (latest pemicro drivers were installed).  However, when I try to attach in XP mode, it will not attach the USB device.   I most cases when I try to attached on several USB ports, it will not attach to the virtual machine and so I can not run the debugger.  In a few attempts, the virtual machine did attach, but the lights on the USB multilink turn off and a message appears in XP Mode that the USB device has become non-functional.  I have tried multiple PE debuggers and encountered the same problem.

Method #2

I installed codewarrior 7.1.1 directly on my Windows 7 64 bit machine.  There were a view warnings/errors during installation, but I ignored these and codewarrior seemed to install ok.  I was able to compile the code.  The USB Multilink 2.0 device shows up in the windows devices list.  However, when I try to connect or run the debugger, Codewarrior produces the following error "ColdFire PE Protocol Adapter: No USB connection found" message.

I appreciate your help.

[mikegr]

I was able to get Method #1 in original description working using Windows XP Mode, although it is flakey.  I am not sure what fixed the problem, but I installed the latest driver in the PE USB Multilink device and I installed the latest PE driver both on the real machine AND the virtual machine.  Finally, I made the observation that when attaching the USB device for the first time, the debugger turns off.  If you then remove the USB connector from the PC and plug it back in, it will be attached to the virtual PC.  Thanks for your help,.

[mikegr · Accepted solution]

I found out later that my answer above was only partially correct.  I was able to use the flash programmer to download data but not step through the debugger.  I now have the debugger working completely.  See thread below for final answer

https://community.freescale.com/message/323667#

[JimDon]

If you have win 7 pro or better it comes with a free xp mode, just google xp mode this and install it.

VMWARE workstation will then convert and load this, if the MS vm will not do what you need.

The xp mode version of XP works quite well.

[TomE]

1 - Buy a copy of VMWare and install a copy of XP under that. VMWare allows sharing of USB devices between the Host and the Client.

2 - You could try VirtualBox.

3 - Dedicate an old machine to be  "The Build Machine" and run XP on it.

Tom

[vier_kuifjes]

No need to buy vmware, just download the vmware player...

http://www.vmware.com/products/player/overview.html

It runs the legacy codewarrior just fine. But unfortunately connecting the debugger via vmware has it's issues also. It's a hit or miss, sometimes it works and sometimes it doesn't.

Also be warned that vmware does not support USB3 ports.

[TomE]

> No need to buy vmware, just download the vmware player...

You're right. I didn't realise the Player would let you create Virtual Machines as well.

But remember the licensing is only for "non commercial use", and "I am recently responsible for maintaining a codebase..." sounds pretty commercial to me. Responsibility should come with a budget for tools, and if you can't keep up to date (with the latest development environment) then you have to spend money to keep old machines and operating systems alive, or you have to run then as VMS to work around the "history gap".

> But unfortunately connecting the debugger via vmware has it's issues also.

> It's a hit or miss, sometimes it works and sometimes it doesn't.

Tell me about it! My desk workstation runs 64-bit Linux, VMWare Workstation and is running Windows XP Pro SP3 under that.

The PE Micro USB Coldfire Multilink seldom works the first time I try. Various combinations of unplugging the USB port, waiting for the lights on the Multilink to come up, then waiting for the device to pop up in  VMWARE "VM / Removable Devices", and then waiting for Windows to see it. It then works about 50% of the time. Connecting/Disconnecting in the VMWare Menu and unplugging it a few times usually gets it working. Except for the times every other week when VMWare refuses to see ANY devices, and that requires VMWare to be restarted. The same drama is needed to get the USB-to-CAN converter working.  It is a pain, but better than not having it work at all.

Tom