JLink CDC driver installer does not work in Windows Vista

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • JLink CDC driver installer does not work in Windows Vista

    When running JLinkCDCInstaller_V1.2b.exe, which is found under Program Files after installing Setup_JLinkARM_V456d.zip, the installation fails, outputting only an overview of available parameters for msiexec. I can only assume that this is because msiexec was called with an invalid parameter. I do not have any other version of Windows available, and thus do not now if it is Vista specific.

    This makes my JLink completely unusable for me, since Windows will not recognize the device without a driver.

    This is the output from the installer:

    -----------------
    Windows ® Installer. V 4.5.6002.18005

    msiexec /Option <Required Parameter> [Optional Parameter]

    Install Options
    </package | /i> <Product.msi>
    Installs or configures a product
    /a <Product.msi>
    Administrative install - Installs a product on the network
    /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
    Advertises a product - m to all users, u to current user
    </uninstall | /x> <Product.msi | ProductCode>
    Uninstalls the product
    Display Options
    /quiet
    Quiet mode, no user interaction
    /passive
    Unattended mode - progress bar only
    /q[n|b|r|f]
    Sets user interface level
    n - No UI
    b - Basic UI
    r - Reduced UI
    f - Full UI (default)
    /help
    Help information
    Restart Options
    /norestart
    Do not restart after the installation is complete
    /promptrestart
    Prompts the user for restart if necessary
    /forcerestart
    Always restart the computer after installation
    Logging Options
    /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
    i - Status messages
    w - Nonfatal warnings
    e - All error messages
    a - Start up of actions
    r - Action-specific records
    u - User requests
    c - Initial UI parameters
    m - Out-of-memory or fatal exit information
    o - Out-of-disk-space messages
    p - Terminal properties
    v - Verbose output
    x - Extra debugging information
    + - Append to existing log file
    ! - Flush each line to the log
    * - Log all information, except for v and x options
    /log <LogFile>
    Equivalent of /l* <LogFile>
    Update Options
    /update <Update1.msp>[;Update2.msp]
    Applies update(s)
    /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
    Remove update(s) for a product
    Repair Options
    /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
    Repairs a product
    p - only if file is missing
    o - if file is missing or an older version is installed (default)
    e - if file is missing or an equal or older version is installed
    d - if file is missing or a different version is installed
    c - if file is missing or checksum does not match the calculated value
    a - forces all files to be reinstalled
    u - all required user-specific registry entries (default)
    m - all required computer-specific registry entries (default)
    s - all existing shortcuts (default)
    v - runs from source and recaches local package
    Setting Public Properties
    [PROPERTY=PropertyValue]

    Consult the Windows ® Installer SDK for additional documentation on the
    command line syntax.

    Copyright © Microsoft Corporation. All rights reserved.
    Portions of this software are based in part on the work of the Independent JPEG Group.
    -----------------
  • Hi,

    We are not aware of such a problem.
    Nevertheless, we will take a look at this short term and come back to you.

    Best regards
    Erik
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hi,

    It's me again with another question.

    Do you use Windows Vista x64 or x86?
    Maybe the windows installer package is corrupted in general? Can you confirm this?


    Best regards
    Erik
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • I'm using Vista x86.

    This is the only Windows installation I have access to, and thus cannot verify if it applies to other versions of Windows, but I have a hunch that the problem only applies to Vista. This hunch is based on that I believe that Nordic Semiconductor, who makes the nRF51822 Evaluation Kit to which the J-Link I am trying to use is soldered onto, test installation of all necessary drivers on Win7 and XP, but not Vista. This belief is based on claims in their documentation.

    If you don't have any Vista machines readily available, I suggest checking what parameters you pass to msiexec in the installer, and check if they are present in the list of valid options cited in my original post. This should give an indication on whether you happen to be trying to use something Win7-specific on Vista. If you need help testing a beta, I will happily volunteer.
  • Today I decided to investigate this a bit further, and tried to open JLinkCDCInstaller_V1.2b.exe using WinRAR, hoping it was a WinZip self-extractor or similar. This turned out to be correct, and I extracted the following three files:

    Installer.exe
    JLinkCDCDriver_x64.msi
    JLinkCDCDriver_x86.msi

    My guess is that Installer.exe is a wrapper which selects which MSI file to use based on the architecture, and that it does not work correctly on Vista. By calling Installer.exe directly, it gives me the error message reported in my first post in the thread. After installing JLinkCDCDriver_x86.msi by double-clicking on the extracted file, I now have a working JLink.

    I believe fixing Installer.exe should be fairly simple, but in the meantime extracting the .msi file and installing it manually is good enough for me.