firmware_FAFTSetup failure: Target servo is not a test lab servo

Martin Yan

unread,

Nov 3, 2017, 1:56:34 PM11/3/17

to faft users

Plan to set up one FAFT test environment on reef reference design board, HW setup is based on https://www.chromium.org/for-testers/faft

Servo v2 (REV: 04) board is used.

Ran following after cros_sdk,

~/trunk/src/scripts $ /usr/bin/test_that --board=reef 192.168.x.x firmware_FAFTSetup

But fails with following main failed & error messages,

INFO | autoserv| Failed: servod service is taking calls

INFO | autoserv| error: [Errno 111] Connection refused

INFO | autoserv| AutoservRepairError: Can't restart servod: not running embedded Chrome OS.

INFO | autoserv| AutoservRepairError: Target servo is not a test lab servo

Also attached “autoserv.DEBUG”, do I miss anything? thanks.

autoserv.DEBUG

Shawn N

unread,

Nov 3, 2017, 2:13:09 PM11/3/17

to Martin Yan, faft users

That looks like an error communicating with servod. Assuming you didn't forget to start servod, please provide the params you're passing to servod and all output from servod.

--
You received this message because you are subscribed to the Google Groups "faft users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+unsubscribe@chromium.org.

Tom Wai-Hong Tam (談偉航)

unread,

Nov 3, 2017, 2:15:51 PM11/3/17

to Martin Yan, faft users

Did you start the servod? like

$ sudo servod --board=$BOARD

What's the port of servod? The port is showed at the last line of the above command, like:

2017-11-01 15:53:52,641 - servod - INFO - Listening on localhost port 9999

The test_that command assumes it is 9999. Other than that, you have to pass some extra

argument to test_that to specify, like --args "servo_port=9999".

On Fri, Nov 3, 2017 at 10:56 AM, Martin Yan <Marti...@microchip.com> wrote:

Martin Yan

unread,

Nov 3, 2017, 3:29:05 PM11/3/17

to faft users, Marti...@microchip.com

Hi Shawn & Wai-Hong.

Thanks your feedbacks! Look like that is root cause.

As following is run after “cros_sdk”

~/trunk/src/scripts $ sudo servod --board=reef

But having error as,

fw88@localhost chromiumos]$ cros_sdk

(cr) ((85217e1...)) fw88@localhost ~/trunk/src/scripts $ sudo servod --board=reef

Traceback (most recent call last):

File "/usr/lib/python-exec/python2.7/servod", line 9, in <module>

load_entry_point('servo===0.0.1-a4cd72a', 'console_scripts', 'servod')()

File "/usr/lib64/python2.7/site-packages/servo/servod.py", line 529, in main

main_function()

File "/usr/lib64/python2.7/site-packages/servo/servod.py", line 435, in main_function

terminal_freezer.CheckForPIDNamespace()

File "/usr/lib64/python2.7/site-packages/servo/terminal_freezer.py", line 24, in CheckForPIDNamespace

raise OSError('You must run this tool in a chroot that was entered'

OSError: You must run this tool in a chroot that was entered with "cros_sdk --no-ns-pid" (see crbug.com/444931 for details)

If I run following after “cros_sdk --no-ns-pid”

~/trunk/src/scripts $ sudo servod --board=reef

It locks at last message, I have to use “ctrl+c” to return to “fw88@localhost ~/trunk/src/scripts $”

Any suggestions? I have to run "cros_sdk --no-ns-pid"?

[fw88@localhost chromiumos]$ cros_sdk --no-ns-pid

(cr) ((85217e1...)) fw88@localhost ~/trunk/src/scripts $ sudo servod --board=reef

2017-11-03 15:04:49,506 - servod - INFO - Start

2017-11-03 15:04:49,670 - servod - INFO - Found servo, vid: 0x18d1 pid: 0x5002 sid: 000000-00149

2017-11-03 15:04:49,672 - servod - INFO - Found XML overlay for board reef

2017-11-03 15:04:49,673 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/servo_v2_r1.xml, None, 0)

2017-11-03 15:04:49,674 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/servo_v2_r0.xml, None, 0)

2017-11-03 15:04:49,691 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/common.xml, None, 0)

2017-11-03 15:04:49,696 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/keyboard.xml, None, 0)

2017-11-03 15:04:49,699 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/uart_common.xml, None, 0)

2017-11-03 15:04:49,734 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/servo_reef_overlay.xml, None, 0)

2017-11-03 15:04:49,736 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/servoflex_v2_r0_p50.xml, None, 0)

2017-11-03 15:04:49,738 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/x86_ec_common.xml, None, 0)

2017-11-03 15:04:49,739 - SystemConfig - INFO - Loading XML config (/usr/lib64/python2.7/site-packages/servo/data/ec_common.xml, None, 0)

2017-11-03 15:04:49,755 - Servod - INFO - Initializing interface 1 to ftdi_uart

2017-11-03 15:04:49,762 - Servod - INFO - /dev/pts/1

2017-11-03 15:04:49,762 - Servod - INFO - Initializing interface 2 to ftdi_i2c

2017-11-03 15:04:49,769 - Servod - INFO - Initializing interface 3 to ftdi_uart

