Search Results

Search results 1-20 of 967.

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

  • Hi Peter, Quote from hotbrix: “As far I understand you, there is no way around this. I need the perma connection to stay open in order to be able to connect to the server. ” This is correct. As long as you want to use RTT, you will have to have an active debug connection. Otherwise it is not possible to retrieve the RTT data from the target. However.. Quote from hotbrix: “So during target programming I have to parallel connections, during unit testing with the telnet client I use only the perma-…

  • Hi tsche, Could you please send us a picture of the front and the back of you J-Link for support purposes? BR Fabian

  • Hi Peter, it seems like you misinterpreted what "SetCompareMode=0" does. This is not really a surprise as it was not properly documented. We will revisit the documentation an adjust this. In short: When SetCompareMode=0 is selected, the J-Link will skip the Blank check and thus has to assume that the device must always be erased before program. => Forcing SetCompareMode=0 will force J-Link to always trigger erase when calling LoadFile. From what I understand you intend to skip the verify, correc…

  • Hi, A good way to approach such an issue is usually the following troubleshooting guide: wiki.segger.com/J-Link_cannot_…the_CPU#Target_connection Additional hints: 1) The STM32F4 devices allow to set permanent protection (RDP level 2), which will effectively disable the debug features of the chip. So if RDP level 2 is set, you will never be able to connect to the chip. 2) In some cases, applications do override the debug pins. In such a case you would also have to connect the nRESET pin between …

  • Hi Peter, First of all: As Alex pointed out, an active debug connection is mandatory for RTT to work. If you are wondering why, please refer to the following article: wiki.segger.com/RTT This does not change regardless of how you retrieve the data (via TELNET channel or via SDK API calls). Quote from hotbrix: “- upload the firmware ” I assume you are referring to programming the target device, correct? From your message it is not clear to me how exactly you are doing this, but I would further as…

  • Hi Pierre, sorry for the delay in response. The issue you described was already fixed with V7.92l: While the update notification pop-up was visible, other dialogs (e.g. flash programming dialog) would not be shown until the pop-up was closed. Fixed. I would suggest to upgrade to the latest version: segger.com/downloads/jlink#J-L…twareAndDocumentationPack To disable the notifications entirely, please refer to the following article: wiki.segger.com/J-Link_Update_Notifications BR Fabian

  • Hi Pierre, The update notification dialog should be non-blocking, so it should not interrupt your script execution. Could you please tell us a little bit more about your setup, so we can investigate this? 1) Which J-Link Software version are you using? 2) Could you please send us a J-Link log file of the session? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File BR Fabian

  • Hi, You are welcome! It is good to hear that this is no longer blocking for you. We will close this thread now. Best regards, Fabian

  • Hi, The RTT TELNET channel is technically a RAW socket. See: wiki.segger.com/J-Link_RTT_TELNET_Channel Except: Quote from https://wiki.segger.com/J-Link_RTT_TELNET_Channel: “Note: The channel is "TELNET-like", which means: - The TELNET protocol is not fully implemented, so not all functionality is supported. - It is TELNET compliant for RTT data that is solely consisting of printable characters, only. - Raw (non-character) RTT data has to be interpreted as raw bytes. ” What does this mean? When …

  • Hi AbhiAsh, Quote from AbhiAsh: “My requirement is to open a text file and send the data line by line to the target in handshake. ” We do not have a tool or example with such a feature directly. However, you could do one of the following: 1) Acquire the J-Link SDK & use e.g. C/C++ or python to read the file contents and send it to the target line by line. The SDK comes with RTT samples in C & python. segger.com/products/debug-probes/j-link/tools/j-link-sdk/ 2) Read the file content & send it lin…

  • Hi, we just gave it a try on the latest MacOS version. Everything worked as expected. Could you please send us a J-Link log file of the failing scenario? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File BR Fabian

  • Hi, J-Flash & the J-Flash project format was updated sever times since V5.02l. I would guess that the Project does not work flawlessly with the new J-Flash version. Does it work when you setup a new J-Flash project with the latest J-Flash Software? Best Regards, Fabian

  • Hi Ali, Did you already check out the troubleshooting guide? wiki.segger.com/J-Link_cannot_…the_CPU#Target_connection Please note that the connection can not be established if RDP was set to Level 2: wiki.segger.com/ST_STM32#Device_security Best regards, Fabian

  • Hi, Thank you for your inquiry. We are not aware of any such issue. We also highly doubt that the issue lies on J-Link side here. Please find the reason below: 1. The NONMAIN region has a separate flashloader which is only called when the NONMAIN region is to be programmed 2. Programming NONMAIN with data containing an invalid CRC checksum will lead to abort of programming. 3. MAIN & NONMAIN flash regions are protected by different registers: - MAIN: CMDWEPROTA & CMDWEPROTB - NONMAIN: CMDWEPROTN…

  • Update: The board arrived. We soldered a 10 pin connector on it and hooked up the J-Link. It did work out of the box on my side (see below). We are confident that this issue is related to your setup (soldering/cable/...) Source Code (23 lines)BR Fabian

  • Hi, Thank you for the detailed post. 1. To be perfectly honest, the solder job looks horrible, but if you verified that all pins connect correctly andthat there are no short circuits (except for the ones between GND pins), so be it. 2. Regarding the flat cable: You say that it was delivered with the J-Link EDU correct? This is a sounds a little bit odd to me. As far as I know all flat cables we deliver with our products - are light grey - have one red wire which connects both pin 1. On the pictu…

  • Hi Gavin, I had a quick look at this. CORTEX_R52 is currently not pre-defined. I will forward this internally. For now you can use the magic value instead: Source Code (1 line)Note: JLINK_CPU and CPU refer to the same variable. BR Fabian

  • Hi everyone, this was officially added with the release of J-Link Software Version V7.92i. Excerpt from the release notes: Source Code (1 line) BR Fabian Federschmidt

  • Hi, I assume that you are using the J-Link SDK, correct? If so, could you please contact us via our support ticket system? segger.com/support/technical-support/ Best regards, Fabian

  • The power pin is not enabled by default. Please refer to: wiki.segger.com/J-Link_Commander#Power Best regards, Fabian