odroid c2 android 6 image download Odroid c2 android 6 image download. Completing the CAPTCHA proves you are a human and gives you temporary access to the web property. What can I do to prevent this in the future? If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware. If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices. Another way to prevent getting this page in the future is to use Privacy Pass. You may need to download version 2.0 now from the Chrome Web Store. Cloudflare Ray ID: 66aa2216fddf1600 • Your IP : 188.246.226.140 • Performance & security by Cloudflare. ODROID. We will need a few things to get started with installing Home Assistant. Links below lead to Ameridroid. If you’re not in the US, you should be able to find these items in web stores in your country. To get started we suggest the ODROID N2+, it’s the most powerful ODROID. It’s fast and with built-in eMMC one of the best boards to run Home Assistant. It’s also the board that powers our Home Assistant Blue. If unavailable, we also recommend the ODROID C4 or ODROID XU4. Write the image to your installation media. Attach the installation media (eMMC module/SD card) to your computer. Download and start Balena Etcher. Select “Flash from URL” Get the URL for your ODROID: Select and copy the URL or use the “copy” button that appear when you hover it. Paste the URL for your ODROID into Balena Etcher and click “OK” Balena Etcher will now download the image, when that is done click “Select target” Select the eMMC module/SD card you want to use for your ODROID Click on “Flash!” to start writing the image When Balena Etcher is finished writing the image you will get this confirmation. Start up your ODROID. Insert the installation media (eMMC module/SD card) you just created. Attach a ethernet cable for network. Attach a cable for power. Within a few minutes you will be able to reach Home Assistant on homeassistant.local:8123. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at homeassistant:8123 or http://X.X.X.X:8123 (replace X.X.X.X with your ODROID’s IP address). With the Home Assistant Operating System installed and accessible you can continue with onboarding. Install Home Assistant Container. These below instructions are for an installation of Home Assistant Container running in your own container environment, which you manage yourself. Any OCI compatible runtime can be used, however this guide will focus on installing it with Docker. This guide assumes that you already have an operating system setup and a container runtime installed (like Docker). Platform Installation. Installation with Docker is straightforward. Adjust the following command so that /PATH_TO_YOUR_CONFIG points at the folder where you want to store your configuration and run it. Once the Home Assistant Container is running Home Assistant should be accessible using http://<host>:8123 (replace with the hostname or IP of the system). You can continue with onboarding. Restart Home Assistant. If you change the configuration you have to restart the server. To do that you have 3 options. In your Home Assistant UI go to the Configuration panel -> Server management and click the “Restart” button. You can go to the Developer Tools -> Services , select the service homeassistant.restart and click “Call Service”. Restart it from a terminal. Docker Compose. In order to use docker-compose you first need to install docker-compose on your system. As the Docker command becomes more complex, switching to docker-compose can be preferable and support automatically restarting on failure or system restart. Create a docker-compose.yml file: Start it by running: Exposing Devices. In order to use Z-Wave, Zigbee or other integrations that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the /dev/tty* file, then add the device mapping to your container instructions: Optimizations. The Home Assistant Container is using an alternative memory allocation library jemalloc for better memory management and Python runtime speedup. As jemalloc can cause issues on certain hardware, it can be disabled by passing the environment variable DISABLE_JEMALLOC with any value, for example: The error message <jemalloc>: Unsupported system page size is one known indicator. Install Home Assistant Core. This guide assumes that you already have an operating system setup and have installed Python 3.8 (including the package python3-dev ) or newer. Install dependencies. Before you start make sure your system is fully updated, all packages in this guide are installed with apt , if your OS does not have that, look for alternatives. Install the dependencies: Create an account. Add an account for Home Assistant Core called homeassistant . Since this account is only for running Home Assistant Core the extra arguments of -rm is added to create a system account and create a home directory. The arguments -G dialout,gpio,i2c adds the user to the dialout , gpio and the i2c group. The first is required for using Z-Wave and Zigbee controllers, while the second is required to communicate with GPIO. Create the virtual environment. First we will create a directory for the installation of Home Assistant Core and change the owner to the homeassistant account. Next up is to create and change to a virtual environment for Home Assistant Core. This will be done as the homeassistant account. Once you have activated the virtual environment (notice the prompt change to (homeassistant) [email protected]:/srv/homeassistant $ ) you will need to run the following command to install a required Python package. Once you have installed the required Python package it is now time to install Home Assistant Core! Start Home Assistant Core for the first time. This will complete the installation for you, automatically creating the .homeassistant configuration directory in the /home/homeassistant directory, and installing any basic dependencies. You can now reach your installation via the web interface on http://homeassistant.local:8123 . If this address doesn’t work you may also try http://localhost:8123 or http://X.X.X.X:8123 (replace X.X.X.X with your machines’ IP address). When you run the hass command for the first time, it will download, install and cache the necessary libraries/dependencies. This procedure may take anywhere between 5 to 10 minutes. During that time, you may get “site cannot be reached” error when accessing the web interface. This will only happen for the first time, and subsequent restarts will be much faster. We get commissions for purchases made through links in this post. ODROID-C2. The ODROID-C2 is a $40 quad-core computer, providing one of the most cost-effective ARMv8 AArch64 development boards available. Board dimensions are identical to the ODROID-C1, and it can use the same power supply or be powered through the micro USB port. Features of the board include: Amlogic S905 ARM Cortex-A53 1.5Ghz quad core CPU Mali-450 MP3 GPU (OpenGL ES 2.0/1.1) 2GB DDR3 SDRAM Gigabit Ethernet HDMI 2.0 4K/60Hz display 40+7pin IO port eMMC5.0 HS400 flash storage slot UHS-1 SDR50 MicroSD Card slot USB 2.0 Host x 4, USB OTG x 1 (power and data capable) Infrared (IR) Receiver. Micro SD and eMMC Creation. Replace sdX in the following instructions with the device name for the SD card as it appears on your computer. Use the provided micro SD to eMMC adapter card to install to eMMC. Zero the beginning of the SD card or eMMC module: Start fdisk to partition the SD card: At the fdisk prompt, create the new partition: Type o . This will clear out any partitions on the drive. Type p to list partitions. There should be no partitions left. Type n , then p for primary, 1 for the first partition on the drive, and enter twice to accept the default starting and ending sectors. Write the partition table and exit by typing w . For e2fsprogs = 1.43: Open the file root/boot/boot.ini with a text editor. Uncomment the line with the desired resolution, and ensure all others are commented. Save and close the file. Login as the default user alarm with the password alarm . The default root password is root . Additional Packages. X.org video driver package: xf86-video-odroid-c2 Note: Add your user to the "video" group to be able to access /dev/mali and /dev/ump. Note: Reboot after installation for udev rules to take effect. Headless Mode. For servers (ie, no need for a display), uncomment the following in /boot/boot.ini to free up approx 300M of memory at the cost of disabling the video subsystem: ODROIDs have dual LEDs: a red power LED which is always on if power is supplied, and a blue LED which can be configured. By default, the blue LED is a heartbeat LED, which flashes when the kernel is running. This can be configured in /sys/class/leds/blue:heartbeat/trigger . To list available triggers: Replace TRIGGER with one of the available triggers. This setting will apply instantly, but be lost upon reboot. To create a persistent configuration, edit or create /etc/tmpfiles.d/leds.conf : Copyright ©2009-2020 Arch Linux ARM The registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide basis.