Friday, May 25th 2018, 5:30am 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.



Date of registration: Mar 24th 2017

Posts: 2


Friday, March 24th 2017, 5:42pm

Guidance on adding / using custom events

I've been experimenting with add my own event module with SystemView 2.42 and FreeRTOS

I'm looking for some usage guidance

* How can I filter to only show my new events (so I can see general high level code flow without getting bogged down in OS level events)? I had tried filtering by User events, but nothing shows up, so events added by RegisterModule() aren't considered User Events. I've not seen any reference to User events in the documentation at all, so I'm not sure how/if they can be used. Is there a way to filter to specific modules after a log has been collected?

* I have added M=MyModule description to the module registration, but it never obviously shows up in the GUI

C/C++ Source code

	"M=MyModule, " \
	"0 WP_EVENT_Post Event=%u arg0=%u arg1=%u, " \
	"1 WP_EVENT_Receive Event=%u arg0=%u arg1=%u res=%u", // sModule
	0,	// Offset - set by SEGGER_SYSVIEW_Register_Module()
	NULL  // pNext - set by SEGGER_SYSVIEW_Register_Module()

* If I add additional registration info, such as T= or S=, then the additional text is treated as the first event's format string. That makes some sense as its a comma separated string, although the documentation suggests I can add multiple module description info. However, it doesn't (obviously) show up in the the GUI

e.g. "M=MyModule,T=MM, " \

Is the answer that I need to add a ...ModuleName.txt file? I'm seeing a log report about that.



SEGGER - Johannes

Super Moderator

Date of registration: Aug 31st 2012

Posts: 379


Wednesday, June 21st 2017, 4:55pm


Sorry for the delay in response.

Filter on specific API events from the OS or other modules can now be set with SystemView PRO.
Otherwise it is only possible to show all or no API functions at all.

The module description looks correct so far. In addition to M=<ModuleName> you can optionally add V=<VersionNumber>, other parameters are not supported.

With module name and version number it is possible to load a description file to not need to describe all functions in the module description (and save some memory).
To do this, place a file SYSVIEW_<ModuleName>_<VersionNumber>.txt or SYSVIEW_<ModuleName>.txt in /description/ of the SystemView installation directory.

With the current version of SystemView, the registered modules also show up in the System Information, so there you can check that registration worked.

Best regards