fh_loader 19.06.10.18.44命令行参数

Base Version: 19.06.10.18.44
Binary build date: Jun 25 2019 @ 03:16:10
Incremental Build version: 19.06.25.03.16.10

benchmarkdigestperformance      getstorageinfo=                 reset
benchmarkreads                  json_in=                        search_path=
benchmarkwrites                 labels=                         sectorsizeinbytes=
createdigests                   loglevel=                       sendimage=
chaineddigests=                 lun=                            sendxml=
contentsxml=                    mainoutputdir=                  setactivepartition=
convertprogram2read             maxpayloadsizeinbytes=          showpercentagecomplete
digestsperfilename=             memoryname=                     signeddigests=
erase=                          notfiles=                       start_sector=
files=                          notlabels=                      verbose
firmwarewrite                   nop                             verify_programming_getsha
fixgpt=                         noprompt                        verify_programming
flattenbuildto=                 num_sectors=                    zlpawarehost=
flavor=                         port=
forcecontentsxmlpaths           porttracename=

Debugging

By default --loglevel=1. This is a decent amount of logging for debugging.
           --loglevel=2. This shows more information such as RAW packets being sent.
           --loglevel=3. This is very verbose, showing every byte in a HEX editor view that is sent/received.
           --loglevel=0. Turns off nearly all logging.
           --createdigests
Usage:
fh_loader.exe --port=\\.\COM19 --sendimage=AnyFile.bin --search_path=c:\builds\Perforce_main\core\storage\tools\ --noprompt
fh_loader.exe --port=\\.\COM19 --sendxml=rawprogram0.xml --search_path=c:\builds\Perforce_main\core\storage\tools\
fh_loader.exe --port=\\.\COM19 --sendxml=rawprogram0.xml --search_path=c:\builds\Perforce_main\core\storage\tools\ --loglevel=2

ARGUMENTS
--json_in=  A text file or json formatted file with the following format
==== FILE START ====
{
  "partition_patch": [
    "\\PAHT_TO_PATCH\patch0.xml",
  ],
  "partition": [
    "\\PAHT_TO_RAWPROGRAM\rawprogram0.xml",
    "\\PAHT_TO_RAWPROGRAM\rawprogram1.xml",
  ],
  "partition_bin": [
    "\\PATH_TO_BINARIESsnowcone\file1.elf",
    "\\PATH_TO_BINARIESsnowcone\file2.elf",
  ]
}
==== FILE END ====

  This file can be generated using meta_cli.py in the metabuild, for example:
    <meta_path>\common\build\app\meta_cli.py get_partition_files flavor='asic' group=True storage='ufs'