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, For clarification, J-Link is the debug probe and just one possibility for the I/O interface. The I/O interface can be anything that your target device supports (UART, Ethernet, USB, Debug Interface, SWO, etc. etc.). If you are using the default configuration of Embedded Studio RTT is the I/O interface, which uses the debug interface and J-Link forwards the collected data to the host terminal. Best regards, Nino

  • Hello, We tried to reproduce the behaviour but with the little information we have we could not see the behaviour. Could you provide more information about your setup? What Linux are you using? Do you see the same behaviour in the latest Ozone version V3.20i? Could you provide an example project for reproduction that would run on an eval board that shows this behaviour? Best regards, Nino

  • Hello, Thank you for your inquiry. Where do you expect the print out to happen? What I/O interface do you use for that? If you are using the default that Embedded Studio sets up it will be SEGGER RTT:…about-real-time-transfer/ So you would see the output in the debug terminal of Embedded Studio. Other available I/O types and how ES has to be set up for them is explained here: Best regards, Nino

  • Hello, Great to hear. Happy debugging. As the original question is answered here we will consider this thread as solved now. Best regards, Nino

  • Hello, See your other post for more details on how to get started. emStudio, arm and ETA We will close this thread now to avoid duplicate threads. Best regards, Nino

  • Hi, On the CPU Support Package website there is a video that shows how a simple hello world project can be created within seconds:…o/technology/cpu-support/ Did you give this a try? All you need to do is to install the package. Create a new project with the package and project generator and press F5 to compile and download the Hello World program. Or is there something that is not clear here? To get started no manual should be needed. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Which Ozone version are you using currently? Is it the latest 3.20h? If not could you give that a try? Best regards, Nino

  • Hello, Yes, the fix should be in the current Ozone release. We also got it confirmed to be fixed by another customer. Eventually it was a different issue that only looked similar. We will check again with the information from the linked thread. Best regards, Nino

  • Hello Jez, Thank you for your inquiry. Quote from JezC3128: “I've tried SWD @4, 8, 10 & 12 kHz but that doesn't seem to make any difference. ” Can you confirm you mean kHz and not MHz? If yes, that might already be the source of the issue. Try >20 MHz. What error message are you getting exactly? Could you provide a screenshot? Could you do the testing with the latest V3.20? V2.52 is no longer in maintenance and support. Best regards, Nino

  • Hello, Thank you for your inquiry. Yes Cortex-A is supported by J-Link Edu Mini. From your description it sounds like you are connecting the debug connector incorrectly to your board. To connect 9-pin to 20-pin you can use the following adapter:…s/9-pin-cortex-m-adapter/ How to test connection is explained here:…ty_using_J-Link_Commander Best regards, Nino

  • Hello, Quote from mattb1969: “The second link you shared references J-Link Commander, I have no such application, which one is on Mac? If I use JLinkExe, it works, I can connect and gather info about processor and indicates 'Cortex-M0 identified.‘ so that appears to suggest there is a connection between the my Mac and the EDU Mini. ” Yes, J-Link Commander is JLinkExe on macOS. So general connection with J-Link is working. From our software perspective there are no issues then. Please understand …

  • Hello David, The linker thread talks about a completely different setup so these two issues are not comparable. For the iMX the fix is implemented. However this will not work for all >10000 devices that we support as it is a target specific implementation each time. It is impossible to maintain automatic handling of this for all devices that we support. That is why it is user responsibility to handle cached memory sections. Best regards, Nino

  • Hello, While that might be true >99% of our customers expect fast and/or small code. That is what the SEGGER RTL is optimized for. So our malloc and other memory management functions are as small as possible. mallinfo is usually used for Linux systems where resources are no issue. That is usually not the case on embedded targets, especially on Cortex-M targets. A generic memory handling where mallinfo is fully implemented would bloat the debug code on your target immensely which is what most of …

  • Hello, Thank you for your inquiry. mallinfo() is no C std lib function which is why it is not available with our current run time libs. We will however consider it and put it on our wish list. Best regards, Nino

  • Hello Stephan, Thank you for your inquiry. isfinite is currently not yet implemented in the math.h of the SEGGER RTL but it should be available with the next Embedded Studio update. Currently we are moving the ES RTL to the SEGGER RTL step by step which is why it can happen that not all functions are transferred yet. But this should be resolved soon and the ES RTL will be replaced + more. You can subscribe here to get notified when the new Embedded Studio version launches:…

  • Hello, Thank you for your inquiry. When you reach the fault handler Ozone the application will usually halt and trace data will be displayed in the instruction trace window and timeline window. If I understand you correctly this is also the case for you. Correct? You can try to increase the number of displayed data in trace settings by increasing the Maximum instruction count value. Depending on how much trace data your application generates the max value will vary. You can try it out with e.g. …

  • Hi, Thank you for your inquiry. The issue is reproducible and yes it is not intended. It will be fixed. Best regards, Nino

  • [SOLVED] SWO usage

    SEGGER - Nino - - General


    Hello, in short yes. But if you are going for pin tracing anyhow you will get many advanced debug features that make any feature the ITM would bring obsolete. If you planned on using SWO for printf we recommend using RTT instead. Then also the SWO pin is not needed:…about-real-time-transfer/ So effectively you do not loose any debug functionality. Best regards, Nino

  • Hi Stavros, Could you provide a little example project which shows the reported behaviour so we can try to reproduce the issue? Best regards, Nino

  • Hello, Thank you for your inquiry. The J-Link does not have any pin tracing capabilities. For this a J-Trace PRO is required: If your target device features a trace buffer, a J-Link can be used for tracing. An overview of the different trace types can be found here: Best regards, Nino