You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we enable SystemView, it always records events data to buffer since system starts. It may often cause overflow event (especially for bigger systems).
I think we could add additional option in KConfig to let users decide if they want to record events since system start or since host application connects. Thanks to this we wouldn't have to allocate big buffer to store all the data collected by SystemView since system start.
This could be implemented easily - for example function SEGGER_SYSVIEW_Start may be called conditionally based on boolean in KConfig.
The text was updated successfully, but these errors were encountered:
When we enable SystemView, it always records events data to buffer since system starts. It may often cause overflow event (especially for bigger systems).
I think we could add additional option in KConfig to let users decide if they want to record events since system start or since host application connects. Thanks to this we wouldn't have to allocate big buffer to store all the data collected by SystemView since system start.
This could be implemented easily - for example function SEGGER_SYSVIEW_Start may be called conditionally based on boolean in KConfig.
The text was updated successfully, but these errors were encountered: