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

Issue 622153 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Email to this user bounced
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[1758] Install Kevin DVT2 and servo

Project Member Reported by tienchang@chromium.org, Jun 22 2016

Issue description

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

Steps:
  Verify device (asset tag: C050184) 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 (Please comment what the open spot was)
  Run network_WiFi_VerifyRouter
  Run platform_InstallTestImage
  Add to autotest with labels: kevin, board:kevin, pool:wificell, wificell, conductive:False, servo
  Update spreadsheet
  Update wifi_release script (Aashutosh to show you how)
 
Kevin firmware is unstable. Will pick up this bug next week. Potentially get new EVTs.

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

According to Raju, we need to wait for EV2 or EVT3 version for further testing.

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

I just checked with Raju today and Kevin EVT or EVT2 has some issues so we need to wait for Kevin DVT version. 

Comment 4 by jongkyuj@google.com, Aug 12 2016

Returned the Kevin EVT to white cabinet.
Summary: [1758] Install Kevin DVT2 and servo (was: [1758] Install Kevin EVT and servo)
Kevin DVT2 asset (C055950)

Comment 6 by jongkyuj@google.com, Aug 17 2016

Status: Started (was: Assigned)
Switch to dev mode Done
Set gbb_flags for fast boot Done
Install ToT test image Done

Run network_WiFi_VerifyRouter Done
-------------------------------------------------------------------------------------------------------
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter                           [  PASSED  ]
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter [  PASSED  ]
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_149                                                               -45
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_6                                                                 -28
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_149                                                               -73
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_6                                                                 -29
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_149                                                               -47
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6                                                                 -28
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_149                                                               -44
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_6                                                                 -28
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_149                                                               -74
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_6                                                                 -29
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_149                                                               -51
/tmp/test_that_results_1sjPSl/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6                                                                 -27
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Comment 7 by jongkyuj@google.com, Aug 18 2016

Install into open spot (Please comment what the open spot was) Done
android1758-cros-rack2-host2

jongkyuj@jongkyuj0:~$ ping android1758-cros-rack2-host2
PING android1758-cros-rack2-host2.cros.corp.google.com (100.107.126.171) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-171.mtv.corp.google.com (100.107.126.171): icmp_seq=1 ttl=60 time=1.49 ms
64 bytes from dhcp-100-107-126-171.mtv.corp.google.com (100.107.126.171): icmp_seq=2 ttl=60 time=1.28 ms
64 bytes from dhcp-100-107-126-171.mtv.corp.google.com (100.107.126.171): icmp_seq=3 ttl=60 time=1.21 ms

Add servo and servo cable Done


Comment 8 by jongkyuj@google.com, Aug 18 2016

jongkyuj@jongkyuj0:~$ ping android1758-cros-rack2-host2-router
PING android1758-cros-rack2-host2-router.cros.corp.google.com (100.107.126.172) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-172.mtv.corp.google.com (100.107.126.172): icmp_seq=1 ttl=60 time=0.905 ms
64 bytes from dhcp-100-107-126-172.mtv.corp.google.com (100.107.126.172): icmp_seq=2 ttl=60 time=0.929 ms
64 bytes from dhcp-100-107-126-172.mtv.corp.google.com (100.107.126.172): icmp_seq=3 ttl=60 time=0.917 ms
64 bytes from dhcp-100-107-126-172.mtv.corp.google.com (100.107.126.172): icmp_seq=4 ttl=60 time=0.841 ms

Comment 9 by jongkyuj@google.com, Aug 18 2016

Add to autotest with labels: kevin, board:kevin, pool:wificell, wificell, conductive:False, servo Done
Update spreadsheet Done

Status: Fixed (was: Started)
jongkyuj@jongkyuj0:~$ ping android1758-cros-rack2-host2-servo
PING android1758-cros-rack2-host2-servo.cros.corp.google.com (100.107.126.173) 56(84) bytes of data.
64 bytes from dhcp-100-107-126-173.mtv.corp.google.com (100.107.126.173): icmp_seq=1 ttl=60 time=0.677 ms
64 bytes from dhcp-100-107-126-173.mtv.corp.google.com (100.107.126.173): icmp_seq=2 ttl=60 time=0.644 ms
64 bytes from dhcp-100-107-126-173.mtv.corp.google.com (100.107.126.173): icmp_seq=3 ttl=60 time=0.566 ms
64 bytes from dhcp-100-107-126-173.mtv.corp.google.com (100.107.126.173): icmp_seq=4 ttl=60 time=0.660 ms
64 bytes from dhcp-100-107-126-173.mtv.corp.google.com (100.107.126.173): icmp_seq=5 ttl=60 time=0.617 ms

Sign in to add a comment