Search Results

Hi Lukasz, Could you update to the latest version of SystemView? There the code is correct. Which version are you using? Best regards Johannes

Hi, You can check the address of _SEGGER_RTT with your debugger/IDE. Best regards Johannes

Hi Aart, Usually all messages should be printed in the terminal. Do you get overflow events? Could you update to the latest version of SystemView, V2.40 and check if the issue still exists? If the issue still exists, could you provide a recording which shows the issue? Best regards Johannes

Hi Torsten, This does not look correct. Can you give some more information about your system, so we can try to reproduce it? Which Linux distribution do you use? Best regards Johannes

Hi, With Embedded Studio V3 and the support for external toolchains the project importer has changed. Since the "Project Template Chooser" is not used, you currently need to add the support files manually to your project. The files (startup, vectors, memory map, registers, system source and header) can be found in the nRF support package. Create a new project for your device and copy the files from this project, or copy them from the package source at C:\Users\<User>\AppData\Local\SEGGER\SEGGER …

Hi, Can you provide your Ozone project file and any commands you entered manually, so we can check what might go wrong here? Best regards Johannes

Hello Eric, Thanks for the report, we will fix the disassembly with the next update. Best regards Johannes

Hi, Thanks for the "flowers" The definition of task states can be configured in the description file, i.e. SYSVIEW_FreeRTOS.txt in the SystemView installation directory. If no task states are configured SystemView uses following default states, derived from the embOS task states: Source Code (15 lines) For the Task State description have a look at the SystemView manual, chapter 10.1.5.2 Best regards Johannes

Hi, To be able to connect to the XMC4500 J-Link has to do a reset of the device. Does SystemView work when you let it run after it hit the breakpoint in the reset handler? To work around this when a debugger (i.e. DAVE) is already attached to the target, you can in SystemView configure the device as Cortex-M4 and add the RTT Control Block search address manually. Then J-Link should be able to do the second connection to the device without a reset. Best regards Johannes

Hi, To restore the settings you can remove the .ini file for your SystemView version from %APPDATA%\SEGGER, e.g. C:\Users\Johannes\AppData\Roaming\SEGGER\SEGGER SystemView V2.40.ini We will also improve SystemView to make sure it is visible on startup. Best regards Johannes

Hi Lukasz, TIMER_ENTER should be called when the timer expired and its handler is called. TIMER_EXIT is then called when the handler returns. So the timer Id is required only for TIMER_ENTER, since on TIMER_EXIT SystemView knows that this must correspond to the last timer entered. IDs 0-31 are internal and cannot be modified. Best regards Johannes

Hi, Since all your environments should be identical, I would expect the same behavior on all of them. Did you try with an STM32 which has proved to be working on one of the other machines? What happens when you simply select "USB" without a serial number as the connection? Best regards Johannes

Hi, Currently you can go through the functions window and search for the range which covers the register value, or you use the disassembly window to go to the address and from there you can go to the source if it is available. We will also add the possibility to locate the register value in memory, disassembly, and source via the context menu in the registers window in a future version. Best regards Johannes

Hi, The 32-bit timestamp limitation has been lifted in the latest release V2.20. Best regards Johannes

Hello Rene, RTT Viewer does no explicit reset, but in some cases it is necessary that J-Link does a reset in order to be able to connect to the target. Which target device do you use? Do you use RTT Viewer in parallel to a debugger or stand-alone? Best regards Johannes

For GCC/LLVM you need to set the attribute packed to the struct or union. struct __attribute__ ((__packed__)) my_packed_struct To make it compiler independent you would need to wrap this with pre-processor macros based on the toolchain defines. Regards Johannes

Hi, In general Embedded Studio supports all ARM devices. The Support Packages only add extra files like specific system initialization or peripheral vectors. Without a Support Package you can always choose to create "A C/C++ executable for a Cortex-M processor" or "A C/C++ executable for a ARM/Cortex-A/R processor", which sets up a generic project where you can add your system initialization and all other required files. Best regards Johannes

Quote: “ What is the recommended way to point to the correct libraries? ” You can set the libraries in the Project Options -> Linker -> Library. Regards Johannes

You can add "A project for running a custom build when files have changed" to your solution, set up to run the python script, creating the source files which are included in your application project. Best regards Johannes

Hi, When "Read Recorded Data" works, live recording should also work. Could you make sure to select the correct device in the configuration dialog and alternatively also set the address of the Control Block manually? Regards Johannes