neo-technologies / rockchip-mkbootimg Goto Github PK

Tools to create firmware / boot images for Rockchip devices

C 93.37% Shell 5.30% Makefile 1.32%

rockchip-mkbootimg's Introduction

Installation

Compilation needs OpenSSL crypto library:

sudo apt-get install libssl-dev

Build and install:

make
sudo make install

Usage

afptool

USAGE:
	afptool <-pack|-unpack> <Src> <Dest>
Example:
	afptool -pack xxx update.img	Pack files
	afptool -unpack update.img xxx	unpack files

img_maker

USAGE:
img_maker [chiptype] [loader] [major ver] [minor ver] [subver] [old image] [out image]

Example:
img_maker -rk30 Loader.bin 1 0 23 rawimage.img rkimage.img 	RK30 board
img_maker -rk31 Loader.bin 4 0 4 rawimage.img rkimage.img 	RK31 board
img_maker -rk32 Loader.bin 4 4 2 rawimage.img rkimage.img 	RK32 board


Options:
[chiptype]:
	-rk29
	-rk30
	-rk31
	-rk32

mkbootimg

mkbootimg
       --kernel <filename>
       --ramdisk <filename>
       [ --second <2ndbootloader-filename> ]
       [ --cmdline <kernel-commandline> ]
       [ --board <boardname> ]
       [ --base <address> ]
       [ --pagesize <pagesize> ]
       [ --ramdiskaddr <address> ]
       -o|--output <filename>

unmkbootimg

usage: unmkbootimg
       [ --kernel <filename> ]
       [ --ramdisk <filename> ]
       [ --second <2ndbootloader-filename> ]
       -i|--input <filename>

mkrootfs

Usage: mkrootfs directory size

    directory   Directory used for the creation of the ext4 rootfs image
    size        Image size in 'dd' format (eg. 256M, 512M, 1G, etc.)

mkupdate

Usage: mkupdate directory

    directory must contain package-file with bootloader, parameter and image files

mkcpiogz

Usage: mkcpiogz directory

unmkcpiogz

Usage: unmkcpiogz initramfs.cpio.gz

rockchip-mkbootimg's People

Contributors

Stargazers

Watchers

rockchip-mkbootimg's Issues

afptool: can't unpack RK3188 update.img

I don't know if this is expected with this kind of quite old RK3188 images, but I get:

$ afptool -unpack update.img tmp/
Invalid header magic
UnPack failed

The same img is correctly unpacked by @naobsd's rkunpack (https://github.com/naobsd/rkutils), which gives:

$ rkunpack input-update.img
VERSION:4.0.2

unpacking
0x00000000 input-update.img-HEAD 102 bytes
0x00000066 input-update.img-BOOT 201038 bytes
0x000311b4 input-update.img-update.img 719009796 bytes

unpacking input-update.img-update.img
================================================================================
FIRMWARE_VER:4.4.2
MACHINE_MODEL:rk3188
MACHINE_ID:007
MANUFACTURER:RK30SDK

unpacking 12 files
-------------------------------------------------------------------------------
0x00000800 package-file:package-file 600 bytes
0x00001000 bootloader:RK3188Loader(L)_V2.19.bin 201038 bytes
0x00032800 parameter:parameter:0x2000@0x0 617 bytes
0x00033000 misc:Image/misc.img:0x2000@0x2000 49152 bytes
0x0003f000 kernel:Image/kernel.img:0x6000@0x4000 8233008 bytes
0x00819800 boot:Image/boot.img:0x6000@0xa000 4693456 bytes
0x00c93800 recovery:Image/recovery.img:0x10000@0x10000 16187392 bytes
0x01c03800 system:Image/system.img:0x180000@0x282000 584753152 bytes
0x249ad800 oem:Image/oem.img:0x40000@0x402000 75497472 bytes
0x291ad800 backup:backupimage/backup.img:0x20000@0x20000 29378564 bytes
0x2adb2800 update-script:update-script 933 bytes
0x2adb3000 recover-script:recover-script 266 bytes
-------------------------------------------------------------------------------
================================================================================

0x2ade49b8 input-update.img-MD5 32 bytes
unpacked

command: mkbootimg --dt dt.img not supported.

After unmake then make bootimg, the newly made bootimg does not function properly.

On my firefly-rk3288 chip, Before making changes to bootimg, i decided to test by unmaking, then making the same bootimg and running from that newly made bootimg.

However after doing this my device won't boot from this newly made bootimg.

Checked that both bootimages have the same size. There is literally 0 changes to any of the bootimg components used to make the image.

Thanks,

Segfault in afptool, if path in "package-file" is longer or equal to 60 characters

While using the afptool with a "package-file", which has a path longer or equal to 60 characters (Which might occur, if used in a yocto build environment) a segmentation fault might occur.

I tried to fix it with Angus71/rockchip-mkbootimg@6a9341e, I've tested it and it worked okay for me, but further testing might be useful.

Add support for RK3229

Can someone please add support for the RK3228 chipset?

Add support for RK3328 & RK3399 devices

Please add support for RK3328 & RK3399 devices.