On 07/03/2017 10:51 AM, Peter Maydell wrote:
On 3 July 2017 at 08:31, KONRAD Frederic wrote:
On 06/30/2017 11:06 AM, Peter Maydell wrote:
On 30 June 2017 at 09:24, KONRAD Frederic
wrote:
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 mov
On 3 July 2017 at 08:31, KONRAD Frederic wrote:
> On 06/30/2017 11:06 AM, Peter Maydell wrote:
>> On 30 June 2017 at 09:24, KONRAD Frederic
>> wrote:
>>> 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 d
On 06/30/2017 11:06 AM, Peter Maydell wrote:
On 30 June 2017 at 09:24, KONRAD Frederic 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 0x800" then we should either
(a) say that's a user error, or
(b)
On 30 June 2017 at 09:24, KONRAD Frederic 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 0x800" then we should either
>> (a) say that's a user error, or
>> (b) handle it right, whether we implement
On 06/29/2017 06:45 PM, Peter Maydell wrote:
On 29 June 2017 at 17:41, KONRAD Frederic wrote:
On 06/29/2017 05:14 PM, Peter Maydell wrote:
This is awkward, because in the "we have a ROM but it's not been
copied into memory yet" case, the only thing we have is the
rom->addr, which is the addr
On 29 June 2017 at 17:41, KONRAD Frederic wrote:
> On 06/29/2017 05:14 PM, Peter Maydell wrote:
>> This is awkward, because in the "we have a ROM but it's not been
>> copied into memory yet" case, the only thing we have is the
>> rom->addr, which is the address which the user's ROM blob said
>> it
On 06/29/2017 05:14 PM, Peter Maydell wrote:
On 29 June 2017 at 10:28, KONRAD Frederic wrote:
This fixes an odd bug when a ROM is present somewhere and an alias @0x
is pointing to the ROM. The "if (rom)" test fails and we don't get a valid reset
state. QEMU later crashes with an excep
On 29 June 2017 at 10:28, KONRAD Frederic wrote:
> This fixes an odd bug when a ROM is present somewhere and an alias @0x
> is pointing to the ROM. The "if (rom)" test fails and we don't get a valid
> reset
> state. QEMU later crashes with an exception because the ARMv7-M starts with
> t
