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, Sorry for the delay in response. There have indeed been changes to the RTL implementation here for the STD I/O. As the error message suggests you need to supply an implementation of __SEGGER_RTL_X_file_write now. This has been addressed in the documentation here: wiki.segger.com/Embedded_Studio_Library_IO#STD Best regards, Nino

  • Hi Detlef, Why would you use an older J-Link version when the one with the fix is already released? Could you try the following? - Power cycle the J-Link. - Open J-Link Commander from the V7.52a release - Accept the FW update Does the J-Link function now? Best regards, Nino

  • Hi Detlef, Thank you for clarifying. Indeed there seems to be an issue with J-Link Ultra/Pro V4.3 and the last update. We are currently working on a fix and a patched release is planned later today. Sorry for any inconveniences caused. To get an automatic notification when the release is available you can subscribe here: segger.com/notification/subscribe.php?prodid=7 Should the FW update from the new release not fix this issue could you open a support ticket as explained in my signature? As a ge…

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you provide your J-Links serial number for reference? Best regards, Nino

  • Hello, Thank you for your inquiry. The error message comes from the llvm.h file. It does not seem to be written to support Cortex-M33 targets. So you have to make sure that the files you add to your project actually work and compile for Cortex-M33 architecture. Somewhere in that file you will find an #ifdef construct where actions/macros for the different architectures and for Arch v8M there probably wont be one but instead this error message. So either implement that same action for v8M or use …

  • Hello, As you contacted us via the support system in parallel and the question has been answered there already, this thread will be closed now. To clarify for other forum users, the supplied elf file is not an executable so the error message is correct. You have to build your application so it is an executable. The supplied elf file is a Shared Object File instead, which might work on e.g. a fully booted Linux System, but will not work on the majority of embedded target device setups. As Ozone i…

  • Hello, Thank you for your inquiry. How do you set the library in your project? Are there any additional library header files that need to be taken account of? If yes, did you make sure their path is set in user include directories? Best regards, Nino

  • Hello Manish, Thank you for your inquiry. What do you mean with windows simulator, could you elaborate? For SystemView to work you need a J-Link and target hardware that is supported by J-Link. Not sure how you plan on simulating our debug probe. Best regards, Nino

  • Hello, Did you read the provided Wiki article? Did you download the provided example project? It was made with FreeRTOS V10.4.3. It was tested and works. If you follow the steps and your resulting project looks like the example project SystemView will work with FreeRTOS V10.4 and on. Best regards, Nino

  • Hello, Thank you for your inquiry. This is expected behaviour as control over the device is only given during the debug session. When leaving the debug session we leave the application running to enable setups where you would attach to certain code parts for example, but do not want to impact the applications behaviour after leaving the debug session. But for some other cases it might be useful/important to halt after ending the debug session. For that we have the exec command SetRestartOnClose.…

  • Hi, Quote from xtrem: “- This is the schematic of the JTAG connector of my board ” On first glance looks correct. Quote from xtrem: “- What version of J-Link EDU includes/works with license SFL ? ” All of them. Quote from xtrem: “- These are the sellers I asked: ” From the screenshot they look genuine. If you are unsure feel free to open a new thread after you receive them with pictures from the front and back. Best regards, Nino

  • Hello Kevin, Thank you for your inquiry. This is indeed a display bug in SystemView and will be fixed with the next verison. To get notified when the release is available you can subscribe here: segger.com/notification/subscribe.php?prodid=7,204 Best regards, Nino

  • Hello, Thank you for your inquiry. The guide for the SystemView integration is pretty straightforward: wiki.segger.com/FreeRTOS_with_…View#System_Configuration We recommend to use the example projects from the Wiki for reference. If your project setup looks different than the example project after following all steps then the guide was not followed correctly or the base FreeRTOS file setup used in your project is not the one that is officially shipped by FreeRTOS. Best regards, Nino

  • Hello, Thank you for your inquiry. Most likely the patch file does not fit the folder structure used in your project. In that case we recommend to patch manually without a patching tool. There are not that many changes necessary. Quote from faulkner: “Also to confirm, the SystemView source files being referred to in the Wiki page include SEGGER_SYSVIEW_FreeRTOS.h & SEGGER_SYSVIEW_FreeRTOS.c, yes? ” Yes. See the example project for reference. Best regards, Nino

  • Hi, Thank you for your inquiry. Not all FreeRTOS versions are backwards compatible. So it is possible that if you update your FreeRTOS Sources SystemView will no longer work. Which is why we supply different patch files for different FreeRTOS versions. A Guide with the patch files can be found here: wiki.segger.com/FreeRTOS_with_…View#System_Configuration Best regards, Nino

  • Hi, Generally a build and debug (F7+F5) is the right approach if you change only a source file or similar. But if you are changing project settings, include paths, other linker related changes, then we recommend a Rebuild (Alt+F7). Quote from MUETA: “So far my "debug search paths" are defined as follows: ” Where do you define them exactly? Make sure they are set as user include directories, not anywhere else. Quote from MUETA: “OK, when I go to the main.c and check the included file, namely righ…

  • Ozone remote debugging

    SEGGER - Nino - - Ozone related

    Post

    Hello, Thank you for your inquiry. The error message usually indicates that a J-Link feature is utilized that is not implemented for remote server yet. Could you provide some additional info of your setup? What is the S/N of your J-Link? With what parameters do you start the Remote Server and with what parameters to you connect with Ozone to it? Does the error happen directly after connect or after you enable some specific debug feature or similar? Is the issue reproducible consistently, if yes …

  • Hello, Thank you for your inquiry. How are you adding the svd file to your project exactly? Could you share your .jdebug file that you try to reopen for reference? Best regards, Nino

  • Hello, Thank you for your inquiry. Was this working for you with Ozone V3.2x versions? What target device are you debugging exactly? Could you provide a reproduction project for an eval board that would run out of the box + reproduction steps? Best regards, Nino

  • Hello, We received this inquiry via our support system in parallel so this thread will be closed now. The solution was that the target application was using a __WFI instruction during debug which caused this issue. Generally we do not recommend to try to debug low power modes if possible to avoid such follow up issues. For more information see here: wiki.segger.com/UM08001_J-Link…Guide#Low_Power_Debugging Best regards, Nino