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. Quote from tipeter: “Is there a solution to using the segger linker and the external gnu tool chain together? ” Yes. You can specify which tool to use with project options under External Build. There you can find Link Command where you can call the SEGGER Linker if you like to. Quote from tipeter: “If there is no other solution, how can I make the "Memory Usage" window work using an external toolchain? ” This is currently not supported. If you want to use all f…

  • Hello, Thank you for your inquiry. To implement something like this we would need to keep the complete timeline recording since start and analyze it on the go. Unfortunately such live analysis would not be viable in most cases as such trace recording would ramp up to a couple GB in size in just a couple of seconds while more data is pouring in from the target. What could work is to dump the data in some file and start analysis after the recording is complete. However this would only be viable fo…

  • Hello Karsten, Thank you for your inquriy. AArch64 support is currently not available in Embedded Studio and is on our low priority list at the moment. First the J-Link would have to support the iMX8 series completely before it makes sense for ES to implement support. As Cortex-A53 is not our core business as most users running an Linux on them which is used for debugging instead of an external debug probe (like the J-Link) we do not have a fixed time schedule. Furthermore, the devices are reall…

  • Hello, We currently have no other user pending with such issue so it is most likely it is related to your particular project setup. Could you provide an example project for reproduction on an evaluation board? Best regards, Nino

  • Hi, Thank you for your explanation. I will send you the CL option for this via PM in this forum. Best regards, Nino

  • Hello Nick, Thank you for your inquiry. When using the GNU Linker you should see for all sections __start and __stop variables in the map file. You can find the .map file in the Output Files folder in the Project Explorer. There you should also find __non_init_start__. This is a pointer that points to the start of the non_init section. To use it in code you first have to declare it: C Source Code (1 line) and then you can use it e.g. in a printf(). C Source Code (1 line)I hope this helps. Best r…

  • 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: wiki.segger.com/Read-Modify-Write_Flash 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: segger.com/downloads/jlink/ 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. segger.com/evaluate-our-s…

  • 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: segger.com/downloads/embedded-studio/ 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…