Install Dongle Driver

[Kahlil Algya]

NoteDuring installation of WkRuntime_6-30a.exe, when asked which WibuKey components you would like to install, you can deselect all options. This will just install the plain driver.

First, do you have a license dongle connected to the machine? The steps above are all under the assumption that someone does have a dongle. These steps are to make sure the driver for the license dongle is installed.

Install.exe is the newest version of the signed KEYLOK installer program. It has the same command line switch options to ensure backward compatibility with the legacy release. It supports key installation on 32-bit and 64-bit Windows 7/8/10/11/Server2012-2022 operating systems. Updated installation methods to assist in making installations smoother. It contains the latest version of KLServer to support network installations. This installer contains the libraries for KEYLOK 2/3 and Fortress installations.

If there are issues using the above Install Versions, we recommend doing a manual installation of the KEYLOK Drivers by downloading and extracting the files in the Manual KEYLOK Driver Download.

Within this folder, you will find detailed instructions to manually install the KEYLOK Device Drivers. If issues persist, please feel free to contact our support team for additional assistance. This driver is intended for Windows 10 and above.

When I installed my ORCAD on a Windows 10 computer a while back, every time I run the Cadence License Server Configuration (when I swap USB dongle/license... because our company has a few), I always get this message at the very last step:

"Cadence License Server Configuration utility has detected that it needs to install the FLEXid 9 dongle driver on your system. Please make sure to connect your FLEXid USB dongle to an available USB port. The driver installation process may take a few minutes. Click OK to continue or Cancel to terminate the Cadence License Server Configuration utility"

I always click "OK" and it does its thing... long wait... and it gives the message below (which I always ignore because at the end the license/dongle still work as intended and the software is usable).

"- Unable to restart Cadence License Server with the new license file "..... ". Failed to install FLEXid dongle driver. Failed to update your CDS_LIC_FILE license path with the new license server setting "....".

Fast forward... June 2020, I installed the same software on a new computer I recently assembled running on the latest Windows 10 update. I went through the above License Server configuration process and when it got to the step where it says that the FLEXid 9 dongle driver needs to be installed, I clicked "OK" as usual. However this time after just a few seconds of clicking "OK", the system rebooted. This process is repeatable and the system will just reboot at this step on the process. The FLEXID information is blank on the System Settings at LMTOOLS which gives me the impression that the dongle is not installed and the information from it could not be retrieved.

After a series of long frustrating trial-and-error and numerous reboots, my computer finally gave up and showed Blue Screen of Death (BSOD). It referenced an error "PAGE_FAULT_IN_NONPAGED_AREA" related to the file "aksdf.sys". Now the more annoying thing is that my computer is now going to an endless loop of BSOD showing that issue. I did some Googling at it seems like the latest Windows 10 May 2020 update (version 2004) has some issues with this file.

Further Googling, this file is described as "The genuine aksdf.sys file is a software component of Aladdin HASP by Aladdin Knowledge Systems. Aladdin HASP (Hardware Against Software Piracy) a digital rights management (DRM) suite of protection and licensing software. Aksdf.sys is a filter driver that is necessary for the proper functioning of HASP. The component adds support for specialized external devices. Removing this file may cause problems with Aladdin hardware." It seems like Flexera is using this.

I think we have a central license server for our other Cadence softwares. However for ORCAD someone started getting a USB-dongle version and that's how everybody went afterwards. We ended up with several USB dongles, each maintained (or misplaced) by different people.

I am seeing suggestions of rolling out older versions of Windows 10 (prior to this update). Unfortunately the new PC has this latest version installed (after fresh installation) so there is no older version to rollback to. I have to find a way to get this older version somewhere.

I have the same issue after fresh setup of windows 10 incl latest updates (19042.685). Before v17.2 just worked fine but now after installing LMTool (v12.7..) my pc ends up with a blue screen immediately after start. Only safe mode booting and deinstalling LMTools stopped it. No idea how to fix that

How to get this working on Windows 10 x64? I have the same problem as mentioned above in that the CC2540 dongle shows up in device manager with no driver installed and is therefore not showing up in the Packet Sniffer. The dongle is untouched as received from TI, which I understand should mean that its flashed with the packet sniffer firmware by default.

