--- wikisrc/ports/evbarm.mdwn 2018/11/07 14:33:50 1.51 +++ wikisrc/ports/evbarm.mdwn 2019/06/27 17:29:39 1.79 @@ -7,61 +7,83 @@ port_var3="earmv6hf" port_var4="earmv7hf" port_var5="earmv7hfeb" port_var_install_notes="evbarm-earm" -cur_rel="8.0" +cur_rel="8.1" future_rel="9.0" -changes_cur="8.0" +changes_cur="8.1" changes_future="9.0" -thumbnail="http://www.netbsd.org/images/ports/evbarm/adi_brh.gif" +thumbnail="//www.netbsd.org/images/ports/evbarm/adi_brh.gif" about=""" NetBSD/evbarm is the port of NetBSD to various evaluation and prototyping boards based on CPUs implementing the ARM architecture. NetBSD/evbarm also supports some specific embedded system products based on prototype board designs. -Matt Thomas is the maintainer of NetBSD/evbarm. - ### CPU types -The evbarm port can be built with a variety of CPU options. There are -three main variables: the instruction set, the endianness, and whether -there is hardware floating point. By default the CPU type is "earm", -and this implies little endian (el when explicitly stated), and soft -(emulated) floating point. Another example, suitable for Raspberry PI -2, is earmv7hf, which is the v7 instruction set, little endian, -and hardware floating point. +The evbarm port can be built with a variety of CPU options, corresponding to the +[large array of ARM CPU architectures](https://en.wikipedia.org/wiki/ARM_architecture#Cores). +There are +four main variables: the word size, the instruction set, the +endianness, and whether there is hardware floating point. By default +the CPU type is "earm", and this implies aarch32 (32-bit), earmv5 cpu +architecture, little endian (el when explicitly stated), and soft +(Emulated) floating point. Another example, suitable for Raspberry PI +2, is earmv7hf, which is aarch32, the v7 instruction set, little +endian, and hardware floating point. Typically, various boards are best compiled with a CPU type that matches the board's CPU and floating point support, but generally a lower CPU instruction set version is workable on a newer board. See build.sh and look for aliases for the evbarm port. -Some processors can operate as arm or the 64-bit ARM variant, aarch64, which is supported by -[[NetBSD/aarch64|aarch64]]. +Through NetBSD 8, the evbarm port has supported exclusively the +aarch32 (32-bit CPU) sub-family of the ARM architecture. Some +processors, such as many supporting the armv8 CPU architecture, also +support a 64-bit instruction set, referred to as aarch64. This is +sometimes referred to as a distinct port, [[NetBSD/aarch64|aarch64]], +with code in src/sys/arch/aarch64, but it is built as the evbarm port +with aarch64 cpu type, and available as the alias evbarm64. + +Note that MACHINE_ARCH=aarch64 currently refers to the A64 instruction +set and the aarch64 architecture, built for the armv8 architecture. +(Note also that armv8 is the first architecture to support aarch64, so +this will not be an issue until at least armv9.) -### Kernels and userland +### anita and qemu -The evbarm userland can be used on any system that can run code of the -CPU type used for the build. Typically, a particular board requires a -kernel for that board. +anita can be used to test builds. (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.) The release subdirectory should follow the naming convention on the autobuild cluster, used below. -### anita and qemu + - evbarm-earmv7hf uses "qemu-system-arm -M vexpress-a15" + - evbarm-aarch64 uses "qemu-system-aarch64 -M virt" + - Information on how to test emulated versions of other specific hardware is welcome. -anita can be used to test builds. evbarm-earmv7hf uses "qemu -M -vexpress-a15" and evbarm-aarch64 uses "qemu -M virt". (Information on -how to test emulated versions of other specific hardware is welcome.) +### invisible.ca builds + +NetBSD developer Jared McNeill provides [builds of NetBSD-current for a vast variety of hardware.](https://www.invisible.ca/arm/) In addition to the standard build, these images have board-specific uboot contents. See also /usr/pkgsrc/sysutils/u-boot*. ### Board specific information - [[Allwinner sunxi family SoCs|Allwinner]] - - [[BeagleBone and BeagleBone Black|BeagleBone]] + - [[BeagleBone, BeagleBone Black, and PocketBeagle|BeagleBone]] - [[NVIDIA Tegra|Tegra]] - [[ODROID C1 and C1+|ODROID-C1]] - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]] -""" +### SSH configuration for installtion +The default configuration will connect to the local network via DHCP and +run an SSH server. In order to use the SSH server, we must configure +users. This can be done by writing to the SD card's MS-DOS partition. + +Create a creds.txt file and use: + + useradd user password + + + +""" supported_hardware=""" -**NOTE**: This list is incomplete. For a full list of configurations, please see the [evbarm kernel configs](http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/evbarm/conf/) directory in CVS. +**NOTE**: This list is incomplete. For a full list of boards, please see the [GENERIC DTS files](http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/arch/evbarm/conf/GENERIC). [[!toc startlevel=3]]