Search Results

Hi Niklas, yes, exactly, it works, but not with the older version. There is nothing i dislike about the new version, it's just that we use 4.98b in our development environment. Since i need to change the scripts to work with the current version and the changed scripts won't work with the old version, all developers would have to update their software. I would like to avoid that. But i'm sure i'll find a workaround for this. Thank you very much for your help! Regards, Alex

Hi Niklas, thanks for your quick reply. This is exactly what i was looking for! Unfortunately it doesn't seem to work with JLink V4.98b. The script will continue to execute even if the SN was not found. I tried it with the current version of JLink, where it worked... I tried it with the command line options, as well as the commands "eoe 1" and "SelectEmuBySN 123" in the script file. So am i correct in the assumption, that i need a newer version of JLink than V4.98b or did i make a mistake? Sourc…

Hi there, i'm using JLink.exe with the -CommanderScript option and the -SelectEmuBySN option in a test automation setup with multiple CPUs and multiple J-Links. Now, the selection via the serial number works fine. However, if only one debugger is plugged in (which could be the case sometimes), this debugger will be always chosen no matter what serial number i enter. I only get the line "Could not find emulator with USB serial number XXXXXXX", but the script will continue nonetheless. Is there a …