Search Results

Hi, could you please give J-Link Commander a try? J-Link commander is part of the J-Link software package, which is available free of charge here . - Start J-Link Commander (jlink.exe) - Type "connect" in order to start a debug session - Type in the target device name if asked (Or type "?" for a target selection Dialog) - Choose the correct target interface (JTAG/SWD/etc..) - Use a valid speed (Default: 4000kHz, try 100-500 if default does not work) - [JTAG only]JTAG conf can be default(most of …

Hi, the device requires a special connect. The special connect has been implemented and tested using a DM3730 device, therefore we cannot add DM3725 to the list of supported devices without having the hardware here. In case you really need DM3725 to be added to the list: If you send us 1-2 sample boards which can stay at SEGGER for test and maintenance, we can add official support for the DM3725 target device. Best regards, Niklas

Hi, sorry for delay in response. Could you please provide us with more information about your setup and the issue? Are you using an eval board or custom hardware? Which version of the J-Link software is used by CCS? Could you please provide us with a screenshot of the issue (in CCS)? Could you please provide us with a J-Link logfile of a session where the issue occurred? Log output can be enabled like as follows: - Open a connection to J-Link, e.g start J-Link Commander - Open the J-Link Control…

Hi, sorry for the delay in response. The QSPI flash used on the eval board is a N25Q128A, which should work fine. Would it be possible for you to provide us access to the board via a J-Link remote Server (Tunnel mode) session? 10-15 minutes of access time should be enough. Best regards, Niklas

Hi Maxime, Quote: “What do you mean by a reproducer? An elf file that causes this kind of issue?” Yes, this is what I meant. Quote: “It seems to be very irregular, and (it seems) usually happens when using some of the low power modes of the device (sleep/standby).” This could be expected behavior. It depends on the device and low power mode used, but it is possible that the debug connection is lost when the device enters low-power mode, and the debugger can not do much about it. You can make the…

Hi, I just gave it a try using a beagleboard with a DM3730 device and could not reproduce any issues. Source Code (54 lines) What do you use? An evalbaord or custom hardware? Best regards, Niklas

Hi, Unfortunately, ITM does not provide Instruction trace. If the A2F200M3F does not support ETM, J-Trace does not provide any benefit over J-Link PRO, since both J-Trace and J-Link PRO support ETB -Tracing. If the A2F200M3F does not support ETB either, I would suggest to use a J-Link ULTRA+ or a J-Link PRO + SEGGER SystemView in order to analyze the runtime behavior of the target. ( Works for all Cortex-M devices). More information can be found here: segger.com/products/development-tools/about-…

Hi, we are currently not aware of any issues regarding J-Link + BlueNRG1. Would it be possible for you to provide us with a reproducer? Quote: “The weird thing is, Ozone seems to be able to recover from this situation (at least in many more cases).” What do you mean by "recover"? When using only Ozone, does it work without issues? (There is a reset & halt option in Ozone). Quote: “Also, is support for BlueNRG2 coming?” Well, lets wait until the evaluation board is available before I ask engineer…

Hi, Does this issue still occur when using the most recent version of the J-Link software & documentation pack (beta)? Best regards, Niklas

Hi, this will be fixed in the next version of the J-Link software & documentation pack J-Link software & documentation pack (beta) Best regards, Niklas

Hi, this will be fixed in the next version of the J-Link software & documentation pack J-Link software & documentation pack (beta) Best regards, Niklas

Hi Angelos, I just gave it a try on a Raspberry and could not reproduce the issue. Does the issue still occur with the current version? Best regards, Niklas

Hi, Quote: “Also tried adding JFlash initialisation steps equivalent to the initialisation performed by the debugger under Source Codebench but still no luck” Could you provide us with the initialization steps executed by Codebench? I can then compare them with what we do internally for the Zedboard...... Best regards, Niklas

Hi, Quote: “Error: JTAG Timeout during adaptive clocking: RTCK did not respond. Cannot connect to target." ” The RTCK pin (pin 11) needs to be connected in order to use adaptive clocking. Quote: “I have nothing on the Segger's DBGRQ or RESET pins.” J-Link does not use the DBGRQ pin, it accesses DBGRQ via the ICE registers. You should connect the nRESET pin if possible. You do not have more information about the target? Name, vendor, schematics? Best regards, Niklas

Hi, the J-Link SDK (Part No 8.08.06 on the price list) is available for Windows, macOS, Linux x86/x64, and Linux ARM. Once you bought it, download links for all 5 packages will be provided to you. Quote: “Linux (Note: The package for running on Linux ARM comes without any support)” Quote: “I'm seeing more and more people who are developing on a RaPi and asking for native versions of code using the JLinkSDK.” Out of curiosity: May I ask where and in which context do you see people ask for the J-L…

Hi, 1000 kHz fixed interface speed is probably too much for the ARM7TDMI-S Core. You either can use a low speed (4 - 50 kHz) or try adaptive clocking. Best regards, Niklas

Hi Forum, we updated the webpage of J-Link EDU mini and added a specifications sheet: segger.com/products/debug-prob…k/models/j-link-edu-mini/ Best regards, Niklas

Hi, Quote: “/opt/SEGGER/JLink/JLinkExe -JLinkScriptFile /opt/SEGGER/JLink/Devices/NXP/iMX7D/NXP_iMX7D_Connect_CortexM4.JLinkScript does not seems to work, the script file is ignored, as far I see because no connection is established, and not even correct target core is selected. For me it was still on A7 from previous steps.” The core is specified in the JLinkScript, and the script itself works fine, as you noticed when using J-Link GDB Server. However, you need to execute the >connect< command …

Hi, do I understand you correctly that both issues (1. Does not work in IAR 2. Erase in J-Link Commander does not work) only occur with this one board, and all other boards continue to work fine? If yes, this seems to be an hardware issue of the specific board. (Could also be an issue of the target application under certain circumstances). If no, I will give it a try on a similar board and see if I can reproduce the issue. Best regards, Niklas

Hi, Quote: “ 2 unknown chips (Segger tells me they have an ARM7 and ARM9 core” To what output message of which application do you refer? Quote: “TotalIRLen = ?, IRPrint = 0x..FFFFFFFFFF80000000000011” This output indicates that J-Link did write a test pattern to TDI, but did never received it via TDO. This could be caused by one of the following: -> TDI and / or TDO not wired correctly -> Debug interface is disabled on the target -> VTRef not connected correctly (What voltage does J-Link Command…