Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

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

  • Hi John, Thank you for providing the connect sequence screenshot. From it we can see that from J-Link perspective everything is working correctly. What seems not to be working is DAVE telling J-Link the correct target device name. For this Infineon DAVE support is the correct contact. Best regards, Nino

  • Hello, Thank you for your inquiry. Could you provide a photo of your front and backside of the J-Link you are using? Best regards, Nino

  • Hello, Thank you for your inquiry. We received your inquiry via our Supportsystem as well. To make sure no information is lost between different channels we will answer you in our Supportsystem. This thread will be closed now. Best regards, Nino

  • Hello, Thank you for your inquiry. From J-Link perspective the connect seems to have worked. For reference could you provide a screenshot of a J-Link Commander connect sequence? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander From the error message it appears that DAVE is using a wrong target device name. For this issue we recommend contacting Infineon support as it is not related to J-Link software. Best regards, Nino

  • Hello, Thank you for your inquiry. The J-Link SDK manual is a separate product that needs to be purchased: segger.com/products/debug-prob…nk/technology/j-link-sdk/ As you seem to be coming from a silicon vendor you most likely already have a license. In that regard we recommend asking your purchasing team. If they do not have such information then feel free to contact our sales department. Best regards, Nino

  • Hello, Thank you for your inquiry. Could you tell us your J-Link S/N for reference? Generally the proposed approach can be achieved with the J-Link commander and a J-Link Command File. See J-Link user guide UM08001 in section Using J-Link Command Files. The sequence would be something like this: -con -TM4C Device Name -jtagconf for first device in jtag chain -set speed -h -erase(optional) -loadfile -jtagconf of second device -h ... -exit This could be an implementation sample. Unfortunately we d…

  • Hello, Thank you for your inquiry. This is possible however most solutions leave the scope of the capabilities and licensing terms of a J-Link Edu Mini. For Flashing our professional production tool J-Flash can be used. However the J-Link EDU Mini does not have a license for that. With the EDU you could use a J-Link Commander script or a JLinkScript file. For more information see the J-Link user manual UM08001. Please note that the J-Link EDU Mini may only be used for private and educational pur…

  • Hello, Thank you for your inquiry. To be able to connect signals GND, 5V and 3V3 must be jumpered. See here for more details: wiki.segger.com/LAUNCHXL_CC2650 Best regards, Nino

  • Hello Paolo, Thank you for your inquiry. The reported issue was reproducible. We are currently working on a fixed J-Link software version. Until then you can use the following workaround: - Create a JLinkScript with function ConfigTargetSettings() - Execute exec command SetSkipInitECCRAMOnConnect and set it to 1 - load JLinkScript in your Ozone project e.g. in hook function BeforeTargetConnect More information about JLinkScript and the Ozone project file can be found in the J-Link user guide and…

  • Hi, little update in this regard. In the latest J-Link software version V6.44c the RTT Viewer should be back to old speeds and according to our measurements even faster. Could you give it a try and report back your findings? Best regards, Nino

  • Hello, Thank you for your inquiry. Generally all cores that follow standard RISC-V RV32 implementation are supported by J-Link. Quote from dsula: “I've taken up this issue with Syntacore and according to them J-Link is NOT compatible with SCR1 (as of March 2019). The only supported option is to use OpenOCD. ” This is quite a worrisome statement by Syntacore as we specifically implemented support for the SCR1 for them... See here for more information with example projects etc.: wiki.segger.com/Sy…

  • Hello, Thank you for your inquiry. From the google links I could not find what core type the Telink chips are. Generally they are currently not supported. If they are Arm cores then you could add support yourself with our Open Flashloader interface. If they are some proprietary core type it is not supported by J-Link. Best regards, Nino

  • Hello, Thank you for your inquiry. We are not exactly sure what you mean from the example you provided. Could you provide a bigger snipped where one can see where the BP is actually set? What behaviour would you expect? What steps do you take when setting the BP? Does the target not halt when reaching the conditional statement? Best regards, Nino

  • Hello, Thank you for your inquiry. Please be aware that this forum is a community forum so there is no guarantee to receive a response here. We tried to reproduce the reported behaviour but everything was working as expected in our example setup. See successful connect sequence attached. Are you using a RX adapter between J-Link and target device? segger.com/products/debug-prob…ries/adapters/rx-adapter/ or segger.com/products/debug-prob…adapters/rx-fine-adapter/ Are the 5 V VTref expected? Could…

  • Hi Hans, We received this inquiry via Supportsystem as well. To keep all information in one place this thread will be closed now. For everyone else, the minimum recommended RAM size is 5-6 kB. Best regards, Nino

  • Hello Dave, Thank you for your inquiry. Please be aware that this is no official support forum so there is no guarantee to receive a response here. If you are entitled to support see my signature for more information. Quote from dmarples: “I can't say which chips it supports but it certainly works with the IS25LP064A as found on the 1021-EVK. ” A list with supported Flash chips can be found here: segger.com/products/debug-prob…es/supported-spi-flashes/ EDIT: Just noticed that we received your in…

  • Hello, Thank you for your inquiry. What is the actual name of the target device you are looking to debug? Is it on our public supported devices list? segger.com/downloads/supported-devices.php If not but it is one of our supported core types you can add support yourself: segger.com/products/debug-prob…pported-cpus-and-devices/ wiki.segger.com/Adding_Support_for_New_Devices Best regards, Nino

  • Hello, Thank you for your inquiry. The folder you are trying to write to is write protected by admin rights. Simply select another saving location for your project file and you should not see this error message anymore. Alternatively operate J-Flash with admin privileges if you really want to write into the installation folder. Best regards, Nino

  • Hello Hans, We received your inquiry via Supportsystem as well where the topic has been solved. A fixed version will be available with our next J-Link software beta. This thread will be closed now to avoid double information. Best regards, Nino

  • Hello Hans, Thank you for your inquiry. We received your inquiry via our Supportsystem as well. To avoid double information this thread will be closed now. Just a quick info to other readers. We were able to improve the load time in this case to around 15 s. The improved version should be available with the next Ozone release V2.62. Best regards, Nino