Currently, if a mount point is provided, the script uses cp to copy over the target binary to the board. Instead, pyocd can be used - this would require modifying the build script to take in the board's target ID instead of passing in the mount point. The target ID of the board is obtained by running mbedls. Another change is to adapt mcuboot.sh to use mbed-tools and to support DISCO_L475VG_IOT01A as a viable target board. The issue, as a whole, involves a bulk of minor changes to the build script's functionality; refer to the requirements below.
Note: Earlier, it had been suggested to use mbedflsh, but this didn't work!
Requirements:
[x] Rename the "say" function to "log"
[x] Update mcuboot.sh to use mbed-tools
[x] Use pyocd to flash the target binary to the board instead of cp (take --flash or -f option)
[x] Add support to accept the disco board as a viable target option
Currently, if a mount point is provided, the script uses
cpto copy over the target binary to the board. Instead,pyocdcan be used - this would require modifying the build script to take in the board's target ID instead of passing in the mount point. The target ID of the board is obtained by runningmbedls. Another change is to adaptmcuboot.shto usembed-toolsand to supportDISCO_L475VG_IOT01Aas a viable target board. The issue, as a whole, involves a bulk of minor changes to the build script's functionality; refer to the requirements below.Requirements:
mcuboot.shto use mbed-toolspyocdto flash the target binary to the board instead ofcp(take --flash or -f option)Associated branch:
script-updates