Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-26 Thread Liviu Ionescu
> On 26 Jul 2022, at 13:56, Peter Maydell wrote: > > ... If you're able to figure out what your original failing binary > setup was and repro the problem again, please send me the executable. Thank you for investigating. I'll try to revert my projects to running from flash, and, if still ha

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-26 Thread Peter Maydell
On Mon, 25 Jul 2022 at 18:02, Liviu Ionescu wrote: > > On 25 Jul 2022, at 19:02, Peter Maydell wrote: > > The one where SYS_HEAPINFO produces the bogus result putting the > > heap at 0x0400, that you mentioned in the original report with > > the command line > > > > .../qemu-system-arm "--mac

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-25 Thread Liviu Ionescu
> On 25 Jul 2022, at 20:33, Peter Maydell wrote: > > ... I'll try a setup with code in flash and > data in RAM, that sounds like it might be a way to cause the > problem if there's not much code and a lot of data (because > then the remaining space in the flash is larger than the > remaining s

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-25 Thread Peter Maydell
On Mon, 25 Jul 2022 at 18:02, Liviu Ionescu wrote: > > On 25 Jul 2022, at 19:02, Peter Maydell wrote: > > The one where SYS_HEAPINFO produces the bogus result putting the > > heap at 0x0400, that you mentioned in the original report with > > the command line > > > > .../qemu-system-arm "--mac

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-25 Thread Liviu Ionescu
> On 25 Jul 2022, at 19:02, Peter Maydell wrote: > > > We document what the guest can assume about the virt board > memory layout here: > > https://www.qemu.org/docs/master/system/arm/virt.html#hardware-configuration-information-for-bare-metal-programming > > Flash at 0, RAM at 0x4000_,

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-25 Thread Peter Maydell
On Mon, 25 Jul 2022 at 16:56, Liviu Ionescu wrote: > > > > > On 25 Jul 2022, at 18:43, Peter Maydell wrote: > > > > ... the memory map for the 'virt' board doesn't change for the a72 > > versus the a15. In both cases, the memory from 0x0 to 0x0800 > > is the flash memory. So QEMU is incorrect

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-25 Thread Liviu Ionescu
> On 25 Jul 2022, at 18:43, Peter Maydell wrote: > > ... the memory map for the 'virt' board doesn't change for the a72 > versus the a15. In both cases, the memory from 0x0 to 0x0800 > is the flash memory. So QEMU is incorrect to have reported that as > the place to put the heap in SYS_HEA

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-07-25 Thread Peter Maydell
On Fri, 3 Jun 2022 at 07:17, Liviu Ionescu wrote: > > On 2 Jun 2022, at 21:36, Liviu Ionescu wrote: > > > > ... SYS_HEAPINFO... > > > > 0x0400 - heap base > > 0x0800 - heap limit > > 0x0800 - stack base > > 0x0 - stack limit > > For Cortex-A72 I see similar values: > > 0x4400 > 0x

Re: TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-06-02 Thread Liviu Ionescu
> On 2 Jun 2022, at 21:36, Liviu Ionescu wrote: > > ... SYS_HEAPINFO... > > 0x0400 - heap base > 0x0800 - heap limit > 0x0800 - stack base > 0x0 - stack limit For Cortex-A72 I see similar values: 0x4400 0x4800 0x4800 0x4000 just that in this case the memory is w

TARGET_SYS_HEAPINFO and Cortex-A15 memory map

2022-06-02 Thread Liviu Ionescu
I'm experiencing some issues with the startup code for an emulated Cortex-a15 machine I plan to use for running unit-tests. I'm starting QEMU with: .../qemu-system-arm "--machine" "virt" "--cpu" "cortex-a15" "--nographic" "-d" "unimp,guest_errors" "--semihosting-config" "enable=on,target=nati