The virtual firmware game plan
Issue 4: When dealing with critical issues or problems, the client or the team may not feel that you give it the sense of urgency it needs.
Game plan: Virtual meetings are now old hat. There are so many tools out there, it's ridiculous!
Issue 5: How the heck do you troubleshoot and debug remotely?
Game plan: Troubleshooting and remote debugging? No big thing! Gang, we're bit heads and I think we can figure this one out. Yes the bandwidth could be better but with screen sharing and a dedicated PC at the client site or even for the remote team, we can handle this. But what if we need to say make or break an electrical connection remotely? What if some physical action like plugging in something is necessary. All can be done simply from the dedicated PC either by remotely programming the MCU to toggle some control bits to turn on/off relays or by a pre-made control board with a USB connection that does the same thing. That and screen sharing to get you access to the IDE and the debugger, and you're done. Does this handle all cases? Can we be completely hands-free with ease? Not always but often.
Loading comments... Write a comment