Hi Dave,
We are looking to test using the latest firmware configuration which has PSCI enabled. I should hopefully have this up and running this week so I can provide you with a tarball of the firmware etc and details on how to set this up for your boards if you would like?
We would like to test this configuration and the current one (already in LAVA) in parallel, so if I created another device type config under /srv/lava/instances/<instance>/etc/lava-dispatcher/device-types called vexpress-tc2-psci is this allowed in LAVA, or are there a set list of device types you can choose from?
I attempted this on Friday, adding vexpress-tc2-psci as a new device type in the admin UI, then, also in the admin UI, switched the existing device to use the vexpress-tc2-psci device type.
I then created the following config files:
-----------------------------------------------------------------------------------------------
$ ls -l /srv/lava/instances/production/etc/lava-dispatcher/devices/pdswlava-vetc2-1.conf -rw-r--r-- 1 pdswauto pdswauto 168 Feb 22 12:20 pdswlava-vetc2-1.conf
$ cat /srv/lava/instances/production/etc/lava-dispatcher/devices/pdswlava-vetc2-1.conf device_type = vexpress-tc2-psci hostname = pdswlava-vetc2-1 connection_command = telnet pdtl-tt1 6002 hard_reset_command = /usr/share/conmux/drivers/reboot-ap7952 pdtl-pdu-5 08
-----------------------------------------------------------------------------------------------
$ ls -l /srv/lava/instances/production/etc/lava-dispatcher/device-types/vexpress-tc2-psci.conf -rw-rw-r-- 1 pdswauto pdswauto 131 Feb 8 10:20 /srv/lava/instances/production/etc/lava-dispatcher/device-types/vexpress-tc2-psci.conf
$ cat /srv/lava/instances/production/etc/lava-dispatcher/device-types/vexpress-tc2-psci.conf boot_cmds = 2
boot_cmds_android = 3
interrupt_boot_prompt = The default boot selection will start in
bootloader_prompt = Start:
-----------------------------------------------------------------------------------------------
My vexpress-tc2-psci.conf is identical to my vexpress-tc2.conf but I created it so not to cause any confusion
This resulted in the same issue I saw when we had a config mismatch before. The board boots the master image then sits waiting at the prompt not knowing what to do until the reboot process times out. It looks as though LAVA doesn't know what device type to use and as a result doesn't know what prompt it should be waiting for.
Am I doing something daft?
Cheers Dean
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.