USB dongle does not work for Win7

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

USB dongle does not work for Win7

30,234 Views
metwk
Contributor I

Hi,

 

Recently, my company migrated from WinXP to Win7 64-bit OS. As a result, the Metrowerks compiler USB dongle (unlimited license) that was fully functional on WinXP would not work with Win7.

 

With the old driver setup files, FlexLm could not display the Dongle FlexLm ID.

 

I implemented the following steps,

Uninstall any version of current driver using --> Sentinel_HASP_Run-time_cmd_line --> haspdinst.exe -r -fr -kp -Purge [Dongle LED switch Off after uninstall]

Install --> Win7 USB dongle drivers --> FLEXId_D_USBDongle_Driver_x64_64bit_Windows [Dongle LED switch ON after install and reboot]

Execute lmtools_x64_64bit_Windows so that FlexLm ID could be detected and seen.

 

Now as my USB dongle could be detected by Win7 and FlexLM showing the ID, I tried to build my source code using the existing unlimited license (that was fully functional on WinXP). However, the license would no more work and the command line would display the error msg - ERROR C5300: Limitation: code size 1969 > 1024 bytes.

 

The license.dat file is located at the same location where it was stored previously while being used on WinXP.

 

Does anyone have an idea what the problem could be?

 

Thanks a lot.

 

Message was edited by: Sameer Chaudhari  Further, Freescale provided me with a test license.dat file. This test license works but my original unlimited license does not work.

Labels (1)
0 Kudos
Reply
14 Replies

6,964 Views
carlgilbert
Contributor II

What I found is that the 64-bit driver lets the dongle be seen by the 64-bit lmtools.  However, the 32-bit lmtools cannot see the dongle.  I assume this affects the compiler as well.

0 Kudos
Reply

6,964 Views
trytohelp
NXP Employee
NXP Employee

We found that an very old version was used under Win 7.

CW for HC12 V4.6 released in December 2006.

Personally I've never tested this old version under Win 7.

We know there is a incompatibility driver with HC12 V5.1 under Win 7 64 bit when the USBdongle license is used.

This is the cause of 2 problems:

      - got strange error each time we launch IDE: this is the last day ...,

      - build tool chain is running but not the debugger.

Why ?

Products built with 8.4a of Flexlm (i.e. All of the classic products) will not be able to support win 7 64-bit with USB dongle licensing.

That support was added in 11.4 of Flexlm and our eclipse products moved to 11.5.

We've already the problem with HC12 V5.1 so I'm pretty sure the USBdongle could not be used with V4.6 released 7 years ago.

I've planned to check it.

Pascal

0 Kudos
Reply

6,964 Views
carlgilbert
Contributor II

Right. I suppose this is just the tough situation of an automotive supplier.  We have to support our products a long time.  Our IT saw fit to changeover to windows 7, but we can't run our compilers in windows 7.  So we are stuck trying to hide windows XP computers like some kind of contraband...

Next compiler we get will have to be guaranteed to support the next version of windows up to 10 years.  its a ridiculous thing to ask, but that's our situation.

0 Kudos
Reply

6,964 Views
trytohelp
NXP Employee
NXP Employee

The key problem is on the USBDongle driver.

The CodeWarrior HC12 V4.6 was released in 2006.

The build tool chain and debugger were released with a specific version of Flexm.

This version is not compatible with USBdongle driver version required by Windows 7.

On my side I've installed HC12 v4.6 on Win 7 64bit.

the Special Edition is used and can be checked fine by compiler.

So a license file locked on Disk/Host D should work fine with this configuration.

Pascal

0 Kudos
Reply

6,964 Views
carlgilbert
Contributor II

What is this special edition you speak of? Is it available?

0 Kudos
Reply

6,964 Views
trytohelp
NXP Employee
NXP Employee

Special Edition is the Free of charge version.

In the past this license was required whereas the tool is encrypted with this limitation by default now on last version.

In all case I've checked on my Win 7 64bit PC with HC12 v4.6.

I've created a Professional license file locked on my DiskID.

This license file is recognized by the tools (Compiler, etc ...).

The license file locked on Disk/Host ID is running.

the restriction is on USBDongle license due to a driver compatibility.

Pascal

0 Kudos
Reply

6,964 Views
metwk
Contributor I

Hi Pascal,

Were you able to check the USB dongle license file provided by me with V4.6 on Win 7, as you have described in your previous reply?

What were the results?

Thanks,

Sameer

0 Kudos
Reply

6,964 Views
trytohelp
NXP Employee
NXP Employee

Sameer,

I've installed the HC12 V4.6 on this PC.

I got some problems due to P&E driver.

Not possible to install CW HC12 V4.6 with default values.

      Error with windr.inf driver installation.

So I unselected the P&E driver …

With a HC12 V4.6 license file locked on the USBDongleID, the license file is not running.

