diff options
| author | Paul Gortmaker <paulg@kernel.org> | 2023-05-09 21:37:32 -0400 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-05-11 09:15:19 +0100 |
| commit | 0c64d0e4317e3749f7f7ed9ecd5d08bbb0cedc9e (patch) | |
| tree | 81a4a523be9a7eb623c81e8f7ee7f86c55b78364 /meta-yocto-bsp/README.hardware.md | |
| parent | ddf68ab675787e69205f4e16002dedc408440c09 (diff) | |
| download | poky-0c64d0e4317e3749f7f7ed9ecd5d08bbb0cedc9e.tar.gz | |
yocto-bsp: drop MIPS Edgerouter support
As per ongoing discussions, there is a general desire to try and update
our hardware reference platforms when an appropriate (newer) substitute
is available. However, in the case of MIPS, there isn't an obvious one
to choose. But continuing to maintain support for an old board that
hasn't been available for purchase for years doesn't make sense either.
So we are dropping support for the Edgerouter for future releases. The
MIPS architecture will still get coverage via QEMU build/boot testing.
(From meta-yocto rev: 5ea231c6c6387804a85adf15d3f03bdae9b2be25)
Signed-off-by: Paul Gortmaker <paulg@kernel.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp/README.hardware.md')
| -rw-r--r-- | meta-yocto-bsp/README.hardware.md | 112 |
1 files changed, 0 insertions, 112 deletions
diff --git a/meta-yocto-bsp/README.hardware.md b/meta-yocto-bsp/README.hardware.md index 44dbb35b93..8ea0ef1461 100644 --- a/meta-yocto-bsp/README.hardware.md +++ b/meta-yocto-bsp/README.hardware.md | |||
| @@ -28,7 +28,6 @@ Hardware Reference Boards | |||
| 28 | The following boards are supported by the meta-yocto-bsp layer: | 28 | The following boards are supported by the meta-yocto-bsp layer: |
| 29 | 29 | ||
| 30 | * Texas Instruments Beaglebone (beaglebone-yocto) | 30 | * Texas Instruments Beaglebone (beaglebone-yocto) |
| 31 | * Ubiquiti Networks EdgeRouter Lite (edgerouter) | ||
| 32 | * General IA platforms (genericx86 and genericx86-64) | 31 | * General IA platforms (genericx86 and genericx86-64) |
| 33 | 32 | ||
| 34 | For more information see the board's section below. The appropriate MACHINE | 33 | For more information see the board's section below. The appropriate MACHINE |
| @@ -48,7 +47,6 @@ Consumer Devices | |||
| 48 | The following consumer devices are supported by the meta-yocto-bsp layer: | 47 | The following consumer devices are supported by the meta-yocto-bsp layer: |
| 49 | 48 | ||
| 50 | * Intel x86 based PCs and devices (genericx86) | 49 | * Intel x86 based PCs and devices (genericx86) |
| 51 | * Ubiquiti Networks EdgeRouter Lite (edgerouter) | ||
| 52 | 50 | ||
| 53 | For more information see the device's section below. The appropriate MACHINE | 51 | For more information see the device's section below. The appropriate MACHINE |
| 54 | variable value corresponding to the device is given in brackets. | 52 | variable value corresponding to the device is given in brackets. |
| @@ -153,113 +151,3 @@ From a Linux system with access to the image files perform the following steps: | |||
| 153 | # dd if=core-image-minimal-beaglebone-yocto.wic of=/dev/sdb | 151 | # dd if=core-image-minimal-beaglebone-yocto.wic of=/dev/sdb |
| 154 | 152 | ||
| 155 | 3. Insert the SD card into the Beaglebone and boot the board. | 153 | 3. Insert the SD card into the Beaglebone and boot the board. |
| 156 | |||
| 157 | Ubiquiti Networks EdgeRouter Lite (edgerouter) | ||
| 158 | ============================================== | ||
| 159 | |||
| 160 | The EdgeRouter Lite is part of the EdgeMax series. It is a MIPS64 router | ||
| 161 | (based on the Cavium Octeon processor) with 512MB of RAM, which uses an | ||
| 162 | internal USB pendrive for storage. | ||
| 163 | |||
| 164 | Setup instructions | ||
| 165 | ------------------ | ||
| 166 | |||
| 167 | You will need the following: | ||
| 168 | * RJ45 -> serial ("rollover") cable connected from your PC to the CONSOLE | ||
| 169 | port on the device | ||
| 170 | * Ethernet connected to the first ethernet port on the board | ||
| 171 | |||
| 172 | If using NFS as part of the setup process, you will also need: | ||
| 173 | * NFS root setup on your workstation | ||
| 174 | * TFTP server installed on your workstation (if fetching the kernel from | ||
| 175 | TFTP, see below). | ||
| 176 | |||
| 177 | --- Preparation --- | ||
| 178 | |||
| 179 | Build an image (e.g. core-image-minimal) using "edgerouter" as the MACHINE. | ||
| 180 | In the following instruction it is based on core-image-minimal. Another target | ||
| 181 | may be similiar with it. | ||
| 182 | |||
| 183 | --- Booting from NFS root / kernel via TFTP --- | ||
| 184 | |||
| 185 | Load the kernel, and boot the system as follows: | ||
| 186 | |||
| 187 | 1. Get the kernel (vmlinux) file from the tmp/deploy/images/edgerouter | ||
| 188 | directory, and make them available on your TFTP server. | ||
| 189 | |||
| 190 | 2. Connect the board's first serial port to your workstation and then start up | ||
| 191 | your favourite serial terminal so that you will be able to interact with | ||
| 192 | the serial console. If you don't have a favourite, picocom is suggested: | ||
| 193 | |||
| 194 | $ picocom /dev/ttyS0 -b 115200 | ||
| 195 | |||
| 196 | 3. Power up or reset the board and press a key on the terminal when prompted | ||
| 197 | to get to the U-Boot command line | ||
| 198 | |||
| 199 | 4. Set up the environment in U-Boot: | ||
| 200 | |||
| 201 | => setenv ipaddr <board ip> | ||
| 202 | => setenv serverip <tftp server ip> | ||
| 203 | |||
| 204 | 5. Download the kernel and boot: | ||
| 205 | |||
| 206 | => tftp $loadaddr vmlinux | ||
| 207 | => bootoctlinux $loadaddr coremask=0x3 root=/dev/nfs rw nfsroot=<nfsroot ip>:<rootfs path> ip=<board ip>:<server ip>:<gateway ip>:<netmask>:edgerouter:eth0:off mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom) | ||
| 208 | |||
| 209 | --- Booting from USB disk --- | ||
| 210 | |||
| 211 | To boot from the USB disk, you either need to remove it from the edgerouter | ||
| 212 | box and populate it from another computer, or use a previously booted NFS | ||
| 213 | image and populate from the edgerouter itself. | ||
| 214 | |||
| 215 | Type 1: Use partitioned image | ||
| 216 | ----------------------------- | ||
| 217 | |||
| 218 | Steps: | ||
| 219 | |||
| 220 | 1. Remove the USB disk from the edgerouter and insert it into a computer | ||
| 221 | that has access to your build artifacts. | ||
| 222 | |||
| 223 | 2. Flash the image. | ||
| 224 | |||
| 225 | # dd if=core-image-minimal-edgerouter.wic of=/dev/sdb | ||
| 226 | |||
| 227 | 3. Insert USB disk into the edgerouter and boot it. | ||
| 228 | |||
| 229 | Type 2: NFS | ||
| 230 | ----------- | ||
| 231 | |||
| 232 | Note: If you place the kernel on the ext3 partition, you must re-create the | ||
| 233 | ext3 filesystem, since the factory u-boot can only handle 128 byte inodes and | ||
| 234 | cannot read the partition otherwise. | ||
| 235 | |||
| 236 | These boot instructions assume that you have recreated the ext3 filesystem with | ||
| 237 | 128 byte inodes, you have an updated uboot or you are running and image capable | ||
| 238 | of making the filesystem on the board itself. | ||
| 239 | |||
| 240 | |||
| 241 | 1. Boot from NFS root | ||
| 242 | |||
| 243 | 2. Mount the USB disk partition 2 and then extract the contents of | ||
| 244 | tmp/deploy/core-image-XXXX.tar.bz2 into it. | ||
| 245 | |||
| 246 | Before starting, copy core-image-minimal-xxx.tar.bz2 and vmlinux into | ||
| 247 | rootfs path on your workstation. | ||
| 248 | |||
| 249 | and then, | ||
| 250 | |||
| 251 | # mount /dev/sda2 /media/sda2 | ||
| 252 | # tar -xvjpf core-image-minimal-XXX.tar.bz2 -C /media/sda2 | ||
| 253 | # cp vmlinux /media/sda2/boot/vmlinux | ||
| 254 | # umount /media/sda2 | ||
| 255 | # reboot | ||
| 256 | |||
| 257 | 3. Reboot the board and press a key on the terminal when prompted to get to the U-Boot | ||
| 258 | command line: | ||
| 259 | |||
| 260 | # reboot | ||
| 261 | |||
| 262 | 4. Load the kernel and boot: | ||
| 263 | |||
| 264 | => ext2load usb 0:2 $loadaddr boot/vmlinux | ||
| 265 | => bootoctlinux $loadaddr coremask=0x3 root=/dev/sda2 rw rootwait mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom) | ||
