Codewarrior 6.2 on a Widows 7 system

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Codewarrior 6.2 on a Widows 7 system

Jump to solution
45,290 Views
UcTechnoGeek
Contributor II
Has anyone tried to use Codewarrior 6.2 and the USBDM on a Widows 7 system?
Labels (1)
0 Kudos
Reply
1 Solution
14,129 Views
natep
Contributor I

 

I was able to get Codewarrior 5.9.0 for HCS12(X) Microcontrollers running on Windows 7 x64 using the following steps.  It was such a pain to get working that I decided to share with the community.  Please note that I have experienced instability with this setup, but it generally works ok.  It seems to be faster than running Codewarrior for HCS12(X)  on Windows Virtual PC in Win XP Mode.  (Some of these steps were borrowed from a previous post.)

 

1) Install the p&e drivers version 10 from:

http://www.pemicro.com/blog/post.cfm/p-e-hardware-interface-drivers-version-10-windows-7

This includes drivers for all windows versions and windows 7 x86 and x64 too !!!

2) Copy from win32 intalled CodeWarrior (like xp 32bits) from Program Files\FrescaleCodeWarrior for S12(X) V5.0 to the c:\Program Files(x86)\Freescale\CodeWarrior for S12(X) V5.0

3) Now, this step is the MOST IMPORTANT:

    Look at the file "Mwregsvr.exe" in the c:\Program Files(x86)\Freescale\CodeWarrior for Microcontrollers V6.1\bin and click the right button on this file, then click properties.

    Now, in the compatibility tab,set the compatibility to WindowsXp (sp2) and set the checkbox

    to run in administrator mode.

    Now, click apply button then click OK button.

4) In the same folder, run once the file regservers.bat

    When windows ask for the permisions, just click yes everytime.

 

5)  You may want to create a desktop icon at this point.

 

6)  If you have a node locked license, you may need to generate a new license file for the new setup since the Win x64 will have a different MAC address than your donor Win XP install or your Windows Virtual PC in Windows XP mode.  See the MyFreescale for how to do this.

 

7)  I could not get my USB Multilink (USB-ML-12E Rev C) to be recognized by the True Time Simulator & Real-Time Debugger, so I contacted PEMicro.  They provided me with an updated unit_12z.dll file.  Using this file (attached here zipped) to replace all other current versions of this file.  (The only version I had was at "C:\Program Files (x86)\Freescale\CodeWarrior for S12(X) V5.0\Prog")

 

Now everything should work with Win x64.

 

Hope this helps anyone trying a work around with Win x64.

 

View solution in original post

0 Kudos
Reply
68 Replies
7,316 Views
RodneyMcGee
Contributor IV

CodeWarrior 6.3 works out of the box for Windows 7 32-bit.

For Windows 7 64-bit checkout checkout this post including info about programmers.

Install CodeWarrior v6.3 directly under Windows 7 x64

I think it's time to let this CW6.2 thread goto sleep.

0 Kudos
Reply
7,316 Views
JTech
Contributor III

Alright, I have spent about 5 hours and have resolved the problem with help from some of the posts in this thread, but info from elsewhere was also crucial. I have v6.3 running now on Windows 7 x64

What you need:

1) A script (see source below). Create a new file with the filename and extension of RemoveOSCHeck.vbs

2) wdapi900_32.dll. This file can be obtained by installing Codewarrior V10.0 in Windows XP Virtual Machine.

Copy the script code, exactly as is, into RemoveOSCHeck.vbs, save and close

