bootm-subcommands.log

=> bootm start
## Loading kernel from FIT Image at 90800000 ...
   Using 'conf-imx7d-sdb-gpmi-weim.dtb' configuration
   Verifying Hash Integrity ... OK
   Trying 'kernel-1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x90800100
     Data Size:    22984704 Bytes = 21.9 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x80008000
     Entry Point:  0x80008000
     Hash algo:    sha256
     Hash value:   42a660e65ded446315b7ea0dc1330883c63ed82d56330ba6cc14a0f9718daca1
   Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 90800000 ...
   Using 'conf-imx7d-sdb-gpmi-weim.dtb' configuration
   Verifying Hash Integrity ... OK
   Trying 'ramdisk-1' ramdisk subimage
     Description:  bantha-netinstall-image
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x91df8230
     Data Size:    13063813 Bytes = 12.5 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    sha256
     Hash value:   033dccac74e2a0c87dcadf3c9c4a9a09f7b2f715f2e3514b671ab269636aa09e
   Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 90800000 ...
   Using 'conf-imx7d-sdb-gpmi-weim.dtb' configuration
   Verifying Hash Integrity ... OK
   Trying 'fdt-imx7d-sdb-gpmi-weim.dtb' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x91deba14
     Data Size:    51024 Bytes = 49.8 KiB
     Architecture: ARM
     Hash algo:    sha256
     Hash value:   41764bc3a6c4a1c7dea04a046470c544e0ccc72a0bd45f0e5b68fce444770f3d
   Verifying Hash Integrity ... sha256+ OK
   Booting using the fdt blob at 0x91deba14
=> bootm loados
   Loading Kernel Image
=> bootm ramdisk
   Loading Ramdisk to 9d293000, end 9df08685 ... OK
=> bootm fdt
   Loading Device Tree to 9d283000, end 9d29274f ... OK
=> bootm cmdline
subcommand not supported
bootm - boot application image from memory

Usage:
bootm [addr [arg ...]]
    - boot application image stored in memory
	passing arguments 'arg ...'; when booting a Linux kernel,
	'arg' can be the address of an initrd image
	When booting a Linux kernel which requires a flat device-tree
	a third argument is required which is the address of the
	device-tree blob. To boot that kernel without an initrd image,
	use a '-' for the second argument. If you do not pass a third
	a bd_info struct will be passed instead
	
For the new multi component uImage format (FIT) addresses
	must be extended to include component or configuration unit name:
	addr:<subimg_uname> - direct component image specification
	addr#<conf_uname>   - configuration specification
	Use iminfo command to get the list of existing component
	images and configurations.

Sub-commands to do part of the bootm sequence.  The sub-commands must be
issued in the order below (it's ok to not issue all sub-commands):
	start [addr [arg ...]]
	loados  - load OS image
	ramdisk - relocate initrd, set env initrd_start/initrd_end
	fdt     - relocate flat device tree
	cmdline - OS specific command line processing/setup
	bdt     - OS specific bd_t processing
	prep    - OS specific prep before relocation or go
	go      - start OS
=> bootm bdt
subcommand not supported
bootm - boot application image from memory

Usage:
bootm [addr [arg ...]]
    - boot application image stored in memory
	passing arguments 'arg ...'; when booting a Linux kernel,
	'arg' can be the address of an initrd image
	When booting a Linux kernel which requires a flat device-tree
	a third argument is required which is the address of the
	device-tree blob. To boot that kernel without an initrd image,
	use a '-' for the second argument. If you do not pass a third
	a bd_info struct will be passed instead
	
For the new multi component uImage format (FIT) addresses
	must be extended to include component or configuration unit name:
	addr:<subimg_uname> - direct component image specification
	addr#<conf_uname>   - configuration specification
	Use iminfo command to get the list of existing component
	images and configurations.

Sub-commands to do part of the bootm sequence.  The sub-commands must be
issued in the order below (it's ok to not issue all sub-commands):
	start [addr [arg ...]]
	loados  - load OS image
	ramdisk - relocate initrd, set env initrd_start/initrd_end
	fdt     - relocate flat device tree
	cmdline - OS specific command line processing/setup
	bdt     - OS specific bd_t processing
	prep    - OS specific prep before relocation or go
	go      - start OS
=> bootm prep
   Loading Device Tree to 9d270000, end 9d28274f ... OK
=>