Search Results

Hi, The hanging/freezing should be fixed by now in the latest version of Ozone + latest version of the DLL. Can you confirm? Best regards, Fabian

Hi, Thank your for your inquiry. We are aware of this issue. A fix will be part of a patched release later today. Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 Best regards, Fabian

Hi, We will try to reproduce the issue and if necessary fix it. We will keep you posted. Best regards, Fabian

Hi, Thanks for your inquiry. Such an issue is not known to us. Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Could you send us a data file to reproduce this issue (e.g. .hex-file)? Best regards, Fabian

Hi Ross, Thanks for your inquiry. If you only want to send raw data to the host, you can use SEGGER_RTT_Write(). For further information about this, and other functions available, please refer to the J-Link User Manual (UM08001). You can find the manual here: %JLinkInstallFolder%\Doc\Manuals And here: segger.com/downloads/jlink/ Please find an excerpt from the manual, regarding said function, attached. Best regards, Fabian

Hi Fabien, sorry for the delay in response. Some target specific settings were missing on the device side. We implemented these settings into the next release planned for tomorrow. It should work out of the box when using said version. Best regards, Fabian

Hi Dave, J-Link Pro does not support VCOM over ethernet. Best regards, Fabian

Hi, Could you provide us with a simple out-of-the-box working code sample to reproduce this issue? Best regards, Fabian

Hi Johannes, Thanks for your inquiry. Recently there was a fix for this device. Could you please download the latest J-Link Software and Documentation Pack version and give it a try with that one? You can find it here: segger.com/downloads/jlink/#J-…twareAndDocumentationPack If this does not help: Are you using an evaluation board or custom hardware? If evaluation board: Which one(including revision)? If custom HW: Does this problem also occur on an evaluation board? Regarding the APP core: Once…

Hi, Thank you for your inquiry. We will change this behavior in the next release planned for tomorrow. It should all work as expected then. Best regards, Fabian

Hi, yes, a bash script would be the best option here. Best regards, Fabian

Hi, Thank you for your inquiry. Such an issue is not known to us. Could you please update your Software and Documentation Pack on Ubuntu to version 6.60a (the same you also use in your W10 VM) and try it again? Best regards, Fabian

Hello, Thank you for your inquiry. The unlock is part of the connect sequence: Open J-Link commander with the following command line: -device <DeviceName> -if swd -speed 4000 -autoconnect 1 When asked if you want to unlock the target, click "Yes" Best regards, Fabian

Hi, Thank you for your inquiry. Such an issue is not known to us. There are different thread awareness plugins etc. Could you tell us which tool are you using exactly (Ozone, GDB,...)? Best regards, Fabian

Hi, Thank you for your inquiry. I am not sure if i understand you correctly. Do you want to pass a script-file to the J-Link GDB Server to have it executing the commands listed above? The thing is, that such a script file would have to be passed via a command line as well. Could you tell me what you would like to use this feature for exactly? If the reason is, that you do not want to type the command lines manually, I would suggest using a .bat-file or similar. Best regards, Fabian

Hi, Thanks for your inquiry. This device is not yet supported by us. You can implement support by your-self. Information about that can be found in the J-Link Manual (UM08001). The easiest way to test whether your connection sequence works or not is by using the J-Link commander, since it keeps the setup simple. Further information about how this device is to be set up etc. can only be provided by Cypress and the device's Manuals. If you manage to make your setup work, you can deploy the handlin…

Hi, the reason why the J-Link is not able to connect to the target when using the J-Link SWD Isolator is, that the board is not able to provide the necessary amperage to supply the isolator. I added a section covering this in the article about this board in our Wiki: wiki.segger.com/CC3220_LaunchP…ith_JTAG-.2FSWD-Isolators Best regards, Fabian

Hi Udo, You are setting the device to WFE mode, which sets the device to low-power mode. Therefore we are not able to connect to the Core. When executing the reset, the device is running again as soon as we leave the reset. To halt the target after reset, it is required to set the Vector Catch reset, but we need to be able to connect to the core to do so. Therefore the target is entering the WFE again before we can connect to the core. If you would not have the option to change the boot mode, yo…

Hi, This sounds like the problem is somehow connected to the applications you are loading to the device. Could you provide us with a sample project to reproduce this? Best regards, Fabian

Hi, after reviewing this, I realized that you are doing some writes after the loadfile-command: w4 0x01000000, xxx w4 0x01000004, xxx w4 0x01000008, xxx These writes are cashed by the DLL and are written Go / Step / Reset, leading to a flash download. We do this to make Downloads from IDEs more efficient. Since loadfile is always flushed directly, this leads to the described behavior. Best regards, Fabian