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, Great to hear that you are up and running again. We will consider this thread as solved now. Happy Debugging! Best regards, Nino

  • Hello, Thank you for your inquiry. Usually this issue appears if source files are moved around and their absolute path on your filesystem changes so the debugger can't reference the disassembly with the source code anymore. Could you try issuing a rebuild of your project instead of just a build? Does this improve the behaviour? If not recheck the paths of your source files and see if they match the paths on your filesystem. Where possible we recommend using relative paths. Best regards, Nino

  • Hello, Thank you for your inquiry. The default flash_placement.xml should always come with a non.init section. So no need to edit the xml. Just make sure to place your code correctly into that section. Quote from DL1GJJ: “* is this section under linker control, i.e. will it grow on demand? (I didn't find something about that) ” Yes it is dynamic depending on how many symbols you place there. Best regards, Nino

  • Hi, Thank you for providing additional information. We were able to reproduce the behaviour now and this behaviour will be fixed/improved. Best regards, Nino

  • Hello, Thank you for your report. The issue is reproducible and will be fixed. Sorry for any inconveniences caused. Best regards, Nino

  • Hello, Thank you for your inquiry. How to tell J-Link to preserve larger areas of Flash memory is explained here: How to use the command string in Ozone is explained in the Ozone user manual. Is that what you were looking for? Best regards, Nino

  • Hello, Thank you for your inquiry. The reported behaviour is known to us and is due to an issue with the J-Link DLL. If you use the same J-Link software version on your Ubuntu system you would see the same behaviour. Simply install the latest J-link software package on your Windows PC and everything should be working again as before: Could you verify this? Best regards, Nino

  • Hi Phillip, The extraction process is working as expected on Nixos as well. But it appears that the setup can't launch correctly. Eventually due to some missing shared library. To verify this could you try the following? Run the installer manually and see if that gives us any more information. To do this, run the following: ./install_segger_embedded_studio --extract-to dir cd dir ./Setup --data-file payload.dat --copy-files-to `pwd`/files Is there a specific reason why you want to skip the licen…

  • Hello, Thank you for your inquiry. Please note that the nRF Connect software and its implementation is maintained and supported through Nordic Semiconductor. So we recommend contacting Nordic support in this regard. Best regards, Nino

  • Hello Braon, Thank you for your inquiry. Do you see the same behaviour in the latest Embedded Studio version? Please understand that we can't provide support for old Embedded Studio versions. Best regards, Nino

  • Hi, OK I see. Unfortunately this behaviour is not reproducible for us. Both window layouts maximized, and windowed are restoring correctly for me. Could you try the following? - Close Ozone - Delete the .user file from the project folder - Reopen Ozone Do you still see this behaviour? Best regards, Nino

  • Hello Pete, Thank you for your inquiry. Such mode is not supported by our software due to its extreme speed limitations in comparison to the parallel trace with 4 data lanes. It would simply constantly create overflows on target device side due to the relatively low speed of the SWO pin. We recommend to use all Trace_Dx pins + Trace_Clkout if you are looking into streaming trace. For example our emPower eval board comes with trace pins populated and is based on the K66.…

  • Hi, Ok the settings look fine. Could you give the attached embOS project a try? It comes with SystemView instrumentation out of the box. You can find the project under \Start\BoardSupport\ST\STM32G431_STM32G431RB_Nucleo To rebuild the project our IDE Embedded Studio can be used: Simply open the .emProject file with Embedded Studio and start the debug session with F5. This will flash the application. After that you can close ES and open SystemView. Does Syste…

  • Hello, Thank you for clarification. The SAMV71 uses ETMv4 for tracing where support for conditional non branch instructions is "implementation defined" so currently this is not available for this target device. That is why the IT block evaluates incorrectly. But we will check if the target device supports this mode and it will be added to the J-Trace software then. Should it not be supported by the target we will check if the display of the code coverage can be improved. In case of the condition…

  • Hello, Thank you for your inquiry. A dark theme is already on our todo. But we currently can't name a fixed timeschedule when it will be available due to higher priorities on other features. To get a notification with the release notes for Ozone on each release you can subscribe here: Best regards, Nino

  • Hello, Ok thank you for verifying. You can either attach the elf file here in the forum, or if the data is confidential simply open a support ticket where you attach the elf file and reference this forum post: Best regards, Nino

  • Hi, I just gave it a quick try with a 2k and 4k display where the 4k display is the secondary on a Win10 machine with Ozone V3.20c and everything was working as expected. Is this still reproducible for you? If yes could you provide a screenshot of the windows before and after the move? What screen resolutions do both your screens have? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you provide a screenshot of the recorder settings in SystemView under Target->Recorder Configuration? Best regards, Nino

  • Hello, Thank you for your inquiry. Did you follow the suggestions in the thread you have linked? That should already provide you with all needed information to solve this issue. Why are you setting Cortex-M4 as the target device? Is your target device not supported by J-Link? If it is we recommend to select the exact target device name. This will in most cases be sufficient for the RTT buffer to be found. Best regards, Nino

  • Hello, Thank you for your inquiry. Currently we do not provide such patch file. We will put this on the wishlist for SystemView but can't promise anything at the moment as FreeRTOS is not our priority at the moment. Eventually the following threads might help: [SOLVED] SystemView in FreeRTOS not starting Best regards, Nino