Hello
Oleksandr Tyshchenko,
Thanks for your quick response. With Xen stable 4.13 branch, the mentioned issue is solved.
Is there any document which I could refer to bring up Xen[DOM0] and have an hands on ? because am currently seeing no output after this
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 324kB init memory.
(XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)
Attaching the complete logs for reference.
Mit freundlichen Grüßen / Best regards
Chockalingam Manikandan
ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart |
GERMANY | www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 |
Manikandan.Chockalingam@xxxxxxxxxxxx
Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner,
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller
From: Oleksandr Tyshchenko <olekstysh@xxxxxxxxx>
Sent: Wednesday, July 15, 2020 1:00 AM
To: Manikandan Chockalingam (RBEI/ECF3) <Manikandan.Chockalingam@xxxxxxxxxxxx>
Cc: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>; nd <nd@xxxxxxx>; xen-devel@xxxxxxxxxxxxx
Subject: Re: [BUG] Xen build for RCAR failing
[Sorry for the possible format issues]
Hello Bertrand,
I succeeded in building the core minimal image with dunfell and its compatible branches [except xen-troops (modified some files to complete the build)].
But I face the following error while booting.
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Timer: Unable to retrieve IRQ 0 from the device tree
(XEN) ****************************************
The reason for that problem *might* be in the arch timer node in your device tree which contains "interrupts-extended" property instead of just "interrupts". As far as I remember Xen v4.12 doesn't have required support to handle "interrupts-extended".
It went in a bit later [1]. If this is the real reason, I think you should either switch to the new Xen version or modify your arch timer node in a way to use the "interrupts" property [2]. I would suggest using the new Xen version if possible
(at least v4.13).
--
