MQX 3.8.1 and CW 10.2 Wizard not working

[joevignola]

I'm using CW 10.2 and MQX 3.8.1 with Windows 7.  I have done a fresh install of CW 10.2 with update 1 and then installed MQX 3.8.1 I get the following error when I try to create a new MQX 3.8 project for the TWRK60n512 board:

!!! ERROR: MQX is NOT installed for selected board !!!

I have followed the exact steps on another computer running Windows XP and it worked ok.  Is this a Windows 7 problem?

Any help would be greatly appreciated.

Thanks,

Joe.

[MarcinG]

Hi Joe,

The New Project Wizard for MQX 3.8 and CodeWarrior 10.2 works with Winodws 7.

The message you get indicates that the New Project Wizard for MQX 3.8 cannot find the installation of MQX.

The NPW first checks the following key in the Windows registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Freescale\Freescale MQX\3.8

It contains PATH value with the path to the MQX 3.8 installation. (Both 3.8.0 and 3.8.1 share this same key).

By default the PATH value is set to: C:\Freescale\Freescale MQX 3.8.

If the PATH value is not found then the message you got is shown. If it is found, then the NPW checks if the folder from the PATH variable exists, and if there is no such directory the same message is shown.

So, check if you have the mentioned key in the registry and if PATH value matches with the real directory with MQX.

If they match and you still have the problem, you may try to reinstall plug-ins for CodeWarrior. To do so, use the install_cw10.2_plugin.bat batch file from the following directory: c:\Freescale\Freescale MQX 3.8\tools\codewarrior_extensions\CW MCU v10.2\ (the directory may differ if you have installed your MQX somewhere else).

Good luck!

Marcin

[joevignola]

I was able to find the Key in the registry. However, since I'm running 64bit Windows 7 the registry settings are in a slightly different location  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Freescale\FreeScale MQX\3.8.  I did install MQX 3.8. into the default PATH "C:\Freescale\Freescale MQX 3.8".  I have tried rerunning the install script multiple times without any luck.

Is there a way that I can have CW 10.2 look at this registry location?

Thanks,

Joe.

[MarcinG]

So the problem is the 64-bit operating system. As you see, the key with the information about MQX has slightly different path and the New Project Wizard cannot find the PATH variable.

Unfortunately, you cannot change the registry location in the CodeWarrior plug-in. However you may try to create the key manually in the appropriate place (copy from the Wow6432Node node one level up), of course if you are not afraid of modifying the Windows registry. To avoid manually copying one by one, you may try to export the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Freescale\FreeScale MQX\3.8 key, open the created .reg file in the text editor and replace all Wow6432Node\Freescale occurences with Freescale. Then import the modified key.

Best Regards,

Marcin

[joevignola]

I was able to move the Keys to in the registry as you described, however,
I'm still getting the error. Do you have any other ideas?

[MarcinG · Accepted solution]

Today I got deeper into the problem. I installed CW 10.2 on the 64-bit Windows machine. Then I installed MQX 3.8. And for me the New Project Wizard worked without any changes in the registry.

The answer why it works on my 64-bit Windows 7 is because CodeWarrior is delivered with 32-bit JRE, which is used by default. And when CodeWarrior runs in 32-bit mode the New Project Wizard reads data from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Freescale\FreeScale MQX\3.8 key. So the keys you had at the beginning were OK.

So first you should check if your CodeWarrior runs in the 32-bit mode. It is marked in the task manager with "* 32" suffix after the process name (cwide.exe for CodeWarrior):

The other issue might be that the directory stored in the PATH variable (under the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Freescale\FreeScale MQX\3.8 key) is different that the real MQX installation. Please ensure that the folder indicated in the PATH variable exists.

Best Regards,

Marcin

[joevignola]

I finally got to the source of the problem.  My computer is on a Windows domain and there are registry limitation being put on my account.  Once I use a local account with loging onto the domain everything works fine.

Thanks for all the time and effort you put into solving my problem.

Joe.