Hi,
I am trying to debug an application we are using in production which programs and tests development kits with the J-Link OB, and have run into the following issue:
- The software calls the JLink programming application and downloads firmware (the OB license is pretty old, the fw sting is J-Link OB-SAM3U128 V1 compiled Aug 27 2013 15:22:27 - I believe it came with Jlink v4.79b). The VCOM is enabled in this fw.
- The production application then updates the firmware to a newer version (6.22a) and the VCOM disappears (this also happens when updating to any intermediate version from JLink v4.98 onwards).
Since the VCOM is needed for subsequent tests, it must get re-enabled. This is all handled by the test app (in Labview, but can call external .dlls or .exes) and should be done preferably without any popups to the operator.
So, is there a way to re-enable programmatically the VCOM or prevent it from disappearing in the first place before updating?
The only workaround I see is calling Jlink.exe and running the "vcom enable" command as described in your Wiki, but it's a bit cumbersome. Isn't there any other more direct way? Like a call to JLinkARM.dll, or some command string?
Thanks for your time
Kostas
I am trying to debug an application we are using in production which programs and tests development kits with the J-Link OB, and have run into the following issue:
- The software calls the JLink programming application and downloads firmware (the OB license is pretty old, the fw sting is J-Link OB-SAM3U128 V1 compiled Aug 27 2013 15:22:27 - I believe it came with Jlink v4.79b). The VCOM is enabled in this fw.
- The production application then updates the firmware to a newer version (6.22a) and the VCOM disappears (this also happens when updating to any intermediate version from JLink v4.98 onwards).
Since the VCOM is needed for subsequent tests, it must get re-enabled. This is all handled by the test app (in Labview, but can call external .dlls or .exes) and should be done preferably without any popups to the operator.
So, is there a way to re-enable programmatically the VCOM or prevent it from disappearing in the first place before updating?
The only workaround I see is calling Jlink.exe and running the "vcom enable" command as described in your Wiki, but it's a bit cumbersome. Isn't there any other more direct way? Like a call to JLinkARM.dll, or some command string?
Thanks for your time
Kostas