' name this file as RemoveOSCHeck.vbs
' This script can be used to remove operating system version checks (2000, xp, vista, 7)
' or architecture checks used for (32-bit x86 or 64-bit x64 systems)
' that are part of an MSI installer. To use drag an MSI file to RemoveOSCHeck.vbs icon.
Option Explicit
Const msiOpenDatabaseModeReadOnly = 0
Const msiOpenDatabaseModeTransact = 1
Dim argNum, argCount:argCount = Wscript.Arguments.Count
If (argCount < 1) Then
Wscript.Echo "Please supply the name of the msi file to be modified."
Wscript.Quit 1
End If
' Scan arguments for valid SQL keyword and to determine if any update operations
Dim openMode : openMode = msiOpenDatabaseModeReadOnly
openMode = msiOpenDatabaseModeTransact
' Connect to Windows installer object
Dim installer : Set installer = Nothing
Set installer = Wscript.CreateObject("WindowsInstaller.Installer") : CheckError
' Open database
Dim databasePath:databasePath = Wscript.Arguments(0)
Dim database : Set database = installer.OpenDatabase(databasePath, openMode) : CheckError
' Process SQL statements and delete the crap out of this installer!
Dim query, view, record, message, rowData, columnCount, delim, column
Set view = database.OpenView("Delete from LaunchCondition") : CheckError
view.Execute
wscript.echo "Launch Conditions Removed"
Set view = database.OpenView("Delete from InstallExecuteSequence where Action='OnCheckSilentInstall'")
view.Execute
wscript.echo "OnCheckSilentInstall step removed"
Set view = database.OpenView("Delete from Property where Property = 'ISSETUPDRIVEN'")
view.Execute
wscript.echo "Property ISSETUPDRIVEN removed"
Set view = database.OpenView("INSERT INTO Property (Property,Value) VALUES ('ISSETUPDRIVEN',1)")
view.Execute
wscript.echo "Property ISSETUPDRIVEN added"
database.Commit
Wscript.Quit 0
Sub CheckError
Dim message, errRec
If Err = 0 Then Exit Sub
message = Err.Source & " " & Hex(Err) & ": " & Err.Description
If Not installer Is Nothing Then
Set errRec = installer.LastErrorRecord
If Not errRec Is Nothing Then message = message & vbLf & errRec.FormatText
End If
Fail message
End Sub
Sub Fail(message)
Wscript.Echo message
Wscript.Quit 2
End Sub



Now, drag the installer msi package, onto the script, in Windows Explorer. It will then pop up some dialog boxes about having removed something. Click OK on all of them.


Then, proceed to run the setup package (the msi package) and it should install fine. Sometimes it will abort during installation the first time, just try again and it should be OK.


When installation is finished, load a project and compile it, it should all work properly, Click on debug, and then you will note HIWAVE throws an error message, specifically complaining about a DLL. Close Codewarrior and HIWAVE.exe


The DLL you copied from Codewarrior 10.0, rename it to wdapi900.dll and copy it into the "prog" folder under your Codewarrior v6.x installation.


Then launch Codewarrior again and all should work.



0 Kudos
Reply
7,316 Views
shbtha005
Contributor I

Can any one help me im trying to run  Codewarrior 6.2 on my windows 7 and when im trying to create a new project it just gives me an error to see that error, please refer to the picture and the document  I HAVE attached below.

0 Kudos
Reply
7,316 Views
Martin152
Contributor I

Hola,

 

como resúmen de las propuestas para operar el CW 6.2 en W7 x64 opté por:

 

-instalar el CW 10.1 eclipse (Special), correr mi aplicación y debugearla correctamente.

-copiar la instalación CW 6.2 en XP x86 al W7 x64 (usar el mismo path de carpetas).

-ejecutar el registro de los elementos con regserver.bat (sito en .../bin ) (no toqué la compatibilidad del Mwregsvr.exe).  

-copiar el PEUSBW32.DLL en el W7 ../system32 y por las dudadas en ..../sysWOW64.

 

Ejecuto el IDE 6.2 cargo mi aplicación la compílo entro al debuger se conecta con el USB Multilink graba la flash e inicia en brakpoint.

Todo se ejecuta correctamente sin mensajes ni notificaciones de errores.

Es muy notable el incremento de velocidad de los sucesos respecto al XP.

 

Suerte y  gracias a todos !!!

 

 

0 Kudos
Reply
14,130 Views
natep
Contributor I

 

I was able to get Codewarrior 5.9.0 for HCS12(X) Microcontrollers running on Windows 7 x64 using the following steps.  It was such a pain to get working that I decided to share with the community.  Please note that I have experienced instability with this setup, but it generally works ok.  It seems to be faster than running Codewarrior for HCS12(X)  on Windows Virtual PC in Win XP Mode.  (Some of these steps were borrowed from a previous post.)

 

1) Install the p&e drivers version 10 from:

http://www.pemicro.com/blog/post.cfm/p-e-hardware-interface-drivers-version-10-windows-7

This includes drivers for all windows versions and windows 7 x86 and x64 too !!!

