futility/update: Assume WP is off for all remote operations
Flashing a remote DUT with `-p raiden_debug_spi` fails when the DUT has
SWWP=1.
This happens because for remote devices, `dut_is_remote` is set, causing
`dut_get_property_int()` to return -1. This return value leads to a
fallback assumption of HWWP=1, and the combination of HWWP=1 and SWWP=1
blocks the operation.
Considering that similar programmers (e.g., --servo, --servo_port,
--ccd_without_servod) unconditionally set `write_protection` override to
0 to mock HWWP=0, SWWP=0, we should strive to ensure that
`dut_is_remote` always implies HWWP=0, SWWP=0. This change implements
this assumption to prevent similar write protection conflicts in the
future.
to assume HWWP=0, we should strive to ensure that
always implies HWWP=0. This change implements this assumption to
prevent similar write protection conflicts in the future.
BUG=b:425419598. b:425867270
TEST=futility --debug gbb -p
'raiden_debug_spi:target=AP,custom_rst=true' --get --flags
now passes.
BRANCH=none
Change-Id: Ia50c6d7a98a4ab019c94f85fe70086972a5ad006
Signed-off-by: Hsuan Ting Chen <roccochen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/6654578
Tested-by: Yu-Ping Wu <yupingso@chromium.org>
Reviewed-by: Yu-Ping Wu <yupingso@chromium.org>
Commit-Queue: Yu-Ping Wu <yupingso@chromium.org>
1 file changed
