Tool/software: Linux
Hi,
We are attempting to interface a Raspberry PI running Raspbian Stretch to a board we designed using the TM4C1294 micro through a USB port using the default Virtual Com Driver. On power up, text that our board sends out is being echoed back by the Raspberry PI before the application we are running on the Raspberry PI has a chance to start and turn off the echo. The echoed back text is not recognized by the firmware on our board and it generates an error message that is sent out and also echoed back. If our application does not start soon enough this snowballs and ends up locking up the port. Is there any way to change the default configuration of the Virtual Com Driver so that it will not echo on power up?
We know we could modify our firmware to handle this, however we have already shipped hundreds of units with this board. We will be supplying the Raspberry PI as part of a new add on feature that can be used with these old units and so we are hoping to find a solution that we can implement in the Raspberry PI only.
Thanks,
Scott