Search Results

Hi, Thank you for your inquiry. 1) Does this issue still persist with the latest version of the J-Link Software? segger.com/downloads/jlink#J-L…twareAndDocumentationPack 2) Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Unfortunately, there are no evaluation boards available with a STM32WB15 device, so it is hard for us to look into this. BR Fabian

Hi, Are you using JTAG or CJTAG? In case you are using CJTAG, it should work with JTAG. BR Fabian

Hi, Sorry for the delay in response. the IS25LP512M is listed as supported, so it should work. Are you using the latest version of the J-Link Software? segger.com/downloads/jlink#J-L…twareAndDocumentationPack Quote from jautry: “Also, is there a way to read external flash registers from JFlash or Commander? They are not CPU memory mapped but would have to be accessed directly. ” If they are not memory mapped, how are they accessible exactly? Via a different AHB-AP? If so, this would be possible …

Hi Lee, Thank you for your inquiry. The ZD25WQ16 is not supported by the J-Link Software: segger.com/products/debug-prob…es/supported-spi-flashes/ Also, I cannot find official information about a ZD25WQ16 flash chip online. Does it also have another name? Can you point us to official documentation about this device? BR Fabian

Hi, Thank you for your inquiry. In 99% of the cases where such a problem appears, the target application itself may run fine but it is uncooperative in regards to debugging. Usually such a Problem is connected to one of the three following points. The application 1) re-configures the debug pins as GPIOs. 2) enables chip security (by accident or on purpose) 3) makes use of low-power modes that disable all debug related clocks inside the chip. All the above prevent a debug connection to the device…

Hi, Could you please open a support ticket for this via our support ticket system? All required information is in my signature below this post. BR Fabian

Hi RL, Could you please open a support ticket regarding this? You can find all required information in my signature below this post. BR Fabian

Hi, Yes it is. See: - wiki.segger.com/UM08001_J-Link…Guide#Target_power_supply - segger.com/products/debug-prob…ogy/interface-description BR Fabian

Hi Amutha S, Thank you for your inquiry. Could you please follow the troubleshooting article on the page linked below and send us a screenshot of the entire J-Link Commander output? wiki.segger.com/J-Link_cannot_…the_CPU#Target_connection BR, Fabian

Hi, Thank you for your inquiry. Yes, the Open Flashloader only supports page sizes with power of 2. This is because in the J-Link internal these values are shifted to work with them. Adjusting this for non power of 2 sizes is on the list, however this will not be supported any time soon. There are good reasons to only use power of 2 for flash sizes and Atmel/Microchip decided to not follow this convention for some reason. Workaround: The page size is used by the dll to call the flash loader to p…

Hi, Thank you for your inquiry. Such an issue is not known to us. 1) What device are you working with exactly? I am asking, because Resets are often very device specific. 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: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards, Fabian

Hi, the only J-Scope fix that made it into 7.64d was the following: Options dialog: The project settings were not updated after pressing "OK". Introduced with V7.64c. Fixed. This is a different issue that is totally unrelated to the issue you described. It does neither mention a crash nor MacOS. So I am not sure where you take the information from that the issue you raised was "clearly marked as fixed"? Unfortunately the issue you raised was not yet fixed, but we are working on it. BR Fabian

Hi, This is a chip specific question and not related to J-Link. I would suggest to look into the manual of the device or contact the support of the silicon vendor. Best regards, Fabian

Hi, Thank you for your inquiry. It seems that a flash sector of the device is locked (as the message indicates). I would suggest to look into the device reference manual to check how to unlock it. BR Fabian

Hi, If a J-Link does not support a certain Interface speed it will use the highest available. However, I would suggest to lower it even further, like 500 kHz. IF it works with an oscilloscope connected, this also points in the direction of a signal integrity issue. BR Fabian

Hi, Thank you for your inquiry and sorry for the delay in response. Could you please send us the xml file you are using? That way we could try to reproduce and fix this issue. BR Fabian

Hi, Disabling flash breakpoints is already supported: wiki.segger.com/J-Link_Command_Strings#DisableFlashBPs How to use command strings in Ozone: wiki.segger.com/J-Link_Command…ng_J-Link_Command_Strings Does this solve the issue? BR Fabian

Hi, Sorry for the delay in response. The CC2642 has a device specific reset implemented. This reset is a reset via reset pin. However, there are some additional steps executed (resetting TAP, initializing ICE-Pick, Halt after bootloader,...). During reset, the reset pin is toggled twice for 50ms (as you already found out). This should be sufficient for the device to fully reset. Even though this might not change anything, I uploaded an adjusted, compiled script file for this device here (reset p…

Hi, All good, I am glad that I could help. We will close this thread now. BR Fabian

Hi Roland, Good to hear that you are up and running again. BR Fabian