Search Results

Search results 1-20 of 955.

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

  • Hi Ali, Did you already check out the troubleshooting guide?…the_CPU#Target_connection Please note that the connection can not be established if RDP was set to Level 2: 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? Best regards, Fabian

  • The power pin is not enabled by default. Please refer to: Best regards, Fabian

  • Hi, We implemented a verbose mode option for J-Link Log files. Please refer to the following article: BR Fabian

  • Update: Device support will be available with the next J-Link Software release (V7.92g) planned for Wednesday, next week (23-09-27). It will be available for download here:…twareAndDocumentationPack BR Fabian

  • Hi, R7FA6M5BG is currently only supported by Flasher. I will check internally, if there are plans to support this chips already. BR Fabian

  • Hi Florent, I just gave this a quick try on the STM32H735G-DK (STM32H735). I could not test it on an STM32H730, as there are no evaluation boards available as far as I know, but both should behave the same from a debug standpoint. On our side it worked without any issues with J-Trace Pro V2 Cortex-M (see below). Do you have any target application running on your device? If so, does the same issue appear after erasing & power-cycling the device? Best regards, Fabian Source Code (49 lines)

  • Hi, Quote from mete: “I think the reflasher does not support st-link v3 boards ” Correct. Quote from mete: “will it support and how soon ? ” There are no plans to add reflash tool functionality for STLINK-V3 and it is unlikely that there will be any in the foreseeable future. The reflash utility was designed to provide J-Link support for ST evaluation boards, which did not come with headers for external debug probes. ST promised, that all evaluation boards that come with a V3 would also come wit…

  • Hi, Usually devices are locked when produced for release to prevent them from being read out. The i.MX534 for example has multiple debug modes which either require the correct key to be passed or disable debug access completely. I would be very surprised if the car manufacturer did not enable security for the device. In such a case there is not much you can do, I'm afraid. I suggest to contact, the car manufacturer for help instead. Best regards, Fabian

  • Hi, We will look into this and see if we want to adjust the code to prevent these warnings. However, we are currently fully booked with projects and this is the first request regarding this, so I cannot say when we will be able to look into this. I would suggest that you suppress these warnings on your side for now, by wrapping the include of the header file in pragmas to disable/enable these warnings. Example: C Source Code (18 lines)That way you can still update the RTT sources without manuall…

  • Hi James, VCOM (virtual COM port) is what is used to use J-Link as a virtual com port device. This makes it possible to use the related J-Link pins to be used as UART interface. The article Alex linked should do exactly what you require: Show J-Link as a COM port device, which can then be used by what ever application you are using to send/receive UART information between your PC and your target chip. For further information please refer to: For informatio…

  • Hi Gabriel, this is intentional. SEGGER_RTT_printf() is (by far) not a complete printf() implementation. Flags, FieldWidth and Precision will be ignored for specifiers s & c. Unfortunately, this information was missing from the API documentation in the Wiki. We just added this information to prevent confusion: For your specific use case, I would suggest to use snprintf() or similar, provided by the library of your choice. BR Fabian

  • Hi, good to hear that the problem could be resolved by a reboot! As the issue is resolved, we will close this thread now. Best regards, Fabian

  • Hi, Sorry for the delay in response. We were able to replicate the issue and fix it. A fix will be part of the next J-Link Software release planned for some time tomorrow (V7.88k). It will be available for download here:…twareAndDocumentationPack We are sorry for any inconvenience caused. BR Fabian

  • Hi Gabriel, RTT is already executed in background mode on the RM4x devices. The background AP is implemented natively, so no actions/script files on your side needed. You can verify this by opening the RTT tab in the J-Link Web Control Panel: Only normal memory reads (e.g. via Mem32 in the J-Link Commander) will use stop mode, as background access mode is currently only used by RTT & HSS. I also answered you in the support ticket case. BR Fabian