Mailing List Archive

Asking for help to debug xen efi on Kunpeng machine
Hello community,

I need help for debugging XEN on aarch64 architecture. The machine I am
working on is a kunpeng 920 armv8 compatible CPU. I use debian 11 as
operating system and installed xen-system-arm64 without any problem. But
when I boot into xen hypervisor mode, the machine screen is black out
without any output or any helpful debugging message.

Could you generously provide some hints for debugging the issue? Thank
you very much in advance and looking forward to hearing from you.

--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hello Stefano,

I am able to obtain some serial logging (by enabling debugging and
verbose debugging messages, hopefully select the right option). The message
looks like

(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 372kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER24
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER28
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER32
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER36
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER40

Could you help find out where it is wrong ? Thank you very much for the
help!

Best Regards,
Jiatong Shen


On Sat, Jun 10, 2023 at 7:15?AM Jiatong Shen <yshxxsjt715@gmail.com> wrote:

> Hello Julien,
>
> Thank you very much for your help!
>
> Best,
>
> Jiatong Shen
>
> On Fri, Jun 9, 2023 at 4:48?PM Julien Grall <julien@xen.org> wrote:
>
>> Hello,
>>
>> On 09/06/2023 03:32, Jiatong Shen wrote:
>> > Thank you for your answer. Can you teach me how to verify if acpi is
>> > enabled?
>>
>> You usually look at the .config. But I am not sure if this is provided
>> by the Debian package. If not, then your best option would be to build
>> your own Xen. To select ACPI, you want to use the menuconfig and select
>> UNSUPPORTED and ACPI.
>>
>> Cheers,
>>
>> --
>> Julien Grall
>>
>
>
> --
>
> Best Regards,
>
> Jiatong Shen
>


--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hello Stefano and Julien,

I tried to do some debugging by adding a printk inside the function
idle_loop in file arm/domain.c. Looks like the idle function is running
normally because the printk function is getting called without stalling.
But the vga screen is still blacked out and the serial terminal does not
display any login message.

the grub config for xen 4.17 is

submenu 'Xen hypervisor, version 4.17' $menuentry_id_option
'xen-hypervisor-4.17-5ebc23af-c2e2-4ac3-b308-3e82ec786c04' {
menuentry 'Debian GNU/Linux, with Xen 4.17 and Linux 5.10.0-23-arm64'
--class debian --class gnu-linux --class gnu --class os --class xen
$menuentry_id_option
'xen-gnulinux-5.10.0-23-arm64-advanced-5ebc23af-c2e2-4ac3-b308-3e82ec786c04'
{
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-ieee1275='ieee1275//sas/disk@20000,gpt2' --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
5ebc23af-c2e2-4ac3-b308-3e82ec786c04
else
search --no-floppy --fs-uuid --set=root
5ebc23af-c2e2-4ac3-b308-3e82ec786c04
fi
echo 'Loading Xen 4.17 ...'
if [ "$grub_platform" = "pc" -o "$grub_platform" = "" ]; then
xen_rm_opts=
else
xen_rm_opts="no-real-mode edd=off"
fi
xen_hypervisor /boot/xen-4.17 placeholder ${xen_rm_opts}
echo 'Loading Linux 5.10.0-23-arm64 ...'
xen_module /boot/vmlinuz-5.10.0-23-arm64 placeholder
root=UUID=5ebc23af-c2e2-4ac3-b308-3e82ec786c04 ro quiet
echo 'Loading initial ramdisk ...'
xen_module --nounzip /boot/initrd.img-5.10.0-23-arm64
}

The code I am modifying is

static void noreturn idle_loop(void)
{
unsigned int cpu = smp_processor_id();

for ( ; ; )
{
dprintk(XENLOG_INFO, "running idle loop \n");
if ( cpu_is_offline(cpu) )
stop_cpu();
}
}
}

Hopes this debugging makes some sense.

Best Regards,
Jiatong Shen

On Sun, Jun 11, 2023 at 12:00?PM Jiatong Shen <yshxxsjt715@gmail.com> wrote:

> Hello Stefano,
>
> I am able to obtain some serial logging (by enabling debugging and
> verbose debugging messages, hopefully select the right option). The message
> looks like
>
> (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
> (XEN) Freed 372kB init memory.
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER4
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER8
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER12
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER16
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER20
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER24
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER28
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER32
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER36
> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER40
>
> Could you help find out where it is wrong ? Thank you very much for the
> help!
>
> Best Regards,
> Jiatong Shen
>
>
> On Sat, Jun 10, 2023 at 7:15?AM Jiatong Shen <yshxxsjt715@gmail.com>
> wrote:
>
>> Hello Julien,
>>
>> Thank you very much for your help!
>>
>> Best,
>>
>> Jiatong Shen
>>
>> On Fri, Jun 9, 2023 at 4:48?PM Julien Grall <julien@xen.org> wrote:
>>
>>> Hello,
>>>
>>> On 09/06/2023 03:32, Jiatong Shen wrote:
>>> > Thank you for your answer. Can you teach me how to verify if acpi is
>>> > enabled?
>>>
>>> You usually look at the .config. But I am not sure if this is provided
>>> by the Debian package. If not, then your best option would be to build
>>> your own Xen. To select ACPI, you want to use the menuconfig and select
>>> UNSUPPORTED and ACPI.
>>>
>>> Cheers,
>>>
>>> --
>>> Julien Grall
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Jiatong Shen
>>
>
>
> --
>
> Best Regards,
>
> Jiatong Shen
>


--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hello Stefano and Julien,

Could you provide more insights for debugging? I tried to connect to
serial console through ipmitool sol activate and enabled ACPI, I do see
some logs but the machine is still stuck. BMC video screen is still not
responsive and black out.

Thank you very much for the help!

Best Regards,
Jiatong Shen

On Sun, Jun 11, 2023 at 5:17?PM Jiatong Shen <yshxxsjt715@gmail.com> wrote:

> Hello Stefano and Julien,
>
> I tried to do some debugging by adding a printk inside the function
> idle_loop in file arm/domain.c. Looks like the idle function is running
> normally because the printk function is getting called without stalling.
> But the vga screen is still blacked out and the serial terminal does not
> display any login message.
>
> the grub config for xen 4.17 is
>
> submenu 'Xen hypervisor, version 4.17' $menuentry_id_option
> 'xen-hypervisor-4.17-5ebc23af-c2e2-4ac3-b308-3e82ec786c04' {
> menuentry 'Debian GNU/Linux, with Xen 4.17 and Linux 5.10.0-23-arm64'
> --class debian --class gnu-linux --class gnu --class os --class xen
> $menuentry_id_option
> 'xen-gnulinux-5.10.0-23-arm64-advanced-5ebc23af-c2e2-4ac3-b308-3e82ec786c04'
> {
> insmod part_gpt
> insmod ext2
> set root='hd0,gpt2'
> if [ x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root
> --hint-ieee1275='ieee1275//sas/disk@20000,gpt2' --hint-bios=hd0,gpt2
> --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
> 5ebc23af-c2e2-4ac3-b308-3e82ec786c04
> else
> search --no-floppy --fs-uuid --set=root
> 5ebc23af-c2e2-4ac3-b308-3e82ec786c04
> fi
> echo 'Loading Xen 4.17 ...'
> if [ "$grub_platform" = "pc" -o "$grub_platform" = "" ]; then
> xen_rm_opts=
> else
> xen_rm_opts="no-real-mode edd=off"
> fi
> xen_hypervisor /boot/xen-4.17 placeholder ${xen_rm_opts}
> echo 'Loading Linux 5.10.0-23-arm64 ...'
> xen_module /boot/vmlinuz-5.10.0-23-arm64 placeholder
> root=UUID=5ebc23af-c2e2-4ac3-b308-3e82ec786c04 ro quiet
> echo 'Loading initial ramdisk ...'
> xen_module --nounzip /boot/initrd.img-5.10.0-23-arm64
> }
>
> The code I am modifying is
>
> static void noreturn idle_loop(void)
> {
> unsigned int cpu = smp_processor_id();
>
> for ( ; ; )
> {
> dprintk(XENLOG_INFO, "running idle loop \n");
> if ( cpu_is_offline(cpu) )
> stop_cpu();
> }
> }
> }
>
> Hopes this debugging makes some sense.
>
> Best Regards,
> Jiatong Shen
>
> On Sun, Jun 11, 2023 at 12:00?PM Jiatong Shen <yshxxsjt715@gmail.com>
> wrote:
>
>> Hello Stefano,
>>
>> I am able to obtain some serial logging (by enabling debugging and
>> verbose debugging messages, hopefully select the right option). The message
>> looks like
>>
>> (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
>> (XEN) Freed 372kB init memory.
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER4
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER8
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER12
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER16
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER20
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER24
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER28
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER32
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER36
>> (XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER40
>>
>> Could you help find out where it is wrong ? Thank you very much for the
>> help!
>>
>> Best Regards,
>> Jiatong Shen
>>
>>
>> On Sat, Jun 10, 2023 at 7:15?AM Jiatong Shen <yshxxsjt715@gmail.com>
>> wrote:
>>
>>> Hello Julien,
>>>
>>> Thank you very much for your help!
>>>
>>> Best,
>>>
>>> Jiatong Shen
>>>
>>> On Fri, Jun 9, 2023 at 4:48?PM Julien Grall <julien@xen.org> wrote:
>>>
>>>> Hello,
>>>>
>>>> On 09/06/2023 03:32, Jiatong Shen wrote:
>>>> > Thank you for your answer. Can you teach me how to verify if acpi is
>>>> > enabled?
>>>>
>>>> You usually look at the .config. But I am not sure if this is provided
>>>> by the Debian package. If not, then your best option would be to build
>>>> your own Xen. To select ACPI, you want to use the menuconfig and select
>>>> UNSUPPORTED and ACPI.
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Julien Grall
>>>>
>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Jiatong Shen
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Jiatong Shen
>>
>
>
> --
>
> Best Regards,
>
> Jiatong Shen
>


--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hi,

On 13/06/2023 02:07, Jiatong Shen wrote:
> Hello Stefano and Julien,
>
> Could you provide more insights for debugging? I tried to connect to
> serial console through ipmitool sol activate and enabled ACPI, I do see
> some logs but the machine is still stuck. BMC video screen is still not
> responsive and black out.

Looking at your command line, you want to use console=hvc0 on the dom0
command line. Hopefully, this will enable more logs from the kernel and
give you an idea where it may be stuck.

Cheers,

--
Julien Grall
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hello Julien,

Thank you for your answer! Adding console=hvc0 indeed provides kernel
output serial console. Looking at the log message,
I found dom0 kernel failed to initialize a lot of device drivers (network
cards, raid cards, etc).

Is it related to iommu? I remember iommu is not enabled during the xen
kernel booting stage.

Thank you again for the help and looking forward to your reply.

Best Regards,
Jiatong Shen

On Fri, Jun 16, 2023 at 4:52?AM Julien Grall <julien@xen.org> wrote:

> Hi,
>
> On 13/06/2023 02:07, Jiatong Shen wrote:
> > Hello Stefano and Julien,
> >
> > Could you provide more insights for debugging? I tried to connect to
> > serial console through ipmitool sol activate and enabled ACPI, I do see
> > some logs but the machine is still stuck. BMC video screen is still not
> > responsive and black out.
>
> Looking at your command line, you want to use console=hvc0 on the dom0
> command line. Hopefully, this will enable more logs from the kernel and
> give you an idea where it may be stuck.
>
> Cheers,
>
> --
> Julien Grall
>


--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hi,

On 15/06/2023 22:52, Jiatong Shen wrote:
> Thank you for your answer! Adding console=hvc0 indeed provides kernel
> output serial console. Looking at the log message,
> I found dom0 kernel failed to initialize a lot of device drivers (network
> cards, raid cards, etc).
>
> Is it related to iommu?

I am afraid I can't tell without seen some logs.

>I remember iommu is not enabled during the xen
> kernel booting stage.

At the moment, the IOMMU is not hidden from dom0. So Linux may try to
use it. However, IIRC, it is only becoming a problem when booting a guest.

Best regards,

---
Julien Grall
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hello Julien,

Sorry for the delay.. I obtained the full xen log and attached it in the
mail. Please take a look when you are available. Thank you very much

Best Regards,

Jiatong Shen

On Sat, Jun 17, 2023 at 4:55?AM Julien Grall <julien@xen.org> wrote:

> Hi,
>
> On 15/06/2023 22:52, Jiatong Shen wrote:
> > Thank you for your answer! Adding console=hvc0 indeed provides
> kernel
> > output serial console. Looking at the log message,
> > I found dom0 kernel failed to initialize a lot of device drivers (network
> > cards, raid cards, etc).
> >
> > Is it related to iommu?
>
> I am afraid I can't tell without seen some logs.
>
> >I remember iommu is not enabled during the xen
> > kernel booting stage.
>
> At the moment, the IOMMU is not hidden from dom0. So Linux may try to
> use it. However, IIRC, it is only becoming a problem when booting a guest.
>
> Best regards,
>
> ---
> Julien Grall
>


--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hi,

On 20/06/2023 08:09, Jiatong Shen wrote:
> Hello Julien,
>
> Sorry for the delay.. I obtained the full xen log and attached it in the
> mail. Please take a look when you are available. Thank you very much

Thanks for sharing the logs. The following lines are interesting:

[ 1.081905] Hisilicon MBIGEN-V2 HISI0152:00: Failed to create mbi-gen
irqdomain
[ 1.082107] Hisilicon MBIGEN-V2 HISI0152:01: Failed to create mbi-gen
irqdomain
[ 1.082204] Hisilicon MBIGEN-V2 HISI0152:02: Failed to create mbi-gen
irqdomain
[ 1.082294] Hisilicon MBIGEN-V2 HISI0152:03: Failed to create mbi-gen
irqdomain
[ 1.082381] Hisilicon MBIGEN-V2 HISI0152:04: Failed to create mbi-gen
irqdomain
[ 1.082466] Hisilicon MBIGEN-V2 HISI0152:05: Failed to create mbi-gen
irqdomain

Looking at a Hisilicon Device-Tree, this is an interrupt controller
behind the GICv3 ITS. You will need to rebuild Xen with CONFIG_HAS_ITS=y.

Also, can you confirm which devices are behind the MBI-Gen? If this is
only PCI devices, then you are probably fine to give the controllers to
dom0. But for PCI passthrough, you will most likely need to implement it
a driver in Xen.

Cheers,

--
Julien Grall
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hello Julien,

Thank you very much for your reply. Can you teach me how to find the
relationship between MBI-gen and devices?
I am not sure how to find out the mbi-gen backed devices..

Best Regards,
Jiatong Shen

On Sat, Jun 24, 2023 at 4:24?PM Julien Grall <julien@xen.org> wrote:

> Hi,
>
> On 20/06/2023 08:09, Jiatong Shen wrote:
> > Hello Julien,
> >
> > Sorry for the delay.. I obtained the full xen log and attached it in
> the
> > mail. Please take a look when you are available. Thank you very much
>
> Thanks for sharing the logs. The following lines are interesting:
>
> [ 1.081905] Hisilicon MBIGEN-V2 HISI0152:00: Failed to create mbi-gen
> irqdomain
> [ 1.082107] Hisilicon MBIGEN-V2 HISI0152:01: Failed to create mbi-gen
> irqdomain
> [ 1.082204] Hisilicon MBIGEN-V2 HISI0152:02: Failed to create mbi-gen
> irqdomain
> [ 1.082294] Hisilicon MBIGEN-V2 HISI0152:03: Failed to create mbi-gen
> irqdomain
> [ 1.082381] Hisilicon MBIGEN-V2 HISI0152:04: Failed to create mbi-gen
> irqdomain
> [ 1.082466] Hisilicon MBIGEN-V2 HISI0152:05: Failed to create mbi-gen
> irqdomain
>
> Looking at a Hisilicon Device-Tree, this is an interrupt controller
> behind the GICv3 ITS. You will need to rebuild Xen with CONFIG_HAS_ITS=y.
>
> Also, can you confirm which devices are behind the MBI-Gen? If this is
> only PCI devices, then you are probably fine to give the controllers to
> dom0. But for PCI passthrough, you will most likely need to implement it
> a driver in Xen.
>
> Cheers,
>
> --
> Julien Grall
>


--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hello Julien,

I tried to enable has_its and looks like the log is different. But dom0
OS still failed to boot up.. Could you please
have a look at the log when you are available? Thank you very much for the
help.

Best regards,
Jiatong Shen

On Sat, Jun 24, 2023 at 10:54?PM Jiatong Shen <yshxxsjt715@gmail.com> wrote:

> Hello Julien,
>
> Thank you very much for your reply. Can you teach me how to find the
> relationship between MBI-gen and devices?
> I am not sure how to find out the mbi-gen backed devices..
>
> Best Regards,
> Jiatong Shen
>
> On Sat, Jun 24, 2023 at 4:24?PM Julien Grall <julien@xen.org> wrote:
>
>> Hi,
>>
>> On 20/06/2023 08:09, Jiatong Shen wrote:
>> > Hello Julien,
>> >
>> > Sorry for the delay.. I obtained the full xen log and attached it
>> in the
>> > mail. Please take a look when you are available. Thank you very much
>>
>> Thanks for sharing the logs. The following lines are interesting:
>>
>> [ 1.081905] Hisilicon MBIGEN-V2 HISI0152:00: Failed to create mbi-gen
>> irqdomain
>> [ 1.082107] Hisilicon MBIGEN-V2 HISI0152:01: Failed to create mbi-gen
>> irqdomain
>> [ 1.082204] Hisilicon MBIGEN-V2 HISI0152:02: Failed to create mbi-gen
>> irqdomain
>> [ 1.082294] Hisilicon MBIGEN-V2 HISI0152:03: Failed to create mbi-gen
>> irqdomain
>> [ 1.082381] Hisilicon MBIGEN-V2 HISI0152:04: Failed to create mbi-gen
>> irqdomain
>> [ 1.082466] Hisilicon MBIGEN-V2 HISI0152:05: Failed to create mbi-gen
>> irqdomain
>>
>> Looking at a Hisilicon Device-Tree, this is an interrupt controller
>> behind the GICv3 ITS. You will need to rebuild Xen with CONFIG_HAS_ITS=y.
>>
>> Also, can you confirm which devices are behind the MBI-Gen? If this is
>> only PCI devices, then you are probably fine to give the controllers to
>> dom0. But for PCI passthrough, you will most likely need to implement it
>> a driver in Xen.
>>
>> Cheers,
>>
>> --
>> Julien Grall
>>
>
>
> --
>
> Best Regards,
>
> Jiatong Shen
>


--

Best Regards,

Jiatong Shen
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
On 24/06/2023 15:54, Jiatong Shen wrote:
> Hello Julien,

Hi,

> Thank you very much for your reply. Can you teach me how to find the
> relationship between MBI-gen and devices?
> I am not sure how to find out the mbi-gen backed devices..

I am afraid I don't have any experience with the MBI-gen. I have also
looked at one Hisilicon Device-Tree but I don't know whether this is the
one for your board.

My recommendation would be to check if there is any technical
documentation for your HW.

Cheers,

--
Julien Grall
Re: Asking for help to debug xen efi on Kunpeng machine [ In reply to ]
Hi Julien,

Thank you for your answer. Do you have any advice on how to debug the
issue?
I have very little experience with xen so I think I still need
debugging even if I can
get MBI-gen's tech doc...

Best regards,
Jiatong Shen

On Fri, Jun 30, 2023 at 5:42?AM Julien Grall <julien@xen.org> wrote:

> On 24/06/2023 15:54, Jiatong Shen wrote:
> > Hello Julien,
>
> Hi,
>
> > Thank you very much for your reply. Can you teach me how to find the
> > relationship between MBI-gen and devices?
> > I am not sure how to find out the mbi-gen backed devices..
>
> I am afraid I don't have any experience with the MBI-gen. I have also
> looked at one Hisilicon Device-Tree but I don't know whether this is the
> one for your board.
>
> My recommendation would be to check if there is any technical
> documentation for your HW.
>
> Cheers,
>
> --
> Julien Grall
>


--

Best Regards,

Jiatong Shen