Search Results

Hello, Thank you for your inquiry. The reported issues seem to be related to the Nordic version of Embedded Studio only. Please note that the additional features of that version are created and maintained/supported through Nordic and not SEGGER. So we recommend to contact Nordic support in that regard. Regarding the download suggestion of new Embedded Studio versions, this will only download the standard Embedded Studio version. To get the latest Nordic version of Embedded Studio we recommend fo…

Hello, Please understand that we can't discuss such things publicly. Could you contact us via the channel pointed to by Alex? This thread will be closed now. Best regards, Nino

Hello Ankur, Thank you for your inquiry. You can right click individual files and select "exclude from build". So if you have the "Debug" configuration active this file will now be excluded from Debug builds. Best regards, Nino

Hi, Thank you for your inquiry. It is still on the wish list. To get notified when it is available you can subscribe to our notification list. This thread will be closed as duplicate of the following thread: [SOLVED] Dark mode on Mac and Linux Best regards, Nino

Hello Markus, Thank you for your inquiry. If I understand you correctly you want to debug the application standalone without having to load the bootloader project. Is that correct? The bootloader also must execute otherwise the application will not run, correct? In that case first make sure that the bootloader was flashed. You can do this in the blinky project in option "Additional load file" where you set the bootloader hex file so you make sure the bootloader is always flashed. After that set …

Hello, Thank you for providing the files. With them the issue was reproducible. It is related to the selected background color for the color scheme you have selected. If you disable the background color marking should work as expected. We will see if we can improve the behaviour here. Best regards, Nino

Hello, This should be fixed in the latest Ozone beta. Could you give it a try and report back if it is working as expected? Best regards, Nino

Hello, Thank you for your inquiry. The reported behaviour was reproducible and will be fixed. Sorry for any inconveniences caused. For now we recommend using V3.10i until it is fixed. Best regards, Nino

Hi Vadim, Great to hear that you are up and running again. This thread will be treated as solved now. Best regards, Nino

Hello Hans, Thank you for your inquiry. Embedded Studio and most of our other debug software falls under the SEGGER Friendly Licensing (SFL) conditions: segger.com/purchase/licensing/license-sfl/ Our long term plans are to stay with that licensing model. But I understand your skepticism, to that I can add that any software already released under the SFL will always be usable under these conditions as we are generally not rereleasing old software. So e.g. if you have set up a project with the cur…

Hello, You seem to be affiliated with one of our supported silicon vendors. Could you open a support inquiry through our support channel for such matters? How is explained in my signature. This thread will be closed now to avoid duplicate information. Best regards, Nino

Hi, Yes that documentation is not correct and will be fixed. Sorry for the confusion. Quote from godmode: “Operator >> does only 2^n divisions/multiplications. ” On the surface yes, you can still write helper functions that do any kind of division with >>. Every CPU is in its core binary and can still do any division with only >>, right? For examples see stackoverflow or similar resources. Best regards, Nino

Hello, Thank you for your inquiry. / is and was never supported in JLinkScript files. Could you point me to the documentation you are referencing? It should be corrected. To do divisions in the JLinkScript you would need to work with the >> operator. Best regards, Nino

Hello Oliver, Quote from obetz: “I'm still most interested whether I can write (watched) variables without stopping the program in Ozone and ES. ” In short, yes in both cases. On Cortex-M targets this works as it is an architecture feature which our debug probes (J-Link, J-Trace etc.) implement. The debuggers in ES and Ozone simply access that functionality. If you are using other core types or architecture (Cortex-A, RISCV etc.) it depends on if the target device supports background memory acce…

Hi Oliver, Thank you for your inquiry. The only difference is that some advanced debug features are a bit different (tracing) and that Ozone can debug nearly and elf file format while ES supports the formats that the toolchain produces that it comes with. All other basic debug features should be the same. The biggest advantage of ES is that it comes with a complete toolchain so from project management to building the application and then debug it all is in one solution where Ozone is "just" a de…

Hi, Sorry I jumped the gun here. It will be fixed in the next release 4.52c. To get notified when the new version is released you can subscribe here: segger.com/notification/subscribe.php?prodid=196 Best regards, Nino

Hi, Thread will be continued in support ticket as you are in valid support period. EDIT: Is an issue with Embedded Studio. Code linked to 0x0 was not detected correctly. Will be fixed in next version. Workaround: Don't link code to 0x0 but starting from e.g. 0x4. Best regards, Nino

Hello, If the J-Link was purchased recently it is eligible for email support. Could you open a ticket as explained in my signature? My engineer colleagues will then provide you with further information. This thread will be closed now to avoid duplicate information or information loss. Best regards, Nino

Hello, I revisited your project and we noticed two things. The first LTRACE error happens in the PLL init section. This can happen if the CPU clock changes because the trace clock is directly dependent on that clock. In most cases the J-Trace PRO will be able to trace over such clock change but in some cases, depending on timing, it can happen that a couple of trace packets are sampled wrong due to the clock change. This seems to be such a setup. In such case we recommend halting the debug sessi…

Hello, Thank you for your inquiry. On the isolator site you can find more information about its power consumption on target side: segger.com/products/debug-prob…tors/j-link-swd-isolator/ It is typically 25 mA. Maximum 40 mA. What it is in your particular setup case you would have to measure for your self. Best regards, Nino