Re: [PATCH v4 6/7] tests/functional/riscv64: Add boot test for Milk-V Duo board

[Kuan-Wei Chiu <visitorckw@gmail.com>]

On Fri, Sep 25, 2026 at 04:02:45AM +0000, Alistair Francis wrote:
> On Sat, 2026-08-22 at 19:43 +0000, Kuan-Wei Chiu wrote:
> > Add a functional boot test for the Milk-V Duo board to validate the
> > end-to-end boot flow.
> > 
> > $ ./build/run ./tests/functional/riscv64/test_milkv_duo.py
> > TAP version 13
> > ok 1 test_milkv_duo.MilkvDuoMachine.test_riscv64_milkv_duo
> > 1..1
> > 
> > Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> > ---
> >  MAINTAINERS                                |  1 +
> >  tests/functional/riscv64/meson.build       |  1 +
> >  tests/functional/riscv64/test_milkv_duo.py | 50
> > ++++++++++++++++++++++
> >  3 files changed, 52 insertions(+)
> >  create mode 100755 tests/functional/riscv64/test_milkv_duo.py
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 245eb7bb58..3f79334c59 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1861,6 +1861,7 @@ F: hw/riscv/milkv_duo.c
> >  F: include/hw/char/dw8250.h
> >  F: include/hw/misc/cv1800b_clk.h
> >  F: include/hw/riscv/cv1800b.h
> > +F: tests/functional/riscv64/test_milkv_duo.py
> >  F: tests/qtest/milkv-duo-test.c
> >  
> >  RX Machines
> > diff --git a/tests/functional/riscv64/meson.build
> > b/tests/functional/riscv64/meson.build
> > index d1a3e6c2bf..8a4f1d00f9 100644
> > --- a/tests/functional/riscv64/meson.build
> > +++ b/tests/functional/riscv64/meson.build
> > @@ -18,4 +18,5 @@ tests_riscv64_system_thorough = [
> >    'sifive_u',
> >    'tt_atlantis',
> >    'tuxrun',
> > +  'milkv_duo',
> >  ]
> > diff --git a/tests/functional/riscv64/test_milkv_duo.py
> > b/tests/functional/riscv64/test_milkv_duo.py
> > new file mode 100755
> > index 0000000000..aff247e61f
> > --- /dev/null
> > +++ b/tests/functional/riscv64/test_milkv_duo.py
> > @@ -0,0 +1,50 @@
> > +#!/usr/bin/env python3
> > +#
> > +# Functional test that boots a Linux kernel on a Milk-V Duo machine
> > +#
> > +# Copyright (c) 2026 Kuan-Wei Chiu <visitorckw@gmail.com>
> > +#
> > +# SPDX-License-Identifier: GPL-2.0-or-later
> > +
> > +from qemu_test import LinuxKernelTest, Asset
> > +from qemu_test import wait_for_console_pattern
> > +
> > +class MilkvDuoMachine(LinuxKernelTest):
> > +
> > +    timeout = 120
> > +
> > +    ASSET_KERNEL = Asset(
> > +       
> > 'https://github.com/visitorckw/milkv-duo-qemu-assets/releases/downloa
> > d/v1.0/Image',
> > +       
> > '3f157ecfcb86d28bfcff9fd3c1a43f60a8513b1919739fdc9a4d946aba35b2af'
> > +    )
> > +    ASSET_DTB = Asset(
> > +       
> > 'https://github.com/visitorckw/milkv-duo-qemu-assets/releases/downloa
> > d/v1.0/cv1800b-milkv-duo.dtb',
> > +       
> > '2a5d165f64c4b2d55bba282b2974941ab223f6f5220c2e7721e35ab81311c098'
> > +    )
> > +    ASSET_ROOTFS = Asset(
> > +       
> > 'https://github.com/visitorckw/milkv-duo-qemu-assets/releases/downloa
> > d/v1.0/rootfs.ext4',
> > +       
> > '9e7de9222ab4a79d1291866453aa47cd67a543216df6159bf9b42d055240a676'
> > +    )
> 
> Is there a more official source we could use?
> 
I initially tried booting the board using milk-v duo's buildroot SDK
release. It failed to boot probably because their downstream device
tree and kernel rely on many custom out oftree bindings that differ
from mainline Linux. This is why I originally hosted my own mainline
compiled images on my personal github.

However, I just experimented with switching to tuxboot assets similar
to how sifive_u is tested, and I can confirm that booting with the
tuxboot kernel, dtb, and rootfs works perfectly all the way to the
shell.

I'll update the test to fetch these assets from tuxboot.

Regards,
Kuan-Wei