Re: [PATCH v1 4/5] hw/arm: Add Axiado SoC AX3005

[Jack Wang <163wangjack@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]


Hi Kuan_Jui

Sorry that my previous message was not clear enough.The build is not hang,but the machine initialization did not return of ax3005-evb. This is the reason why I said 'initialization did not complete’. If you want to reproduce the mistake,commands below will help you

../qemu/configure --target-list=aarch64-softmmu --enable-debug --enable-werror --disable-rust

ninja qemu-system-aarch64

After the build completes, start the emulator with:

printf '%s\n''{"execute":"qmp_capabilities"}' '{"execute":"query-status"}' '{"execute":"query-memory-size-summary”}'{"execute":"quit”}’ | build/qemu-system-aarch64 -M ax3005-evb -m 2G -display none -serial none -qmp stdio -S

QEMU printed the QMP greeting, but no response to the`qmp_capabilities` command was received. The process did not complete machine initialization and remained in the initialization path around `ax3005_init()`

And i noticed that you deliver new version. Cheer for this,maybe we could discuss more in new series.

Best regards : )
Jack Wang 
> On Mon, 24 Aug 2026 09:50:09 +0800, Kuan-Jui Chiu <kchiu@axiado.com> wrote:
> Hi Jack
> 
> Thanks for the test, could you share how you built and what the command 
> was you used to test?
> 
> I did not see this issue on my side, maybe I missed something
> 
> B.R.
> Howard
> 
> Jack Wang 於 2026/8/23 下午 06:33 寫道:
> 
> 

>> On Sun, 23 Aug 2026 18:33:01 +0800, Jack Wang <163wangjack@gmail.com <mailto:163wangjack@gmail.com>> wrote:
>> Hi Kuan-Jui
>> 
>> I tested this series with ax3005-evb machine,the initialization did not complete.
>> The process showed it repeatedly executing in 'ax3005_init'
>> 
>>> +static const TypeInfo ax3005_soc_types[] = {
>>> +    {
>>> +        .name           = TYPE_AX3005_SOC,
>>> +        .parent         = TYPE_SYS_BUS_DEVICE,
>>> +        .instance_size  = sizeof(Ax3005SoCState),
>>> +        .instance_init  = ax3005_init,
>>> +        .class_init     = ax3005_class_init,
>>> +    }
>>> +};
>> 
>> You add instance_size here but forget to add class_size. Then qemu defaultly use SysBusDeviceClass’s class_size cause of father-son relationship.
>> 
>>> +typedef struct Ax3005SoCClass {
>>> +    SysBusDeviceClass   parent;
>>> +
>>> +    uint32_t            num_cpus;
>>> +} Ax3005SoCClass;
>> 
>> Here your struct apparently extend SysBusDeviceClass field. I think it is the way why previous repeating behavior.After add class_size locally and rebuild the the machine completed initialization and responded to QMP commands successfully.
>> 
>> Best regards :)
>> Jack Wang

[-- Attachment #2: Type: text/html, Size: 17116 bytes --]