New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 652904 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[1758] Convert DUTs from OTA to conductive setups

Project Member Reported by tienchang@chromium.org, Oct 5 2016

Issue description

The following DUTs are in the PVT/MP phase but still have an OTA setup:
android1758-row4-rack1-host1 Samus
android1758-row4-rack2-host1 Sentry
android1758-row4-rack2-host2 Edgar
android1758-row4-rack5-host2 Heli
android1758-row4-rack6-host3 Elm
android1758-row4-rack8-host3 Minnie
chromeos9-row1-cart3-host6 Sumo

Steps:
  Confirm write-protect is disabled (flashrom -p host --wp-status; flashrom -p ec --wp-status; flashrom -p ec:dev=1 --wp-status (only for Type-C devices))
  Check for servo debug header
  Install servo cable
  Install pigtails
  Verify no firmware screen on boot
  Install factory firmware (chromeos-firmwareupdate --mode=factory)
  Boot test image in dev mode (3 finger, insert USB w/ test image)
  Run chromeos-tpm-recovery to clear TPM; reboot
  Switch to normal mode (/usr/share/vboot/bin/setgbbflags.sh 0)
  Run network_WiFi_VerifyRouter on test-station
  Connect servo and run platform_InstallTestImage on test-station
  Update autotest with labels: conductive:True
  Add brick of power splitters
  Add conductive AP
  Run network_WiFi_VerifyRouter in B1758
  Run platform_InstallTestImage in B1758
  Update spreadsheet (go/wifi-device-life-cycle)
 
Owner: dschimmels@chromium.org
Reassigning to dschimmels@ to pass onto donator@. After these bugs are completed, we can file bugs with Buganizer and assign directly to donator@.
Status: Archived (was: Assigned)

Sign in to add a comment