Hi Leo, I took a look at the raw log. It seems that the test-case is outputting too many characters onto the u-boot prompt due to which the log size has gotten exceeded. Can you somehow increase the log size and then try ?
Thanks. On Wed, Oct 5, 2022 at 11:47 AM Leo Liang <ycli...@andestech.com> wrote: > > Hi Kautuk, > > On Fri, Sep 23, 2022 at 12:33:20PM +0530, Kautuk Consul wrote: > > To enable semihosting we also need to enable the following > > configs in defconfigs: > > CONFIG_SEMIHOSTING > > CONFIG_SPL_SEMIHOSTING > > CONFIG_SEMIHOSTING_SERIAL > > CONFIG_SERIAL_PROBE_ALL > > CONFIG_SPL_FS_EXT4 > > CONFIG_SPL_FS_FAT > > > > Signed-off-by: Kautuk Consul <kcon...@ventanamicro.com> > > --- > > configs/qemu-riscv32_defconfig | 4 ++++ > > configs/qemu-riscv32_smode_defconfig | 4 ++++ > > configs/qemu-riscv32_spl_defconfig | 7 +++++++ > > configs/qemu-riscv64_defconfig | 4 ++++ > > configs/qemu-riscv64_smode_defconfig | 4 ++++ > > configs/qemu-riscv64_spl_defconfig | 7 +++++++ > > 6 files changed, 30 insertions(+) > > This patch set seems to cause some CI error. > (https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/13667) > Could you please take a look at it? > > Besides, will anything go wrong if we do not attach a debugger but enable > semihosting on qemu? > > Best regards, > Leo
