Search Results

Hi Niklas, Please note that this is not a support forum. If you require support and you are still within support period for the J-Trace, you can contact us via our support ticket system (link in my signature below). 1) Could you please send us - the Ozone console output? (View -> Console or Alt+Shif+C) - a J-Link logfile? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File 2) Did you enable trace in Ozone (Tools -> trace settings -> Trace pins)? Please also note that we generally re…

Hi, did you check the troubleshooting section already? wiki.segger.com/J-Link_RTT_Viewer#Troubleshooting Best regards, Fabian

Hi, sorry for the delay in response. This is on our ToDo already, however we did not manage to implement this as the demand for this feature is currently still very low, so other projects are prioritized. Support is planned until the end of this year. If you require this feature earlier, you could add it yourself for your device, using a J-Link Script FIle with an InitTarget() function establishing the connection: wiki.segger.com/J-Link_script_files#InitTarget.28.29 BR Fabian

Hi, Thank you for your inquiry. Just to rule this out: Did you make sure that the RESET-pin is connected between J-Link and MCU? For the connect under reset this is absolutely necessary. BR Fabian

Hi Lee, Quote from essele: “I'm quite surprised you couldn't find it ... if you just google the part number the top response seems to be one of your competitors programmers that supports the chip ” This is not what I said at all. What I wrote is: Quote from SEGGER - Fabian: “Also, I cannot find official information about a ZD25WQ16 flash chip online. ” What I meant was: After having a quick look on google, I could not find an official Zetta presence in the web providing information about this Fl…

Hi, This would absolutely explain the issue. Please note that these voltage differences can also damage the J-Link. In case your J-Link was damaged, you could make use of the SEGGER Trade-In Program: segger.com/purchase/trade-in-program/ To prevent such kind of damage caused by ground loops or similar, we recommend to use an isolator between J-Link and target: segger.com/products/debug-prob…tors/j-link-swd-isolator/ BR Fabian

Hi, Currently, we do not have a configuration for the STM32H747-DISCO. I added this to our feature request list, however I cannot provide a timeline for this yet. It might take a while as we are currently fully booked. If you require support for this any time soon, you would have to create a flashloader yourself (link you posted). BR Fabian

Hi, Could you please tell us the serial number of the J-Link you are using? BR Fabian

Hi TIller, Thank you for the information. We will order the board and have a look at this. I will keep you posted. BR Fabian

Hi, I highly suspect that this is connected to your hardware. We did not receive a single other report of such a case happening. Does the same issue appear when using an evaluation board? The J-Link uses the voltage between VDD and GND (VTref) as reference voltage for the communication. I would suggest to measure the voltage between VDD and GND and compare it to the evaluation board. Also, you could connect an oscilloscope to the SWD signals to check and compare them with VTref. If there is inde…

Hi GVG, Good to hear that you are up and running again. We will close this thread now. BR Fabian

Hi, Reading erased ECC flash will result in an ECC error and in a memory read to fail.For most ECC flashes (including this one), reading programmed areas is allowed only and reading erased flash is expected to fail. I assume that this is what happens in your case (you can check this by verifying the ECC error flag of the flash controller). Solution: Either you disable ECC or you do not read erased sections of the flash. Best regards, Fabian

Hi, Thank you for verifying that the change works. Debug and flash programming support for these devices will be available with the next J-Link beta (V7.67b) and in the next full release (V7.68). The beta release is planned for sometime next week. We will close this thread now. Best regards, Fabian

Hi, Update: We managed to squeeze this in. I sent you a PM with a Link to a preliminary version. Could you please give this version a try and tell us if it works? Best regards, Fabian

Hi, Yes we will add them. Rough estimate: Within the next 2 weeks. Stay up-to-date regarding J-Link: segger.com/notification/subscribe.php?prodid=7,94 BR Fabian

Hi, what you experience is intended behavior and does not require a "fix" as nothing is broken. Short explanation: - Most flashes can only be written when in erased state. - A sector is the smallest unit that can be erased. => To write data to a programmed sector, the sector must be erased first. The reason why this is only happening if > 1KB is written is, that by default J-Link will use read-modify-write (RMW) for all data that is to be programmed if it is < 1KB (RMW threshold). This means, J-…

Hi, J-Flash Lite and J-Link Commander are using the exact same API calls to flash a data-file. If it works with the J-Link Commander, it will also work correctly with J-Flash Lite. Could you please send us J-Link log files from the download with J-Link Commander and from the download with J-Flash Lite? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File BR Fabian

Hi, I suggest to check out the following article: wiki.segger.com/J-Link_cannot_…the_CPU#Target_connection BR Fabian

Hi GMG, Yes there is. The most customizable and solid way would be to acquire and use the J-Link SDK. segger.com/products/debug-prob…nk/technology/j-link-sdk/ But you could also use the J-Link Commander: wiki.segger.com/J-Link_Commander#WJTAGIR BR Fabian

Hi Gavin, is there a specific reason why you are adding a new device instead of extending the existing RV32? It should work when extending the RV32, as it will use the same connection sequence and simply add the specified flash range. wiki.segger.com/Open_Flashload…ending_an_Existing_Device If you need to add a new device: The RV32 requires the short cJTAG init sequence. J-Link uses the long one by default, because it is the one used by most RISC-V architectures. For more information and how to …