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.

  • Hello, Thank you for your inquiry. We received it via ticket system as well. To make sure no information gets lost between the different communications channels this ticket will be closed now. Best regards, Nino

  • Hello Lars, Thank you for your inquiry. It seems that J-Link can't access the device properly. Attached is a working SWD connection to a SAMV71 XPlained Ultra eval board. Unfortunately it does not have JTAG so I could not test that. Do you have such an eval board? We recommend using it as reference and compare the signal quality from J-Link to target device. To make sure the J-Link has not been damaged does connection work to another target device with J-Link? Could you provide a J-Link log of a…

  • Hello, Thank you for your inquiry. What exactly is the setup you are trying to achieve? Are you using the internal compiler or an external one? Could you provide your project for reproduction? Best regards, Nino

  • Hello, Thank you for explaining your setup. Quote from jev: “However. We have the habit of using a single includefile to store all the generic control-macro's in. They must be available throughout the whole program. I do not want to hide these in an IDE somewhere. That's why we use the pre-include feature from IAR for (or add it to the CFLAGS in the Makefile for GCC through said -include option). Doesn't work though in SES. How can I do that? ” This can be done using global macros under Tools->O…

  • Hi, That sounds strange indeed. An example implementation can be found attached. We create a ENV SYSTMP. When called in Ozone as $(SYSTMP) it resolves as expected. Best regards, Nino

  • Hello, Quote from weiqj: “I MCU is TI CC2538. The address is not in the flash section. Is it the reason that j-flash won't work? ” Yes in that case J-Flash is the wrong tool to use. This could be achieved with J-Flash via init or exit steps but it is much more complex than doing it with J-Link Commander. However using the J-Link Commander for production comes with the mentioned drawbacks. To have 100% control over your setup we suggest getting a J-Link SDK and write a simple tool based on J-Link…

  • Hello, Thank you for your inquiry. 1: It is not necessary to port IAR projects if you are using Nordic SDK. The latest SDK already has working Embedded Studio projects. For e.g. the blinky project you can find the emProject file under examples\ble_central\ble_app_blinky_c\pca10040\s132\ses If you still need to import some non Nordic SDK example from IAR the following guide can be used: wiki.segger.com/SEGGER_Embedde…to_SEGGER_Embedded_Studio 2: The license prompt should come up once you try to b…

  • Hello, Thank you for your inquiry. Such an issue is not known to us. How did you create the project? You can also alternatively create an Atollic project and use the ES project importer for Eclipse. This should import your CubeMX project without any issues. Best regards, Nino

  • Hi, We retested it and it was working as expected. Then we noticed that you are using a macro within a macro with "$HOME/nRF... This is currently not supported. So if you use the full home path instead it should be working. Best regards, Nino

  • Hello, Thank you for your inquiry. Please understand that discussion J-Link SDK content in a public forum is against the license terms. If you are still under valid support period feel free to open a support ticket. More information can be found in my signature. This thread will be closed now. Best regards, Nino

  • Hello, Please understand that we can't put more time into checking your custom setup, as this leaves the scope of assistance we can give through the forum. As your project is based on the Nordic SDK we recommend using the latest SDK and one of the ready Embedded Studio example projects. For example in \examples\ble_central\ble_app_blinky_c\pca10040\s132\ses you can find the Embedded Studio project for the blinky project. You can use this as baseline for your additional files and add them to it. …

  • Hello, Thank you for your inquiry. Such an issue is not known to us. We tried to reproduce the behaviour using an RTT sample in Embedded Studio + RTTClient V6.40 and there was no double echo, see image attached. Which J-Link software version are you using? Could you send a screenshot that shows the issue you are seeing? What are the steps to reproduce the behaviour? Best regards, Nino

  • Hello, We received your inquiry per ticket system as well. Could you try to keep information together in one communication channel for future inquires to make sure no information gets lost? To answer the solder bride question for all that stumble upon this thread: There is only one solder bridge on the adapter. Simply close that. We tried to reproduce the issue with a FRDM-K64F eval board and indeed unlock is not working when selecting JTAG as interface. With SWD everything was working as expect…

  • Hello Russ, Thank you for your inquiry. Quote from schmalr: “Are there any reasons to consider including connectors for both the large grey "Target" cable and the small black "Target+Trace" cable? Or does the "Target+Trace" cable provide 100% functionality and thruput? ” Only use the Target+Trace interface if you are looking to trace. The bigger grey cable interface is only meant for backwards compatibility and only debugging. Connecting both will result in degradation of Trace signal quality. W…

  • Hello, Thank you for your inquiry. The reason we do not encourage using J-Link Commander for production is that the Commander is more a debugging and troubleshooting tool which is under constant changes and new features are added etc. This is usually unwanted by customers who want a stable production environment that will work for years even after updates. That is what J-Flash is for + many other production features the Commander does not have. To read back the MAC and save it you can use the CL…

  • Hello Martin, Thank you for your inquiry. Please note that this is no support forum but a community forum. Threads with no response after 30 days will be autoclosed. If you are looking for support we suggest contacting our official channels via e-mail or ticket system where you are guaranteed a response. Both your devices you have registered with seem to be in valid support period so I suggest to open a ticket. More information about the Forum rules and contacting methods can be found in my sign…

  • Hello, Thank you for your inquiry. Quote from smithron99: “Searching I've done suggests the linker needs to be directed to link to C++ runtime ( -lstdc++ ) but this option does not appear to be supported by the SEGGER linker. Linker version info is below. ” Correct, see here: Segger Linker 2.25 However Embedded Studio also comes with the gcc Linker which should support this. Best regards, Nino

  • Hello, Thank you for your inquiry. The MB9DF125 is currently not one of our supported devices: segger.com/downloads/supported-devices.php It was supported in the past but support was maintained by Fujitsu, now Cypress. Unfortunately Cypress no longer maintains the necessary JLinkScript file for this particular device so we had to remove this device from the list of supported devices. For guidance we suggest contacting Cypress support. Best regards, Nino

  • Hello, Thank you for your inquiry. The Flash protection bytes will be set if you erase the Flash to all 0xFF (quite an inconvenient default by NXP). To unlock your device you can use J-Link commander and type "unlock kinetis". However for this to work the reset pin of the target device must be connected to J-Link. When working with Kinetis devices J-Link will offer you two different device names for each Kinetis device. One with "allow security" and one without. For debugging purposes we recomme…

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Connect to all our nRF boards is working without any issues. Could you post a screenshot of a J-Link Commander connect session? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander Do you have an external J-Link to use for testing? It might be that the J-Link OB was damaged in some way. Does connecting work with another "fresh" eval board? Could you provide a J-Link log of the failed session? wiki.segger.com/Enable_J-Link_l…