topic Re: Re: CodWarrior unhandled exception in Classic/Legacy CodeWarrior

CodWarrior unhandled exception

dpaul — Tue, 25 Feb 2014 14:52:53 GMT

Greetings:

I've recently been forcibly upgraded from a faithful XP machine to Windows 7 (32-bit). I have loaded CodeWarrior 6.3 and continued working on my project (MCF51 based, if that's important). CW seems to run (although I'm writing code only at this point, not debugging) but when I exit CW I get these three errors.

"CodeWarrior encountered an unhandled exception 0xc0000005 at address 0x773e77a2

(The memory at address 0x00000004 could not be written)

Location: nddll.dll:0x773e77a2"

"CodeWarrior encountered an unhandled exception 0x0eedfade at address 0x0012d4ec

Location: COMMITTED_MEMORY: 0x0022a9d8"

"Runtime error 217 at 045D4BA1"

A forum search finds reports of these errors quite routine. Most cases seem to be successfully resolved by changing the CodeWarrior IDE Properties to "Disable desktop composition".

Alas, but this solution has proved ineffective in my case. As most of the forum entries are dated a couple of years ago, I was hoping their might be some additional thoughts or advice available now.

In the mean time, I have experimented with a couple of samples and older and much smaller projects. These Win7 + CW 6.3 digests without complaint. Could my problem be size related? (I have a Standard license, but have left CW 6.3 in Special Edition mode as I will shortly have to switch machines again).

I also dragged out an ancient XP machine. Despite being frustratingly slow, I loaded the same CW 6.3 there as Special Edition. My Win7 + CW 6.3 adverse project builds without complaint in that environment.

There are forum comments that CW 6.3 is not fully Win 7 compatible (although one cannot vouch for the authority of those authors). Switching to CW 10 has been suggested (I use the word "switching" meaningfully as there doesn't seem to be a direct migration path), but I'm hesitant to follow that advice owing to fast looming deadlines. If CW 6.3 is, in fact, unstable under Win 7, then I suppose the next option would be to drop back to XP - and risk the ire of IT for my effort.

Thank you for any suggestions.

Re: CodWarrior unhandled exception

trytohelp — Wed, 26 Feb 2014 08:05:03 GMT

Hi Doug,

I will try to provide you some information.

You're using CodeWarrior for Microcontroller V6.3.

Officially this version doesn't support Windows 7.

Only XP/Vista 32 bits are supported and fully tested.

You can install it under Win 7 32 bit OS but not on 64 bit version because the installer doesn't allow installation on 64 bit.

By default we recommend to switch on Eclipse version.

The last version is CW for MCU V10.5.

CW for MCU V6.3 is the last version based on Classic IDE.

No new development will be done for this version anymore.

The MCU V6.3 was released in September 2009 ... 4-5 years ago.

CodeWarrior for Microcontrollers v10.5 is the last version.

It integrates the development tools for the :

ColdFire®, ColdFire+, DSC, Kinetis, Qorivva, PX, RS08, S08 and S12Z architectures

into a single product based on the Eclipse open development platform.

This version is running on Host platforms

Microsoft® Windows XP 32/64-bit (Business)

Windows Vista 32/64-bit (Business and Home Premium)

Windows 7 32/64-bit (Professional and Home Premium)

Windows 8 32/64-bit (Professional)

You can download an evaluation on the web site:

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=CW-MCU10

I recommend you to sign the news letter for the product.

Via the web site:

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=CW-MCU10

Click on Subscribe

++++++++++++++++++++++++++++++++

Back to CodeWarrior for Microcontroller V6.3 ...

Some customers are using it on Windows 7 but some of them (5% probably) were not able to run CodeWarrior.

There are some information about that on the forum.

I recommend you to have a look on it.

Be aware our help with V6.3 and Windows 7 OS is limited.

On my Win 7 32 bit I've installed several classic version including MCU V6.3.

The tool is working fine on my side.

There are some tips which could help you to solve the problem below.

Another solution is to install the tool on Virtual PC too.

For details please have a look to AN: AN3936, How to install and run Classic CodeWarrior products on 64-bit Windows 7 PC - Application Notes

http://cache.freescale.com/files/soft_dev_tools/doc/app_note/AN3936.pdf

Now if you want to switch on last version and if you've already a project running under V6.3 you can:

- create a new project under Eclipse and import your source files.

We have an AN explaining the process: AN4727, Import project from CW clasic to CW MCU v10 4 CodeWarrior for Microcontrollers v10.4

http://cache.freescale.com/files/soft_dev_tools/doc/app_note/AN4727.pdf

- use an previous version name MCU V10.2 which include a classic importer feature.

This feature is working for no-complex project.

To get access to this tool, you must contact our support team at support@freescale.com or by your Freescale account.

Freescale Account:

- Go to following URL: http://www.freescale.com/TechSupport

- Click on Submit a Service Request. You will come to a login page.

- If you are already registered with Freescale (using the Forum, subscribed to newsletter, ...) use your Freescale login and password. Otherwise, Click on "Register Now" to get registered.

- You can submit your request through the web from there.

See below extract of the info found

================================

- Run Windows 7 in Windows XP SP3 mode. Forward the USB ports to the XP VM.

- Don't use Windows 7 RC. Ever.

- Get the 64-bit drivers from P&E Microsystems here: http://www.pemicro.com/support/downloads_find.cfm and download the P&E Hardware Interface Drivers Version 10.

- Installer for PowerPC (ColdFire?) balks, but will install if pressed. Nothing works, however. Install CodeWarrior onto a 32-bit system, then copy the installation to the 64-bit system.

Then from Administrator privileged account, run the regservers.bat file in CodeWarrior's bin directory.

================================

Disable Desktop Composition:

- Right click on ide.exe and select "Properties"

- Click on the "Compatibility" tab

- In the "Settings" area select "Disable Desktop Composition"

A lengthy list of Windows 7 workarounds

http://forums.freescale.com/t5/CodeWarrior-General/Codewarrior-6-2-on-a-Widows-7-system/td-p/47405

(three forum pages)

Another Win 7 work-around, graphics driver

http://forums.freescale.com/t5/CodeWarrior-General/Windows-7-Unhandled-Exception/td-p/42063

(two forum pages)

Problem with license file under Windows XP mode with Win 7

http://forums.freescale.com/freescale/board/message?board.id=CW816COMM&thread.id=5909

(two forum pages)

Windows Unhandled exception

http://forums.freescale.com/t5/CodeWarrior-General/Windows-7-Unhandled-Exception/td-p/42063

(two forum pages)

Another point to check:

http://208.74.204.137/freescale/board/message?board.id=CWCOMM&message.id=7019

Hope this will help you.

Pascal

Re: CodWarrior unhandled exception

dougpaulsen — Fri, 28 Feb 2014 21:57:17 GMT

Pascal:

Thank you for your exhaustive reply.

Since my original posting I have installed the Virtual PC on a new 64-bit Win7 system and now have a XP Mode window. I have installed CW 6.3 within this VM. My original errors have gone away. Hooray!

But not so fast to declare victory. Although CW 6.3 no longer crashes, the XP VM requires one to manually "attach" my USB P&E MultiLink to the VM. Alas, but this attaching consistently fails. I can build my project, but I'm not quite at a skill level where I can ship it without debugging....

This is, I think, a P&E Micro issue rather than a Freescale one. I have had extended discussions with their support regarding this. The upshot is you must install the latest version 11 drivers in both Win7 and then in the XP VM window. This apparently works for many, but unfortunately not for me.

I did speak with another developer who reported very qualified success with an identical setup as mine. He reports, however, attaching the MultiLink to the VM window is unreliable in the extreme (a careful reading of P&E's driver instructions alludes to this possibility). Consequently, he has elected to continue to develop on a native XP machine. Considering the time already lost trying to get CW Classic 64-bit Win7 operational , I may do the same (never, never, never surrender your old system until/unless the new one works with all your old gear!).

I would like to explore using CW 10. I don't believe my standard license includes CW 10, which could be trouble.

In the mean time, I will carefully and fully digest the numerous references you kindly provided and report back later.

Again, thank you.

doug

Re: Re: CodWarrior unhandled exception

trytohelp — Mon, 03 Mar 2014 09:25:46 GMT

Hi Doug,

In fact I got same problem on my side with Multilink and other interface plugged on USBport.

When you click on attach and select Multilink, the interface is:

- un-plugged from Win 7 OS,

- plugged to Win XP Virtual.

However it seems the interface is not "fully" recognized or installed by virtual OS.

The problem appears (from my experiences) with all interfaces using USBport (Multilink, USBTap, MiniUSB to Tower board, ...).

On my side I've solved the problem ...

See below for more information

++++++++++++++++++++++

I'm back to my Win 7 32 bit OS with Virtual PC for Multilink Universal and TWR-MCF5441x board.

First I've created a project using CW for MCU V10.4 under Win 7.

Refer to Multilink_win_7.jpg for Multilink driver.

I launched debugger and got refer Eclipse_connection.jpg.

The debugger is working fine via Multilink Universal Interface.

Second, I've launched the Virtual PC.

I've created a project for same hardware under CW for Coldfire V7.2.

Build the project and launch the debugger I got an error (Multilink was not attached).

Refer to problem_1.jpg

Then I attached the Multilink - problem_2.jpg

In this case the Multilink led switch off and Multilink under Win 7 driver is not listed.

However the Virtual PC didn't recognized it at this time.

Now un-plug the Multilink and re-plug it.

The Multilink will be listed under Virtual PC device - refer to problem_3.jpg

Now you can launch the debugger.

At this time the Multilink is attached to Virtual PC.

++++++++++++++++++++++

To be fully installed the interface must be un-plug and re-plug a second time.

Regards

Pascal