![Technologic Systems TS-7100 Series Manual Download Page 19](http://html1.mh-extra.com/html/technologic-systems/ts-7100-series/ts-7100-series_manual_1070487019.webp)
2/11/2020
TS-7100 - Technologic Systems Manuals
https://wiki.embeddedarm.com/w/index.php?title=TS-7100&printable=yes
19/44
Note:
This section is incomplete at this time.
7.2 Restoring Stock / Backup / Production Image
7.2.1 Booted from USB / NFS
These instructions assume the TS-7100 is booted to Linux from network via NFS or USB mass storage. They also
assume that the eMMC is unmodified, with a single partition. If the partition table has been modified, a utility such
as 'gparted' or 'fdisk' may be needed to remove the existing partition table and recreate it with a single partition.
Note that the partition table must be "MBR" or "msdos", the "GPT" partition table format is not supported by U-
Boot.
Once booted to any device that is not the eMMC:
# Verify nothing else has the first eMMC partition mounted
umount
/dev/mmcblk0p1
mkfs.ext3 /dev/mmcblk0p1
mount
/dev/mmcblk0p1 /mnt/emmc
wget
http://ftp.embeddedarm.com/ftp/ts-arm-sbc/ts-7100-linux/distributions/ts7100-linux4.9-latest.tar.xz
tar
-xf
ts7100-linux4.9-latest.tar.xz
-C
/mnt/emmc
umount
/mnt/emmc
sync
Note:
The ext4 filesystem can be used instead of ext3, but it may require
additional options. U-Boot does not support the 64bit addressing added as
the default behavior in recent revisions of mkfs.ext4. If using e2fsprogs
1.43 or newer, the options "-O ^64bit,^metadata_csum" must be used
with ext4 for proper compatibility. Older versions of e2fsprogs do not
need these options passed nor are they needed for ext3.
Once written, the files on disk can be verified to ensure they are the same as the source files in the archive. To do
so, run the following commands:
mount
/dev/mmcblk0p1 /mnt/emmc
cd
/mnt/emmc/
md5sum
--quiet
-c
md5sums.txt
cd
-
umount
/mnt/emmc
sync
The 'md5sum' command will report any differences between files and their checksums. Any differences are an
indication of failure to write data or a damaged disk. Note that the "/md5sums.txt" file is present in our stock
tarballs and is created in custom images as a part of our scripts to do so. This file may not be present in custom
images created without our tools, or it may be present but not properly updated. This will result in reported errors.
8 Compile the Kernel