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 your inquiry via our support channel in parallel as well. To make sure no information is lost between channels this thread will be closed now. Please do not use multiple contact channels for the same inquiry as this will only cause extra workload on our side slowing down our response time. Best regards, Nino

  • Hi, it is generally recommended to power cycle a MCU when protection is enabled. This ensures on (most) chips, that the settings get active. Additionally this also ensures that the J-Link connection is reset as well Best regards, Nino

  • Hi Marco, Great to hear that you are up and running again. Case closed. Best regards, Nino

  • Hello, Thank you for your inquiry. As mentioned in the other thread, this is intentionally not public knowledge so I will drop you a PM. Best regards, Nino

  • Hello, Thank you for your inquiry. Your GCC toolchain should give you some elf output file. If you load that up in Ozone the assembly sources should be referenced automatically. Just make sure that you set compiler options so debug info is generated. Otherwise the source file reference might be missing from the resulting elf file. Best regards, Nino

  • Hi Marco, yes it is still on our ToDo but not with high priority. So we can't name any fixed release date. But it is not forgotten Best regards, Nino

  • Hello Marco, Thank you for your inquiry. Such an issue is not known to us. Which version of Ozone are you using? Do you see the same behaviour in the latest version? Does it happen with binary files only or also with elf files? Could you provide exact reproduction steps? I gave it a quick try and the ODR register in my example setup stayed expanded when reloading the project due to application change. Best regards, Nino

  • Hello, Thank you for your inquiry. Correct embOS is our own RTOS so the plugin would not work with other RTOS's. Generally it is possible to view RTOS info of any RTOS in Ozone. But you need to supply a plugin so Ozone knows where to look for task/thread information of your RTOS. For this Ozone has an open JavaScript based interface which you can use to create your own RTOS awareness plugin. How is described in the Ozone manual in chapters 6.3 and 7.10. Best regards, Nino

  • Continuous data sampling

    SEGGER - Nino - - Ozone related


    Hello, Which J-Link Ultra+ exactly? There are multiple hardware revisions. Could you share your serial number please? What target device are you debugging exactly? Continuous recording is possible. However there will be naturally gaps as the gaps are defined by your sampling frequency. You have set it to Max which is >10 kHz. But e.g. if you set it to 100 Hz it is expected that between each sampling point there is a delay of ~10 ms (for 10 kHz it would be 0.1 ms). There is some delta here as J-L…

  • Hello, Thank you for your inquiry. Indeed the definition for I was removed. I will check with the team. Most likely it will be reintroduced with a future update. EDIT: I talked to the team. It will be reintroduced with the next Embedded Studio update. To get notified automatically when it is available you can subscribe here: Best regards, Nino

  • Hello, Thank you for your inquiry. emSSL works with any standard sockets, so the proposed setup would work. For more information feel free to contact our support team as described in my signature. Best regards, Nino

  • PowerPC

    SEGGER - Nino - - Ozone related


    Hello, Thank you for your inquiry. Currently there are no plans to add PowerPC support in Ozone. Best regards, Nino

  • Hello, correct dark theme is not available yet. It is still on our wish list but simply not with a high priority. Quote from AndyR: “i alwasy run with the windows Dark mode as well so you aren't even honouring the same thing as you do with Linux / OsX still ” We would if the OS's would be remotely comparable, unfortunately they are not. Quote from fraengers: “Totally agree with that. Better syntax highlighting would also be nice. Alternatively, the integration of Ozone features in Embedded Studi…

  • Continuous data sampling

    SEGGER - Nino - - Ozone related


    Hello, Thank you for your inquiry. Maximum data sampling frequency depends on the debug probe you are using. Which one are you using? What is its serial number? What is the expressions you are sampling? Could you provide a screenshot of your setup? Best regards, Nino

  • Hi, Thank you for your inquiry. That is correct. For advanced performance analysis features Ozone needs to be used. In Embedded Studio the focus is more on the toolchain and project management. The debugger only supports some basic performance analysis features. Best regards, Nino

  • Hello, OK thank you for clarifying. Regarding RTOS, maybe our RTOS embOS would be of interest for you. It runs on any MCU and is a perfect fit to Embedded Studio: It also comes with hundreds of BSP example projects for all kinds of boards and architectures that work out of the box. So you can get started with your application directly without having to worry how to start an RTOS. Best regards, Nino

  • Hello, Thank you for your inquiry. Which linker are you using in your project? SEGGER Linker or gnu linker? Generally you should be able to create a section for each code part and place the application accordingly. Now when you compile with Embedded Studio you can display the different memory usage of the different symbols and sections via View->Memory Usage. There you will find the memory regions defined for your device. If you now expand one of them you will find all symbols and sections that …

  • Hello, Are you sure that the same code worked on another Cortex-M0+? Because the Syntax you are using is not supported for Cortex-M0+ which is Arm architecture Arm v6M. So this could have never have worked with a Arm V6M target. This code will only work on Arm v7M and later, such as Cortex-M4 or M7. For more information we recommend to check out the Arm v6M architecture manual. Best regards, Nino

  • Hello, Unfortunately the issue is not reproducible for us. Could you attach an example project that shows the describe behaviour? Best regards, Nino

  • Hello, Great to hear that you are up and running again. Actually the process is documented, but in the J-Link Wiki as device specifics do not have to do anything with Ozone. The Ozone articles will only describe how to get a Ozone debug session running. Having hardware set up correctly is another story and user responsibility. Best regards, Nino