Rpi boots with boot.scr and does not with extlinux.conf

Hello,
I am new to u-boot and I am facing the following problem.
I use U-Boot 2021.04-rc3-00073-g6a026e5649 in a raspberry pi zero w board.
It boots linux when using boot.scr made by using the following boot.cmd " fdt addr ${fdt_addr} && fdt get value bootargs /chosen bootargs fatload mmc 0:1 ${kernel_addr_r} uImage bootm ${kernel_addr_r} - ${fdt_addr} " cmdline.txt is: root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200 See boot messages [1]
But if I delete boot.scr and use the following extlinux.conf " label rpi0w-buildroot kernel uImage devicetree bcm2708-rpi-0-w.dtb append root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200 " the boot stops at "Starting kernel ...". See boot messages [2].
Any ideas why it works with boot.scr and it does not with extlinux.conf?
Thank you, L-C
[1] scanning mmc 0:1... Found U-Boot script /boot.scr 213 bytes read in 2 ms (103.5 KiB/s) ## Executing script at 02400000 4688408 bytes read in 201 ms (22.2 MiB/s) ## Booting kernel from Legacy Image at 00080000 ... Image Name: Linux kernel Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4688344 Bytes = 4.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 19bea100 Booting using the fdt blob at 0x19bea100 Loading Kernel Image Using Device Tree in place at 19bea100, end 19bf2f9b
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.95 (laur@laurPC100) (gcc version 7.4.0 (Buildroot 2019.02)) #3 Mon Dec 2 18:29:57 EET 2019 [ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] OF: fdt: Machine model: Raspberry Pi Zero W Rev 1.1 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] cma: Reserved 8 MiB at 0x19000000 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 104545 [ 0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:AA:52:0F vc_mem.mem_ba0
[2] Scanning mmc 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 146 bytes read in 4 ms (35.2 KiB/s) 1: rpi0w-buildroot Retrieving file: /boot/extlinux/uImage 4688408 bytes read in 202 ms (22.1 MiB/s) append: root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200 Retrieving file: /boot/extlinux/bcm2708-rpi-0-w.dtb 23315 bytes read in 5 ms (4.4 MiB/s) ## Booting kernel from Legacy Image at 00080000 ... Image Name: Linux kernel Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4688344 Bytes = 4.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02600000 Booting using the fdt blob at 0x2600000 Loading Kernel Image Using Device Tree in place at 02600000, end 02608b12
Starting kernel ...

I did it.
The solution was append: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:AA:52:0F vc_mem.mem_base=0x1ec00000 vc_mem.mem_size =0x20000000 root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyS0,115200
Is there any way to enter the /chosen bootargs in append line?
Thanks
On 3/5/21, Laurentiu-Cristian Duca laurentiu.duca@gmail.com wrote:
Hello,
I am new to u-boot and I am facing the following problem.
I use U-Boot 2021.04-rc3-00073-g6a026e5649 in a raspberry pi zero w board.
It boots linux when using boot.scr made by using the following boot.cmd " fdt addr ${fdt_addr} && fdt get value bootargs /chosen bootargs fatload mmc 0:1 ${kernel_addr_r} uImage bootm ${kernel_addr_r} - ${fdt_addr} " cmdline.txt is: root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200 See boot messages [1]
But if I delete boot.scr and use the following extlinux.conf " label rpi0w-buildroot kernel uImage devicetree bcm2708-rpi-0-w.dtb append root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200 " the boot stops at "Starting kernel ...". See boot messages [2].
Any ideas why it works with boot.scr and it does not with extlinux.conf?
Thank you, L-C
[1] scanning mmc 0:1... Found U-Boot script /boot.scr 213 bytes read in 2 ms (103.5 KiB/s) ## Executing script at 02400000 4688408 bytes read in 201 ms (22.2 MiB/s) ## Booting kernel from Legacy Image at 00080000 ... Image Name: Linux kernel Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4688344 Bytes = 4.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 19bea100 Booting using the fdt blob at 0x19bea100 Loading Kernel Image Using Device Tree in place at 19bea100, end 19bf2f9b
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.95 (laur@laurPC100) (gcc version 7.4.0 (Buildroot 2019.02)) #3 Mon Dec 2 18:29:57 EET 2019 [ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] OF: fdt: Machine model: Raspberry Pi Zero W Rev 1.1 [ 0.000000] Memory policy: Data cache writeback [ 0.000000] cma: Reserved 8 MiB at 0x19000000 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 104545 [ 0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:AA:52:0F vc_mem.mem_ba0
[2] Scanning mmc 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 146 bytes read in 4 ms (35.2 KiB/s) 1: rpi0w-buildroot Retrieving file: /boot/extlinux/uImage 4688408 bytes read in 202 ms (22.1 MiB/s) append: root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200 Retrieving file: /boot/extlinux/bcm2708-rpi-0-w.dtb 23315 bytes read in 5 ms (4.4 MiB/s) ## Booting kernel from Legacy Image at 00080000 ... Image Name: Linux kernel Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4688344 Bytes = 4.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02600000 Booting using the fdt blob at 0x2600000 Loading Kernel Image Using Device Tree in place at 02600000, end 02608b12
Starting kernel ...
participants (1)
-
Laurentiu-Cristian Duca