Linux 内核的启动启动分区信息，和实际的怎么不一致？

hzw

cmdline指定的分区信息：
[    0.000000] Kernel command line: earlycon=uart8250,mmio32,0xff1a0000 swiotlb=1 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyFIQ0
init=/init
mtdparts=rk29xxnand:
0x00002000@0x00002000(uboot),
0x00002000@0x00004000(trust),
0x00002000@0x00006000(misc),
0x00008000@0x00008000(resource),
0x0000C000@0x00010000(kernel),
0x00010000@0x0001C000(boot),
0x00010000@0x0002C000(recovery),
0x00038000@0x0003C000(backup),
0x00040000@0x00074000(cache),
0x00300000@0x000B4000(system),
0x00008000@0x003B4000(metadata),
0x00002000@0x003BC000(baseparamer),
-@0x003BE000(userdata)
storagemedia=emmc uboot_logo=0x02000000@0xf5c00000 loader.timestamp=2018-05-02_10:34:49 hdmi.vic=-1 SecureBootCheckOk=0


实际的分区信息：
[    1.319333] mmcblk1: mmc1:0001 AJTD4R 14.6 GiB
[    1.320456] mmcblk1boot0: mmc1:0001 AJTD4R partition 1 4.00 MiB
[    1.320680] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: vbus_drv is not assigned
[    1.321685] mmcblk1boot1: mmc1:0001 AJTD4R partition 2 4.00 MiB
[    1.324683] rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops)
[    1.325131] rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops)
[    1.325383] mmcblk1rpmb: mmc1:0001 AJTD4R partition 3 4.00 MiB
[    1.326112] i2c i2c-9: of_i2c: modalias failure on /hdmi@ff940000/ports
[    1.326150]      uboot: 0x000400000 -- 0x000800000 (4 MB)
[    1.326165]      trust: 0x000800000 -- 0x000c00000 (4 MB)
[    1.326175]       misc: 0x000c00000 -- 0x001000000 (4 MB)
[    1.326181] dwhdmi-rockchip ff940000.hdmi: registered DesignWare HDMI I2C bus driver
[    1.326200]   resource: 0x001000000 -- 0x002000000 (16 MB)
[    1.326209]     kernel: 0x002000000 -- 0x003800000 (24 MB)
[    1.326219]       boot: 0x003800000 -- 0x005800000 (32 MB)
[    1.326228]   recovery: 0x005800000 -- 0x007800000 (32 MB)
[    1.326238]     backup: 0x007800000 -- 0x00e800000 (112 MB)
[    1.326248]      cache: 0x00e800000 -- 0x016800000 (128 MB)
[    1.326257]     system: 0x016800000 -- 0x076800000 (1536 MB)
[    1.326267]   metadata: 0x076800000 -- 0x077800000 (16 MB)
[    1.326276] baseparamer: 0x077800000 -- 0x077c00000 (4 MB)
[    1.326286]   userdata: 0x077c00000 -- 0x3a3a00000 (12990 MB)


为什么实际的分区大小和起始地址都不一致？？？请教各位！

penguin

出于对loder的保护，烧写时会偏移0x2000个扇区可以参考一下roc rk3328 cc 烧写emmc一章 http://wiki.t-firefly.com/zh_CN/ROC-RK3328-CC/flash_emmc.html#   有你需要的资料