Before we hand over a session to the user, execute an ./em100 -l on the controller to confirm both devices report available. If not available, fix issue before handoff to the customer (see #3)
Once FW has been loaded into the emulator by the user, do not allow or perform a different FW load without killing the currently running process and making sure everything is "cleaned up". Need to determine all the emulator cleanup steps that should be taken before we start a new process with the new FW.
Need an automatic and customer initiated rescue process that allows reset of the emulators should they manage to get in an unresponsive state.
In no particular order