2017-11-03 15:04:49,774 - Servod - INFO - /dev/pts/2

2017-11-03 15:04:49,774 - Servod - INFO - Initializing interface 4 to ftdi_uart

2017-11-03 15:04:49,779 - Servod - INFO - /dev/pts/3

2017-11-03 15:04:49,779 - Servod - INFO - Use the next FTDI part @ pid = 0x5003

2017-11-03 15:04:49,780 - Servod - INFO - Initializing interface 5 to ftdi_dummy

2017-11-03 15:04:49,780 - Servod - INFO - Use the next FTDI part @ pid = 0x5003

2017-11-03 15:04:49,780 - Servod - INFO - Initializing interface 6 to ftdi_dummy

2017-11-03 15:04:49,780 - Servod - INFO - Use the next FTDI part @ pid = 0x5003

2017-11-03 15:04:49,780 - Servod - INFO - Initializing interface 7 to ftdi_uart

2017-11-03 15:04:49,786 - Servod - INFO - /dev/pts/4

2017-11-03 15:04:49,786 - Servod - INFO - Use the next FTDI part @ pid = 0x5003

2017-11-03 15:04:49,786 - Servod - INFO - Initializing interface 8 to ftdi_uart

2017-11-03 15:04:49,791 - Servod - INFO - /dev/pts/5

2017-11-03 15:04:49,791 - Servod - INFO - Initializing interface 9 to ec3po_uart

2017-11-03 15:04:49,791 - Servod - INFO - Initializing interface 10 to ec3po_uart

2017-11-03 15:04:49,805 - EC3PO Interface - INFO - /dev/pts/6

2017-11-03 15:04:49,808 - EC3PO.Console - INFO - /dev/pts/6 - EC Console is being served on /dev/pts/6.

2017-11-03 15:04:49,812 - Servod - INFO - Initialized i2c_mux to rem

2017-11-03 15:04:49,813 - Servod - INFO - Initialized i2c_mux_en to on

2017-11-03 15:04:49,816 - Servod - INFO - Initialized pch_disable to off

2017-11-03 15:04:49,818 - Servod - INFO - Initialized jtag_buf_on_flex_en to off

2017-11-03 15:04:49,819 - Servod - INFO - Initialized cold_reset to off

2017-11-03 15:04:49,821 - Servod - INFO - Initialized warm_reset to off

2017-11-03 15:04:49,822 - Servod - INFO - Initialized spi1_buf_on_flex_en to off

2017-11-03 15:04:49,824 - Servod - INFO - Initialized spi_hold to off

2017-11-03 15:04:49,825 - Servod - INFO - Initialized pwr_button to release

2017-11-03 15:04:51,802 - Servod - INFO - Initialized lid_open to yes

2017-11-03 15:04:51,804 - Servod - INFO - Initialized spi2_buf_on_flex_en to off

2017-11-03 15:04:51,807 - Servod - INFO - Initialized rec_mode to off

2017-11-03 15:04:51,810 - Servod - INFO - Initialized fw_up to off

2017-11-03 15:04:51,811 - Servod - INFO - Initialized uart3_en to on

2017-11-03 15:04:51,813 - Servod - INFO - Initialized dut_hub_pwren to on

2017-11-03 15:04:51,813 - Servod - INFO - Initialized kbd_en to off

2017-11-03 15:04:51,816 - Servod - INFO - Initialized spi1_vref to off

2017-11-03 15:04:51,818 - Servod - INFO - Initialized spi2_vref to off

2017-11-03 15:04:51,819 - Servod - INFO - Initialized uart2_en to on

2017-11-03 15:04:51,821 - Servod - INFO - Initialized uart1_en to on

2017-11-03 15:04:51,822 - Servod - INFO - Initialized jtag_buf_en to off

2017-11-03 15:04:51,824 - Servod - INFO - Initialized fw_wp_en to off

2017-11-03 15:04:51,825 - Servod - INFO - Initialized sd_vref_sel to off

2017-11-03 15:04:51,825 - Servod - INFO - Initialized ec_ec3po_interp_connect to on

2017-11-03 15:04:51,827 - Servod - INFO - Initialized uart3_vref to off

2017-11-03 15:04:51,828 - Servod - INFO - Initialized jtag_vref_sel0 to off

2017-11-03 15:04:51,830 - Servod - INFO - Initialized jtag_vref_sel1 to off

2017-11-03 15:04:51,830 - servod - INFO - Listening on localhost port 9999

^C(cr) ((85217e1...)) fw88@localhost ~/trunk/src/scripts $

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

Tom Wai-Hong Tam (談偉航)

unread,

Nov 3, 2017, 3:50:16 PM11/3/17

to Martin Yan, faft users

Hi Martin,

You should open a separated terminal to run servod in parallel. servod is daemon that the test will do RPC calls to it.

Tom

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+unsubscribe@chromium.org.

Martin Yan

unread,

Nov 3, 2017, 5:27:14 PM11/3/17

to faft users, Marti...@microchip.com

Hi Tom,

Thanks your help! Servo board comm. is good now, I can move to next step...

Regards,

Martin

Tom

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

Reply all

Reply to author

Forward