Skip to content

Commit

Permalink
Merge pull request #361 from home-assistant/dev
Browse files Browse the repository at this point in the history
Release 3.0
  • Loading branch information
pvizeli authored Feb 21, 2019
2 parents c37a6d4 + 2703ec3 commit aa392e7
Show file tree
Hide file tree
Showing 105 changed files with 9,989 additions and 1,000,439 deletions.
23 changes: 23 additions & 0 deletions Documentation/boards/odroid-xu4.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Odroid-XU4

## eMMC

The Odroid XU4 has a hidden boot sector that is only visible on the Odroid itself (can't be written by a card reader). There are a couple possibilities:
1) If the eMMC already had a working image before flashing HassOS:
* It will be booting to uBoot (but no further).
* If you have the serial adapter, you should be able to enter `distro_bootcmd` at the uboot prompt to continue booting.
* If not, flash the HassOS image to an SD card and boot off that temporarily (while the eMMC is also plugged in).
* Once booted, login at the prompts and then enter `dd if=/dev/mmcblk0 of=/dev/mmcblk0boot0 bs=512 skip=63 seek=62 count=1440` at the linux prompt.
* Reboot with eMMC (don't forget to flip the boot switch to eMMC)
2) Clean/wiped/corruped boot sector:
* You'll need to follow [Hardkernel's instructions](https://forum.odroid.com/viewtopic.php?f=53&t=6173) to get a working boot sector. Then flash HassOS and follow instructions above.
* Alternatively, you can try flash HassOS to both an SD and eMMC, then boot off the SD with the eMMC also plugged in, then run `dd if=/dev/mmcblk1 of=/dev/mmcblk0boot0 bs=512 skip=1 seek=0 count=16381` at the Linux prompt. Note that this is untested, but in theory should work..

## Console

By default, console access is granted over the serial header and over HDMI. Certain startup messages will only appear on the serial console by default. To show the messages on the HDMI console instead, swap the order of the two consoles in the `cmdline.txt` file on the boot partition. You can also delete the SAC2 console if you don't plan on using the serial adapter.
eg. `console=tty1 console=ttySAC2,115200`

## GPIO

Refer to [the odroid wiki](https://wiki.odroid.com/odroid-xu4/hardware/expansion_connectors).
6 changes: 3 additions & 3 deletions Documentation/boards/tinker.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,11 +7,11 @@ Supported Hardware:
| Tinker RK3288 | tinker |
| Tinker S RK3288 | tinker |

## EMMC
## eMMC

Actual we support only SD cards. The support for EMMC will follow.
eMMC support is provided transparently. Just flash the image to the eMMC by connecting your Tinker Board S to your PC via Micro-USB.

## Serial console

For access to terminal over serial console, add `console=ttyS2,115200` to `cmdline.txt`. GPIO pins are: 34 = GND / 32 = UART TXD / 33 = UART RXD.
To access the terminal over serial console, add `console=ttyS2,115200` to `cmdline.txt`. GPIO pins are: 34 = GND / 32 = UART TXD / 33 = UART RXD.

6 changes: 3 additions & 3 deletions Documentation/kernel.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,9 @@

| Board | Version |
|-------|---------|
| Open Virtual Applicance | 4.14.82 |
| Raspberry Pi | 4.14.81 |
| Tinker Board | 4.14.82 |
| Open Virtual Applicance | 4.19.20 |
| Raspberry Pi | 4.14.98 |
| Tinker Board | 4.19.20 |
| Odroid-C2 | 4.19.15 |
| Odroid-XU4 | 4.19.15 |
| Orangepi-Prime | 4.19.13 |
Expand Down
Loading

0 comments on commit aa392e7

Please sign in to comment.