ser2net integration script may generate incorrect configuration
Issue Background
ser2net must be configured to connect to specific device names. The serial device name used to connect to the console of the board under test will vary between systems.
Issue description
The integration script configure_ser2net.sh assumes that the board under test will be attached to /dev/ttyUSB0. This will not always be the case, e.g. on my laptop this corresponds to a 3G modem. Developers might also have multiple boards attached by USB-serial cables for different purposes, or might (on a desktop) use a non-USB serial port.
The setup instructions need to say that the device name may need changing. It might actually be better to document the small number of configuration steps that this script does.
Secondly, it is not safe to run the script multiple times. It will add multiple configuration entries for port 8020.
Acceptance criteria
- Setup instructions mention possible need to change ser2net configuration
- Running configure_ser2net.sh twice leaves only configuration line for port 8020