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
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