Perhaps it is more understandable with "more rational" numbers
idbloader is < 4M bs=512 seek=64 (ie,, 64 sectors from start of SD card)
uboot is often 4M size (or less),,bs=1M seek=8 (ie, from 8M->12M)
ATF/trust is often 4M (or less),,bs=1m seek=12 (ie,,from 12->16M)
user partitions start at 16M,, 32768 sectors, check with fdisk to see
The locations of idbloader, uboot, ATF(arm trusted firmware)
are "baked into" the bootrom
ATF does not seem to change very much, idbloader is very low-level initialization
uboot is either some version of rockchips BSP or mainline, both a bit immature
--edit--
Rarely, uboot and ATF are catted together,, uboot padded so ATF is in right place
This will be an image ~6.5M or more (up to 8M, last 1.5M zeros)
If this is happening, at 4M will be signature, "magic" for ATF,,, "BL3X" but hex of course
Not at all common
idbloader is < 4M bs=512 seek=64 (ie,, 64 sectors from start of SD card)
uboot is often 4M size (or less),,bs=1M seek=8 (ie, from 8M->12M)
ATF/trust is often 4M (or less),,bs=1m seek=12 (ie,,from 12->16M)
user partitions start at 16M,, 32768 sectors, check with fdisk to see
The locations of idbloader, uboot, ATF(arm trusted firmware)
are "baked into" the bootrom
ATF does not seem to change very much, idbloader is very low-level initialization
uboot is either some version of rockchips BSP or mainline, both a bit immature
--edit--
Rarely, uboot and ATF are catted together,, uboot padded so ATF is in right place
This will be an image ~6.5M or more (up to 8M, last 1.5M zeros)
If this is happening, at 4M will be signature, "magic" for ATF,,, "BL3X" but hex of course
Not at all common