What is the CubeProgrammer button "Start wireless stack" actually doing and can it be automated?

[A.D.]

Could you shed some light on what the button "start wireless stack" actually does?

1) Is there some flag in flash that has to be set after flashing the wireless stack? Or is it just an option byte or something?

2) Why is this seperate button necessary? It would be easier and less likely to result in long debugging sessions if flashing the stack would automatically start it as well.

3) Can this process be automated via the CubeProgrammer to have a single to click to install and start wireless stack?

[STTwo-32 · Accepted solution]

Hello @A.D. 

At the end of wireless stack installation, FUS is responsible of setting boot on wireless stack. So yes it shall start automatically.

Usually, the reason it may not start (from user perspective), is that some extra FUS_GETSTATE commands would have been sent after the end of the operation and while wireless stack already started. Which makes the wireless stack (at reception of 2 FUS_GETSTATE commands) go back to FUS. 

In this situation we will need to Start the Wireless stack manually using a separated button to go back to wireless stack.

That's why we need to have a separated button for this function.

Best Regards.

STTwo-32

[A.D.]

Hello @STTwo-32 ,

thanks for your answer. I see, this explains the behaviour we have seen.

Can this task also be done by the application firmware?

Say for some reason the stack is not started.  Can I catch this case in my application and somehow set a flag or something to start the stack manually?

[STTwo-32]

Hello @A.D. 

This is a new request. I suggest you to create a new post for this (after closing this post by selecting the solution of your original request as best answer) to give it more visibility on the community.

Best Regards.

STTwo-32