Porting mer-qtmediahub to hi3716m (5): starting the Mer-qtmediahub-hi3716m

(1) Modify bootargs. For the mbflash board, you can modify it as follows:

'Mem = 128 mconsole = ttyama0, 115200 root =/dev/mtdblock12rootfstype = jffs2mtdparts = hinand: 1 m (fastboot), 512 K (bootargs), 512 K (bootargsbak ), 1 m (stbid), 1 m (loaderdb), 1 m (loaderdb_bak), 5 m (loader), 5 m (loader_bak), 1 m (baseparam ), 1 m (logo), 1 m (logobak), 5 m (kernel), 163 m (rootfs),-(other) mmz = DDR, 88000000,128 x m'

(2) run the kernel:

MW. B 82000000 FF 500000 // write the DDR as 0xff, write 5 mtftp 82000000 uimage // download the kernel to ddrnand erase 1200000 500000 // erase the 5 m flashnand write 82000000 1200000 500000 after 0x1200000 // write the kernel in the DDR to the NAND Flash, size of 5 MB written

(3) Burn and write the jffs2 File System:

MW. B 82000000 FF a300000tftp 82000000 hi3716m_rootfs.jffs2nand erase 1700000 a300000nand write. jffs2 82000000 $ (filesize ). Note that the size of the mer-qtmediahub-hi3716m rootfs after making the jffs2 file is 109838336 bytes, that is, about 104.5 MB. Use a 128 MB flash board to free up MB space for rootfs. However, in fact, a MB board cannot start Mer. stskeeps considers that it may be related to jffs2's flash operations, and the remaining space of about MB is not enough.