lava-users July 2025

lava-users@lists.lavasoftware.org

4 participants
5 discussions

Connect a device through serial without PDU

by Ali Tariq

Hello, I am trying to connect a RISC-V VisionFive 2 device with the LAVA web server. I do not have a PDU at the moment and I do not know which one will be appropriate for this device setup. The LAVA master and worker are running on the same machine, so I have localhost set up. I added the following device dictionary for VisionFive 2. {% extends 'jh7100-visionfive.jinja2' %} {% set console_backend = 'serial' %} {% set serial_port = '/dev/ttyUSB0' %} {% set serial_baud_rate = 115200 %} The dictionary template, which is extended for VisionFive 2, is from the VisionFive 1 device type. As I won't be needing initramfs and other uboot env variables, I am using visionfive 1's dictionary template just for getting the setup to work. Following is the VisionFive 1 dictionary template. {% extends 'base-uboot.jinja2' %} {% set uboot_mkimage_arch = 'riscv' %} {% set console_device = console_device|default('ttyS0') %} {% set baud_rate = baud_rate|default(115200) %} {% set booti_kernel_addr = '0x84000000' %} {% set booti_dtb_addr = '0x88000000' %} {% set booti_ramdisk_addr = '0x88300000' %} {% set uboot_initrd_high = '0xffffffffffffffff' %} {% set uboot_fdt_high = '0xffffffffffffffff' %} {% set bootloader_prompt = 'VisionFive#' %} {% set uboot_tftp_commands = [ "tftpboot {KERNEL_ADDR} {KERNEL}", "tftpboot {RAMDISK_ADDR} {RAMDISK}", "tftpboot {DTB_ADDR} {DTB}"] -%} I was able to run a job on QEMU. But the VisionFive 2 is not detected by the LAVA web server. The physical connection is complete because I can use picocom on my computer to attach to the VisionFive 2 using the command sudo picocom -b 115200 /dev/ttyUSB0. I created several job definitions just for testing the setup but they all are just loading. The device health check is bad. Following is the simplest job that I am trying to run and see if it completes. job_name: simple-uboot-test device_type: visionfive2 priority: medium visibility: public timeouts: job: minutes: 5 actions: - deploy: timeout: minutes: 1 to: u-boot - boot: method: bootloader bootloader: u-boot connection: serial commands: - printenv But all the jobs are on infinite loading. This is my first time connecting a physical device with the LAVA web server, so I would appreciate it if someone could tell me what the issue is here. Regards, Ali

1 week

Is there any job using the ssh.jinja2 template as a learning example?

by 93831920＠qq.com

Is there any job using the ssh.jinja2 template as a learning example? Thank you

1 month, 2 weeks

Not able to update default to qemu.jinja2 with updated configuration

by sweta.ghosh＠nagarro.com

Hello, I would like to replace -net legacy values with -netdev as netdevice in /etc/lava-server/dispatcher-config/device-types/qemu.jinja2 file but even after creating new jinja file my device is not able to identify it. I have tried restarting all the LAVA services but still not able to . Could you please share the how can I change or update existing jinja file. Thanks, Sweta

2 months, 2 weeks

how to discrib a ssh device?

by 93831920＠qq.com

Device is RAM, directly connected to the FT4232H through JTAG, FT4232T connected to the windows host through USB-MicroUsb, the windows host provides the telnet test command interface to the workers of the lava automated test environment through the telnet server, in this scenario, how to create the device type, device and job in lava, Can you use lava to automate testing of RAM?

2 months, 2 weeks

Running Lava in docker on Ubuntu.

by Gregory Machin

Hi, I have been asked by our hardware dev team to stand up a server that will run Lava. I was advised that Debian was the only supported OS. But as they will be running the official docker images is there any reason I couldn't deploy use Ubuntu 24.04 LTS ? Thank you Greg

3 months, 1 week

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users July 2025