lava-users June 2025

lava-users@lists.lavasoftware.org

3 participants
3 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

Using LAVA to transfer file via Ymodem from LAVA dispatcher(HOST machine) to DUT

by hina.hafeez＠10xengineers.ai

Hi LAVA users, I have set-up a LAVA server, dispatcher and connected my device (banana-pi) board serially via UART to host machine on which dispatcher is running. I have defined a job which uses deploy "tmpfs" to download .itb file from local file server. After that, under "boot" action, i am using u-boot method to boot the device. Output: 1. deploy images section runs successfully 2. uboot action starts 3. After connecting to device using telnet, device is reset(pdu-reboot). 4. Device enters in Y modem state waiting for image to get transferred. 5. After some time, "CCC CCCCCCC[ 99.943] spl: ymodem err - Timed out" Issue/Question: 6. At this stage, i want LAVA dispatcher(HOST machine) to send .itb file over UART using Ymodem to device. 7. But LAVA is unable to execute this command "sz -Y --ymodem /uboot-opensbi.itb < /dev/ttyUSB0 > /dev/ttyUSB0" to transfer opensbi.itb file to device. 8. I need to know what am i missing in writing job definition for this case. 9. Which device template should i use and how it should be extended. 10. is there any job definition syntax to fulfill my requirement? Regards,

3 months, 3 weeks

Open ID Connect (OIDC) authentication providers with LAVA

by sweta.ghosh＠nagarro.com

Hello Team, I am trying to use Azure AD for user authentication in LAVA. I followed the document https://validation.linaro.org/static/docs/v2/authentication.html#using-open… and created a yaml file with all details under /etc/lava-server/settings.d and restarted lava-server-gunicorn.service. Additionally , added ssl_header configuration to trust X-Forwarded-Proto header for detecting HTTPS. cat secure_proxy_ssl_header.yaml SECURE_PROXY_SSL_HEADER: - HTTP_X_FORWARDED_PROTO - https During sign in I am able get Microsoft login page but after successfully login I get "Bad Request (400)" . Could you please suggest if Lava can work with mozilla-django-oidc or if i am missing any configuration.

4 months, 1 week

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users June 2025