Search Results

Hi, Quote: “- ERROR: Timeout while checking target RAM, core does not stop. (PC = 0x00000004, CPSR = 0x0000019B, LR = 0x00000014)! - ERROR: Failed to prepare for programming. Failed to execute RAMCode for RAM check!” In the "MCU" tab of the J-Flash project settings, what RAM address & size is configured? Does it work if you reduce the amount of RAM used(e.g to 8 KB)? Best regards, Niklas

Hi, Quote: “after installation (Linux , 64bit) each time I try to start Segger GDBServer, the JLink USB device gets kicked-out , disconnected by kernel. I see device disconnect in the kernel log. ” Sorry to hear that. Could you please provide us with further information regarding your setup?: Which version of the J-Link software? V6.18? Which Linux distribution? Which J-Link package was used? x86 or x64? DEB, rpm or tar? Quote: “I see device disconnect in the kernel log.” Would it be possible fo…

Hi, Quote: “ for a few years and have recently run into a problem on one of my boards.” This sound like a hardware issue. Quote: “VTref = 0.333V” Could you please check if the voltage is correct? What is the voltage of a working board in J-Link Commander? Best regards, Niklas

Hi, it is not possible to connect to the Cortex-M4 of a i.MX7 without enabling it beforehand. For further information, please refer to wiki.segger.com/IMX7D, section M4 Debug Application (Example). Does this work for you? Best regards, Niklas

Hi Christian, Quote: “I was thinking but to write the CFG register it's necessary a read of status register before to write the CFG. It looks like a "special" access for this register.” I could not find anything like this in the documentation of the flash device. Could you please point me to the respective documentation? Quote: “Does the J-FLASH take care of this or do we need to do a commands sequence (read status, write CFG, etc..)?” You need to do a command sequence. An example can be found i…

Hi, sorry for the delay in response. Does this issue also occur with a simple application, like a loop which increments a counter? Quote: “ I got disconnect or retry window” Could you please provide us with a screenshot of the error message? Could you please also provide us with the output of IAR of a session where the error ocurred? Best regards, Niklas

Hi Torsten, Cortex-A53 / A57 support is planned to be available by the end of this year. In case you need support at the earliest, please get in touch via mail in order to discuss a custom solution. Best regards, Niklas

Hi, Good to hear that you are all up and running again! Best regards, Niklas

Hi, you can use the command "expdevlist <path to output file>" in J-Link Commander (JLinkEXE on Linux) in order to create a text file of supported devices. Quote: “I'm not necessarily using latest Segger tools ” May I ask why? If there is any regression, we would be happy to know about it in order to be able to fix it. Best regards, Niklas

Hi, for an overview of the IMX device series supported by J-Link, please refer to this wiki article: wiki.segger.com/IMX_Series_Devices Quote: “The xDx's must be for iMX7 Dual? But whats the difference between D3 , D5, D7?” Well, what device / eval board are you using currently? We use the names defined by NXP. You can find them on NXPs website: nxp.com/products/microcontroll…-7-processors:IMX7-SERIES Just click one of the device series, e.g. "i.MX 7Dual" (link: nxp.com/products/microcontroll…D?…

Hi, No worries! Good to hear that it works for you now /closed Best regards, Niklas

Hi Thomas, thanks for the feedback! Good to hear that it works for you Best regards, Niklas

Hi, Quote: “I have unchecked this option, debugger starts without error every time,” Sounds good. Quote: “but has often problem with stability during debug, I got disconnect or retry window.” Do you use low power-modes in your application? Some low power modes interfere or even disable the debug interface, which can cause J-Link to loose the connection. Best regards, Niklas

Hi, could you please update to the latest version of the J-Link software & documentation pack and provide feedback if the issue persists? Best regards, Niklas

Hi, Welcome to the ARM stuff Quote: “nrf52382 breakout board” Could you post me a link to the board? What debug header is mounted on the board? (Cortex-M 19 pin? Cortex-M 9 pin?). Or are you using single wires? To MCU needs to be powered, otherwise J-Link (or any other debug probe for that matter) will not be able to connect. If you have voltage meter at hand, I would recommend to measure the pins of the debug interface in order to make sure that the MCU is powered and that the debug interface i…

Hi, Quote: “So, I started uboot on iMX6Q and changed the VMA to a legal ddr address such as 0x10000000 so that I could download .elf file on ddr via J-LINK and debug. But it turns out useless, because simulator will reset CPU after download is done.” This is not a default behavior of J-Link, therefore the reset is probably issued by eclipse. Or this also occur via J-Link Commander? Do you want to give Ozone - The J-Link Debugger a try? You can build the executable as usual (make sure its located…

Hi, Quote: “Should I add "r" before erase? I'll try... ” looking forward to hearing the results! Best regards, Niklas

Hi, the best workaround is to update to V6.18 of the J-Link software & documentation pack, since the issue is fixed in V6.18 Best regards, Niklas

Hi Vinay, good to hear that you are up and running Quote: “If the device I want to flash DOES work out-of-the-box with JLink, then is there a way to program a particular device in daisy chained configuration of such devices using only commander script (without using JlinkScript) ?” Yes, just omit the "-JLinkScriptFile ${path to script file for Device x}" parameter. If there are multiple devices of the same type in the daisy chain, you then probably need to specify the current position by adding …

Hi, we are currently reworking the documentation of open flash loader. In the mean time, if you have any questions, please do not hesitate to ask vial mail or here in the forum. - Niklas