2) Copy from win32 intalled CodeWarrior (like xp 32bits) from Program Files\FrescaleCodeWarrior for S12(X) V5.0 to the c:\Program Files(x86)\Freescale\CodeWarrior for S12(X) V5.0

3) Now, this step is the MOST IMPORTANT:

    Look at the file "Mwregsvr.exe" in the c:\Program Files(x86)\Freescale\CodeWarrior for Microcontrollers V6.1\bin and click the right button on this file, then click properties.

    Now, in the compatibility tab,set the compatibility to WindowsXp (sp2) and set the checkbox

    to run in administrator mode.

    Now, click apply button then click OK button.

4) In the same folder, run once the file regservers.bat

    When windows ask for the permisions, just click yes everytime.

 

5)  You may want to create a desktop icon at this point.

 

6)  If you have a node locked license, you may need to generate a new license file for the new setup since the Win x64 will have a different MAC address than your donor Win XP install or your Windows Virtual PC in Windows XP mode.  See the MyFreescale for how to do this.

 

7)  I could not get my USB Multilink (USB-ML-12E Rev C) to be recognized by the True Time Simulator & Real-Time Debugger, so I contacted PEMicro.  They provided me with an updated unit_12z.dll file.  Using this file (attached here zipped) to replace all other current versions of this file.  (The only version I had was at "C:\Program Files (x86)\Freescale\CodeWarrior for S12(X) V5.0\Prog")

 

Now everything should work with Win x64.

 

Hope this helps anyone trying a work around with Win x64.

 

0 Kudos
Reply
7,316 Views
natep
Contributor I

Sorry all.  I don't know why the unit_12z.zip attachment did not post.  Here is my second try.

0 Kudos
Reply
7,316 Views
Aesir
Contributor I

Thank you a lot for the unit_12z.dll !!!!!!!!!
That's works fine !

  For the instal of CW 5 on a Seven pc, it's work on a Seven Ultimate 64, but it doesn't work on a Seven Home 32.

 

0 Kudos
Reply
7,316 Views
JimDon
Senior Contributor III

Wow you guys are amazing. Sounds like too much fiddleing for me....

I just took my free XP mode vm that comes with Profesional Plus, imported into VMware, set the MAC to match my license file and it all runs perfectly. If you import the VM (never say copied always say moved) correctly, you can even make copies of the vm Of course I need to run 4 different versions of CW, so I guess I would have to play those trick time 5x (I use CFV2 7.1 and 7.2). The real beautie of it I can make a backup and run it on other Win7 64 boxes as well.

I map a drive from the host machine for the code base.

0 Kudos
Reply
7,316 Views
Armature_Curren
Contributor I

Hello!

 

I have problem with programing by FlashPrommer using LPT port.

Earlier (Windows XP) it worked good, but now (Windows 7 64bit) i have error

CCCSClient::ConfigChain::CC not present

Could you help me with this truble?

 

CodeWarrior version: CW fo DSC56800 R8.0 IDE 5.6.1.1658

0 Kudos
Reply
7,316 Views
CrasyCat
Specialist III

Hello

 

This question is completely unrelated to the subject "Codewarrior 5.9.0 for HCS12(X) Microcontrollers on Windows 7 x64".

 

Please create  a new post in the "CodeWarrior for 56xxx DSC" forum. 

 

CrasyCat

0 Kudos
Reply
7,316 Views
marceloc
Contributor I

Hey, I use Windows 7 Professional x64. I have installed it by getting a previous installation of it on a Windows 7 Professional x86, it worked, but when I tried to run the debug, it says that was no device connected. Then I replace the unit_12z.dll but it still not worked. What should I do now?

0 Kudos
Reply
7,316 Views
admin
Specialist II

where should i place this dll file? I searched the entire fold of the CW and find no former copy to replace.

0 Kudos
Reply
7,316 Views
layman
Contributor I

my system has this dll at :

C:\Program Files\Freescale\CodeWarrior for S12(X) V5.0\Prog

-pramod

 

0 Kudos
Reply
7,316 Views
admin
Specialist II

I used the attachment, and i still can not get my multilink connected

0 Kudos
Reply
7,316 Views
kef
Specialist I

ToBeNoOne,

 

