The Twilio CLI Microvisor Plugin

apps

The apps command provides the following sub-commands:

• bundle — Build an application bundle that can be uploaded. It has two required arguments:

  twilio microvisor:apps:bundle /path/to/bin path/to/bundle/zip

  The latter is the path at which the bundle will be created: the path you will subsequently pass into the create call as shown below.
  
  If you are using remote debugging, include the debugging public key with the --debug-auth-pubkey switch as follows:

  twilio microvisor:apps:bundle /path/to/bin /path/to/bundle/zip \
    --debug-auth-pubkey=/path/to/public/key/pem

  You can generate a suitable private-public key pair with the debug:generate_keypair sub-command.

• create — Upload an application bundle. It takes as its argument a path to the application bundle to upload:
  

  twilio microvisor:apps:create /path/to/bundle/zip

  
  If you specify a path that doesn’t reach a bundle file, or the uploaded file is not a bundle, an error will be thrown.
  
  Optionally, you may also provide a unique friendly name to help you locate and reference the bundle in future.:
  

  twilio microvisor:apps:create /path/to/app/bundle <OPTIONAL_UNIQUE_NAME>

debug

The debug command takes a device SID and a path to a remote debugging private key as its arguments. For more information on why this key is required and how it is generated, please see Microvisor Remote Debugging.

twilio microvisor:debug $MV_DEVICE_SID /path/to/private/key/pem

Your call may also include the --listen-port flag, which is used to select the port through which debugging data will flow.

twilio microvisor:debug $MV_DEVICE_SID /path/to/private/key/pem \
  --listen-port=<PORT_NUMBER>

The default port is 8001. If you specify an alternative port number, you will need to update your .gdbinit file or run the command

target remote localhost:<PORT_NUMBER>

within gdb.

It also has the following sub-commands:

• generate_keypair — Generate private and public remote debugging encryption keys. It takes two arguments: paths to where the generated private and public keys shold be stored:

  twilio microvisor:debug:generate_keypair \
    --debug-auth-privkey=/path/to/private/key/pem \
    --debug-auth-pubkey=/path/to/public/key/pem​

  If you don’t provide either or both key paths, your current working directory will be used.

deploy

This command provides a streamlined application build and deploy flow based on the standard Microvisor CMake-based workflow. It has no sub-commands, but takes the path to a CMake project directory (i.e., the directory containing the root CMakeLists.txt file) as a required argument.

The --devicesid switch is mandatory in cases where a deploy will take place, i.e., the call is made without the -b flag. It takes as a value the SID of the device you wish to deploy code to.

The deploy command also provides the following optional flags and switches:

• -b, --build — Build without deploying.

• -c, --clean — Clean the build folder first.

• -d, --deploy — Deploy the most recent build without rebuilding.

• --genkeys — Generate remote debugging key.

• --privatekey=<value> — Path to your private key. Default: none.

• --publickey=<value> — Path to your public key. Default: none.

• --log — Start logging after a deploy and/or build.

• --logonly — Start logging immediately without building or deploying.

Examples

Build and deploy the app in the working directory:

twilio microvisor:deploy . --devicesid $MV_DEVICE_SID

Build and deploy the app in the working directory, adding remote debugging keys, and initiating logging immediately:

twilio microvisor:deploy . --devicesid $MV_DEVICE_SID --genkeys --log

Build and deploy the app in the working directory, using pre-existingh remote debugging keys:

twilio microvisor:deploy . --devicesid $MV_DEVICE_SID \
  --publickey ~/rdkeys/pukey.pem \
  --privatekey ~/rdkeys/pvkey.pem

Just build the current code:

twilio microvisor:deploy . --build

info

To use these commands, connect a USB Micro A cable between your computer and, for example, the Nucleo Development Board’s CONTROL port, then press the board’s RESET button. The board’s SYSTEM LED will turn solid blue and your application will halt.

The info command provides the following sub-commands, all of which require you to pass the Unix path to the device file, e.g., /dev/tty.usbmodem14244401 or /dev/ttyACM0.

If you are using Windows, replace /path/to/device in the following sub-commands with the COM port, e.g., COM7. See the wificonfig:ports sub-command, below, for more information.

• sid — Display the connected device’s SID.

  twilio microvisor:info:sid /dev/cu.usbmodem14101
  Device SID: UVxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx​

• version — Display the version of Microvisor installed on the connected device.

  twilio microvisor:info:version /dev/cu.usbmodem14101
  Microvisor version: 0.5.1
  Build date: Tue Mar  7 12:39:36 2023​

logs

The logs command provides the following sub-commands:

• stream — Initiate log streaming. It takes as its argument a device SID — the Microvisor-enabled device from which you wish to receive log messages:
  

  twilio microvisor:logs:stream $MV_DEVICE_SID

  If you specify a device that isn’t associated with your account, an Unknown device SID error will be thrown.
  
  Your call may also include the -o flag, which is used to output log messages either in plain text (the default) or in JSON format:

  twilio microvisor:logs:stream $MV_DEVICE_SID -o=json​

  If you select JSON output, you can pipe the output of the command through the JQ utility to present the JSON in a more reader-friendly form:

  twilio microvisor:logs:stream $MV_DEVICE_SID -o=json​ | jq

  The contents of the JSON payload are described below. The plain text output is the value of a message object’s message property.

wificonfig

The wificonfig command provides tools to allow you to get, set, and clear WiFi credentials stored on a Microvisor device.

To use these commands, connect a USB Micro A cable between your computer and, for example, the Nucleo Development Board’s CONTROL port, then press the board’s RESET button. The board’s SYSTEM LED will turn solid blue and your application will halt.

The wificonfig command has the following sub-commands, all of which require you to pass the Unix path to the device file, e.g., /dev/tty.usbmodem14244401 or /dev/ttyACM0.

If you are using Windows, replace /path/to/device in the following sub-commands with the COM port, e.g., COM7. See the ports sub-command, below, for more information.

• get — Get and display the current WiFi credentials.
  

  twilio microvisor:wificonfig:get /path/to/device​

• set — Set the device’s WiFi credentials, passed as follows:
  

  twilio microvisor:wificonfig:set <SSID> <PASSWORD> /path/to/device​

• clear — Clear any WiFi credentials stored on the device.
  

  twilio microvisor:wificonfig:clear /path/to/device​

There is an additional sub-command which does not require a device path or any other argument. Indeed it is intended to help you locate your connected Microvisor device by listing the serial devices currently connected to your computer:

• ports — List currently available device paths:
  Linux
  

  $ twilio microvisor:wificonfig:ports
  Available ports on your computer:
  1. /dev/ttyACM0

  
  macOS
  

  $ twilio microvisor:wificonfig:ports
  Available ports on your computer:
  1. /dev/tty.usbmodem14244401

  
  Windows
  

  C:\Users\user>twilio microvisor:wificonfig:ports
  Available ports on your computer:
  1. COM1
  2. COM4