In juno board How to connect the COM/serial ports in WA running env. about workload-automation HOT 22 CLOSED

WA does not support serial as a primary communication channel. For Android on Juno, WA will use adb-over-Ethernet. You just need to specify the IP address and port 5555 as the adb name

device: juno
device_config:
    adb_name: 192.168.0.2:5555

Alternatively, WA can auto-discover the IP address over the serial, which you can get it to do by pointing serial at the serial connection to the Juno

device: juno
device_config:
    port: /dev/ttyUSB0

Note that even in this case, WA will use Ethernet as the communication channel; the serial connection only used to discover the IP address.

from workload-automation.

Hello, setrofim
In juno board Tried your two suggestions one by one in ~/.workload_automation/config.py as followings:
device_config = dict(
# The name used by adb to identify the device. Use "adb devices" in bash to list
# the devices currently seen by adb.
#adb_name: 192.168.0.2:5555 ,
port: /dev/ttyUSB0

but Failed, prompts ,
INFO Connecting to device
CRITICAL Could not boot generic_android (None).
... stopped.

Thanks.

from workload-automation.

Make sure you're specifying the device as "juno", it looks like you're using the default "generic_android", which doesn't know about serial port. Also, please note that my earlier examples were given suing the YAML config syntax. If you're still using the .py config, you will need to translate those to the equivalent Python:

    device = 'juno'
    device_config = dict(
        port='/dev/ttyUSB0',
    )

from workload-automation.

Yes, eg.
Yes, it is modified by your comments.

Try any method but failed yet.

Thanks.

from workload-automation.

If config files, WA running as cmdline:
SPREADTRUM\zhengkun.zuo@zkzubtpc:/usr$ sudo wa run -f ipa_tuning_practical_1_dhystone.yaml -c config_1.py
INFO Removing existing output directory.
INFO Creating output directory.
INFO Initializing
INFO Running workloads
INFO Connecting to device
CRITICAL File "/usr/local/lib/python2.7/dist-packages/wlauto/core/entry_point.py", line 63, in main
CRITICAL sys.exit(command.execute(args))
CRITICAL File "/usr/local/lib/python2.7/dist-packages/wlauto/commands/run.py", line 98, in execute
CRITICAL executor.execute(agenda, selectors={'ids': args.only_run_ids})
CRITICAL File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 342, in execute
CRITICAL runner.run()
CRITICAL File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 480, in run

others error info.

from workload-automation.

Please can you attach (don't paste) the complete run.log and __meta/run_config.json from wa_output. Above you've omitted the actual error.

Also, do not run WA via sudo. To access the serial, either chmod the dev node appropriately, or add the regular user to the dialout group.

from workload-automation.

1. " sudo " opertions should be OK , I used its in some test cases.
2. attachments.

from workload-automation.

Hello,

"Please can you attach (don't paste) the complete run.log and __meta/run_config.json from wa_output. Above you've omitted the actual error."

attachments is:

Thanks.

Best Regards,

Spreadtrum Communications
ext. 6831
MP: 136 836 76439
mailto:[email protected]://www.spreadtrum.comhttp://www.spreadtrum.com/

?件人: setrofim [email protected]
?送??: 2016年7月25日 18:03
收件人: ARM-software/workload-automation
抄送: Zhengkun Zuo (左正坤); Author
主?: Re: [ARM-software/workload-automation] In juno board How to connect the COM/serial ports in WA running env. (#211)

Please can you attach (don't paste) the complete run.log and __meta/run_config.json from wa_output. Above you've omitted the actual error.

Also, do not run WA via sudo. To access the serial, ether chmod the dev node appropriately, or add the regular user to the dialout group.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/211#issuecomment-234912867, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ARNkbDALKUllHrTAUG9G0qaizBskWT4Aks5qZIoKgaJpZM4JT3gT.

from workload-automation.

1. I'm not saying that sudo is related to the current problem. WA may well work when run as root, however it is highly unsafe, and may cause other issues -- just don't do it.
2. It looks like your attachments did not get included. Please could you try attaching via GitHub issue web page, rather than via email.

from workload-automation.

file:///usr/wa_output/run.log
file:///usr/wa_output/__meta/run_config.json

from workload-automation.

Why can't attach them by
"Attach files by dragging & dropping or . "
menu .
But failed , ..
So i emailed them to you .

Thx.

from workload-automation.

2016-07-25 18:31:48,243 DEBUG serial_send:
2016-07-25 18:31:48,343 DEBUG Juno: Waiting for the Android prompt.
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/entry_point.py", line 63, in main
2016-07-25 18:31:48,344 CRITICAL root: sys.exit(command.execute(args))
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/commands/run.py", line 98, in execute
2016-07-25 18:31:48,344 CRITICAL root: executor.execute(agenda, selectors={'ids': args.only_run_ids})
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 342, in execute
2016-07-25 18:31:48,344 CRITICAL root: runner.run()
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 480, in run
2016-07-25 18:31:48,344 CRITICAL root: self._initialize_run()
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 533, in _initialize_run
2016-07-25 18:31:48,344 CRITICAL root: self._connect_to_device()
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 566, in _connect_to_device
2016-07-25 18:31:48,344 CRITICAL root: self.device.connect()
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/devices/android/juno/init.py", line 153, in connect
2016-07-25 18:31:48,344 CRITICAL root: target.expect(self.android_prompt)
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/pexpect/spawnbase.py", line 315, in expect
2016-07-25 18:31:48,344 CRITICAL root: timeout, searchwindowsize, async)
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/pexpect/spawnbase.py", line 339, in expect_list
2016-07-25 18:31:48,344 CRITICAL root: return exp.expect_loop(timeout)
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/pexpect/expect.py", line 102, in expect_loop
2016-07-25 18:31:48,344 CRITICAL root: return self.eof(e)
2016-07-25 18:31:48,344 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/pexpect/expect.py", line 49, in eof
2016-07-25 18:31:48,344 CRITICAL root: raise EOF(msg)
2016-07-25 18:31:48,344 CRITICAL root:
2016-07-25 18:31:48,344 CRITICAL root: EOF(End Of File (EOF). Empty string style platform

from workload-automation.

Please could you confirm that

1. Juno's serial is connected on /dev/ttyUSB0; if not please adjust the setting accordingly in your config
2. Juno is booted into Android and that you are able to access the shell via screen/minicom

Also, there have been issues with the laster versions of pexpect on some systems. It may be worth trying downgrading pexect to v3.3 to see if that resolves the issue

from workload-automation.

Hi,
Two points:

1. it is OK.
   /dev$ ll ttyUSB*
   crwxrwxrwx 1 root dialout 188, 0 Jul 25 19:04 ttyUSB0
   crwxrwxrwx 1 root dialout 188, 1 Jul 25 17:42 ttyUSB1
2. it can run into by minicom :
   [ 5769.080607] type=1400 audit(1469435616.660:27): avc: denied { getattr } for pid=1208 comm="ls" path="/init" dev="rootfs" ino=1060 scontext=u:r:shell:s0 tcontext=0
   root@juno:/ #

About downgrading pexect to v3.3 ... ?

from workload-automation.

Remove pexect module from your machine; if this was installed via pip (e.g. automatically as a dependency when installing WA), you should be able to do it by

sudo pip uninstall pexpect

Then re-install it explicitly specifying the version:

 sudo pip install pexpect==3.3

from workload-automation.

It is OK during runing WA in other Android devices by usb port in the same env.
Of course device = 'generic_android' .

from workload-automation.

OK;
Try to downgrad pexpect .

from workload-automation.

Hello,
After downgrading pexect to v3.3 ... tested.
WA run to the end, errors info as followings:
2016-07-26 10:24:29,216 DEBUG serial_read: root@juno:/ # ip addr list eth0
2016-07-26 10:24:29,217 DEBUG serial_read:
2016-07-26 10:24:29,217 DEBUG serial_read: 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
2016-07-26 10:24:29,217 DEBUG serial_read: link/ether 00:02:f7:00:5a:15 brd ff:ff:ff:ff:ff:ff
2016-07-26 10:24:39,327 DEBUG serial_send: ip addr list eth0
2016-07-26 10:24:40,429 DEBUG serial_read: root@juno:/ # ip addr list eth0
2016-07-26 10:24:40,429 DEBUG serial_read:
2016-07-26 10:24:40,429 DEBUG serial_read: 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
2016-07-26 10:24:40,430 DEBUG serial_read: link/ether 00:02:f7:00:5a:15 brd ff:ff:ff:ff:ff:ff
2016-07-26 10:24:50,544 CRITICAL root: Could not acquire IP address.

Thanks.

from workload-automation.

Or another info prompt,
2016-07-26 11:01:44,318 INFO Runner: Connecting to device
2016-07-26 11:01:44,419 DEBUG serial_send:
2016-07-26 11:01:44,520 DEBUG Juno: Waiting for the Android prompt.
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/entry_point.py", line 63, in main
2016-07-26 11:04:57,804 CRITICAL root: sys.exit(command.execute(args))
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/commands/run.py", line 98, in execute
2016-07-26 11:04:57,804 CRITICAL root: executor.execute(agenda, selectors={'ids': args.only_run_ids})
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 342, in execute
2016-07-26 11:04:57,804 CRITICAL root: runner.run()
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 480, in run
2016-07-26 11:04:57,804 CRITICAL root: self._initialize_run()
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 533, in _initialize_run
2016-07-26 11:04:57,804 CRITICAL root: self._connect_to_device()
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/core/execution.py", line 566, in _connect_to_device
2016-07-26 11:04:57,804 CRITICAL root: self.device.connect()
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/wlauto/devices/android/juno/init.py", line 153, in connect
2016-07-26 11:04:57,804 CRITICAL root: target.expect(self.android_prompt)
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/pexpect/init.py", line 1451, in expect
2016-07-26 11:04:57,804 CRITICAL root: timeout, searchwindowsize)
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/pexpect/init.py", line 1466, in expect_list
2016-07-26 11:04:57,804 CRITICAL root: timeout, searchwindowsize)
2016-07-26 11:04:57,804 CRITICAL root: File "/usr/local/lib/python2.7/dist-packages/pexpect/init.py", line 1554, in expect_loop
2016-07-26 11:04:57,804 CRITICAL root: raise EOF(str(err) + '\n' + str(self))
2016-07-26 11:04:57,804 CRITICAL root:
2016-07-26 11:04:57,804 CRITICAL root: EOF(End Of File (EOF). Empty string style platform.
2016-07-26 11:04:57,804 CRITICAL root: <pexpect.fdpexpect.fdspawn object at 0x4da2d50>
2016-07-26 11:04:57,804 CRITICAL root: version: 3.3
2016-07-26 11:04:57,804 CRITICAL root: command: None
2016-07-26 11:04:57,804 CRITICAL root: args: None
2016-07-26 11:04:57,804 CRITICAL root: searcher: <pexpect.searcher_re object at 0x4da2c90>
2016-07-26 11:04:57,804 CRITICAL root: buffer (last 100 chars): ''
2016-07-26 11:04:57,804 CRITICAL root: before (last 100 chars): ''
2016-07-26 11:04:57,804 CRITICAL root: after: <class 'pexpect.EOF'>
2016-07-26 11:04:57,804 CRITICAL root: match: None
2016-07-26 11:04:57,804 CRITICAL root: match_index: None
2016-07-26 11:04:57,804 CRITICAL root: exitstatus: None
2016-07-26 11:04:57,804 CRITICAL root: flag_eof: True
2016-07-26 11:04:57,804 CRITICAL root: pid: None
2016-07-26 11:04:57,804 CRITICAL root: child_fd: 5
2016-07-26 11:04:57,804 CRITICAL root: closed: False
2016-07-26 11:04:57,804 CRITICAL root: timeout: 300
2016-07-26 11:04:57,804 CRITICAL root: delimiter: <class 'pexpect.EOF'>
2016-07-26 11:04:57,804 CRITICAL root: logfile: None
2016-07-26 11:04:57,804 CRITICAL root: logfile_read: <wlauto.utils.serial_port.PexpectLogger object at 0x4da2d90>
2016-07-26 11:04:57,804 CRITICAL root: logfile_send: <wlauto.utils.serial_port.PexpectLogger object at 0x4da2e10>
2016-07-26 11:04:57,804 CRITICAL root: maxread: 2000
2016-07-26 11:04:57,804 CRITICAL root: ignorecase: False
2016-07-26 11:04:57,804 CRITICAL root: searchwindowsize: None
2016-07-26 11:04:57,804 CRITICAL root: delaybeforesend: 0.05
2016-07-26 11:04:57,804 CRITICAL root: delayafterclose: 0.1
2016-07-26 11:04:57,804 CRITICAL root: delayafterterminate: 0.1)
...

from workload-automation.

wa --version IS
wa 2.4.0

from workload-automation.

It looks like the network interface on your Juno is DOWN. As stated above, WA talks to the Juno over Ethernet. Please make sure your board has a working network connections before attempting to use WA with it.

It also looks like your WA is out of date -- it is strongly recommended that you upgrade to v2.5.0.

from workload-automation.

Assumed resolved

from workload-automation.