Here is Extract tool with which You can unpack patch.e2 ( RTi core Enigma 2 is in patch.e2 format ).
With this tool You will get kernel and image2 ( this is cramfs with e2 files )
Then copy image2 to Your linux machine like in /root/ , and You will have /root/image2
mkdir /root/realise
mkdir /Patch
mount -t cramfs /root/image2 /Patch -o loop
cd /Patch
tar -cf - . | tar -C /root/realise/ -xpf -
now you have extracted RTi Core image in : /root/realise/
now you can make changes
and when all is ok , send command:
mkcramfs /root/realise/MMP /root/my_image_2
copy my_image_2 on win pc , start AZ_E2_Packer, load my_image_2, load kernel file (if you want) thats all
Then use AzBox E2 Packer to pack it to patch.e2 format
Details:
-ID TEam - 10 bytes ( example: like RTi Team, SIF Team, or PB Team )
-ID Enigma - 20 bytes ( example: next 20 bytes are ID Enigma, like BlackHole Enigma usb dvb-t etc. etc )
-Version - 10 bytes ( example: this describe version like RC5 )
-About Enigma - 12 bytes ( example: This is PB Enigma )
-size of cramfs - 4 bytes
-cramfs - content of e2 files
-Kernel Description - 12 bytes
-size of kernel - 4 bytes
-kernel
This is content of patch.e2 when it is opened with any Editor.
On LINUX:
you can use the software-tool made by Doume
1- How to install :
In attached archive file, you'll find some files :
- pack_e2.c source file
- pack_e2_64bits executable file (if you run a 64 bits OS only)
- build_kernel_only.sh
- build_both.sh
If you need to compile yourself the tool, in a shell session, type :
Code:
make pack_e2 That should compile, and produce a file 'pack_e2' executable, usable on your platform
If you run a 64 bits, only rename the given file 'pack_e2_64bits' to 'pack_e2', and that's all
2- How to use :
Copy the files produced by cross-compilation in your current directory ( kernel and E2 image)
Adapt parameters into scripts 'build_XXXXX.sh' to match your files to be packed, and team_name, and so on....
And run the script needed :
Code:
./build_both.sh Note : build_both.sh generates a patch.e2 file containing both E2 image and kernel
build_kernel_only.sh generates a patch.e2 file containing only kernel
You should obtain the file designed by your parameter 'output' into scripts (generally patch.e2 by default)
Have fun, Doume.
