[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Call failed: MCTP Endpoint did not respond: Qemu CXL switch with mctp-1.
From: |
Maverickk 78 |
Subject: |
Call failed: MCTP Endpoint did not respond: Qemu CXL switch with mctp-1.0 |
Date: |
Fri, 17 Mar 2023 00:11:10 +0530 |
Hi
I am trying mctp & mctpd with aspeed +buildroot(master) + linux v6.2
with Qemu 7.2.
I have added necessary FMAPI related patches into QEMU to support CLX
switch emulation
RFC-1-2-misc-i2c_mctp_cxl_fmapi-Initial-device-emulation.diff
RFC-2-3-hw-i2c-add-mctp-core.diff
RFC-4-4-hw-misc-add-a-toy-i2c-echo-device.diff
RFC-2-2-arm-virt-Add-aspeed-i2c-controller-and-MCTP-EP-to-enable-MCTP-testing.diff
RFC-3-3-hw-nvme-add-nvme-management-interface-model.diff
Executed following mctp commands to setup the binding,
mctp link set mctpi2c15 up
mctp addr add 50 dev mctpi2c15
mctp link set mctpi2c15 net 11
systemctl restart mctpd.service
busctl call xyz.openbmc_project.MCTP /xyz/openbmc_project/mctp
au.com.CodeConstruct.MCTP AssignEndpoint say mctpi2c15 1 0x4d
The above busctl configuration is reaching fmapi patch and sets up
the endpoint id but then mctpd fails with log after timeout.
Call failed: MCTP Endpoint did not respond
Any clue what's going on?
Regards
Raghu
- Call failed: MCTP Endpoint did not respond: Qemu CXL switch with mctp-1.0,
Maverickk 78 <=