TBM/tbm-docs
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

user-doc: fix offsets

Browse source
This commit is contained in:
S.J.R. van Schaik 2017-08-04 14:58:33 +02:00
parent 71f7cb40dc
commit 78fbe03b20
1 changed files with 8 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

17
user-doc/user-doc.tex
View file

@ -215,12 +215,12 @@ flashrom v0.9.4 : bc6cab1 : Oct 30 2014 07:32:01 UTC on Linux 4.9.4-gentoo (x86
\end{minted}
Further, Google's fork of flashrom allows us to tag regions on the SPI NOR flash chip with a custom name.
Assuming that the SPI NOR flash chip is 8 MiB, that the u-boot image is 512 kiB and that the Linux image is 3.5 MiB, we will be using the following \path{layout.txt} file for the ROTS:
Assuming that the SPI NOR flash chip is 16 MiB, we will be using the following \path{layout.txt} file for the ROTS:
\begin{minted}[breaklines]{text}
000000:07ffff uboot
080000:3fffff linux
400000:7fffff initramfs
000000:09ffff uboot
0a0000:5fffff linux
600000:ffffff initramfs
\end{minted}
We can then write \path{u-boot.bin}, \path{bzImage} and \path{initramfs.cpio.gz} to the SPI NOR flash chip by using the respective names of the regions.
@ -293,8 +293,8 @@ Then we can write the \path{u-boot.bin}, \path{bzImage} and \path{initramfs.cpio
\begin{minted}[breaklines]{text}
./sunxi-fel -p spiflash-write 0x000000 u-boot.bin
./sunxi-fel -p spiflash-write 0x080000 bzImage
./sunxi-fel -p spiflash-write 0x400000 initramfs.cpio.gz
./sunxi-fel -p spiflash-write 0x0a0000 bzImage
./sunxi-fel -p spiflash-write 0x600000 initramfs.cpio.gz
\end{minted}
\section{Booting ROTS}
@ -304,8 +304,8 @@ After powering up the board, \emph{u-boot} will be loaded.
\begin{minted}[breaklines]{text}
sf probe 0:0 6000000
sf read 42000000 80000 380000
sf read 43000000 400000 400000
sf read 0x42000000 0xa0000 5636096
sf read 0x43000000 0x600000 10485760
bootm 0x42000000 0x43000000
\end{minted}
@ -314,5 +314,4 @@ At some point the kernel will run the init script in the initramfs.
When this happens the ROTS will start communicating with the TBM to fetch the time as well as the certificates.
Once these have been retrieved from the TBM, the ROTS will mount the external media such as hard disks and enumerate and verify possible boot images on those media.
\end{document}