Making "snapshot"

vittly

I've installed you t-firefly ubuntu and have configured it. Is there a way to make my own image of device (boot, kernel, fs ...) as a backup for "may be" situation of system failure?

busybee

This is a brief document about this packing process.

1. Copy following files to your packing directory.

a. Control files
- ATTACHMENT/package-file (describes package content of update.img)
- ATTACHMENT/parameter (parameter for Ubuntu, contains eMMC partition info)
- ATTACHMENT/update-script (not used for Linux, for completion only)
- ATTACHMENT/recovery-script (not used for Linux, for completion only)
- ATTACHMENT/misc-zero.img (boot command, zero will lead to normal boot)

b. RKTools
- RKTools/linux/Linux_Upgrade_Tool_v1.2/rockdev/afptool (RK firmware packing tools)
- RKTools/linux/Linux_Upgrade_Tool_v1.2/rockdev/rkImageMaker (RK image maker)

c. Bootloader and your images
- SDK/RKTools/bootloader/uboot-emmc/RK3288Loader_uboot_V2.17.02.bin, renamed to RKLoader.bin
- Your linux-rootfs.img (ext4 filesystem image, for Linux root)
- Your linux-boot.img (See wiki doc http://wiki.t-firefly.com/index.php/Fir ... _kernel/en to create your own)
- Your resource.img (In SDK/kernel, after successful kernel compilation)

2. do the packing
First, cd to your packing directory. Then run the following commands:

./afptool -pack ./ update_tmp.img
./rkImageMaker -RK32 RKLoader.bin update_tmp.img update.img -os_type:androidos
rm -f update_tmp.img

Now, your update.img is ready to serve.

rk-pack-linux-control-files.zip (1.99 KB, Down times: 12)

3/17/2015 16:15 Uplaod

Click on the file name to download attach

tedd77

Hello busybee,




Thank you , it is working now. great script.




Best regards

busybee

Annoying forum attachment which won't accept *.txt, *.sh, except .zip file.




Please uncompress the zip file first.

tedd77

Hello busybee,




Assume I will be obliged to use the dualboot image in order to overcome the issue of backup.

How can I have the linuxroot partition size as large as 8Gbytes? I tried to look on ways to enlarge it with no luck.

If I can do that then I guess my issue of backing and restoring the partitions will be straight forward.

tedd77

Hello busybee,




Thank you for the prompt reply, could you please attach the script file ? you missed to attach it to your post.

And where from to get linux-rootfs-ubuntu-14.04.img ?

tedd77

Hello busybee,




Attached is the screenshot, yet the command is producing errors.

Yes I am using the ubuntu image only on my firefly board.

The linuxroot is still not recognized.

busybee

Sorry, tedd77, I though it just worked, but it didn't.

Especially I've been using rkflashkit and never met your problem.

I did not notice your linuxroot partition is special, in that the size is ommited ('-'), which means to use rest of the storage.

(I spent most of my time in dual firmware.)




But rkflashkit already has the solution, you can specify "SIZE@OFFSET(PART)" instead of "@PART", like:

sudo rkflashkit flash 0x202000@0x0002e000(linuxroot) linux-rootfs-ubuntu-14.04.img reboot




The size and offset are both using units of sector (512 bytes).

Since it is error-proned, I write a script named "flash-linux-root" to do this.

Please save the attachment file "flash-linux-root.txt" as "flash-linux-root.sh", and do a chmod before use:

chmod 755 flash-linux-root.sh




Then run it:

./flash-linux-root.sh /path/to/your/linux-rootfs-ubuntu-14.04.img 0x0002e000




This is my output of running this:

$ ~/flash-linux-root.sh linux-rootfs-ubuntu-14.04.img 0x0002e000
About to run:
sudo rkflashkit flash 0x202000@0x0002e000(linuxroot) linux-rootfs-ubuntu-14.04.img reboot
Press enter to continue...
Found devices:
0x2207:0x320a
[('202000', '0x0002e000')]
============= 2014-12-26 15:49:17 ============

Writing file linux-rootfs-ubuntu-14.04.img to partition 0x00202000@0x0002E000
writing flash memory at offset 0x0002e000
.....




Hope it finally helps. Thanks.

busybee

Ahha, you're using the pure Ubuntu firmware. That's the reason you don't have the system partitiion etc.

The correctly flash command is (fixed in my previous post):

sudo rkflashkit flash @linuxroot your_linux_root.img

and you can get the usage by:

rkflashkit help

tedd77

Hello busybee,




Please find attached the screenshots, as I mentionned in an earlier post I do not see all partitions.

1. Screeshot of the error for the command sudo rkflashkit @linuxroot my_image_path_and_name

2. the sudo rkflashkit part