sorry, wrong email thread.

Another way around is to not support "hot reset" in ATF, but make qemu reboot is implement some watchdog for qemu virt platform. That also works for me with quick implementation with lhe link which I sent in the previous email.

Maxim.

On Thu, 24 Sep 2020 at 15:16, Maxim Uvarov via TF-A tf-a@lists.trustedfirmware.org wrote:

I.e. that implementation works for me: https://github.com/muvarov/qemu/commit/f5e3fb83170613a9eed46b87358ab2e37de26...

On Mon, 21 Sep 2020 at 18:16, Maxim Uvarov maxim.uvarov@linaro.org wrote:

...

Hello,

I'm trying to understand why "warm reboot" is not currently implemented in TF-A for qemu targets. I.e. in case of qemu armv8 boot atf->optee->uboot->linux and then reboot, cpu jumps to BL31 qemu_system_reset() function which just calls panic(). I'm wondering why loading images from this stage is not happening? Something similar to bl2_load_images()->load_image() to load uboot and optee os again and run them with bl31_main()?

If I understand "CPU reset" spec [1] correctly, warm boot from reset vector in BL31 again to Non-Secure world has to work.

[1] https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/design...

Best regards, Maxim.

-- TF-A mailing list TF-A@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-a