Kevin

I've been waiting for the addition into QHsm, have a design that would benefit by removing quite a bit of duplicated code. I'd put it in the "nice-to-have" category, have been designing great state-machines with QP since 2005 without them. To answer your question directly, no, not used in any current or past projects.

Here's another design approach, you may need to provide more details on the state machines and/or event structures if there is something I am missing. I think the main challenge you are trying to resolve is how to route the response event from the SPI AO to the specific component within the Hub AO? One way I've handled this in the past is with a unique component ID parameter that is provided in every event that is published to the SPI AO. Not sure if using the actual HSM address for the component...

The last qspyview command line parameter in your example specifies the target UDP...

I've attached an image that contains the call stack and annotated 'C stack'. I added...

I do not have anything written up, but I have chosen to not use the Nordic SDK's...

Henry, The SWI2_IRQHandler lives in the SDK/Application, not the SoftDevice code....

Agree, I always use QSpy when possible, but there is only a single UART available...

Agree, I always use QSpy when possible, but there is only a single UART available...