2/3/2024 0 Comments U boot manual![]() The salient issue is that the system seems to hang after U-Boot outputs the text Starting kernel. Using Device Tree in place at 905a30ac, end 905ae821 # Loading fdt from FIT Image at 90000000. # Loading kernel from FIT Image at 90000000. Root=/dev/mmcblk0p1 rw rootwait tegraboot=sdmmc gptĭescription = "Simple image with single Linux kernel and FDT blob" ĭescription = "Flattened Device Tree blob" ĭescription = "Boot Linux kernel with FDT blob" ![]() How do I pass kernel arguments to the kernel when using an ITB file?Ĭommand line arguments (taken from the APPEND command of the examples nf): console=ttyS0,115200n8 console=tty1 video=tegrafb memtype=255 pmuboard=0x0177:0x0000:0x02:0x43:0x00 usbcore.old_scheme_first=1 core_edp_mv=1150Ĭore_edp_ma=4000 tegraid=40.1.1.0.0 debug_uartport=lsport,3 power_supply=AdapterĪudio_codec=rt5640 modem_id=0 android.kerneltype=normal usb_port_owner_info=0įbcon=map:1 commchip_id=0 usb_port_owner_info=0 lane_owner_info=6 board_info=0x0177:0x0000:0x02:0x43:0x00 I tried setting the bootargs environment variable but this did not change the situation. I assume that this is because no boot arguments are passed to the kernel (the original startup adds loads of arguments) but I am a little dumbfounded on how to pass the arguments to the kernel. ![]() U-Boot can load the ITB file and tries to start the kernel but the system hangs after this message. As we are pushing for verified boot I am using the Flat Image Tree (unifying kernel image, device tree blob. I am trying to get my own build of U-Boot to boot Linux on a Jetson TK1 board.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |