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

Issue 622060 link

Starred by 2 users
Status: Verified
Owner:
█ jongkyuj@chromium.org
Email to this user bounced
Closed: Jul 2016
Cc:
█ dschimmels@chromium.org
█ jashur@chromium.org
aashuto...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[1758] Install Relm DVT2 and servo

Project Member Reported by tienchang@chromium.org, Jun 21 2016 
Firmware team will be testing Relm on Friday 6/24. Please hold off installing this DUT until next week when the dust has settled.

Please work with Aashutosh on getting the DUT ready and with Joe on verifying the DUT and servo setup.

Steps:
  Verify device (asset tag: C050852) powers on and boots
  Switch to dev mode
  Set gbb_flags for fast boot
  Install ToT test image
  Add servo and servo cable
  Install into open spot (android1758-row4-rack6-host1)
  Run network_WiFi_VerifyRouter
  Run platform_InstallTestImage
  Add to autotest with labels: relm, board:relm, pool:wificell, wificell, conductive:False, servo
  Update spreadsheet (go/wifi-device-life-cycle)
  Update wifi_release script

Comment 1 by jongkyuj@google.com, Jul 7 2016

Status: Started (was: Assigned)
Verify device (asset tag: C050852) powers on and boots Done
  Switch to dev mode Done
  Set gbb_flags for fast boot Done
  Install ToT test image Done
  Add servo and servo cable Done
Gave it to hardware lab for cutting for servo cable and pigtail.

Comment 2 by jongkyuj@google.com, Jul 8 2016 

Run network_WiFi_VerifyRouter Done


/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter                           [  PASSED  ]
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter [  PASSED  ]
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_149                                                               -59
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_6                                                                 -61
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_149                                                               -50
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_6                                                                 -71
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_149                                                               -57
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6                                                                 -66
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6{1}                                                              -67
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_149                                                               -56
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_6                                                                 -63
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_149                                                               -53
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_6                                                                 -70
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_149                                                               -57
/tmp/test_that_results_76GNpt/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6                                                                 -66
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Comment 3 by jongkyuj@google.com, Jul 12 2016 

android1758-row4-rack6-host1 c0:c1:c0:76:38:8e              
android1758-row4-rack6-host1-servo bc:6a:29:7e:45:6e   
Update spreadsheet (go/wifi-device-life-cycle) Done
Add to autotest with labels: relm, board:relm, pool:wificell, wificell, conductive:False, servo Done

Gave above MAC addresses to Joe for approval.

Comment 4 by jongkyuj@google.com, Jul 13 2016

Status: Fixed (was: Started)
ongkyuj@jongkyuj0:~$ ping android1758-row4-rack6-host1
PING android1758-row4-rack6-host1.cros.corp.google.com (100.107.127.141) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-141.mtv.corp.google.com (100.107.127.141): icmp_seq=1 ttl=60 time=1.15 ms
64 bytes from dhcp-100-107-127-141.mtv.corp.google.com (100.107.127.141): icmp_seq=2 ttl=60 time=0.948 ms
Able to ping both host1 and servo.

64 bytes from dhcp-100-107-127-141.mtv.corp.google.com (100.107.127.141): icmp_seq=3 ttl=60 time=0.535 ms
^C
--- android1758-row4-rack6-host1.cros.corp.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.535/0.878/1.153/0.259 ms
jongkyuj@jongkyuj0:~$ ping android1758-row4-rack6-host1-servo
PING android1758-row4-rack6-host1-servo.cros.corp.google.com (100.107.127.143) 56(84) bytes of data.
64 bytes from dhcp-100-107-127-143.mtv.corp.google.com (100.107.127.143): icmp_seq=1 ttl=60 time=1.20 ms
64 bytes from dhcp-100-107-127-143.mtv.corp.google.com (100.107.127.143): icmp_seq=2 ttl=60 time=0.645 ms

Comment 5 by jongkyuj@google.com, Jul 13 2016

Status: Verified (was: Fixed)
Able to ping host and servo.
►

Sign in to add a comment