Saturday, April 21st 2018, 3:35pm UTC+2

You are not logged in.

  • Login
  • Register


Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Message information
Automatically converts internet addresses into links by adding [url] and [/url] around them.
Smiley code in your message such as :) is automatically displayed as image.
You can use BBCode to format your message, if this option is enabled.
Security measure

Please enter the letters that are shown in the picture below (without spaces, and upper or lower case can be used).

The last 2 posts

Friday, April 13th 2018, 5:10pm

by SEGGER - Nino


Thank you for your inquiry.


Am I supposed to specifically enable these specific events?

All needed information can be found in the SystemView user manual.

Best regards,

Thursday, March 1st 2018, 9:25pm

by txpomeroy

uC/OS-II Q, MBOX, Mutex and other events not recorded

I'm using instrumented uC/OS-II core and am viewing task and ISR entry and exits as expected. However, I'm not seeing entry/exit events for mutexes, mboxes, queues or other RTOS resources. I see the RTOS is instrumented to trace these issues but I don't see anything in SystemView. Am I supposed to specifically enable these specific events?

Also, does anyone have an example where they used the user event recording? We have a macro for entering and exiting a critical section (ie, disable/enable interrupts) and I'd like SystemView to analyze these entry/exit functions. My intent is to be able to analyze worst case critical section duration.