Search Results
Search results 141-160 of 386.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi, HardFaults/Resets are most commonly caused by stack overflows. SystemView may need ~200 Bytes on the stack. Make sure enough stack is available in every context (Task, Interrupt, Scheduler) which can create SystemView events. Best regards Johannes
-
Hello, You can use the Low Frequency RTC for the SystemView tiemstamps as well. Just make sure your configuration is correct and you provide a SEGGER_SYSVIEW_X_GetTimestamp() or alike which generates the timestamp from the RTC. IRQs cannot be recorded automatically, if the IRQ handlers do not call a generic function, i.e. Enter/Leave_Interrupt(), yet, all of them need to be instrumented. If the application sends accurate information when it idle and when it is executing, you will see the load in…
-
Hi, The DebugIO functions (e.g. debug_printf) use the configurable library functions in Embedded Studio for I/O. The library configuration can be Breakpoint (Semihosting), DCC or Memory Poll. The RTT file override printf directly to print via RTT, which is faster and does not affect the target system. It is recommended to use RTT instead of other I/O mechanisms on all Cortex-M devices. Regards Johannes
-
Hi, The links on the Dashboard will be fixed with the upcoming version. In the meantime you can select Tools -> Installed Packages, Select your package and there you will find the sample solutions as well. Regards Johannes
-
Hi, On one hand you can start GDB Server with the command line options -noir which will prevent GDB Server from setting all registers to 0, so you can attach to your application. On the other hand writing the PC is done by GDB, not by GDB Server, after it downloaded the application. It looks like you call "load" or "load <FileName>" somewhere in GDB, which loads the application to the target and when GDB does this it automatically sets the PC to the entry point. To avoid the download and load th…
-
Then continuously recording is not supported on your device, since it does not allow to access memory while the target is running. In general this is only possible on Cortex-M, Renesas RX, and some Cortex-A devices. The difference between read data and start recording is, that with read data the target is halted and the data is read only once. Best regards Johannes
-
"DEBUG=1" is usually defined in the Debug configuration of the solution. You can either change it there or undefine it in another configuration. Best regards Johannes
-
Did I get this correct: You included SystemView in your project but did not start the SystemView app on the host, but your application crashes? When the SystemView app is not connected and recording is not started explicitly, SystemView basically does nothing but discarding the event and checking for an incoming packet. When SystemView is configured to use a static buffer (default) RECORD_END() will simply call SYSVIEW_UNLOCK(). I don't see how this could cause a hard fault. Do you have high pri…
-
Doing printf() via RTT outputs to the RTT Terminal Channel (Buffer 0), SystemView uses a second RTT Channel (i.e. Buffer 1), so those are two different data streams. To get printf-like output in SystemView you need to use the SystemView printf/print functions. You can print to both at the same time, automatic switching is not possible. Best regards Johannes