On Thu, 22 Nov 2018 at 12:34, Manoj Tiwary manojtiwary22@gmail.com wrote:

Hi all,

In Tftp deploy , How to give new set of u-boot bootargs by modifying device configuration file? I've tried by giving: {% set base_kernel_args = "setenv bootargs console=serial1,115200 console=tty1 root=/dev/ram0 ip=dhcp rootwait" %}

First, don't try to change all those values in one setting.

Which values actually need to be changed? root=/dev/ram0 is the default for a ramdisk, ip=dhcp is default for base.

Not all TFTP deployments are U-Boot, so you need to let us know if you are using U-Boot or something else.

You can define console_device to change the value passed to console= but the baud rate should include parity and databits as well, so 115200n8 - those are defaults.

{% set console_device = "serial1" %}

Generally, do not change any variable prefixed with base_ because the change will not take effect. There will be an alternative argument for each use of the base_ variable.

See https://master.lavasoftware.org/static/docs/v2/simple-admin.html#overriding-...

Simplest thing to do is make changes in the device dictionary and check the rendered YAML output - there is no need to run a test job until you are sure that the various settings, combined, have given you the right values.

But it is not taking these args. Please suggest the modifications I have to make.

Thanks and regards, Manoj _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

On Thu, 22 Nov 2018 at 13:30, Manoj Tiwary manojtiwary22@gmail.com wrote:

I'm using tftp with U-Boot. Default bootargs are setenv bootargs 'root=/dev/ram0 earlycon=uart8250,mmio32,0x3f215040 ip=dhcp'

When I boot with these arguments LAVA won't get any serial data the kernel messages stops at [ 0.018988] console [tty0] enabled [ 0.022435] bootconsole [uart8250] disabled "lvl": "warning", "msg": "ShellCommand command timed out.: Sending # in case of corruption.

Then I gave Set console_device=serial1 Now the serial data is coming but kernel boot stops at [ 16.680021] bcm2835-aux-uart 3f215040.serial: unable to register 8250 port - -28

So , I wanted to try by removing earlycon bootarg.

earlycon doesn't appear in base-uboot.jinja or base.jinja2 so it must be in your device-type template. That is entirely down to you to create a suitable override, as detailed in the documentation link I have already given. It wasn't in the output you mentioned last time.

First work out all the boot commands you need to have and all the ones you mustn't have by running various U-Boot commands manually on the board. Once you have the set, then you go to the templates and work out which variables you need to set and where.

You've skipped at least one stage for this device. Get it working outside LAVA first. Then set the overrides to generate the U-Boot commands that your device actually needs.

Please suggest a way to remove that from bootargs set.

You need to work that our for yourself.

Thanks and regards, Manoj

On Thu, Nov 22, 2018 at 6:38 PM Neil Williams neil.williams@linaro.org wrote:

...

On Thu, 22 Nov 2018 at 12:34, Manoj Tiwary manojtiwary22@gmail.com wrote:

...

Hi all,

In Tftp deploy , How to give new set of u-boot bootargs by modifying device configuration file? I've tried by giving: {% set base_kernel_args = "setenv bootargs console=serial1,115200 console=tty1 root=/dev/ram0 ip=dhcp rootwait" %}

First, don't try to change all those values in one setting.

Which values actually need to be changed? root=/dev/ram0 is the default for a ramdisk, ip=dhcp is default for base.

Not all TFTP deployments are U-Boot, so you need to let us know if you are using U-Boot or something else.

You can define console_device to change the value passed to console= but the baud rate should include parity and databits as well, so 115200n8 - those are defaults.

{% set console_device = "serial1" %}

Generally, do not change any variable prefixed with base_ because the change will not take effect. There will be an alternative argument for each use of the base_ variable.

See https://master.lavasoftware.org/static/docs/v2/simple-admin.html#overriding-...

Simplest thing to do is make changes in the device dictionary and check the rendered YAML output - there is no need to run a test job until you are sure that the various settings, combined, have given you the right values.

...

But it is not taking these args. Please suggest the modifications I have to make.

Thanks and regards, Manoj _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users

--

Neil Williams

neil.williams@linaro.org http://www.linux.codehelp.co.uk/