diff options
Diffstat (limited to 'manual/getting_started/gigabeats_install.tex')
-rw-r--r-- | manual/getting_started/gigabeats_install.tex | 80 |
1 files changed, 75 insertions, 5 deletions
diff --git a/manual/getting_started/gigabeats_install.tex b/manual/getting_started/gigabeats_install.tex index 56de5adcc7..2bc8e094c8 100644 --- a/manual/getting_started/gigabeats_install.tex +++ b/manual/getting_started/gigabeats_install.tex | |||
@@ -1,8 +1,78 @@ | |||
1 | % $Id$ | 1 | % $Id$ |
2 | 2 | ||
3 | \warn{Before starting this procedure, ensure that you have a copy | ||
4 | of the original \playerman{} firmware. Without this, it is | ||
5 | \emph{not} possible to uninstall Rockbox. The \playerman{} | ||
6 | firmware can be downloaded from | ||
7 | \url{http://www.tacp.toshiba.com/tacpassets-images/firmware/MESV12US.zip}.\\} | ||
8 | |||
3 | Installing the bootloader is only needed once. It involves replacing the | 9 | Installing the bootloader is only needed once. It involves replacing the |
4 | existing firmware file on your \dap{} with another version. To be able | 10 | existing firmware file on your \dap{} with another version. |
5 | to boot the original firmware you must generate your own \fname{nk.bin} file | 11 | When running the original \playerman{} firmware (a version of Windows CE), it is |
6 | using the mknkboot utility. Alternatively you can use a pre-built bootloader, | 12 | only possible to connect the \dap{} to a PC in ``MTP mode'', which hides |
7 | however you must keep in mind that by using the pre-built version you will be | 13 | the actual content of your \daps{} disk and provides restricted access |
8 | unable to dual-boot your \dap{}. | 14 | to its contents. |
15 | In reality, the \daps{} hard disk contains two partitions, a small | ||
16 | (150MB) ``firmware partition'' containing the \daps{} firmware (operating | ||
17 | system), and a second ``data partition'' containing your media files. The main | ||
18 | firmware file in the bootloader partition is called \fname{nk.bin}, and | ||
19 | this is the file that is loaded into RAM (by the \daps{} ROM-based | ||
20 | bootloader) and executed when your \dap{} is powered on. | ||
21 | |||
22 | \subsubsection{Bootloader installation from Windows} | ||
23 | |||
24 | \begin{enumerate} | ||
25 | \item Download \fname{sendfirm.exe} from \fixme{add download location}. | ||
26 | \item Download the bootloader (\fname{nk.bin}) from \fixme{add download location}. | ||
27 | \item From the command prompt, enter the directory into which you downloaded | ||
28 | \fname{sendfirm.exe} and \fname{nk.bin} and run: | ||
29 | \begin{code} | ||
30 | sendfirm.exe nk.bin | ||
31 | \end{code} | ||
32 | \item After a successful installation, your \dap{} will immediately reboot | ||
33 | and (because it is still connected to your PC) enter the Rockbox bootloader's | ||
34 | ``USB Mass Storage'' mode, which exposes your \daps{} disk to your computer | ||
35 | as a standard USB Mass Storage device. | ||
36 | \end{enumerate} | ||
37 | |||
38 | \subsubsection{Bootloader installation from Unix (Linux / Mac OS X)} | ||
39 | |||
40 | \begin{enumerate} | ||
41 | \item Download \fname{sendfirm} from \fixme{add download location}. | ||
42 | \item Download the bootloader (\fname{nk.bin}) from \fixme{add download location}. | ||
43 | \item From the terminal, enter the directory into which you downloaded | ||
44 | \fname{sendfirm} and \fname{nk.bin} and run: | ||
45 | \begin{code} | ||
46 | chmod +x sendfirm | ||
47 | ./sendfirm nk.bin | ||
48 | \end{code} | ||
49 | \item After a successful installation, your \dap{} will immediately reboot | ||
50 | and (because it is still connected to your PC) enter the Rockbox bootloader's | ||
51 | ``USB Mass Storage'' mode, which exposes your \daps{} disk to your computer | ||
52 | as a standard USB Mass Storage device. | ||
53 | \end{enumerate} | ||
54 | |||
55 | \subsubsection{Fixing the partition table} | ||
56 | The factory-standard partition table on your \daps{} disk is technically | ||
57 | invalid, and the Linux kernel (and maybe other operating systems) rejects it. | ||
58 | To fix this, you need to use the fdisk utility to correctly set the ``bootable | ||
59 | flag'' field to a valid value (it doesn't matter if this is true or false).\\ | ||
60 | |||
61 | \note{Windows does not seem to mind this, so if you only use your \dap{} with | ||
62 | Windows the following steps are not necessary.\\} | ||
63 | |||
64 | Assuming your \dap{} is appearing as /dev/sdz (the output of the dmesg | ||
65 | command will show the log messages including the device node assigned to | ||
66 | your \dap{}), type the following: | ||
67 | |||
68 | \begin{code} | ||
69 | fdisk /dev/sdz | ||
70 | a | ||
71 | 1 | ||
72 | a | ||
73 | 2 | ||
74 | w | ||
75 | \end{code} | ||
76 | |||
77 | After exiting fdisk, you may need to unplug and then reattach your \dap{} | ||
78 | in order for it to be recognised by your computer. \ No newline at end of file | ||