On 6 January 2017 at 15:24, Max Filippov wrote:
> On Fri, Jan 6, 2017 at 2:23 AM, Peter Maydell
> wrote:
>> On 5 January 2017 at 22:52, Max Filippov wrote:
>>> Hello,
>>>
>>> debugging XIP kernel running directly from CFI FLASH I've got to a point
>>> where QEMU aborts with the message "Bad ram
On Fri, Jan 6, 2017 at 2:23 AM, Peter Maydell wrote:
> On 5 January 2017 at 22:52, Max Filippov wrote:
>> Hello,
>>
>> debugging XIP kernel running directly from CFI FLASH I've got to a point
>> where QEMU aborts with the message "Bad ram pointer 0xbb4".
>>
>> It turns out that that happens when
On 5 January 2017 at 22:52, Max Filippov wrote:
> Hello,
>
> debugging XIP kernel running directly from CFI FLASH I've got to a point
> where QEMU aborts with the message "Bad ram pointer 0xbb4".
>
> It turns out that that happens when QEMU tries to translate code from FLASH
> immediately after th
Hello,
debugging XIP kernel running directly from CFI FLASH I've got to a point
where QEMU aborts with the message "Bad ram pointer 0xbb4".
It turns out that that happens when QEMU tries to translate code from FLASH
immediately after the kernel has written to the FLASH address range:
writing to F
