Search Results

Search results 1-20 of 196.

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

  • Hi, The external power supply has to be connected to the target side of the Isolator, not to the target supply pins. We updated the article and added a picture to it to prevent any misunderstanding. Does it work on your side, when you use a similar setup as described in the article? If not: Are both power LEDs of the Isolator turned on? Could you please provide us with a picture of your setup? Best regards, Fabian

  • Hi, Please understand that the Open Flashloader support is not given by SEGGER. Also it appears that J-Link SDK API was discussed in this thread, which is not allowed (please refer to your first post for more information). All information required for the creation of an Open Flashloader is provided here: wiki.segger.com/Open_Flashloader This is the same information we use to create our Flashloaders. Since SDK API was discussed in this thread we will close it to prevent further discussion about i…

  • Hi, Thank you for your inquiry. We do not officially support OMAP5912, but OMAP5910, please refer to our "Supported devices" page: segger.com/downloads/supported-devices.php For what you want to do, a flash loader is required. You could implement support yourself via the Open Flashloader. For more information, please refer to the following article: wiki.segger.com/Open_Flashloader Best regards, Fabian

  • Hi Joe, firstly, the J-Link GDB Server serves another purpose as J-Flash. J-Flash is a production utility for the J-Link and the J-Link GDB Server is an interface between a GDB client and the J-Link. If you want a little deeper view on what is happening, you can create and compare the J-Link log files for both applications. How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Does this answer your question? Best regards, Fabian

  • Hi, You could read the register which contains the bit that indicates which bank mode is active. A tool to do this very easily is the J-Link Commander (JLink.exe), using the "mem32" command. Please refer to the article linked above for more information about the J-Link Commander and all available commands. Does this answer your questions? Best regards, Fabian

  • Hi, Thank you for your inquiry. Such an issue is not known to us. Quote from nlivic: “test0.hex :020000042001D9 ” Address 0x20000004 is not covered by the .hex-file excerpt you provided to us. It is covering 0x2001xxxx. To be more specific: 0x20010000, 0x20010010, 0x20010020, 0x20010030, 0x20010040. Looking at your hex file, this means 0x28818193 should be found at 0x2001004. What I do not understand from the information you provided us with is: Why does J-Link Commander say it is writing to 0x2…

  • Hi, Thank you for your inquiry. Please note that the usage of the J-Link on the ST board in such way is a license violation and illegal. You can read the license agreement in the daily pop-up and here: segger.com/products/debug-prob…nk-on-board/#terms-of-use Since you seem to be using this setup in an educational purpose please find information about our official products for educational use here: Small/cheaper version: segger.com/products/debug-prob…k/models/j-link-edu-mini/ More robust version…

  • Hi, Thank you for your inquiry. For size reduction we recommend implementing your flash loader bare metal (do not use libraries, HAL, or similar). Usually a flash loader should not be bigger then a couple of kB. If it is bigger you probably have some unnecessary code in it. To eliminate symbols and such is not the recommended way, because some symbols are needed for the flashloader to work. Please refer to the Open Flashloader wiki article if you want to learn more. There, you can find all infor…

  • Hi, Thank you for your inquiry. If you locked your device with a password, there is no way for the J-Link to unlock your device without it. You will have to unlock the device manually (e.g. via the J-Link Commander). The necessary registers should be writable after connecting to the device. For all necessary commands (e.g. w4) please refer to the following article: wiki.segger.com/J-Link_Commander#Commands Does this resolve the problem? Best regards, Fabian

  • Hi, Thank you for your inquiry. How to change the bank mode can be found in the manual for your device (normally some register writes). You will have to execute the necessary steps yourself (e.g. via the J-Link Commander or J-Flash via init steps). Further information about the J-Link Commander can be found here: wiki.segger.com/J-Link_Commander For further information about J-Flash please refer to the J-Flash User Manual (UM08003). Does this answer your question? Best regards, Fabian

  • Hi, Thank you for your inquiry. Could you please provide more specific information? 1) Which device are you trying to flash? 2) Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an evaluation board? 3) Could you please send us a J-Link log file? How to enable: https://wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File 4) Which tool do you use to flash your device? 5) Are you using the J-Link with the SN you p…

  • Hi, Thank you for your inquiry. Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards, Fabian

  • Hi, Thank you for your inquiry. We are not aware of any issues related to the J-Link GDB Server in combination with the J-Link Remote Server. When using the J-Link GDB Server in combination with the J-Link Remote Server, the GDB server is supposed to connect to the remote server. The connection should be established like this: Client side (GDB client <-> GDB server) <-> Host side (Remote server <-> J-Link). Could you please make sure that 1) the J-Link Remote Server is connected to the J-Link co…

  • Hi, Thank you for your inquiry. Yes, the J-Trace works when connected to a hub. We also do not recommend a particular hub, as essentially all hubs have some kind of downside. So it depends on what suits you the most. Therefore we recommend working without a hub for this reason, wherever possible. You will have to choose a hub which is able to supply the J-Trace with enough power to work. The J-Trace CM can draw up to 400 mA. Looking at the specification of the hub you are using shows that it can…

  • Hi Álvaro, Good to hear that you are up and running again. We will consider this case as closed now. Best regards, Fabian

  • Hi, No, it does not. As you can read in the self same thread, we plan to add official support from the SEGGER side for this device sometime later this year: Quote from SEGGER - Fabian: “2) We do not yet support i.MX8. We will add support sometime later this year. ” Until that time, NXP will have to provide support for this device. Best regards, Fabian

  • Hi Álvaro, Inside of the J-Flash "Project settings" (Project settings > MCU > Use J-Link script file). Do you have any further questions? Best regards, Fabian

  • Hi, Thank you for your inquiry. Generally the flash loader provided by us works with the eval board with default configurationsIf you want to use another mode you will have to edit the flash loader. I sent you a PN with the link to the sources. Best regards, Fabian

  • Hi, Thank you for your inquiry. Since you submitted a ticked we will consider this forum thread as closed now. Best regards, Fabian

  • Hi, Quote from awneil: “is there any restriction on using the VCOM and SWD simultaneously ? ” no there are no restrictions. So if you use the FTDI cable, everything works as expected? Could you tell us what your exact setup is? Best regards, Fabian