> What's the best way to solve the issue. How can I tell LAVA not to deal with the RAMDISK at all?

    I saw this problem on some other board (don't remember which one). The
    quick fix is to replace the bootloader commands with custom ones
    either in device dictionary or in the job. In the long run this needs
    to be fixed in LAVA. I'll create a ticket if there isn't one already.
    For updating the commands in the job, here is the snippet:

     - boot:
        timeout:
          minutes: 10
        method: u-boot
        commands:
          - setenv autoload no
          - dhcp
          - env print
          - setenv serverip {SERVER_IP}
          - tftp {KERNEL_ADDR} {KERNEL}
          - tftp {DTB_ADDR} {DTB}
          - setenv bootargs 'console=ttyS0,115200n8 root=/dev/nfs rw
    nfsroot={NFS_SERVER_IP}:{NFSROOTFS},tcp,hard,intr,vers=3
            rootwait coherent_pool=2M ip=dhcp'
          - '{BOOTX}'

    This should do the trick for now.

    milosz

Milosz,

I've come up with a similar solution. I've added the following lines into the device type of the board:

{% set uboot_tftp_commands = [
    "tftp {KERNEL_ADDR} {KERNEL}",
    "tftp {DTB_ADDR} {DTB}"]
-%}

Thanks



IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users