hooks: Pass --instance of L4T flash.sh to flash the correct board

This is required when multiple boards may be in recovery mode at once.
This option isn't currently supported by flash.sh; it needs to be patched
in manually...

Signed-off-by: Stephen Warren <swarren@nvidia.com>

test/hooks/bin/flash.recovery_l4t

@@ -30,13 +30,11 @@ done
 sleep 1
 
 cp "${U_BOOT_BUILD_DIR}"/u-boot-dtb.bin "${flash_l4t}/${flash_l4t_uboot_path}/u-boot.bin"
-# FIXME: Need to enhance flash.sh to accept --instance parameter and pass to
-# tegraflash.py. Sigh.
 # FIXME: To speed things up here, we could add "-k kernel" and just reflash the
 # "kernel" partition (which holds U-Boot when it's in use). However, this
 # relies on having the right L4T already flashed, which isn't likely on my
 # system since I use the board for other things.
-(cd "${flash_l4t}" && sudo "${flash_l4t}/flash.sh" -r "${flash_l4t_board}" mmcblk0p1)
+(cd "${flash_l4t}" && sudo "${flash_l4t}/flash.sh" --usb-instance "${board_usb_port_path}" -r "${flash_l4t_board}" mmcblk0p1)
 # Prevent the system from booting before the reset script is run. Otherwise,
 # either (a) the test system won't capture the start of the UART log, or (b)
 # U-Boot will start running early, and the test system will start capturing

test/hooks/bin/swarren-lx1/conf.p2371-2180_na

@@ -39,6 +39,7 @@ recovery_impl=pm342
 nv_board_automation_bin="${HOME}/ubtest-nvidia-board-automation"
 pm342_serial=SRW-0
 board_usb_dev=/dev/usbdev-p2371-2180
+board_usb_port_path=3-13
 
 if [ ${boot_from_cboot} -eq 1 ]; then
   echo conf.p2371-2180_na: U-Boot branch requires flashing for testing

test/hooks/bin/swarren-lx1/conf.p2771-0000-500_na

@@ -29,3 +29,4 @@ reset_impl=pm342
 nv_board_automation_bin="${HOME}/ubtest-nvidia-board-automation"
 pm342_serial=SRW-1
 board_usb_dev=/dev/usbdev-p2771-0000
+board_usb_port_path=3-1