aboutsummaryrefslogtreecommitdiffstats
path: root/board/raspberrypi/readme.txt
blob: 32877951da0988014321f6a83c74a3b6caa31e48 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
RaspberryPi

Intro
=====

To be able to use your RaspberryPi board with the images generated by
Buildroot, you have a prior choice to make, will you use:
    - Volatile rootfs in RAM (The rootfs is an initramfs) or
    - Persistent rootfs on the SDCard

Also, a good source of information is http://elinux.org/R-Pi_Hub

Volatile rootfs
===============

How to build it
---------------

You need to use the rpi_defconfig, to do so:
 * make rpi_defconfig

Then, you need to select the kind of images you want:
 * make menuconfig
 * Select "Filesystem images"
 * Select "initial RAM filesystem linked into linux kernel"

What is generated
-----------------

After building, you should obtain this tree:

    output/images/
    +-- rootfs.tar
    +-- rpi-firmware
    |   +-- bootcode.bin
    |   +-- config.txt
    |   +-- fixup_cd.dat
    |   +-- fixup.dat
    |   +-- start_cd.elf
    |   `-- start.elf
    `-- zImage

Note : rootfs.tar will only be there if you kept "tar the root filesystem"
option selected in "Filesystem images".

Where should the binaries be copied on the SDCard
-------------------------------------------------

Your SDCard must have its first partition using fat32 and marked bootable.

At the root of the partition, the RaspberryPi must find the following files:

 * bootcode.bin
 * config.txt
 * fixup_cd.dat
 * fixup.dat
 * start_cd.elf
 * start.elf
 * zImage

So you should copy the entire content of output/images/rpi-firmware along with
zImage.

Note: You can create any number of partitions you desire, the only requirement
is that the first partition must be using fat32 and bootable.

Persistent rootfs
=================

How to build it
---------------

You only need to use the rpi_defconfig, to do so:
 * make rpi_defconfig

What is generated
-----------------

After building, you should obtain this tree:

    output/images/
    +-- rootfs.tar
    +-- rpi-firmware
    |   +-- bootcode.bin
    |   +-- config.txt
    |   +-- fixup_cd.dat
    |   +-- fixup.dat
    |   +-- start_cd.elf
    |   `-- start.elf
    `-- zImage

Where should the binaries be copied on the SDCard
-------------------------------------------------

Your SDCard must have its first partition using fat32 and marked bootable.
It should also have another partition which will contain your rootfs, it should
be partitioned as ext4.

Boot partition
~~~~~~~~~~~~~~

The first partition will contain everything used to boot the RaspberryPi.
You must copy theses files at the root of partition:

 * bootcode.bin
 * config.txt
 * fixup_cd.dat
 * fixup.dat
 * start_cd.elf
 * start.elf
 * zImage

So you should copy the entire content of output/images/rpi-firmware along with
zImage.

Rootfs partition
~~~~~~~~~~~~~~~~

The second partition will contain your rootfs.
Simply extract (as root!) the contents of the rootfs.tar archive
into this partition.

For example: (Assuming mountpoint is a directory and exist)

 $ sudo mount /dev/sdXY /mnt/mountpoint
 $ sudo tar xf rootfs.tar -C /mnt/mountpoint