[SOLVED] JLINKARM_Close() target behaviour

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

  • [SOLVED] JLINKARM_Close() target behaviour

    Hello,

    We use use Python for test automation. Previously we used our own wrapper for jlink.exe since we don't have the SDK. However, recently, we have discovered the Pylink project which acts as a Python interface to the SDK.

    We have an issue which we think is related to the JLINKARM dll. When JLINKARM_Close() is invoked some internal timing related test metrics in our DUT changes. If we skip the invocation of JLINKARM_Close() and just exit the test, the DUT is in no way influenced.

    So the question is: what does JLINKARM_Close() do? Is it feasible that the call in any way could interfere with the firmware?

    I've attached the jlink log where JLINKARM_Close() is invoked just before EOF.

    I hope you can give us some hits as to what could cause this issue.

    Best regards,

    Rune
    Files
    • jlink.txt

      (879.41 kB, downloaded 88 times, last: )
  • Hello Rune,

    Thank you for your inquiry.
    Generally SDK related support is not given via forum.
    To give a hint for the behaviour of JLink_Close, it closes the connection to the target device, to the J-Link and resets any set debug bits on the target device.
    Keep in mind that Pylink is not our product and is not supported by us.
    Should you run into troubles contact Pylink support. Alternatively we suggest getting the J-Link SDK yourself and implement a tailored solution for your test setups.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    The following contact form can be used for this: Contact Us

  • Hello Rune,

    Pylink is not our software and we will not support it. If you have a specific setup that needs a tailored solution we suggest purchasing the J-Link SDK yourself and create an application that fits your needs. Should you run into troubles then you can contact our mail support.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    The following contact form can be used for this: Contact Us