אינדקס
DGStation uses several different image file-formats
These are the main ones and their consequences:
** states the way of transfer eg: USB or Serial. USB-files can be flashed with FTP (ftp-server or pc-editor)(only on 200s/400s).
usb_uboot images and *_all.images must be flashed by flashtools on 400s using usb, for flashing the 200s you need a serial_uboot.img.
So for example, if you flash a kernel_root_db, it won't change the bootloader nor the welcome.img
if you only flash the u-boot, kernel-root or welcome image, it will not affect the other parts.
These are the main ones and their consequences:
| Image type | descryption | 400 s/usb in Bytes | 200s/serial in Bytes |
| **_uboot_*.img | Bootloader (sometimes formats the HDD) | ||
| **_all.img | Complete image with bootloader | ||
| **_all_noboot*.img | Complete image without bootloader: all data will be erased(except recordings on HDD) | 8.196.096 | |
| **_kernel_root*.img | Core image, most suitable for updates, leaves usersettings intact. | 5.640.192 | 6.668.768 |
| **_kernel_root_db**.img | Core image incl db.img | 7.933.952 | 7.934.016 |
| **_db*.img | Database update, you need to setup the STB again, so save your settings first. | 2.297.856 | 1.249.344 |
| **_welcome.img | Replaces the usual starting picture on STB | 200.704 | 200.768 |
usb_uboot images and *_all.images must be flashed by flashtools on 400s using usb, for flashing the 200s you need a serial_uboot.img.
So for example, if you flash a kernel_root_db, it won't change the bootloader nor the welcome.img
if you only flash the u-boot, kernel-root or welcome image, it will not affect the other parts.
