Version including the additional command-line argument used to decide whether to drain the incoming uart data (like boot logs and any possible "garbage" logs that come before doing actual driver-involved communication with the board) . Up to this version these logs are handled not really well, as the device waits 2 seconds upon powering up and then sends a synchronization marker to inidicate start of driver control-related communications. That's why if we run the driver as soon as the cam get's connected, we should call it as ucd /dev/ttyUSBX X 1 indicating we are reading the incoming serial data and waiting for the synchronization marker. Otherwise if 2 seconds have already elapsed and the driver wasn't running, then we can run the driver using ucd /dev/ttyUSBX X 0 so that we aren't waiting for a sync marker which won't come.