Re:‏ qemu running uefi problem

Peter Maydell, can I assume that It would be possible if there was the full emulation of the Lenovo hardware, including the all firmware blobs and Intell ME? Regards, Aleksey מאת: ‏‏qemu-discuss-bounces+shevandin_al=hotmail@nongnu.org בשם Peter Maydell ‏‏

Failed to start qemu-system-aarch64 virt: qemu-system-aarch64: device requires ... bytes, block backend provides

Hi, I'm trying ti start virt emulation and fails with the follow error: qemu-system-aarch64: device requires 67108864 bytes, block backend provides 1112576 bytes What exactly does it mean and what could be done to prevent it? I start it with the follow command line parameters: qemu-system-aarch64

Custom soc on ARM64, failed to load the firmware properly

I'm building the custom SoC emulation that is based on the Cortext-a55. During the runtime $pc register contains 0 instead the address that is provided in means of arm_boot_info.loader_start : (gdb) p $pc $1 = (void (*)()) 0x0 x/3i 0xFF 0xff <_start>: .inst 0x464c457f ; undefi

SoC emulation: what is the purpose of object_property_add_child that adds SoC device as a child of MachineState?

I had looked over the implementations of SoC emulation. SoC emulation is usually implemented as object that is derived from DeviceState. It is common to connect the SoC object to the MachineState object as a child, for instance ../hw/arm/orangepi.c, line 57: object_property_add_child(OBJECT(ma

Custom SoC emulation asserts “../hw/core/qdev.c:316": qdev_assert_realized_properly_cb: Assertion `dev->realized' failed

My custom SoC emulation is based on the state struct that is derived from DeviceState. It seems that the all epected parts - the class initialization, the instance initialization, machine initialization are there. The implementation asserts at at ../hw/core/qdev.c, line 316 (master branch, comm

Re:‏ ‏ Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

Maydell ‏‏נשלח: יום שלישי 14 פברואר 2023 16:17 ‏‏אל: Alyosha Shevandin עותק: qemu-discuss@nongnu.org ‏‏נושא: Re: ‏ Crash in memory_region_init_ram call chain, when --bios command line parameter is presented. On Tue, 14 Feb 2023 at 11:54, Alyosha Shevandin wrote: > > Thank you for your ans

Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

I would appreciate any clue about the crash. When I start my custom SoC emulation and the –bios command line parameter us presented, the QEMU processes crashes before the custom code even tries to load the firmware. It crashes in the *memory_region_init_ram* call chain with the follow stack:

Suitable API do build the custom SoC emulation

I wonder if there is any other way to build emulation for the custom SoC except using QEMU C API? I mean, the C API the one, that is used in a lot of examples under /hw folder. The other way – the high level abstractions – based: XML, Json, Python etc. The custom hardware that I need to emulate

Re:‏ Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

init_ram(&state->ram,   OBJECT(state),   "mysoc.ram",   mysoc_memmap[MYSOCK_DEV_RAM].size,   &error_abort); Regards, Aleksey מאת: Peter Maydell ‏‏נשלח: יום שלישי 14 פברואר 2023 13:07 ‏‏אל: Alyosha Shevand

Re - SOLVED, it is actually, supported:‏ Support for Cortex-A55

, Alyosha Shevandin wrote: > The below call: > > qemu-system-aarch64 -nographic -machine virt,secure=on -cpu cortex-a55 -smp > clusters=1,cores=1 -m 1024 -bios ../bl1.bin -d unimp -semihosting-config > enable=on,target=native > > fails with error: > > qemu-system-aarch6

Support for Cortex-A55

I would like to know what is the status of Cortex-A55 support. I had read all relevant messages in this mail list and the documentation and still can not understand if it is supported. For instance, this documentation states that there Cortext-A55 is supported by generic virtual platform (virt