NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.
CRAMFS Utilities
Contents
What are the CRAMFS Utilities?[edit]
The [CRAMFS Utilities] are used to create a CRAMFS file system image and to run a check of that file system image. The following utilites are part of the [CRAMFS Utilities] package:
- mkcramfs - Creates a CRAMFS file system image from the contents of a specified directory.
- cramfsck - Checks a CRAMFS file system image for errors.
At the very least you will need the mkcramfs tool installed on your host Linux workstation in order to create the cramfs file system image.
Where to Obtain the CRAMFS Utilities[edit]
The CRAMFS utilities can be obtained from the sourceforge project page at [[1]]. Here you can obtain the latest version of the utilities as well as submit bugs.
Compilation[edit]
Obtain the latest version of the tool at [[2]]. After downloading the tools (Here we assume the tools were downloaded to the /home/user directory) you can perform the following steps to compile and install the tools.
- Untar the tools package
host $ cd /home/user/ host $ tar xzf cramfs-1.1.tar.gz host $ cd cramfs-1.1
- Compile the tools
host $ make
This creates the mkcramfs and cramfsck utilities. You can install both if you want but you only need the mkcramfs utility in most cases.
- Install the tools
Since the Makefile does not have an install section it is up to you to install the utilities yourself. This can be done by simply copying the tools to the /usr/bin directory.
host $ cp mkcramfs /usr/bin/ host $ cp cramfsck /usr/bin/ (optional)
Conclusion[edit]
You should now have the CRAMFS utilities installed on your host Linux workstation. To verify that the tools are installed an available in your path do:
host$ which mkcramfs
You should see output similar to:
host$ which mkcramfs /usr/bin/mkcramfs
If you do not see this output please make sure that /usr/bin is in your PATH variable.