So you will have to clear up the bootargs set by u-boot. Nfsroot=10.0.0.4:/home/dileep/beaglebone/rootfs,Īnd since you have also set the bootargs " bootargs = "console=ttyO0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait" " in the devicetree wouldnt affect as uboot has already set those parameters, ie if same parameter is set in the device tree and in the tags (uboot), the one from the uboot tags will be chosen. Kernel command line: console=ttyO0,115200 Looking at your pastie, the boot log says the command line is the following: The following is the chosen node of the existing deviceīootargs = "console=ttyO0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait"
#U BOOT BOOTARGS HOW TO#
If you change U-Boot's bootargs variable to an empty string as mentioned in another answer, the kernel will use its default kernel command string (CONFIG_CMDLINE) rather than the DT.Īlso see How to set Linux kernel command line on ARM?Īs per my understanding chosen node is used to send boot arguments to The scheme that selects the DT bootargs is to use the existing kernel configuration, but simply delete that U-Boot environment variable (i.e. Note that this list of choices is only available when CONFIG_ATAGS is enabled (" Support for the traditional ATAGS boot data passing"). If you want to always ignore the command line in U-Boot's bootargs variable (and the command line from the DT), but exclusively use the default kernel command string as defined in CONFIG_CMDLINE, then the kernel should be configured for the third choice (CONFIG_CMDLINE_FORCE) on that list. PetaLinux reads the DDR base address from the hardware file and appends it to the offsets provided. In the u-boot script configuration sub-menu, you have the following options: To append memory/DDR base address to provided offsets, select Append base address to image offsets. ( ) Always use the default kernel command string Select u-boot Configuration > u-boot script configuration. (X) Use bootloader kernel arguments if available There are actually three possible ARM kernel boot configuration choices: Kernel command line type: The rationale according to U-Boot author/maintainer Wolfgang Denk seems to be that any hardcoded, built-in bootargs are inferior to bootargs that can be easily customized and supplied by a bootloader. U-Boot) is the actual list of parameters currently used when you boot the board.įor ARM Linux the default kernel configuration gives precedence to the bootloader's command line over the default kernel command string and the bootargs in the chosen node in the Device Tree. As per my understanding chosen node is used to send boot arguments to the kernel.Īs already mentioned in another answer, the kernel command line provided by the bootloader (i.e.
0 kommentar(er)
