diff options
-rw-r--r-- | README.hardware | 51 |
1 files changed, 47 insertions, 4 deletions
diff --git a/README.hardware b/README.hardware index a1417ebea8..5147bd6fee 100644 --- a/README.hardware +++ b/README.hardware | |||
@@ -125,11 +125,13 @@ FIXME | |||
125 | FreeScale iMX31ADS (mx31ads) | 125 | FreeScale iMX31ADS (mx31ads) |
126 | =========================== | 126 | =========================== |
127 | 127 | ||
128 | FIXME - needs testing | 128 | The correct serial port is the top-most female connector to the right of the |
129 | ethernet socket. | ||
129 | 130 | ||
130 | It is assumed a serial connection to the board is available (115200 8N1), a | 131 | For uploading data to RedBoot we are going to use tftp. In this example we |
131 | TFTP server is available at 192.168.9.1 and the board is to be given an IP | 132 | assume that the tftpserver is on 192.168.9.1 and the board is on192.168.9.2. |
132 | address of 192.168.9.2. To set the IP address, run: | 133 | |
134 | To set the IP address, run: | ||
133 | 135 | ||
134 | ip_address -l 192.168.9.2/24 -h 192.168.9.1 | 136 | ip_address -l 192.168.9.2/24 -h 192.168.9.1 |
135 | 137 | ||
@@ -159,6 +161,47 @@ To load and boot a kernel from a TFTP server with the rootfs over NFS: | |||
159 | load -r -b 0x100000 zimage | 161 | load -r -b 0x100000 zimage |
160 | exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=192.168.9.1:/mnt/nfsmx31 rw ip=192.168.9.2::192.168.9.1:255.255.255.0" | 162 | exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=192.168.9.1:/mnt/nfsmx31 rw ip=192.168.9.2::192.168.9.1:255.255.255.0" |
161 | 163 | ||
164 | Alternative flash (NAND) | ||
165 | ~~~~~~~~~~~ ~~~~~ ~~~~~~ | ||
166 | |||
167 | The instructions above are for using the (default) NOR flash on the board, | ||
168 | there is also 128M of NAND flash. | ||
169 | |||
170 | It is possible to install Poky to the NAND flash which gives more space for the | ||
171 | rootfs. | ||
172 | |||
173 | To switch to the NAND flash: | ||
174 | |||
175 | factive NAND | ||
176 | |||
177 | This will then restart RedBoot using the NAND rather than the NOR. If you | ||
178 | have not used the NAND before then it is unlikely that there will be a | ||
179 | partition table yet. You can get the list of partitions with 'fis list'. | ||
180 | |||
181 | If this shows no partitions then you can create them with: | ||
182 | |||
183 | fis init | ||
184 | |||
185 | The output of 'fis list' should now show: | ||
186 | |||
187 | Name FLASH addr Mem addr Length Entry point | ||
188 | RedBoot 0xE0000000 0xE0000000 0x00040000 0x00000000 | ||
189 | FIS directory 0xE7FF4000 0xE7FF4000 0x00003000 0x00000000 | ||
190 | RedBoot config 0xE7FF7000 0xE7FF7000 0x00001000 0x00000000 | ||
191 | |||
192 | Partitions for the kernel and rootfs need to be created: | ||
193 | |||
194 | fis create -l 0x1A0000 -e 0x00100000 kernel | ||
195 | fis create -l 0x5000000 -e 0x00100000 root | ||
196 | |||
197 | You may now use the instructions above for flashing. However it is important | ||
198 | to note that the erase block size for the NAND is different to the NOR so the | ||
199 | JFFS erase size will need to be changed to 0x4000 | ||
200 | |||
201 | You will also need to update the kernel command line to use the correct root | ||
202 | filesystem. This should be '/dev/mtdblock7' if you adhere to the partitioning | ||
203 | scheme shown above. If this fails then you can doublecheck against the output | ||
204 | from the kernel when it evaluates the available mtd partitions. | ||
162 | 205 | ||
163 | Marvell PXA3xx Zylonite (zylonite) | 206 | Marvell PXA3xx Zylonite (zylonite) |
164 | ================================== | 207 | ================================== |