This scripts allows for a quicker way for users to build and deploy their code to the robot. Instead of a really long mbed-cli command, use is now ./builddeploy [fname] where [fname] is an optional folder name. Without an argument, this script checks for mbed-greentea and if it is installed, will use it to deploy. If not, it will copy the compiled binary to the robot in the default location in the ubuntu filesystem on the lab computers. With an argument, the script ignores mbed-greentea and copies the compiled binary to that folder.
Example use-case for the optional [fname] argument: Windows Subsystem for Linux (WSL) does not support udev, which mbed-greentea uses. Users can mount the robot into the ubuntu filesystem then deploy to it from WSL using this argument.
This scripts allows for a quicker way for users to build and deploy their code to the robot. Instead of a really long
mbed-clicommand, use is now./builddeploy [fname]where[fname]is an optional folder name. Without an argument, this script checks formbed-greenteaand if it is installed, will use it to deploy. If not, it will copy the compiled binary to the robot in the default location in the ubuntu filesystem on the lab computers. With an argument, the script ignoresmbed-greenteaand copies the compiled binary to that folder.Example use-case for the optional
[fname]argument: Windows Subsystem for Linux (WSL) does not supportudev, whichmbed-greenteauses. Users can mount the robot into the ubuntu filesystem then deploy to it from WSL using this argument.