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.

  • 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

  • Hello Phillip, As I said, Nixos is not officially supported by us so please understand that we can't put more time into this investigation. Maybe the Nixos community/support could provide you with information what would be needed here to make the installer work on that platform. Best regards, Nino

  • Hello, Thank you for your inquiry. It is unfortunately not easily possible for the J-Link to detect what device is connected currently so the J-Link software assumes that the device name that is passed at the beginning of the debug session is correct. We had a autodetection in the early days of J-Link, but due to many silicon vendors not following the Arm specification the autodetection either did not work for many devices or in some hard cases even lead to bricked target devices. This is why we…

  • Hello, Thank you for your inquiry. The application does not stop. For printf this example uses SEGGER RTT which uses a buffer on the target as a I/O channel to J-Link. The default buffer is 1 kB in size. Depending on how fast the target device is this can be filled up faster than the J-Link reads it out. To avoid this you can e.g. increase the buffer size in the SEGGER_RTT_Conf.h file. Simply increase the value for BUFFER_SIZE_UP to e.g. 2048 and you should now see all 100 prints in the buffer. …

  • Hi, Thank you for your inquiry. What target device are you tracing currently? Do you see this behaviour only on IT blocks or also with other conditional instructions e.g. conditional branches? Best regards, Nino

  • Hi, Great to hear that you are up and running again. We will consider this case as solved now. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. How did you call the installer exactly? Did you do it with sudo (or whatever Nixos equivalent is)? I just gave the headless installer a try under Ubuntu LTS 19.04 and everything was working as expected. Please note that Embedded Studio is only tested and supported on Ubuntu LTS 12.04-20.04. Other versions and Linux distributions might also work but are not officially supported by us. Best regards, Nino

  • Hi, Thank you for the flowers We always try to listen, we just can't promise always to add something right away as our resources have to be planned accordingly. But great to hear that you like it. Happy Debugging! Best regards, Nino