Dear All,
I'm currently trying to check and implement a complete validation of my PSCI solution.
The standard behavior for PSCI is to manage shutdown, reset and low power mode.
I'm wondering to find the best way to manage it through LAVA.
So two questions:
- Is there a proper way to check the reboot behavior on a target (soft reboot)? Using shell command is not possible as the is no return from reboot.
- Shutdown? I'm wondering to test the shutdown command and trig an automatic wake up after x seconds. My wish is to check that no watchdog occurred during that time (which is the only way to know if the shutdown was properly working). So it will be a similar behavior that the reboot command.
Thanks for your support,
BR
Lionel
On Thu, 21 Feb 2019 at 08:19, Lionel DEBIEVE lionel.debieve@st.com wrote:
Dear All,
I'm currently trying to check and implement a complete validation of my PSCI solution.
The standard behavior for PSCI is to manage shutdown, reset and low power mode.
I'm wondering to find the best way to manage it through LAVA.
So two questions:
- Is there a proper way to check the reboot behavior on a target (soft
reboot)? Using shell command is not possible as the is no return from reboot.
Typically, a soft reboot causes the next output on the serial to be from the bootloader. Are you saying that the serial output is *disconnected* on reboot? If that happens, then none of this can be supported. The serial connection must remain active at all times.
A lot depends on the type of device. Which device is this? What bootloader and how is power controlled remotely?
Soft reboot support isn't directly supported. The resulting boot action should be defined in the test job submission and managed by LAVA.
I'm not sure if the interactive test method can help with this. Depends a lot on exactly what kind of device this is and what kind of bootloader is in use.
- Shutdown? I'm wondering to test the shutdown command and trig an
automatic wake up after x seconds.
How is the wake up to be achieved? You will need a PDUReboot Action to be defined if you want to execute a PDU reboot - after shutdown, the power is still on.
In summary, a lot depends on the specific device and how that is integrated into LAVA.
My wish is to check that no watchdog occurred during that time (which is the only way to know if the shutdown was properly working). So it will be a similar behavior that the reboot command.
Thanks for your support,
BR
Lionel
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On 2/21/19 9:46 AM, Neil Williams wrote:
On Thu, 21 Feb 2019 at 08:19, Lionel DEBIEVE lionel.debieve@st.com wrote:
Dear All,
I'm currently trying to check and implement a complete validation of my PSCI solution.
The standard behavior for PSCI is to manage shutdown, reset and low power mode.
I'm wondering to find the best way to manage it through LAVA.
So two questions:
- Is there a proper way to check the reboot behavior on a target (soft
reboot)? Using shell command is not possible as the is no return from reboot.
Typically, a soft reboot causes the next output on the serial to be from the bootloader. Are you saying that the serial output is *disconnected* on reboot? If that happens, then none of this can be supported. The serial connection must remain active at all times.
I confirm, there is no disconnection from serial output, so no issue here.
A lot depends on the type of device. Which device is this? What bootloader and how is power controlled remotely?
Device is STM32MP1 https://www.st.com/content/st_com/en/about/media-center/press-item.html/p414.... Today, boot chain is Arm-trusted-firmware (No tx console here)-> UBoot -> Linux kernel. And power is controller by external PDU.
Soft reboot support isn't directly supported. The resulting boot action should be defined in the test job submission and managed by LAVA.
I've quickly seen in your code that there maybe a soft-reboot possibility from boot action but there is no associated option to use it from a new boot action block.
I'm not sure if the interactive test method can help with this. Depends a lot on exactly what kind of device this is and what kind of bootloader is in use.
Maybe interactive method can be a way, but need to ensure that an autologin can be trigged later, boot action may be the best way to launch a reset.
- Shutdown? I'm wondering to test the shutdown command and trig an
automatic wake up after x seconds.
How is the wake up to be achieved? You will need a PDUReboot Action to be defined if you want to execute a PDU reboot - after shutdown, the power is still on.
On my side, a simple RTC trigger can be used to wakeup the system for now, ensuring that the system was shutdown. So, yes we keep the power on here, no PDU action needed. But same, no trigger here to confirm that power off is complete and issue can come from watchdog timeout. Idea could be to just ensure that no traces are back after complete poweroff or timeout is properly achieve.
In summary, a lot depends on the specific device and how that is integrated into LAVA.
My wish is to check that no watchdog occurred during that time (which is the only way to know if the shutdown was properly working). So it will be a similar behavior that the reboot command.
Thanks for your support,
BR
Lionel
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org
-
Lionel DEBIEVE -
Neil Williams