U-Boot / mmcblkXboot0
arwen is right, what linux calls mmcblkXbootY now is not and looks like cannot be used*. flash the uboot pieces in the general area (mmcblkX) where they are expected to reside.
* - these special purpose storage subdevices of an emmc module are for the platform firmware, but for being used and usable, the initial start up code of the SoC (ROM code), needs to try them in its boot sequence. does it? looks like not, or rockchip forgot to tell about it. you might try by yourself, would make a favor,
it's really interesting, but I don't have the emmc. zero the first megabyte of the GP area and write uboot (all its pieces) into mmcblkXboot0, attach terminal to your board, make sure you don't have anything written in SPI and SD, and look what you see in the output. most probably nothing more than scarce ROM code babbling, but if uboot starts, it will be well seen, then wahoo, we all may use boot areas for the firmware! so cool.
* - these special purpose storage subdevices of an emmc module are for the platform firmware, but for being used and usable, the initial start up code of the SoC (ROM code), needs to try them in its boot sequence. does it? looks like not, or rockchip forgot to tell about it. you might try by yourself, would make a favor,
it's really interesting, but I don't have the emmc. zero the first megabyte of the GP area and write uboot (all its pieces) into mmcblkXboot0, attach terminal to your board, make sure you don't have anything written in SPI and SD, and look what you see in the output. most probably nothing more than scarce ROM code babbling, but if uboot starts, it will be well seen, then wahoo, we all may use boot areas for the firmware! so cool.
ANT - my hobby OS for x86 and ARM.
