Hi, I think the lava web document is relatively simple.I still have some basic questions that didn’t understand. I want to add new real board(for example the arm development board,includes serial,ethernet interface etc)into lava environment. The board had ordinary uboot program, and uboot can download linux kernel image by ethernet interface. If treat it as DUT to run test,do the uboot and kernel program need to be modified or both configuration need to be modified?
On Wed, 8 Aug 2018 at 11:36, ljh_dev ljh_dev@126.com wrote:
Hi, I think the lava web document is relatively simple.I still have some basic questions that didn’t understand. I want to add new real board(for example the arm development board,includes serial,ethernet interface etc)into lava environment. The board had ordinary uboot program, and uboot can download linux kernel image by ethernet interface. If treat it as DUT to run test,do the uboot and kernel program need to be modified or both configuration need to be modified?
The U-Boot environment might need to be modified for automation - you should ensure that the bootdelay is set to something sensible (at least 5, preferably 10 seconds) so that the Hit any key to interrupt autoboot prompt will always be caught.
Details from the current U-Boot environment are going to be needed to create a new Jinja2 device-type template file for these DUTs. That's covered in the Device Integration - U-Boot section of the docs.
The kernel image doesn't typically need modification - if you can boot the kernel manually using TFTP then the Jinja2 device-type instructions should work for the same kernel image.