Natep provided DLL is used by CW for S12(X). CW for MCUs uses different unit_xxxx DLLs. Using Natep instructions I was able to install CW for S12(X) V5.0 on 64bits Win7. P&E debugging didn't work with original DLL. Replacing unit_12z.dll with attached one made debugger working.

 

0 Kudos
Reply
7,316 Views
admin
Specialist II

  kef

thank you for your reply.

 

I tried both for S12 and S08, but none of them worked. I even tried different version of codewarrior, from 5.5 to 5.9. Now I only compile the code in my win7 and download it into the S12, but i can not debug.

 

I contacted with P&E and they reply me that the driver of multilink in win7 doesnot support codewarrior. I almost give it up, but in this post many of you seem to make it work fine. Is it possible that i intalled both for S12 and S08 in my computer?

0 Kudos
Reply
7,317 Views
kef
Specialist I

I don't think that your problem is caused by installing both CW for S08 and S12. Maybe you have older unit_12z.dll somewhere in the search path and debugger loads older DLL?

Did you install older P&E drivers before installing v10 drivers? Did you check driver version in device manager?

 

I followed Natep instruction and that worked. The only instruction I violated - I installed (copied) CW to users\my_user_name, not to Program Files\ . But I think this is not very important, since as I understand CW is working on your machine, except multilink connection.

 

0 Kudos
Reply
7,316 Views
admin
Specialist II
thank you for your reply although i can use CW for compiling, i still have to debug. i searched my whole disk for this dll file and got nothing. is there any other things i can do to make the hi-wave work?
0 Kudos
Reply
7,316 Views
kef
Specialist I

Chances are we need not new unitxxx DLL's, but some DLL's from older P&E drivers. CW5.0 for S12 and CW6.3 for MCU's seem using DLL's from WINDOWS\SYSTEM32 folder, which are now not present on 64bit machine after installing P&E V10 drivers! When PEUSBWD2.DLL is missing, hiwave is unable to detect USB Multilink. I copied PEUSBWD2.DLL from x86 WinXP WINDOWS\SYSTEM32 folder to CW\PROG folder on 64bits Win7, and to my surprise hiwave now is able to detect multilink and connect to target. I didn't test yet if flash programming and everything else is working.

 

ToBeNoOne, I have no idea why your setup isn't working. Are you using full multilink in plastic case, or multilink integrated to some demo board?

0 Kudos
Reply
7,316 Views
kef
Specialist I

Hi All

 

Regarding PEUSBW2.DLL. I knew it must be not as simple as I thought. On one 64bits Win7 machine I tried if CW for MCUs V10.0 installs and if it is working, including P&E drivers. It's working. I guess V10.0 will be improved to decent level soon, but I'm not happy with this new concept, at least at the moment. Maybe I'm too conservative.

So I tried to make V6.3 working. IDE worked, but not P&E drivers/API. Hiwave gave a clue about PEUSBW2.DLL, I copied it from 32bits WinXP install, and voila, it got working.

But what the lack of success, on machine on which CW V10.0 wasn't installed, PEUSBW2.DLL trick didn't work! I compared driver versions - the same. I compared contents of system folders - no missing relevant files. Etc etc.

I found that wdapi900.dll is missing on 64bits machine. But copying wdapi900.dll from WinXP install didn't help. How it worked on mahine with CW 10.0 installed? - It must using different wdapi900.dll. I searched CW 10.0 folder and found two folders with wdapi900.dll:

 

"CW MCU v10.0\MCU_10.0\ccs\drivers\usb\x32\redist\wdapi900.dll"

 

and

 

"CW MCU v10.0.zip\CW MCU v10.0\MCU_10.0\ccs\drivers\usb\x64\redist\wdapi900.dll"

"CW MCU v10.0.zip\CW MCU v10.0\MCU_10.0\ccs\drivers\usb\x64\redist\wdapi900_32.dll"

 

 

I found that our wdapi900.dll is renamed wdapi900_32.dll from x64\ folder.

 

So my solution is to

1) take WINDOWS\SYSTEM32\PEUSBW2.DLL from WinXP machine and copy it to CW\PROG folder.

2) take 

"CW MCU v10.0.zip\CW MCU v10.0\MCU_10.0\ccs\drivers\usb\x64\redist\wdapi900_32.dll"

from CW 10.0 install, rename it to wdapi900.dll and copy CW\PROG folder.

 

0 Kudos
Reply