The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device-type...
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Don't need to set connection_list command?
https://validation.linaro.org/static/docs/v2/lava-scheduler-device-dictionar... It say: connection_list - the list of hardware ports which are configured for serial connections to the device.
在 2018-08-14 20:24:06，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device-type...
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
_______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam...
Zoran
On Tue, Aug 14, 2018 at 2:29 PM, ljh_dev ljh_dev@126.com wrote:
Don't need to set connection_list command? https://validation.linaro.org/static/docs/v2/lava-scheduler- device-dictionary.html It say: connection_list - the list of hardware ports which are configured for serial connections to the device.
在 2018-08-14 20:24:06，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device- types/beaglebone-black.jinja2
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hi,Zoran, https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam... Under boot label, it has some sub labels such as oe,matser,nfs .. Could you explain to me about the relationship among oe,matser,nfs ..
在 2018-08-14 20:37:52，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam...
Zoran
On Tue, Aug 14, 2018 at 2:29 PM, ljh_dev ljh_dev@126.com wrote:
Don't need to set connection_list command?
https://validation.linaro.org/static/docs/v2/lava-scheduler-device-dictionar... It say: connection_list - the list of hardware ports which are configured for serial connections to the device.
在 2018-08-14 20:24:06，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device-type...
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
_______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hello 126.com,
Two things here: [1] your question has almost nothing to do with Lava, but almost everything with kernel system configuration; [2] I'll do very short explanation (my way), and then you need to google it, since there are megatons of materials out there.
We start from the boot arguments, which translates directly to kernel command line:
u-boot: oe: - setenv bootargs 'console=ttyO0,115200n8 root=/dev/mmcblk0p5 rootwait ro' master: - setenv bootargs 'console=ttyO0,115200n8 root=LABEL=testrootfs rootwait ro' nfs: - "setenv nfsargs 'setenv bootargs console=ttyO0,115200n8 root=/dev/nfs rw nfsroot={SERVER_IP}:{NFSROOTFS},tcp,hard,intr ip=dhcp'" nbd: - setenv nbdkbootargs ' ip=dhcp nbd.server={NBDSERVERIP} nbd.port={NBDSERVERPORT} root=/dev/ram0 ramdisk_size=16384 rootdelay=7 fixrtc nocompcache vram=48M omapfb.vram=0:24M mem=456M@0x80000000 mem=512M@0xA0000000 rootdelay=5 ip=dhcp' - setenv bootargs verbose console=ttyO2,115200n8 rw ${nbdbasekargs} ${nbdkbootargs} ramdisk: - setenv bootargs 'console=ttyO0,115200n8 root=/dev/ram0 ip=dhcp' usb: - setenv bootargs 'console=ttyO0,115200n8 root={ROOT} ip=dhcp'
As you see, each way to boot differs by how rootfs is mounted to the system. OE boots from flash, ramdisk from ram0 (initramfs), nfs uses rootfs from the host, mounting to it using network it is physically attached to it, and so on, and so on...
But, in order to do this, you need to manipulate initial kernel menuconfig, called mostly defconfig, defined in the kernel root tree. Then, in order to choose how to boot, you need to manipulate CONFIG (.config).
As for example, to make system to boot from initramfs, you have to have the following set in .config: https://github.com/ZoranStojsavljevic/cip-rt-misc/blob/master/configs/bbb/co...
So, from here you continue walking yourself. :-)
Good Luck, Zoran _______
On Tue, Aug 14, 2018 at 3:53 PM, ljh_dev ljh_dev@126.com wrote:
Hi,Zoran, https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam... Under boot label, it has some sub labels such as oe,matser,nfs .. Could you explain to me about the relationship among oe,matser,nfs ..
在 2018-08-14 20:37:52，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam...
Zoran
On Tue, Aug 14, 2018 at 2:29 PM, ljh_dev ljh_dev@126.com wrote:
Don't need to set connection_list command?
https://validation.linaro.org/static/docs/v2/lava-scheduler-device-dictionar... It say: connection_list - the list of hardware ports which are configured for serial connections to the device.
在 2018-08-14 20:24:06，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device-type...
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hi Zoran, How does dispatcher select ot,master or nfs at startup?
In adition,in https://validation.linaro.org/static/docs/v2/actions-boot.html#index-9, -setenv loadkernel 'tftp {KERNEL_ADDR} {KERNEL}' It say the {KERNEL} will be substituted. Where is {KERNEL} variable defined? When I submit job definition by web ui,I did't find where to define {KERNEL} variable
At 2018-08-15 14:04:36, "Zoran S" zoran.stojsavljevic.de@gmail.com wrote:
Hello 126.com,
Two things here: [1] your question has almost nothing to do with Lava, but almost everything with kernel system configuration; [2] I'll do very short explanation (my way), and then you need to google it, since there are megatons of materials out there.
We start from the boot arguments, which translates directly to kernel command line:
u-boot: oe: - setenv bootargs 'console=ttyO0,115200n8 root=/dev/mmcblk0p5 rootwait ro' master: - setenv bootargs 'console=ttyO0,115200n8 root=LABEL=testrootfs rootwait ro' nfs: - "setenv nfsargs 'setenv bootargs console=ttyO0,115200n8 root=/dev/nfs rw nfsroot={SERVER_IP}:{NFSROOTFS},tcp,hard,intr ip=dhcp'" nbd: - setenv nbdkbootargs ' ip=dhcp nbd.server={NBDSERVERIP} nbd.port={NBDSERVERPORT} root=/dev/ram0 ramdisk_size=16384 rootdelay=7 fixrtc nocompcache vram=48M omapfb.vram=0:24M mem=456M@0x80000000 mem=512M@0xA0000000 rootdelay=5 ip=dhcp' - setenv bootargs verbose console=ttyO2,115200n8 rw ${nbdbasekargs} ${nbdkbootargs} ramdisk: - setenv bootargs 'console=ttyO0,115200n8 root=/dev/ram0 ip=dhcp' usb: - setenv bootargs 'console=ttyO0,115200n8 root={ROOT} ip=dhcp'
As you see, each way to boot differs by how rootfs is mounted to the system. OE boots from flash, ramdisk from ram0 (initramfs), nfs uses rootfs from the host, mounting to it using network it is physically attached to it, and so on, and so on...
But, in order to do this, you need to manipulate initial kernel menuconfig, called mostly defconfig, defined in the kernel root tree. Then, in order to choose how to boot, you need to manipulate CONFIG (.config).
As for example, to make system to boot from initramfs, you have to have the following set in .config: https://github.com/ZoranStojsavljevic/cip-rt-misc/blob/master/configs/bbb/co...
So, from here you continue walking yourself. :-)
Good Luck, Zoran _______
On Tue, Aug 14, 2018 at 3:53 PM, ljh_dev ljh_dev@126.com wrote:
Hi,Zoran, https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam... Under boot label, it has some sub labels such as oe,matser,nfs .. Could you explain to me about the relationship among oe,matser,nfs ..
在 2018-08-14 20:37:52，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam...
Zoran
On Tue, Aug 14, 2018 at 2:29 PM, ljh_dev ljh_dev@126.com wrote:
Don't need to set connection_list command?
https://validation.linaro.org/static/docs/v2/lava-scheduler-device-dictionar... It say: connection_list - the list of hardware ports which are configured for serial connections to the device.
在 2018-08-14 20:24:06，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device-type...
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
On Tue, 14 Aug 2018 at 14:56, ljh_dev ljh_dev@126.com wrote:
Hi,Zoran,
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam... Under boot label, it has some sub labels such as oe,matser,nfs ..
Those are blocks of instructions used to boot that particular method in U-Boot.
Typically you can ignore "master", that's from older styles. NFS differs from ramdisk by setting the variables to tell the kernel where to find the NFS, for example.
The nice thing with U-Boot is that most U-Boot device integrations don't need to make any changes here.
It sounds, from other messages about this device, that your device might need some changes. So limit yourself to those instruction blocks which will be useful for your testing - typically ramdisk and nfs. You might be interested in nbd but ums is specialised to devices which offer a USB mass storage interface from U-Boot to write to local flash etc. The sata commands are for the (few) devices which can load files from SATA within U-Boot. It doesn't hurt to have these instruction blocks listed - the block to use is determined by the test job:
https://staging.validation.linaro.org/scheduler/job/233049/definition#deflin...
That test job specifies commands: nfs so the nfs instruction block is sent to the DUT.
oe and master are no longer used.
https://git.linaro.org/lava/lava.git/tree/lava_scheduler_app/tests/device-ty...
base-uboot has become quite complex over time - possibly the best view is to look at a working U-Boot device dictionary and compare the Jinja2 view with the YAML view:
https://staging.validation.linaro.org/scheduler/device/staging-black03/devic...
Could you explain to me about the relationship among oe,matser,nfs ..
在 2018-08-14 20:37:52，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam...
Zoran
On Tue, Aug 14, 2018 at 2:29 PM, ljh_dev ljh_dev@126.com wrote:
Don't need to set connection_list command?
https://validation.linaro.org/static/docs/v2/lava-scheduler-device-dictionar... It say: connection_list - the list of hardware ports which are configured for serial connections to the device.
在 2018-08-14 20:24:06，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device-type...
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
The nice thing with U-Boot is that most U-Boot device integrations don't
need to make any changes here.
Hello Neil,
With all due respect, this, what you have presented to us, all, as lava-dispatcher U-Boot configuration: https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam...
Was so useful (👍👍👍) and so well done, that I do NOT use these for Lava testing, rather I use fragments of these to test the full systems NOT using Lava, albeit to simulate virtual drivers on HW platforms... I just use these fragments to upgrade U-Boot ENV variables on the embedded targets using Lava VMs NOT for Lava testing (I use my own scripts based on the above net pointer), rather for downloading true system configurations with full YOCTO initramfs implemented/ported applications to the DUT platforms. One time testing environment, wrt to testing, discovering the problems, and fixing YOCTO build system by fixing YOCTO recipes, bitbake scripts, adding new packages, reusing old packages, and so on... 😎
Kudos to you and the Lava team for giving me keys-in-hand for U-Boot initramfs commands' upgrades!
Lava is powerful tool. Both ways. Mostly NOT to be used for Lava testing. in my case. Rather to reuse Lava parts for DUT complete application simulation, temporarily stored in initramfs and mounted to the kernel!
Another use case for Lava, after all. ✌
Thank you, Zoran _______
On Tue, Aug 28, 2018 at 9:27 AM Neil Williams neil.williams@linaro.org wrote:
On Tue, 14 Aug 2018 at 14:56, ljh_dev ljh_dev@126.com wrote:
Hi,Zoran,
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam... Under boot label, it has some sub labels such as oe,matser,nfs ..
Those are blocks of instructions used to boot that particular method in U-Boot.
Typically you can ignore "master", that's from older styles. NFS differs from ramdisk by setting the variables to tell the kernel where to find the NFS, for example.
The nice thing with U-Boot is that most U-Boot device integrations don't need to make any changes here.
It sounds, from other messages about this device, that your device might need some changes. So limit yourself to those instruction blocks which will be useful for your testing - typically ramdisk and nfs. You might be interested in nbd but ums is specialised to devices which offer a USB mass storage interface from U-Boot to write to local flash etc. The sata commands are for the (few) devices which can load files from SATA within U-Boot. It doesn't hurt to have these instruction blocks listed - the block to use is determined by the test job:
https://staging.validation.linaro.org/scheduler/job/233049/definition#deflin...
That test job specifies commands: nfs so the nfs instruction block is sent to the DUT.
oe and master are no longer used.
https://git.linaro.org/lava/lava.git/tree/lava_scheduler_app/tests/device-ty...
base-uboot has become quite complex over time - possibly the best view is to look at a working U-Boot device dictionary and compare the Jinja2 view with the YAML view:
https://staging.validation.linaro.org/scheduler/device/staging-black03/devic...
Could you explain to me about the relationship among oe,matser,nfs ..
在 2018-08-14 20:37:52，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.yam...
Zoran
On Tue, Aug 14, 2018 at 2:29 PM, ljh_dev ljh_dev@126.com wrote:
Don't need to set connection_list command?
https://validation.linaro.org/static/docs/v2/lava-scheduler-device-dictionar... It say: connection_list - the list of hardware ports which are configured for serial connections to the device.
在 2018-08-14 20:24:06，"Zoran S" zoran.stojsavljevic.de@gmail.com 写道：
https://github.com/ZoranStojsavljevic/lava-server-vm/blob/master/device-type...
Zoran _______
On Tue, Aug 14, 2018 at 1:42 PM, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
On Tue, 14 Aug 2018 at 12:42, ljh_dev ljh_dev@126.com wrote:
The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?
You will need a service which maps the device node to a serial interface - we typically recommend ser2net.
Always use the /dev/serial/by-id/ path and not the device-node name because the node can enumerate as ttyUSB1 or ttyUSB0 depending on local configuration but the /dev/serial/by-id/ path does not change.
Something like:
# UART1 - nearest power connector - current kernel console. 6080:telnet:0:/dev/serial/by-id/usb-FTDI_TTL232RG-VREG1V8_FTXODY29-if00-port0:115200 8DATABITS NONE 1STOPBIT banner LOCAL
This allows the connection_command to be "telnet localhost 6080" and this can be tested locally.
https://git.linaro.org/lava/lava-lab.git/tree/staging.validation.linaro.org/...
{% set connection_list = ['uart0'] %} {% set connection_tags = {'uart0': ['primary', 'telnet']} %} {% set connection_commands = {'uart0': 'telnet localhost 7105'} %}
/etc/ser2net.conf needs to be modified on the worker if you want to use localhost. (This is expected because the DUT USB serial cable is plugged into the worker in most cases, so that the /dev/serial/by-id/ path exists on the worker.)
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org
-
ljh_dev -
Neil Williams -
Zoran S