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, 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…

  • Hello, Thank you for your inquiry. There is no automatic importer for makefiles so you would need to set a Embedded Studio project up manually. First create a new project and select your target device. Now create folders to place your files in. ES uses virtual folders so you can create any topology. We suggest replicating the actual topology of the project for easier maintenance. Next add all project files. You can also drag and drop them. Add user include paths for your .h files etc. Depending …

  • Hello, Thank you for sharing your findings. As the reported behaviour seems to be solved now this thread will be closed now. Quote from pge: “What made it really difficult to find it is there is absolutely no error on it even in log file.... Any way to enable a verbose mode to help to catch this kind of error more quickly ? ” Error handling of external devices is rather difficult especially as the CFI interface does not offer any error handling whatsoever so J-Link has no chance to know what mig…

  • Hello, Thank you for your inquiry. The Globals.h used in that particular release is obsolete and was updated by a shipping script error accidentally. A corrected version V2.52f is now available in the download section that should remove any build errors. Sorry for any inconveniences caused. Best regards, Nino

  • Hello, Great to hear that you are up and running again with the debug setup. Quote from pge: “I cannot launch the firmware but that's probaly another story... ” Most likely some target device specific boot settings are missing. For this information we suggest contacting the silicon vendor. Best regards, Nino

  • Hello, Thank you for your inquiry. The reported behaviour was reproducible and is not intended. We found a fix already and it will be available with next Ozone release. Sorry for any inconvenience caused. To stay up to date regarding Ozone releases you can subscribe to our update notification list: segger.com/notification/subscribe.php?prodid=178,7 Best regards, Nino

  • Hello, Thank you for your inquiry. J-Link Commander script and JLinkScript are different formats. Eclipse will not accept a J-Link Commander script. How to use a JLinkScript in Eclipse is explained here: wiki.segger.com/Using_J-Link_Script_Files JLinkScript format is explained in J-Link user manual UM08001 and can be found in your J-Link software installation folder under Doc/Manuals. Quote from pge: “Also I don't understand how I configure debug profile to program the external flash and debug f…

  • Hello, Thank you for your inquiry. Virtual memory addresses are not supported by SEGGER Linker. Best regards, Nino

  • Hello, You should be able to expand these topics, see attached. Best regards, Nino

  • Hello Tom, Great to hear that you are up and running again. This thread will be closed now. Best regards, Nino

  • Hello, From J-Link perspective everything seems to be working as expected. Connection and download works as well as debugging in Ozone. Please understand that we can't put more time into this as the issue is most likely related to a incorrect Turestudio setup or similar which is maintained and supported by Atollic. In that case we suggest contacting Atollic. One more thing that you could check is if the Atollic settings are correct. A guide can be found on our website: segger.com/products/debug-…