2018-05-25 23:34:41 +08:00
.. _getting_started_up2:
Getting started guide for UP2 board
###################################
2018-05-17 11:28:26 +08:00
Hardware setup
2018-05-25 23:34:41 +08:00
***** ***** *** *
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
The `UP Squared board <http://www.up-board.org/upsquared/> `_ (UP2) is the x86 maker board based on Intel Apollo Lake platform. The UP boards have been used in IoT, industrial automation, digital signage and more. The UP2 features Intel `Celeron N3550 <https://ark.intel.com/products/95598/Intel-Celeron-Processor-N3350-2M-Cache-up-to-2_4-GHz> `_ and Intel `Pentium N4200 <https://ark.intel.com/products/95592/Intel-Pentium-Processor-N4200-2M-Cache-up-to-2_5-GHz> `_ SoCs. Both have been confirmed to work with ACRN.
2018-05-17 11:28:26 +08:00
Connecting to the serial port
2018-05-25 23:34:41 +08:00
=============================
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
The UP2 board has two serial ports. Please refer to the `UP2 specifications <http://www.up-board.org/upsquared/specifications-up2/> `_ for more information. We'll access the serial port through the I/O pins in the 40-pin HAT connector using a `USB TTL serial cable <http://www.ftdichip.com/Products/USBTTLSerial.htm> `_ . Connect pin 6 (`` GND `` ), pin 8 (`` TX `` ) and pin 10 (`` RX `` ) of the HAT connector to respectively the `` GND `` , `` RX `` and `` TX `` pins of your USB serial cable. Plug the USB TTL serial cable into your PC and use a console emulation tool such as `` minicom `` or `` putty `` to communicate with the UP2 board for debugging.
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
Software setup
***** ***** *** *
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
Setting up the ACRN hypervisor (and associated components) on the UP2
board is no different than other hardware platforms so please follow
the instructions provided in the :ref: `getting_started` .
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
There are a few parameters specific to the UP2 board that differ from
what is referenced in the :ref: `getting_started` section:
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
1. Serial Port settings
#. Storage device name
#. `` pci_devices_ignore `` parameter
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
You will need to keep these in mind in a few places:
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
* When mounting the EFI System Partition (ESP)
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
.. code-block :: console
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
# mount /dev/mmcblk0p1 /mnt
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
* When adjusting the `` acrn.conf `` file
* Change the `` options `` line and set `` pci_devices_ignore=(0:18:1) ``
* Set the `` root= `` parameter using the `` PARTUUID `` or device name directly
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
* When configuring the EFI firmware to boot the ACRN hypervisor by default
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
.. code-block :: console
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
# efibootmgr -c -l "\EFI\acrn\acrn.efi" -d /dev/mmcblk0 -p 1 -L "ACRN Hypervisor" \
-u "bootloader=\EFI\org.clearlinux\bootloaderx64.efi uart=mmio@0x9141e000"
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
UP2 serial port setting
=======================
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
The serial port in the 40-pin HAT connector is located at `` MMIO 0x0x9141e000 `` .
You can check this from the `` dmesg `` output from the initial Clearlinux installation.
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
.. code-block :: console
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
# dmesg | grep dw-apb-uart
[2.150689] dw-apb-uart.8: ttyS1 at MMIO 0x91420000 (irq = 4, base_baud = 115200) is a 16550A
[2.152072] dw-apb-uart.9: ttyS2 at MMIO 0x9141e000 (irq = 5, base_baud = 115200) is a 16550A
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
The second entry associated with `` dw-apb-uart.9 `` is the one on the 40-pin HAT connector.
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
UP2 block device
================
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
The UP2 board has an on-board eMMC device. The device name to be used
throughout the :ref: `getting_started` therefore is `` /dev/mmcblk0 ``
(and `` /dev/mmcblk0pX `` for any partition).
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
The UUID of the partition `` /dev/mmcblk0p3 `` can be found by
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
.. code-block :: console
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
# blkid /dev/mmcblk
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
.. note ::
You can also use the device name directly, e.g.: `` root=/dev/mmcblk0p3 ``
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
Running the hypervisor
***** ***** ***** ***** **
2018-05-17 11:28:26 +08:00
2018-05-25 23:34:41 +08:00
Now that the hypervisor and Service OS have been installed on your UP2 board,
you can proceed with the rest of the instructions in the :ref: `getting_started`
and install the User OS (UOS).
2018-05-17 11:28:26 +08:00