Search Results

Search results 1-20 of 127.

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

  • Hi, Thank you for your inquiry. Could you please elaborate what kind of work you are using the J-Link EDU Mini for? I am asking because you are talking about working days and it is illegal do use the J-Link EDU Mini in a commercial context. You can read up on this here (Licensing and support/Terms of use):…k/models/j-link-edu-mini/ The TOS should also pop up at least once a day when using the J-Link EDU Mini. Regarding your question: Such an issue is not known to u…

  • Hi, Does the issue persist when issuing a reset before erasing? Source Code (2 lines) If the problem persists: Could you please provide us with a .hex file of the application that is running when you try to erase the chip? Best regards, Fabian

  • Hi Álvaro, Thank you for your inquiry. From what I understand, you are trying to write the external flash via the on chip memory controller. Is that correct? Regarding the datasheet, the memory controller lists external memory from 0x8000 0000 on-wards (in 0x1000 0000 steps) with a size of 64MByte for each. Since the external flash you are trying to write data to is 4 MByte in size (32MBit), it is probably places at 0x8000 0000, so there is most likely no flash at 0x9000 0000. Please make sure t…

  • Hi Hugo, Thank you for your inquiry. From what we can see, the J-Link seems to be defective. Could you please provide us with the serial number of this J-Link? I am asking because the the S/N you have added to your forum profile is from a unit which is out of support and warranty. For such a unit we recommend to make use of our trade-in program: Best regards, Fabian

  • Hi, Thank you for your inquiry. Please note this is not a support forum, but a community forum. For more information please refer to my signature. Regarding your issue: There is no issue known to us regarding the LPC55S69 series. I am not entirely sure if I understand you correctly. What you mean with "LPC55S69 0A" and "LPC55S69 1B" ? Is this referring to an evaluation board revision? If so, which evaluation board are you using exactly? Could you give the latest Software and Documentation Pack v…

  • Hi Mehmet, Thank you for your inquiry. The "x" is just a place holder for a letter or for a number (in this case a letter). There are multiple STM32F051x4 devices, we do support:…3c8d546a798f8118d354fd795 Does this answer your question? Best regards, Fabian

  • Hi, Thank you for your inquiry. Such an issue is not known to us. Our Cortex-M Trace Reference Board uses the same chip and there have been no issues reported. It is most likely that this issue is connected to your custom board. Do you experience the same problem on an evaluation board? Best regards, Fabian

  • Hi, we will be looking into this. I will come back to you as soon as we have news. Best regards, Fabian

  • Hi, Thank you for your inquiry. If you are unsure whether a specific device is supported or not, please refer to this list here: It contains all devices supported by J-Link. Best regards, Fabian

  • Hi, Thank you for your inquiry. There should be no issues with reading the registers with J-Link + J-Link Commander. The base address should be mentioned somewhere in the PDF you are using (memory map, register category). If you cannot find it, please contact TI support about this. Best regards, Fabian

  • Hi, Do you have any peripheral flash connected to the chip at address 0x90000000? Could you please check, that there are no flash banks enabled in the J-Flash project, that are not accessible? You can do so here:…3c8d546a798f8118d354fd795 Best regards, Fabian

  • Hi, Do you have the possibility to test the J-Link EDU Mini on another board or another J-Link you can connect to the board with? Unfortunately, there is not much more we can do for you, as long as we are not able to reproduce this with. Best regards, Fabian

  • Hi, Did you set the RTT Viewer to use "existing session" + "auto reconnect"? If not, does it work when using RTT Viewer with these options enabled? Could you please provide us with a screenshot of the RTT Viewer's "Configuration" dialog? Best regards, Fabian

  • Hi Thomas, Sorry for the delay in response. We have pretty busy days right now (preparations Embedded World, etc.). We looked at this again. The issue is in the HAL.c and not in the way how the memory accesses are executed. To access the DBGMCU registers from CPU space (your application), you are supposed to use 0xE00E1000, see STM32H7 reference manual:…3c8d546a798f8118d354fd795 (Taken from RM0433) Therefore we suggest that you correct the HAL-init to use the right…

  • Hi Radhika, Thank you for your inquiry. When using Open Flashloader, you do not need to have position independent code. The flash loader is downloaded into the RAM area specified in the application. The Open Flashloader is designed to be used with the J-Link debug probes. It will work with the J-Link Plus. Best regards, Fabian

  • Hi Radhika, Thank you for your inquiry. Reg 1.: As I can see in the image you attached, you are doing this already ("[..] Loader = [..]"). You actually have to provide a flashloader for each memory area. For more info, please refer to this page: Reg 2.: Best regards, Fabian

  • Hi, Thank you for your inquiry. Does this problem still occur with the latest version of the J-Link Software and Documentation Pack? You can download it here:…twareAndDocumentationPack NOTE: Please also update the J-Link DLL of Keil via the J-Link DLL Updater included in the Pack mentioned above. If the problem still persists after updating: 1) Do you use custom hardware or an evaluation board? In the latter case which one? 1.2) If custom hardware, do you experienc…

  • Hi, We will announce this feature in our news letter as soon as it is added:,94 Best regards, Fabian

  • Hi, 1) So you were able to connect to the device with another debug probe? 1.1) If so, which one? 2) Did you you set the device into any low-power mode or did you lock the device in any way? 3) Could you provide us a datafile (e.h. .hex) of the application running on the target? Best regards, Fabian

  • Hi, We fixed the issue. The fix is part of version V6.62a and later. Best regards, Fabian