On 30 June 2017 at 09:24, KONRAD Frederic <address@hidden> wrote:
On 06/29/2017 06:45 PM, Peter Maydell wrote:
It's the same thing, though, right? If the user's ELF file
says "vector table is at 0x8000000" then we should either
(a) say that's a user error, or
(b) handle it right, whether we implemented the QEMU model with
the flash at 0 and the alias at 0x8000000, or with the flash
at 0x8000000 and the alias at 0.
Fondamentaly yes, it is the same.. but it seems really strange to
me to load the elf in the alias.
The user creating the ELF file has no idea whether we
modelled the flash at 0 and the alias at highmem or
the other way around -- that is an implementation detail
that should be completely invisible to the user.
My two suggestions are based on that point -- either we
should treat "ELF loaded at highmem" as always wrong, or
we should always support it.
If I choose (a) I'll need to objcpy all the elf to 0 or modify
the build script which should work on the real board.. This seems
not really a good option to me.
I agree that I don't like this.
If I choose (b) I won't be able to load it to SRAM and it is
basically the same result I'll need to move or modify the config.
I don't understand this, though. Option (b) is probably painful
to implement (I don't have a good idea of how to do it) but
it ought to mean that the ELF files that work on the board
also work for QEMU (regardless of how the board model
implemented the aliased flash).