My situation is similar to one described by the guys above, but with some difference: when I first installed SmartRF Studio + Packet Sniffer + SmartRF Flash Programmer, everything worked just fine: I was able to use cc2540 dongle with sniffer, read and write firmware from/to cc2540 chips through SmartRF05EB.

Yesterday I tried to read the firmware from cc2531 chip and found out that now neither Packet Sniffer nor Flash Programmer nor Studio don't see any of the chips! It seems that the main big thing that happened in between is the automatic Win 10 upgrade to ver 1703 (build 15063.413 as it says now; don't remember, which one was before). It's x64.

As everything worked before, I didn't look to Windows' device manager. Now I looked there and under "Other devices" I have CC2540USB Dongle with error 28, driver not installed, like mentioned in above messages. It's pretty surprising to see that, but at least it correlates to the fact that things are broken now.

Further, I don't see any "cebal2_x64.inf under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\drivers\cebal\win_64bit_x64". Under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\drivers\cebal there are only 2 dirs: \not_certified and \win_32bit_x86, no mentioning of 64bit version at all. So, as far as I see, I have latest versions of all tools and neither one has installed 64bit version. Where can I find it?

Apparently, there has been a change in Windows 8 related to signing of drivers. Win 8 now enforces that all drivers (related .inf files) have a digital signature. Without the signature, the driver will not be installed. On win 7, you could ignore the error and install anyway, but not so for Win 8. The driver (or really, the .inf file) for the dongle has not been certified by TI yet.

However that clearly isn't the case, at least for me. I get the signature problem that everyone else is having on Windows 8 machines. This driver you provided however works fine! It would probably help a lot of people out if you guys updated that package or at least made a note on the TI BLE stack download page. Thanks again.

Thanks for noticing! The BLE stack installer is actually missing the .cat file (it only includes the new .inf file). So for now, please continue to use the one I posted in this thread, and we will update the installer.

Maybe I'm just doing something wrong but after downloading and extracting the driver folder I can't seem to get it to work. I've tried directing the device manager to the extracted folder only to have it tell me that it can't find any driver files, then I tried picking from the list of drivers on my computer as shown in the pictures below only to have download errors. Can anyone fill me in as to what I'm doing wrong?

I have installed the RFStudio 7 which includes all necessary drivers as suggested on some of the post. I have noticed one thing when adding device manually. I can see the Texas Instrument in standard Serial port devices.But no device like TI CC45XXXX CDC?

I have noticed one more thing with RFStudio 7 that when I connect the SensorTag on serial port RFStudio detects the CC2541 but unable to detect the usb dongle when connected on CC debugger's serial port.

Not sure if I understand your second question. Do you connect the CC debugger to the CC2540 USB dongle, but can't see the device in SmartRF Studio? Have you applied any power to the dongle (it needs to get power from a USB port)?

Have you checked the CC Debugger cable? In a very few cases, we've seen that the cable might be broken or that there's something wrong with the small adapter board between the debugger and the small cable.

what is terrible is i saw it passed to green one time and unconnected it to make sure i could reproduce it again, and since then , no green anymore on any of all the deive i have : keyfob, dongle, sensor tag

I would not be amazed this is a cable issue coming from the jtag cable... as i just see the led passed to green again (and then rf studio indicate CC1201 instead of nochip) and then when i pressed again it turn to red, very strange..

Perhaps we can add a feature that allows to place driver package to auto pre-install into the boot directory . For now I think it you need to download and place the driver package from you desktop, place it onto SDcard and install it manually. You should be able after first run update fails, to install the diver and rerun dietpi-software to complete.

It seems to be a widely known issue that this WiFi adapter 0BDA:8176 is until now badly supported by current repos. Even the provided deb package from manufacturer seems to not work in many cases. Instead if was necessary to build the drivers oneself:

Hmm but you say you tried many of them and have power supply errors?

Btw, I forgot firmware-ralink + firmware-misc-nonfree + firmware-realtek above. These are as well pre-installed and the last one is the one that should be relevant in your case.

3a8082e126