Armbian. Chromium OS for SBC. PicUntu. RISC OS Open. Supporting RISC OS Open RISC OS is getting ever more popular and there are more people trying it out every day. While this is great, please remember that this also means an increase in the amount of work ROOL and our helpers are having to do behind the scenes, as well as increases in our operating costs. Please consider donating something to help us to keep making RISC OS better. What are you interested in? RISC OS has been ported to a variety of platforms. Developers will no doubt be wanting to download the RISC OS source code from the links below: We also provide source code for our website, for anyone who is interested: If you want to have direct access to our source code repositories, you should look at this page for accessing CVS (the RISC OS source tree) and this page for accessing Subversion (the website source tree). BeagleBoard and PandaBoard logos are distributed under the CC BY-SA licence, courtesy of the respective BeagleBoard and PandaBoard sites.
Angstrom. Ubuntu ac100. Ubuntu on AC100 is currently an official demonstration of the Ubuntu ARM port and works fairly well. This page collects information necessary to get a working Ubuntu 12.04 port on the AC100. Installing Ubuntu 12.04 or Lubuntu 12.10 on the AC100 Installation requirements Mini-usb cable Host computer with linux (virtual or physical) Usb-stick or sd-card (min. 1GB) About 1-2h of your life (depending on the download-time) Files to download For the installation, you will need to download these things: 12.04 (Precise Installer) There are two AC100 related files in the 12.04 release directory: Get them both and make sure that the md5sum corresponds after the download. 12.10 (Quantal Installer) With the 12.10 release the AC100 image switched to Lubuntu as the default desktop.
There are two AC100 related files in the 12.10 release directory: nvflash The bootimage needs to be flashed via a mini-USB cable and using the nvflash tool. Install nvflash using a debian package Installation Flashing the bootimage. Arch Linux. Fedora. ARM chips are the most widely-produced processor family in the world; they have historically been used in cell phones and embedded applications, and are increasingly used in tablet devices and low-power-consumption servers. The Fedora-ARM project is an initiative to bring Fedora to this processor family. New to ARM and not sure how to get started?
What is the difference between ARM and ARMHFP? Use our Secret Decoder Ring document to get up to speed quickly and start using and contributing to Fedora ARM. ARM Secret Decoder Ring Fedora 20 This is the most recent stable release of Fedora. For virtualization through QEMU: Versatile Express (Cortex A9 & A15 emulation) Fedora for ARM - Releases and Remixes If you are looking to use Fedora on a device that isn't mentioned above it may not have official support due to licensing issues or lack of upstream support. Raspberry Pi Pidora, the optimized Fedora Remix released by Seneca College can be found at . Creating a Fedora Remix for ARM. Linaro. Tiny Core. OpenSUSE. Most all of the usual openSUSE distribution (>6000 packages) builds and runs on all the ARM hardware we have tested it on so far. Thanks to OBS we can cross build and if need be cross compile packages for numerous architectures (ARM included) which speeds up our efforts significantly. Currently we target armv7l/armv7hl (hard floating point with aapcs-linux ABI, for armv7) and armv6l/armv6hl (hard floating point, for armv6).
If you have knowledge and experience, please help out. If you don't take part you have no justification to complain - you've got to be in it to win it ;-) If you're looking for 64bit ARM, see the AArch64 page. Feel free to join the openSUSE ARM mailing list as well as the #openSUSE-arm IRC channel for questions or help. We are also actively looking for people to enable hardware we don't support yet. If you have an armv7 based device that doesn't work yet and are willing to spend some time to get it working with openSUSE, please contact us on the mailing list.
FreeBSD. Planning for getting ARM to Tier 1 EABI status Boards that are supported or currently in the works: ArndaleBoard (Samsung Exynos5250) Atmel AT91RM9200 BeagleBoard and BeagleBoard-xM (TI OMAP3) - GSoC 2012, stable - aleek@ BeagleBone Cubieboard(1,2) (Allwinner A10/A20) Device Solutions Quartz Gateworks Avila GW2348 Gateworks Cambria GW2358 Genesi Efika MX Smarttop Genesi Efika MX Smartbook Globalscale Technologies OpenRD platform Kwikbyte KB9202B (as well as the older KB9202 and KB9202A) Marvell DB-88F5182, DB-88F5281, DB-88F6281, RD-88F6281, DB-78100 Marvell DB-88F6781 (ARMv6) Marvell DB-78460 (ARMv7) Marvell Sheeva Plug Marvell Dream Plug Pandaboard (OMAP4) Phytec Cosmic Board (Freescale Vybrid Family) Raspberry Pi Radxa Rock (Work in progress) SBC6045 with Atmel at91sam9g45 - under heavy development - aleek@ Technologic Systems TS-7200 Technologic Systems TS-7800 Wandboard Zedboard (Xilinx Zynq) Colibri VF50 Evaluation Board (r261411) CPUs that are supported or currently in the works:
NetBSD. About NetBSD/evbarm 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. Release Info Mailing List The NetBSD/arm mailing list, covering NetBSD's port to arm machine: [ subscribe | archive ] Mail the NetBSD/evbarm port maintainer Supported Hardware ADI Engineering BRH ("Big Red Head") The BRH is an evaluation and development platform for the Intel i80200 XScale processor.
Support for the BRH was written by Jason Thorpe, and contributed by Wasabi Systems, Inc. On-board NS16550-compatible serial ports (com)On-board Intel i82559 Ethernet on the PCI bus (fxp)On-chip timer on the BECC (used as system clock)Other devices inserted into the PCI slot The BRH comes with 128M of SDRAM. Allwinner Technology A10/A20/A31 Arcom Viper Support for the Arcom Viper was written by Antti Kantee. Tizen. Introduction The purpose of this Community page is to list all ongoing efforts to get Tizen on the ARM platform using Linux kernel Related pages : News Tizen:Common Tizen:Common now supports ARM arch (armv7l) ... At the moment packages and image's partitions are built, Since image depends on bootloaders configurations, you'll have to do the partition scheme your own and copy boot, rootfs parts over it.
The alternative is to work over the unofficial Sunxi image released. Related : Download As previously announced Tizen:Common is able to boot on ARM architecture ( watch video : ) Now let's me announce that generic ARM images are released on tizen's infra (thanks sdx) and can be used as a base. The default platform is ARM vexpress because it has good (best?)
Here the few steps to use it : Download and unpack tizen-common_20140812.3_common-qa-unsafe-wayland-2parts-armv7l.tar.gz from : Mount kernel partition : Hardware ARM vexpress / qemu. MINIX. This page describes how to build and run Minix/ARM. The Minix ARM port targets the BeagleBoard-xM and it's QEMU based emulator, the BeagleBone and the BeagleBone Black products from the BeagleBoard community. These are all based on system on chip designs from TI and all contain a Cortex-A8 ARM core. The code is developed and integrated in the same (master) code branch as the official MINIX3 x86 port. This is a preliminary list of what's supported and what isn't. Feel free to add anything important that was left off the list and/or update the list with the latest developments. First do a checkout of the code $ mkdir -p $HOME/minix $ cd $HOME/minix $ git clone src $ cd src Secondly configure your build by creating a .settings file.
For the BeagleBoard-xM use these settings: # beagleboard-xm U_BOOT_BIN_DIR=build/omap3_beagle/ CONSOLE=tty02 For the BeagleBone(s) use the following settings: #beaglebone (and black) U_BOOT_BIN_DIR=build/am335x_evm/ CONSOLE=tty00 $ . reboot. Freescale Yocto. Yoctoproject is a framework for creating Linux distributions for embedded devices. Its layering mechanism makes it easy to add Linux to new target devices highly customized for a particular platform; it can include custom start-up scripts, software packages built with a high degree of optimization for a particular architecture, and different user interfaces from full Gnome desktop to a simple a serial console.
Yocto has 2 basic layers: board support packages layer and core layer. In the BSP layer is where all the custom software and configuration tweaks for a particular platform are included, while the core layer provides the common software stack to provide from a simple command line interface to Sato desktop interface (Matchbox based and Gnome mobile software stack). A third layer could be added to provide additional user interfaces LXDE, XFCE, and more; YP is quite flexible&emdash;one of it major strengths.
For example, if building machine was an Ubuntu machine: Testing Yocto for i.MX6. A20 Yocto. Some time ago I ordered a A20-OLinuXino-LIME-4GB board. This was planed as a replacement for my not so beloved Raspberry PI. I am not that big fan of the PI because of the wacky SD-Card holder and the USB stability. I hope the 4GB NAND of the A20-OLinuXino-LIME-4GB Will improve the stability of my target application. [Update - 2014-10-01] I’ve created a successful pull-request to merge my changes into the meta-sunxi repository and succeeded with the current master branch.
Maybe I also start a pull request for the daisy branch. As a big fan of the Yocto Project I decided to run poky on my OLinuXino. Clone the git repositories and switch to the daisy branch. mkdir /data/src/yocto cd /data/src/yocto git clone git clone cd poky git checkout -b daisy origin/daisy cd .. Prepare a warm and cozy environment for the build cd /data/src/yocto/poky mkdir -p .. Add the sunxi meta-layer to the build environment.