So you can not use this version with USBdongle license on Win 7 64 bit.

We recommend you to install the tool on Virtual PC.

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

Pascal

0 Kudos
Reply

6,964 Views
trytohelp
NXP Employee
NXP Employee

Hi,

The old dongle driver used under Win XP is not working under Win 7.

A new version was released to solve the problem.

It seems you've installed it:

      http://www.freescale.com/webapp/sps/site/overview.jsp?code=CW_LICENSE_FXDL_DD

I've performed several tests on my side under XP, Win 7 64 bit and 32 bit OSs.

Some customers experienced similar issue after to have installed the new USBdongle driver.

The USBdongle red led switched on and Flexlm showed the ID but the tools said that the tool worked at demo mode.

This seems to be the case here too.

By default you can check with the device manager if you've the right driver version installed.

Attached you will find my version.

You should have 2 keys for Safenet only: HASP Key and USB key.

Is it the case ?

      - in some case I know customer has another one too named Hasp HL key.

If it's your case I recommend you to uninstall the driver and re-install it.

During the installation process be sure you don't select check on web for last driver.

To avoid problem I recommend to unplug your network cable or turn off wifi during the installation.

To be sure you've followed the right process I recommend you to:

      - downloaded the last version from Aladin web site: Sentinel_HASP_Run-time_ cmd_line.zip

           ftp://ftp.aladdin.com/pub/hasp/Sentinel_HASP/Runtime_%28Drivers%29/Sentinel_HASP_Run-time_cmd_line.z...

     - Unzip it and execute:

            haspdinst.exe -r -fr -kp -Purge Now the dongle river is uninstall.

If the USBdongle was plugged, the red light switched off.

I launched the LMTools and now the Flexid is not showed anymore.

    

From Freescale web site, download the last dongle driver:

     http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=01521027262444119D11A5

The file is USB dongle Driver Installer for Windows

Unplug the network connection to be sure the right driver is used (important).

Now launch FLEXId_D.exe, and re-install the FLEXID drivers.

Select FLEXid 9 and 10.

During the installation as my USBdongle was plugged, a message New hardware found /installed appeared and the red light switched on.

At the end the Dongle installer propose to restart the computer.

Is it working on your side ?

Else can you please provide me more details about the exact tool version used.

To do that you must:

  Under CodeWarrior IDE (classic)

      Start the IDE and click on Help | About Freescale CodeWarrior.

      Click on Installed Products

      Provide us all info displayed.

      Or you can save them in a txt file.

Under Eclipse IDE

    1-      Start Eclipse and click on Help ¦ Freescale Licenses

      The Status column gives the status of the license.

      Under Product, select it and click on details.

      A new dialog show up giving license details.

      Provide us all info displayed

    2-      Start Eclipse and click on Help ¦ About CodeWarrior Development Studio

      Under Installed Products, you will see the version used.

And provide me the USBdongle license file used.

Regards

Pascal

0 Kudos
Reply

6,966 Views
metwk
Contributor I

Hi,

Thank you for detailed info.

I have already tried the procedure for install and re-install without network connection before I posted my previous message but it didn't work.

File - FS_Driver.jpg: Snapshot of the driver on my computer

File - license_Freescale_Test.dat: Temporary license file from Freescale for tests

File - license_USB_Dongle_ORG.dat: Original license file that doesn't work.

Please advice the next steps to resolve this issue at the earliest.

Freescale support hasn't been responding to e-mails or is extremely slow.

Thanks.

0 Kudos
Reply

6,966 Views
trytohelp
NXP Employee
NXP Employee

Do you have contacted the support team via Service Request ?

In this case what is the SR ?

According to the license file you're using CW for HC12 v5.x.

On my side the USBdongle license is working fine on Win 7 32 and 64 bit machine.

However there are 2 known problems:

      - when you will launch the IDE you will always get a message saying : this is the last day.

            don't care about it

      - the build tool chain will work fine but not the debugger due to an incompatibility driver.

the most important point is to unplug the network connection when you will re-install the driver.

Pascal

0 Kudos
Reply

6,966 Views
metwk
Contributor I

Hi Pascal,

The SR no. is SR 1-1075982221. Enclosed is the result of output from chc12.exe. Please let me know how we can solve this issue as my project and customer both are stuck.

Thanks.

0 Kudos
Reply

6,969 Views
trytohelp
NXP Employee
NXP Employee

Hi,

Peformed some tests on my side with Win 7 64 bit.

The USBdongle license file is not compatible with HC12 V4.6.

Regards

Pascal

0 Kudos
Reply

6,969 Views
trytohelp
NXP Employee
NXP Employee

Thanks.

The SR is on my side too.

I propose you we continue to handle the problem via the SR only.

Regards

Pascal

0 Kudos
Reply