Template:ROM-Maker-lite Introduce

If you have a customized U-boot, Linux kernel and file system and want to use them to make a customized Linux image file(we call it "ROM" in the following sections) you can use the "dd" command the copy all the data and files from an existing SD card with a Linux ROM. However this is inefficient. We suggest you use our rom-maker-lite utility which can be downloaded at rom-maker-lite.

The rom-maker-lite utility is a general tool to make a ROM. It currently supports making a Linux based sd/eflasher ROM for FriendlyElec's H3/H5 boards .Making an Android image is not supported.

• Run ./mkimage.sh to check usage info:

$ ./mkimage.sh 
Usage:
    $ apt-get install tree exfat-utils dosfstools python3-tk
    $ ./mkimage.sh -c <filesystem type> -m <partmap> -d "<misc dir>;<partition1 dir>;<partition2 dir>;..."
        -c <filesystem type>: 
            1: misc(bootloader) + fat32 boot.img + ext4 rootfs.img
            2: misc(bootloader) + fat32 boot.img + ext4 rootfs.img + exfat friendlyarm.img
            3: misc(bootloader) + ext4 boot.img + ext4 rootfs.img

Parameter	Comment
-c <filesystem type>	-c specifies file systems' formats for the partitions in a ROM Image. Specifically for an H3/H5 based board: -c 1 stands for "misc(bootloader) + fat32 boot.img + ext4 rootfs.img" and this applies to an sd ROM of FriendlyCore/Ubuntu/Debian/OpenWrt; -c 2 stands for "misc(bootloader) + fat32 boot.img + ext4 rootfs.img + exfat friendlyarm.img" and this applies to an eflasher ROM.
-m <partmap>	-m specifies a partmap file for making a ROM. A partmap file is used to specify the files and their sizes included in a ROM. ROMs made for different boards or BSPs may need different partmap files.
-d "<misc dir>;<partition1 dir>;<partition2 dir>;..."	-d specifies file system's path and each path is separated by a ";". Specifically for an H3/H5 based board: <misc dir>: specifies the bootloader's path; <partition1 dir>: specifies the boot partition's path; <partition2 dir>: specifies the rootfs partition's path; "..." means more paths can be defined. When you make an eflasher ROM you need to include the friendlyarm partition's path;

• Preparations

We tested the following Ubuntu versions that worked with a PC host:
1) ubuntu-16.04.5-desktop-amd64.iso
2) ubuntu-18.04.1-desktop-amd64.iso
If you cannot make a ROM under a Linux system with your PC host you'd better use either one of the above two systems we tested.

Before proceed make sure you have installed the following packages:

$ apt-get install tree exfat-utils dosfstools python3-tk

You need the root access right to make a ROM:

$ su root