Hey,
I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know.
I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices?
Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers!
Best regards, Olli
Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files]
- boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]
Hi, Oliver,
I think current "uuu boot action" did not consider your use case, it won't accept commands from device/devicetypes. It needs code changes to support your scenario ...
-----Original Message----- From: Westermann, Oliver Oliver.Westermann@cognex.com Sent: Tuesday, November 17, 2020 4:27 PM To: lava-users@lists.lavasoftware.org; Larry Shen larry.shen@nxp.com Subject: [EXT] Moving boot commands from definition to device for UUU boot action
Caution: EXT Email
Hey,
I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know.
I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices?
Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers!
Best regards, Olli
Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files]
- boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]
Hey Larry,
Thanks for the swift response.
I've to admit I'm not really deep in the lava development yet, but I've to admit I got curious and I poked around in the other deployment methods. However I did not find a method that seemed to have what I wanted. Your response sounds like you have a feeling what should be needed, could you share that feeling? I looking for a "take a look at the deployment method X, it has the parsing you're looking for implemented" 😉 So I can take some "inspiration" and maybe come up with a PR for LAVA 😊
Best regards, Olli
-----Ursprüngliche Nachricht----- Von: Larry Shen larry.shen@nxp.com Gesendet: Dienstag, 17. November 2020 10:50 An: Westermann, Oliver Oliver.Westermann@cognex.com; lava-users@lists.lavasoftware.org Betreff: RE: [EXT] Moving boot commands from definition to device for UUU boot action
Hi, Oliver,
I think current "uuu boot action" did not consider your use case, it won't accept commands from device/devicetypes. It needs code changes to support your scenario ...
-----Original Message----- From: Westermann, Oliver Oliver.Westermann@cognex.com Sent: Tuesday, November 17, 2020 4:27 PM To: lava-users@lists.lavasoftware.org; Larry Shen larry.shen@nxp.com Subject: [EXT] Moving boot commands from definition to device for UUU boot action
Caution: EXT Email
Hey,
I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know.
I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices?
Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers!
Best regards, Olli
Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files]
- boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]
I didn't take a detail look, you may need to change next I guess: https://git.lavasoftware.org/lava/lava/-/blob/master/lava_dispatcher/actions...
-----Original Message----- From: Westermann, Oliver Oliver.Westermann@cognex.com Sent: Wednesday, November 18, 2020 3:48 PM To: Larry Shen larry.shen@nxp.com; lava-users@lists.lavasoftware.org Subject: AW: [EXT] Moving boot commands from definition to device for UUU boot action
Caution: EXT Email
Hey Larry,
Thanks for the swift response.
I've to admit I'm not really deep in the lava development yet, but I've to admit I got curious and I poked around in the other deployment methods. However I did not find a method that seemed to have what I wanted. Your response sounds like you have a feeling what should be needed, could you share that feeling? I looking for a "take a look at the deployment method X, it has the parsing you're looking for implemented" 😉 So I can take some "inspiration" and maybe come up with a PR for LAVA 😊
Best regards, Olli
-----Ursprüngliche Nachricht----- Von: Larry Shen larry.shen@nxp.com Gesendet: Dienstag, 17. November 2020 10:50 An: Westermann, Oliver Oliver.Westermann@cognex.com; lava-users@lists.lavasoftware.org Betreff: RE: [EXT] Moving boot commands from definition to device for UUU boot action
Hi, Oliver,
I think current "uuu boot action" did not consider your use case, it won't accept commands from device/devicetypes. It needs code changes to support your scenario ...
-----Original Message----- From: Westermann, Oliver Oliver.Westermann@cognex.com Sent: Tuesday, November 17, 2020 4:27 PM To: lava-users@lists.lavasoftware.org; Larry Shen larry.shen@nxp.com Subject: [EXT] Moving boot commands from definition to device for UUU boot action
Caution: EXT Email
Hey,
I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know.
I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices?
Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers!
Best regards, Olli
Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files]
- boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]
lava-users@lists.lavasoftware.org
-
Larry Shen -
Westermann, Oliver