Difference between revisions of "Dumping and Flashing images by hand"
m (moved Manually flashing images via telnet or console (without the need for XOR and CRC32) to Dumping and Flashing images by hand: Old title, "Manually flashing images via telnet or console (without the need for XOR and CRC32)" is too long for ) |
(Using cat and dd tool as flash dumpers...) |
||
| Line 26: | Line 26: | ||
*(4) Take a backup of the current image in the flash. | *(4) Take a backup of the current image in the flash. | ||
bml.dump /dev/bml0/8 /mtd_swu/exe.img.orig | bml.dump /dev/bml0/8 /mtd_swu/exe.img.orig | ||
| + | If you dont have bml.dump tool, than you can use '''dd''' or '''cat''' tool too. | ||
| + | cat /dev/bml0/8 > /mtd_swu/exe.img.orig | ||
| + | or | ||
| + | dd if=/dev/bml0/8 of=/mtd_swu/exe.img.orig | ||
*(5) Move backup image to a safe space ( e.g. USB ) and remove file from '''/mtd_swu''' | *(5) Move backup image to a safe space ( e.g. USB ) and remove file from '''/mtd_swu''' | ||
mv /mtd_swu/exe.img.orig /dtv/usb/sda1 | mv /mtd_swu/exe.img.orig /dtv/usb/sda1 | ||
Revision as of 12:37, 6 December 2009
The steps outlined below allow the flashing of an image directly into the flash of your TV, without using the offical upgrade process of the TV.
The example shown below is for flashing a modified exe.img on a UExxB70xx.
There is no need to flash app_data Image, if you are just flashing modifications of the same exeDSP Version.
In any case you need to ensure that you erase the respective flash before overwriting it.
Contents
Device files used
Find below the device files for different areas of the firmware for FW types listed ( this information is taken from the run.sh file and was not validated! )
T-CHL5DSEUC, T-CHL5DEUC and T-CHU7DEUC
- BOOTLOADER_DEVICE=/dev/bml0/2
- FNW_DEVICE=/dev/bml0/4
- KERNEL_DEVICE=/dev/bml0/5
- RFS_DEVICE=/dev/bml0/6
- BOOT_DEVICE=/dev/bml0/7
T-CHL5DSEUC and T-CHL5DEUC Specific
- EXE_DEVICE=/dev/stl0/8
- APPDATA_DEVICE=/dev/stl0/9
T-CHU7DEUC Specific
- EXE_DEVICE=/dev/bml0/8
- APPDATA_DEVICE=/dev/bml0/9
Manual flashing steps
- (1) Prevent TV from rebooting when exeDSP is stopped
/mtd_boot/MicomCtrl 23
- (2) Stop exeDSP binary
killall -9 exeDSP
- (3) Unmount the respective directory
umount /mtd_exe
- (4) Take a backup of the current image in the flash.
bml.dump /dev/bml0/8 /mtd_swu/exe.img.orig
If you dont have bml.dump tool, than you can use dd or cat tool too.
cat /dev/bml0/8 > /mtd_swu/exe.img.orig
or
dd if=/dev/bml0/8 of=/mtd_swu/exe.img.orig
- (5) Move backup image to a safe space ( e.g. USB ) and remove file from /mtd_swu
mv /mtd_swu/exe.img.orig /dtv/usb/sda1 rm /mtd_swu/exe.img.orig
- (6) Copy Image to be flashed from your USB to /mtd_swu
cp /dtv/usb/sda1/exe.img /mtd_swu
-> this is the safest way, even though flashing directly from USB-Device may also be possible, which I have not tested
- (7) Erase the flash before flashing the new file
bml.erase /dev/bml0/8
- (8) Perform the actual step of flashing the file.
bml.restore /dev/bml0/8 /mtd_swu/exe.img
->Flashing progress will be shown 0% ... 100%. Don't interrupt this process!!
- (9) Mount the updated image( afterwards check out content and ensure it mounts without problems and looks ok from a content perspective. )
mount -t auto /dev/tbml8 /mtd_exe
- (10) Starting exeDSP
/mtd_exe/rc.local
-> If something went wrong and your exeDSP doesn't start up properly, then you can flash back your backup ".orig" image following steps 3-9.
-> Don't worry, if you see your screen upside down after re-starting exeDSP ;-) as
the exeDSP binary seems to expect a freshly initialized HW to start-up properly
Attention:This process does not validate the correctness and validity of the file being flashed. THIS IS YOUR RESPONSIBILITY!!!
--Dynamic1969 17:59, 3 October 2009 (UTC)
