Search Results

Hi davidxiong- I found a work-around: I use the old DOS pipe "|" and "more" commands. Here is my CMD input: cmd /c JLink -device %s -CommanderScript "%s" | more The first %s is the target device number, the second is the complete filename of the .jlink CommanderScript file. This returns everything that you see on the screen to the standard output pin on the CMD vi. I hope this helps! -Randy

Hi Nino- Thanks for the reply. Quote from SEGGER - Nino: “You can enable in J-Link Commander to exit the script when running into an error by calling command exitonerror. See J-Link manual for more information. ” I was hoping for a complete capture of all information from J-Link, not only errors. Is that possible? Quote from SEGGER - Nino: “ For a proper LavView implementation we recommend using the J-Link SDK: segger.com/products/debug-prob…nk/technology/j-link-sdk/ ” Thank you for the SDK sugg…

Hi- I am trying to use J-Link in a command prompt that is controlled by LabVIEW. I am using the CommanderScript method, and am able to control the J-Link, but am unable to get any useful returned data. I have tried creating a log file, but it simply tells me the times some of the function were done, not anything about the STATUS of the various steps (like the uP already has an up-to-date load). Is there a way to get the information that exists on the cmd screen under J-Link to either be returned…