To top
Support & Downloads Support & Downloads

Frequently Asked Questions

Share:

Information

  •  

    In general, a CmDongle with at least firmware version 3.0 is required for Universal Firm Codes (Firm Codes greater than 6.xxx.xxx).

    If the licenses should also have license transfer options, at least firmware version 3.10 is required.

    To check whether Universal Firm Codes or license transfer is supported by the CmDongle, first, create a CmDust.log file and, second, read the information in the 'capabilities' entries for CmDongles.

     

    I. Creating the CmDust.log file

    To create a CmDust.log file, please proceed as follows for the different operating systems:

     

    Windows

    1. Plug in the CmDongle. This is not necessary when using CmActLicense.

    2. Call CmDust via "Start | Programs | CodeMeter | Tools" in the start menu.

    Then the Windows Explorer opens with the file CmDust-Result.log.

    The text file is located in the respective user directory, which opens automatically after running CmDust.

    3. Send the file to support@wibu.com.

    You can display this file with an editor, e.g. Notepad, so that you can see that no personal data is stored. All stored information is in plain text.

     

    macOS

    For macOS, create the CmDust file using the cmu command line program as follows. The call of cmu is stored in the search path:

    1. Open the commandline/terminal.

    2. Enter the command cmu --cmdust.

    With the add-on --file it is possible to save the information in a file.

    cmu --cmdust --file CmDust.log

    By default, without the add-on the file is printed to the console.

    3. Send the file to support@wibu.com.

     

    Linux, Sun

    For Linux and Sun, create the CmDust file using the cmu command line program as follows.

    The call of cmu is stored in the search path.

    1. Open the command line / terminal.

    2. Enter the command cmu --cmdust.

    With the add-on --file it is possible to save the information in a file.

    cmu --cmdust --file CmDust.log

    By default, without the add-on the file is printed to the console.

    3. Send the file to support@wibu.com.

     

    II. Reading the information

    The 'Capabilities' entries for the CmDongle can be found in the listings of the CmContainers, e.g:

     

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

    ******************************** CmContainers **************************************

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

    There are 3 CmContainers found

    CmDongle with serial number 2-2944166 and firmware version 2.04. 

    CmDongle with serial number 2-2986439 and firmware version 2.04. 

    CmDongle with serial number 3-4261470 and firmware version 4.12. 

     

    [...]

     

    Specific CmContainer Data:

    CmDongle 3-4261470 --------------------------------------------------------------

    Firmware Version: 4.12

    [...]

    Field Update Capabilities: HID

    Crypt Capabilities: AES

    [...]

    Available PIOs: Text

    [...]

    UFC Capabilities: UFC support

    License Transfer

    Generic Programming Sequences

    History Pio Fill

    [...]

  •  

    Depending on the type, CmDongles support different communication types (USB device classes):

    Human Interface Device (HID) and Mass Storage Device (MSD).

    In the case of HID, a connected CmDongle behaves like a keyboard or mouse. No drive of the CmDongle appears in the Windows Explorer.

     

    In the case of MSD, there are 2 different modes to distinguish: PassThrough and FileIo.

    For PassThrough higher rights are needed, which are usually available, because CodeMeter runs as a service. The codemtr.io file is not required for PassThrough, but is created automatically if it is missing.

    If no higher rights are available, CodeMeter automatically communicates via FileIo in the case of MSD. A codemetr.io file must already exist on the CmDongle.

     

    This file must have been created by CodeMeter with higher rights. The file can also be repaired/created manually, e.g. via batch file under Windows/Linux. The cmu command line tool is required for this.

    With the command cmu32 --create-io --file [drive letter]: the file can be repaired/created. e.g.cmu32 --create-io --file F:

     

    When the codemtr.io file is created by CodeMeter, the memory address of this file is transferred to the CmDongle.

    Please note that copying the codemtr.io file is not sufficient as the CmDongle will probably not use the correct memory address.

  •  

    In earlier firmware versions it could happen that the certificates within a Firm Item were no longer correctly available due to a very rare error.

    In this case, no Context File of this Firm Item could be created anymore and the error 705 was displayed in CodeMeter.log.

    Example:

    Runtime Event RT705-507 (4018056) occurred.

    : EBL Trace: I1P1I1P1I1P1CX1CX1CX1CX1CX1CX1CX1H1A2I1P1M1

    : FillPkcs7Template failed. Error 0x2c1

    Create RaC/RaU/RaR failed error 0x2c1

    : Current action create CmRaC aborted.

    : Event WB0705 (UNKNOWN) occurred:

     

    With the command line tool cmu it is possible to create a shortened context file with the option "--lt-push".

    Please enter the following command:

     

    cmu32 --create-lt-context --firmcode %FIRM_CODE% --lt-push --lt-request-file push.WibuCmRaC -s %SERIAL%

     

    %FIRM_CODE% Universal Firm Code of the Firm Item to be updated.

    %SERIAL% Serial number of the CmDongle.

     

    The generated file "push.WibuCmRaC" can then be sent to the software vendor.

    The software vendor can use tools from CodeMeter SDK version 6.70 to create an update, e.g. CmBoxPgm, which first deletes the complete Firm Item from the CmDongle. Then the CmDongle can be reprogrammed as usual and later updated again.

     

    An update of the firmware to the current status is recommended to prevent the recurrence of the error.

  •  

    To use the True Random Number Generator (RNG) in the CmDongle, you can use the API function CmCalculateSignature().

    This function uses the RNG of the CmDongle in the background to create a signature. You can then use the resulting signature as a seed of any random number generator on the software side.

    The CmCaluculateSignature() call requires a handle on a CmDongle or a Firm Item/License entry on a CmDongle. Furthermore, a CmAuthenticate structure is required which contains the configuration to be used for creating the signature. SerialKey and Direct are sufficient for the Ctrl field.

    More information can be found in the CodeMeter Core API help (http://localhost:22352/%24api_help/CmAPIHelp/index.html?start.htm).

  •  

    The flashing represents mainly an information for our hardware department to gain further information in special cases.

    As a rule, the LED of the CmDongle flashes during read or write accesses and can be permanently red if communication errors occur.

     

    Unfortunately, we cannot provide you with an exact breakdown of the behavior. This depends partly also on the version of the firmware.

    Furthermore, the flashing can also be triggered via the CodeMeter Core API, i.e. unexpected behaviour can never be excluded.

     

    If your CmDongle lights up continuously and you want to interrupt this, you can select the CmDongle in CodeMeter Control Center and click on the light bulb symbol on the right.

    This causes the CmDongle to flash briefly and should stop flashing until another reason triggers the blinking.

  •  

    Please register your CmDongle at my.codemeter.com and request the Master Password for your CmDongle by specifying the serial number with an email to support(at)wibu.com. You will receive the CmDongle Master Password at your registered email address after your data has been checked. Please allow some time for this, since the check is done manually.

  •  

    CmDongles without real flash memory, i.e. devices with a memory of less than 128 MB, can be configured to be detected as a local disk or removable disk. Depending on how your system is configured and interacts with the CmDongle, it might be helpful to change the configuration. For reconfiguring a CmDongle, please proceed as follows:

     

    1. Open a CodeMeter Command Prompt using "Start | All Programs | CodeMeter | Tools | CodeMeter Command Prompt".

    2. Read the current configuration.

    Execute the following command, replacing the <serial> with your CmDongle serial number, e.g. "3-4567890":

    cmu32 -s <serial> --show-config-disk

    3. Reconfigure your CmDongle to be detected as removable device.

    Execute: cmu32 -s <serial> --set-config-disk RemovableDisk

    4. Reconfigure your CmDongle to be detected as local disk.

    Execute: cmu32 -s <serial> --set-config-disk LocalDisk

    5. Reconfigure your CmDongle to HID Communication. Please note the technical requirements. Details see KB-0111

    Execute: cmu32 -s <serial> --set-config-disk HidCommunication

    6. Remove and replug the CmDongle.

    7. To set a CmDongle back to MSD communication.

    Execute: cmu32 -s <serial> --set-config-disk MsdCommunication

  •  

    Up to CodeMeter Version 5.10, you have to install the CodeMeter Development Kit including the Firm Code for CmDongle and/or CmActLicense on both the server computer and the clients which use the network to access the Firm Security Box (FSB) on the server. Beginning with CodeMeter Version 5.10, a fully installed CodeMeter Software Development Kit (SDK) on the server computer is no longer required for access to the FSB. A lean installation of CodeMeter as FSB server in a network environment now requires only an installed runtime and the CmFirm.wbc file. Wibu-Systems recommends an update to the most current CodeMeter version.

    In addition, the FSB on the server computer must be made available as accessible over the network.

     

    Server

    For installing the CodeMeter Runtime, Firm Code import, and FSB availability on the server, please proceed as follows:

    1. Install the CodeMeter Runtime you have downloaded from our website at www.wibu.com/en/downloads-user-software.html.

    Note: This step is not necessary, if you already have the latest CodeMeter Runtime installed on the computer acting as server.

    2. Import the Firm Code(s)s obtained from Wibu-Systems.

    For the licensing system CmDongle this is the file CmFirm.wbc. For the licensing system CmActLicense these are the files CmActFirm-XXX.wbc and CmFirmFI-XXX.wbc. XXX stands for the CmActLicense Firm Code.

    To start the import, please proceed as follows:

    - Drag&drop the file(s) onto the open CodeMeter Control Center.

    Alternatively: Open the "File | Import License" menu item and select the file(s) using the dialog.

    3. Configure the FSB for access on the network. If you are using CodeMeter smaller than version 6.80, please proceed as follows:

    - Open CodeMeter WebAdmin.

    - Navigate to page " Configuration | Server | License Access Privileges".

    - Activate the option "Activate FSB Access" and click the "Apply" button.

    - Navigate to the page " Configuration | Server | Server Access".

    - Activate the option "Activate" in group "Network server" and click the "Apply" button.

    - Open CodeMeter Control Center

    - Click the "Process | Restart CodeMeter Service" menu item to restart the service.

     

    If you use CodeMeter version 6.80 and later and the extended access list, the option "Enable access to FSB" has no influence anymore.

    Access to the FSB is enabled by default, but can be restricted using the Firm Code 99.

     

    Client

    For installing the CodeMeter Development Kit, Firm Code import, and the FSB availability on the client computer, please proceed as follows:

    1. Install the CodeMeter Development Kit you have downloaded after registration from our website at www.wibu.com/en/downloads-developer-software.html.

    Note: This step is not necessary, if you already have the latest CodeMeter Development Kit installed on the computer acting as client

    2. Import the Firm Code(s)s obtained from Wibu-Systems.

    For the licensing system CmDongle this is the file CmFirm.wbc. For the licensing system CmActLicense these are the files CmActFirm-XXX.wbc and CmFirmFI-XXX.wbc. XXX stands for the CmActLicense Firm Code.

    For the import, please proceed as follows:

    - Drag&drop the file(s) onto the open CodeMeter Control Center.

    Alternatively: Open the "File | Import License" menu item and select the file(s) using the dialog.

    3. Configure the network settings, if the server computer is not found. Please proceed as follows:

    - Open CodeMeter WebAdmin.

    - Navigate to the page "Configuration | Basic | Server Search List".

    - Enter the IP address or DNS name of the server computer into the server search list (client list) in the group "Simple Mode settings".

    - Click the "Apply" button.

  •  

    Please send an e-mail to support(at)wibu.com.

    If you have a license request file (*.WibuRaC) you previously created via CodeMeter Control Center, attach it to the mail.

    Alternatively, you can also attach the latest backup file, which you can find in the directory "%\ProgramData%\CodeMeter\Backup".

    To identify you as the owner of the CmDongle, you must send at least one attachment.

    If the CmDongle later connects to a CodeMeter Timeserver, it is automatically locked and can not be used anymore.

    The licenses are bound to the CmDongle and are also lost. You can, of course, ask your software vendor, for a license replacement. Depending on their policy, you may be entitled to a special discount.

  •  

    To update the firmware of a CmDongle that is connected to a system without internet access, it is possible to update it with an offline firmware update.

     

    You can find the required update files on our website following the link:

    www.wibu.com/support/developer/downloads-developer-software.html

     

    CodeMeter additional Downloads -> Offline Firmware:

     

    Instructions on how to perform an offline firmware update are included in the download archive.

     

    The Offline Firmware Update feature requires:

    - CmDongle mask number "3" and a

    - Minimum firmware version 2.04 or higher.

    The update can be started at any existing release version of the firmware, e.g. version 3.12 to 4.03.

    There is no mandatory release sequence.

     

    To install the offline updates, please proceed as follows:

    1. Open the CodeMeter Command Prompt.

    2. Execute the command:

    cmu32 -d -f <path to the directory of the update files or a specific file>.

    3. Replug the CmDongle.

     

    Further information can also be found in the document in the downloaded archive.

     

    If you require previous older offline firmware update files (CmDongle mask number "2"), please contact our support.

  •  

    There are two ways to perform an online firmware update. Either you use CodeMeter Control Center or the CodeMeter command line utility cmu.

     

    CodeMeter Control Center

     

    - Open CodeMeter Control Center.

    - Select the CmDongle to be updated.

    - Click the button with the circular arrow.

     

    CodeMeter command line utility - cmu

     

    Windows

    1. Open CodeMeter Command Prompt (Start | All Programs | CodeMeter | Tools).

    - Command to perform a firmware update for all locally connected CmDongle:

    cmu32 -d

    - Command to perform a firmware update for a specific CmDongle:

    cmu32 -d -s <serial number>, e.g.: cmu32 -d -s 2-2944166

    - If a password is configured for the CmDongle, use the following command:

    cmu32 -d -s <serial number> -p <password>, e.g.: cmu32 -d -s 2-2944166 -p MyPassword

     

    Linux & macOS

    1. Open a terminal.

    - Command to perform a firmware update for all your locally connected CmDongle:

    cmu -d

    - Command to perform a firmware update for a specific CmDongle:

    cmu -d -s <serial number>, e.g.: cmu -d -s -s 2-2944166

    - If a password is configured for the CmDongle, use the following command:

    cmu -d -s <serial number> -p <password>, e.g.: cmu -d -s 2-2944166 -p MyPassword

  •  

    Starting with Version 5.0, CodeMeter supports devices that conform to the USB Human Interface Device (HID) class specification. As an alternative option to the Mass Storage Device status, CmDongles can now be displayed as HID without a drive status.HID is currently available for all CmDongles, 1001-02-xxx (without FlashDisk).

     

    Requirements

    - CmContainer with the ID "2-xxxxxxx" (Samsung chips)

    - Minimum CodeMeter Firmware 2.02

    - Minimum CodeMeter Runtime 5.0.

     

    The USB communication standard can be switched any time from Mass Storage Device (MSD) to Human Interface Device (HID) or vice versa. Please see CodeMeter User Help on how to perform the switch.

     

    A manual on how to configure a CmDongle as HID device can be found in article KB-0110.

  •  

    You can reset the CodeMeter password for your CmDongle using the CodeMeter Master Password of this CmDongle. Please proceed as follows:

     

    - Open CodeMeter Control Center.

    - Select the desired CmDongle on the left side.

    - Click the "Change Password" button.

    - Activate the option "Input Master Password" via control "Yes".

    - Enter the CodeMeter Master Password in the right field.

    - Enter the new CodeMeter Password twice.

    - Click the "OK" button.

  •  

    To run the CmStick BMC under current Debian-based / Red Hat Enterprise Linux distributions, the CodeMeterLin Deamon must be started as 'root'.

     

    Proceed as follows:

    1. Execute the following command in the terminal.

    - printf '[Service]\nUser=root\n' > /etc/systemd/system/codemeter.service.d/as-root.conf

    Before you can do this, the configuration file ../codemeter.service.d/as-root.conf

    must be created.

    2. Read in the configuration via systemd:

    - systemctl daemon-reload

    3. Restart the CodeMeter Deamon:

    - systemctl restart codemeter.service