Search Results

Search results 1-5 of 5.

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

  • Hello Fabian and thank You for answer. 1) As for silent unlocking: If we want to avoid unlocking, we would set device to CORTEX-M3. Is then debugging of UNLOCKED firmware identical with device=EFM32GG... and device=CORTEX-M3? 2) As for missing value in registry, which should control the window with unlock prompt, do You have any idea, what is wrong? Thank You Best Regards Ondrej

  • Hello, I have caught even more interesting behaviour- J-Link commmander silently unlocks only specific EFM32. If device is set as general Cortex-M3, it correctly refuses connection. In the example below two attempts were made- one with CORTEX-M3 and the other with EFM32GG380F1024 (Note that the difference is in InitTarget()!): SEGGER J-Link Commander V7.64b (Compiled Apr 8 2022 15:31:33) DLL version V7.64b, compiled Apr 8 2022 15:30:15 Connecting to J-Link via USB...O.K. Firmware: J-Link V9 comp…

  • Hello Fabian, thank You for answer. When looking for solution, I have already found that method. But I have no such register. I have reinstalled J-Link suite, but it is still not there. I have added register maually, both inJlink and v764b folders, but still- the dialog window is missing.

  • Hello, please help me understand J-Link commander behaviour. My software locks debug interface of EFM32 (DLW). When trying to connect via AtollicTRUE Studio, connection is refused as expected. But connection via J-Link commander is succesfull and it also clears the debug interface lock without prompt. It may be something with InitTarget(), but I have not found any docs. Thank You for any info! Best Regards Ondrej. Log: ------------------------------------------- Atollic TRUE Studio Console: ----…

  • Hello, We use J-Link SWO Viewer CL in automated test environment. We use SWO for passing test results from microcontroller. When the testing is finished the Viewer task is simply killed. I wonder if there is a more decent way how to terminate/close J-Link SWO Viewer. 1) via some command-line command (I have not found anything regarding this neither in UM08001_JLink.pdf, nor in Forum) 2) Preferably via SWO data (after a test on the target was finished some magic sequence would be sent terminating…