Le 2018-01-15 12:09, Fabien Chouteau a écrit :
On 12/01/2018 15:10, Jean-Christophe Dubois wrote:
Le 2018-01-12 11:55, Fabien Chouteau a écrit :
On 11/01/2018 13:35, Jean-Christophe Dubois wrote:
Thanks Fabien,
Now, as a side question, could you tell me which reference LEON3
platform is implemented by Qemu in leon3_generic?
I think it was the based on the FPGA version of Leon3 I was using at
the
time. The name leon3_generic comes from my will to make it a
configurable board where users could define the number and the
location
of the different peripherals, I never had time to work on this.
I see. I am not sure how to bring configurability to Qemu. There is
the possibility to describe the hw PTF with DTC/DTB or something
similar. I think some people were working on it for the ARM Qemu
platform (but I am not sure what happened to this initiative).
Now in the meantime, would it make sense to move leon3_generic to a
tsim compatible platform?
I don't think so, leon3_generic is compatible with a real hardware
which
is also interesting for comparison.
What real hardware (gaisler reference platform) is it? Could you point
to the public reference manual for this hardware?
Another possibility is to add a leon3_tsim platform into Qemu to support
the compatibility with the tsim emulator. But the difference with
leon3_generic would be minimal.
This would allow to validate the same software on the 2 simulators
(obviously it would not be compatible with your specific FPGA version
for now).
The Leon3 AMBA bus provides a way to discover the peripherals and their
address, so any system should be capable of supporting different
peripheral layouts.
Here's an example of AMBA discovery code from a very old project of
mine
(don't judge me on this :) :
https://github.com/Fabien-Chouteau/kabitbol/blob/master/src/amba.c
There was a couple of patches submitted some times ago to add Leon3
AMBA
support in QEMU, I think it's time to bring them back...
What you are talking about here is the possibility for the software
running inside Qemu to probe/discover the hardware. For such feature
Qemu should implement what is required for this AMBA discovery. But it
does not solve how you decide at run time at what addresses are the
various AMBA devices (how you decide to emulate a tsim platform or
another one).
Note: For now I am not so much interested in the AMBA discovery as the
type of software platform I am thinking about is embedded where the
hardware is well known ahead of time. This discovery capability would
make sense for more generic OS like linux or such. We cannot require all
embedded OS to implement the AMBA discovery process.
