Flash and run an ELF program

Usage: probe-rs run [OPTIONS] <PATH>

Arguments:
  <PATH>
          The path to the ELF file to flash and run

Options:
      --always-print-stacktrace
          Always print the stacktrace on ctrl + c

      --no-location
          Suppress filename and line number information from the rtt log

      --log-format <LOG_FORMAT>
          The default format string to use for decoding defmt logs

      --rtt-scan-memory
          Scan the memory to find the RTT control block

  -h, --help
          Print help (see a summary with '-h')

RUN OPTIONS:
      --catch-reset
          Enable reset vector catch if its supported on the target

      --catch-hardfault
          Enable hardfault vector catch if its supported on the target

DOWNLOAD CONFIGURATION:
      --disable-progressbars
          

      --disable-double-buffering
          Use this flag to disable double-buffering when downloading flash data. If download fails during programming with timeout errors, try this option

      --restore-unwritten
          Enable this flag to restore all bytes erased in the sector erase but not overwritten by any page

      --flash-layout <filename>
          Requests the flash builder to output the layout into the given file in SVG format

      --verify
          After flashing, read back all the flashed data to verify it has been written correctly

      --binary-format <BINARY_FORMAT>
          If a format is provided, use it. If a target has a preferred format, we use that. Finally, if neither of the above cases are true, we default to ELF

      --base-address <BASE_ADDRESS>
          The address in memory where the binary will be put at. This is only considered when `bin` is selected as the format

      --skip <SKIP>
          The number of bytes to skip at the start of the binary file. This is only considered when `bin` is selected as the format
          
          [default: 0]

      --idf-bootloader <IDF_BOOTLOADER>
          The idf bootloader path

      --idf-partition-table <IDF_PARTITION_TABLE>
          The idf partition table path

      --chip-erase
          Whether to erase the entire chip before downloading

PROBE CONFIGURATION:
      --chip <CHIP>
          [env: PROBE_RS_CHIP=]

      --chip-description-path <chip description file path>
          [env: PROBE_RS_CHIP_DESCRIPTION_PATH=]

      --protocol <PROTOCOL>
          Protocol used to connect to chip. Possible options: [swd, jtag]
          
          [env: PROBE_RS_PROTOCOL=]

      --probe <PROBE>
          Use this flag to select a specific probe in the list.
          
          Use '--probe VID:PID' or '--probe VID:PID:Serial' if you have more than one probe with the same VID:PID.",
          
          [env: PROBE_RS_PROBE=]

      --speed <SPEED>
          The protocol speed in kHz
          
          [env: PROBE_RS_SPEED=]

      --connect-under-reset
          Use this flag to assert the nreset & ntrst pins during attaching the probe to the chip
          
          [env: PROBE_RS_CONNECT_UNDER_RESET=]

      --dry-run
          [env: PROBE_RS_DRY_RUN=]

      --allow-erase-all
          Use this flag to allow all memory, including security keys and 3rd party firmware, to be erased even when it has read-only protection
          
          [env: PROBE_RS_ALLOW_ERASE_ALL=]

LOG CONFIGURATION:
      --log-file <LOG_FILE>
          Location for log file
          
          If no location is specified, the behaviour depends on `--log-to-folder`.

      --log-to-folder
          Enable logging to the default folder. This option is ignored if `--log-file` is specified

Process finished with exit code 0