Yes and no, rather depends what you're trying to get out of it. You can certainly link in the segger systemview library with your source using the softdevice, you can even do it if you have an RTOS running and you can also use an instrumented version of the RTOS (see the segger docs) and capture lots of information about that. SystemView in the end just uses RTT which is a simple memory buffer constantly read by the Segger.
However none of the calls into the softdevice will be instrumented because the SD isn't and nothing will call the SystemView hooks to provide any useful information. I suppose if you were feeling very creative you could replace the interrupt handler table with one of your own which calls the segger start/end functions and then forwards on to the usual place. That's not a job for the faint of heart however.
Yes and no, rather depends what you're trying to get out of it. You can certainly link in the segger systemview library with your source using the softdevice, you can even do it if you have an RTOS running and you can also use an instrumented version of the RTOS (see the segger docs) and capture lots of information about that. SystemView in the end just uses RTT which is a simple memory buffer constantly read by the Segger.
However none of the calls into the softdevice will be instrumented because the SD isn't and nothing will call the SystemView hooks to provide any useful information. I suppose if you were feeling very creative you could replace the interrupt handler table with one of your own which calls the segger start/end functions and then forwards on to the usual place. That's not a job for the faint of heart however.
Would be great if Nordic could add an official support for a such tool. I would be interested in monitor the events generated by the SoftDevice and the time it uses.
