Search Results

Hello Remco, The title is more than misleading. Embedded studio will produce the exact binary that you set it up to generate. Why your release build is not working but the debug build does can have numerous reasons. And none of them have to do with SEGGER products. So we recommend to get in contact with Nordic support in this regard. This thread will be closed now. Some generic pointers on what is usually forgotten when moving from debug to release build: - Check if the correct preprocessor defi…

Hello, we will check the default sample. But this sample is meant to be used only to get a feeling on how Embedded Studio works. It is possible that it will not cover all use cases automatically. If you plan on testing more features that are even architecture specific we recommend to create a new project with the project generator for the exact device or coretype that you are looking for to avoid exactly such issues. Best regards, Nino

Hello, Thank you for your inquiry. The register xml files are based on the silicon vendors svd files so ST made a mistake here. We will make sure this is fixed in the next package update. Best regards, Nino

Hello, Unfortunately this is not helping. We would need to reproduce the behaviour on hardware. Could you provide an example project for reproduction that would run on an eval board? An elf file + the Ozone project .jdebug file should be sufficent. Best regards, Nino

Hello, Thank you for your inquriy. The HPMicro Package is maintained by HPMicro directly. So you would have to contact HPMicro support in this regard. As soon as they send us the updated package we will make it public. Best regards, Nino

Hello, The solution in the linked thread was to use Debug.ReadIntoInstCache on the RAM section after the RAM code is loaded. In that case there was information missing from the elf file that the section will be copied into RAM so Ozone has no way to know that there will be a copy to RAM later on. So it is possible that this is the same issue with your setup. We recommend to check the documentation of the linker you are using and see if you can add that debug information to your elf file so Ozone…

Hello, The reported behaviour is not reproducible for me with Ozone V3.26h, see picture attached. Could you provide an example project for reproduction that would run on an eval board? An elf file + the Ozone project .jdebug file should be sufficent. Best regards, Nino

Hello, Thank you for your inquiry. The behaviour is expected as the project you have loaded it the default Hello project which only runs in the simulator. You need to create a new project where you select the nRF52832 as target device. For more information on how to get started see here: segger.com/videos/#c168119 Another great resource are Nordics setup guides for Embedded Studio which you can find on the website of Nordic Semiconductor. Best regards, Nino

Hello, Thank you for your inquiry. Yes PC sampling was removed as it was rarely used and in some cases could case issues on certain architectures. It may be reintroduced in future but there is currently no fixed time frame for this. May I suggest to use SystemView instead? segger.com/products/development-tools/systemview/ This can be used for performance analysis on any of the supported architectures by J-Link and does not require any specifc hardware support as the debug interface SWD/JTAG itse…

Hello, Thank you for your inquiry. Such an issue is not known to us. The reported behaviour was not reproducible for me with V6.32a. Could you give that version a try? If the issue persists, could you provide a simple example project that shows the behaviour for reproduction? Best regards, Nino

Hello, Thank you for your inquiry. No that package supports the SAME70 series only. What you want is the SAME51 package. That will work with any board that uses a SAME51 chip as the packages are CPU Support packages and not board specific. Best regards, Nino

Hello, Thank you for your inquiry. Essentially all you need to do is to implement your own version of handle_trap as it is defined as weak. See the following Wiki page for more information: wiki.segger.com/How_to_impleme…rrupt_handlers_for_RISC-V Best regards, Nino

Hello, Great to hear that you are up and running again. This thread will be considered solved now. Happy Debugging. Best regards, Nino

Hello, Thank you for providing more information about your setup. In this case Ozone behaves correctly. After Reset there is no Code in the TCM, per default Ozone will try to set a breakpoint at the startup completion point, which is usually main. But in your specific setup main is copied later to TCM after startup so there is no code after reset where Ozone could set a breakpoint. That is why you get the accurate error message. To avoid this you can try to change the startup completion point to…

Hello, Thank you for your inquiry. Sounds like your source file was not added to the current active project but only to the solution. So when building your project the source file will naturally not be build. Could you provide a screenshot of your project explorer or alternatively an example project for reproduction? Here is the article describing how projects and solutions work in Embedded Studio: studio.segger.com/ide_project_system_overview.htm Additional Technical articles can be found here:…

Hello Gavin, As these questions are not related to Embedded Studio this thread will be closed now. My colleagues from the J-Link team will answer your other forum thread soon regarding your JLinkScript questions. Please note that this is no support forum. If you have bought one of our products and if you are in valid support period feel free to contact our support channel as explained in my signature. Best regards, Nino

Hello, Thank you for your inquiry. The issue should be fixed with the next Embedded Studio update. Sorry for any inconveniences caused. To get notified automatically when the new version is available you can subscribe here: segger.com/notification/subscribe.php?prodid=196 Best regards, Nino

Hi Gavin, Thank you for your inquiry. .jlink files are deprecated and no longer supported. Instead we recommend to use JLinkScript files: wiki.segger.com/J-Link_script_files Best regards, Nino

Hello, Thank you for your inquiry. Also thank you for the documentation feedback on the linker. I agree that it could be better explained where to find which filename is used by SEGGER Linker and how to access it easily within Embedded Studio. For completion, to easily navigate to your linker script file simply right click your project in the Embedded Studio project explorer and select "Edit Linker Script". A general documentation of the SEGGER Linker can be found here: segger.com/doc/UM20005_Li…

Hello, Thank you for your inquiry. Well does your application have a main function? If yes, do you have any code optimization active that might remove debug data? Try to disable any code optimization and see if it works then. Should you still see this message could you provide your axf file for reproduction? Best regards, Nino