Etesting

Deploy_Manual.4D02

发表于 | 分类于 ， |

Introduction

This documentation describes how to get, build, deploy and bring up target system based Estuary Project, it will help you to make your Estuary Environment setup from ZERO.
All following sections will take the D02 board as example, other boards have the similar steps to do, for more detail difference between them, please refer to Hardware Boards sections in http://open-estuary.com/hardware-boards/.

Preparation

Prerequisite

Local network: To connect hardware boards and host machine, so that they can communicate each other.
Serial cable: To connect hardware board’s serial port to host machine, so that you can access the target board’s UART in host machine.

Two methods are provided to connect the board’s UART port to a host machine:
Method 1 : connect the board’s UART in openlab environment
Use board_connect command.(Details please refer to board_connect --help)
Method 2 : directly connect the board by UART cable
a. Connect the board’s UART port to a host machine with a serial cable.
b. Install a serial port application in host machine, e.g.: kermit or minicom.
c. Config serial port setting:115200/8/N/1 on host machine.
For more details, please refer to UEFI_Manual.md “Upgrade UEFI” chapter.

Check the hardware board

Hardware board should be ready and checked carefully to make sure it is available, more detail information about different hardware board, please refer to http://open-estuary.com/d02-2/.

Upgrade UEFI and trust firmware

You can upgrade UEFI and trust firmare yourself based on FTP service, but this is not necessary. If you really want to do it, please refer to UEFI_Manual.md.

Upgrade DTB file(Necessary step)

Because this dtb file is important to this D02 boards, firstly you must flash this DTB file into SPI flash before any methods of bringing up systerm.

“EFI internal shell” mode and “Embedded Boot Loader(EBL)” mode often used to upgrade DTB file , about how to enter two modes and how to switch between them, please refer to UEFI_Manual.md “Upgarde UEFI” chapter.

  1. IP address config at “EFI Internal Shell” mode(Optional, you can ignore this step if DHCP works well)
    Press any key except “enter” key to enter into UEFI main menu. Select “Boot Manager”->”EFI Internal Shell”.

    1
    2
    # Config board's IP address
    ifconfig -s eth0 static <IP address> <mask> <gateway>

    e.g. ifconfig -s eth0 static 192.168.1.4 255.255.255.0 192.168.1.1

  2. Download dtb file from FTP at “Embedded Boot Loader(EBL)” mode
    Enter “exit” from “EFI Internal Shell” mode to the UEFI main menu and choose “Boot Manager”-> “Embedded Boot Loader(EBL)”after setting the IP address done. 

    1
    2
    3
    4
    # Download file from FTP server to target board's RAM
    provision <server IP> -u <ftp user name> -p <ftp password> -f <dtb file> -a <download target address>
    # Write data into FLASH
    spiwfmem <source address> <target address> <data length>

    e.g.

    1
    2
    provision 192.168.1.107 -u sch -p aaa -f hip05-d02.dtb -a 0x100000 
    spiwfmem 0x100000 0x300000 0x100000

  3. Reboot your D02 board
    You must reboot your D02 board after above two steps, this new DTB file will be used on booting board.
    Note: It is necessary to flash the DTB file to SPI flash to solve a known MAC address duplicate Issue. Also it is to be noted that the DTB file should not be input in the Grub config file. So if you wish to use a modified DTB file, then you should always have it flashed to SPI flash before bootup.

Bring up System

There are several methods to bring up system, you can select following anyone fitting you to boot up.

Boot via ESL

In this boot mode, the kernel image, dtb file and rootfs file should be downloaded into RAM at first and then start the system by ESL.
After reboot or power off, all downloaded data will be lost.
This boot mode is just used for debugging.

Boot D02 to UEFI main menu. Select “Boot Manager”->”Eembedded Boot Loader(EBL)” and type the follow commands in EBL:

  1. Download Image binary file from FTP server to target board’s RAM

    1
    2
    # Download Image binary file from FTP server to target board's RAM
    provision <server IP> -u <ftp user name> -p <ftp password> -f <Image binary file> -a <download target address>

    e.g. provision 192.168.1.107 -u sch -p aaa -f Image -a 0x80000

  2. Download dtb file from FTP server to target board’s RAM

    1
    2
    # Download dtb file from FTP server to target board's RAM
    provision <server IP> -u <ftp user name> -p <ftp password> -f <dtb file> -a <download target address>

    e.g. provision 192.168.1.107 -u sch -p aaa -f hip05-d02.dtb -a 0x06000000

  3. Download rootfs file from FTP server to target board’s RAM

    1
    2
    # Download rootfs file from FTP server to target board's RAM
    provision <server IP> -u <ftp user name> -p <ftp password> -f <rootfs file> -a <download target address>

    e.g. provision 192.168.1.107 -u sch -p aaa -f mini-rootfs-arm64.cpio.gz -a 0x07000000

  4. Start operating system
    Type “exit” to exit EBL. Select “Boot Manager”->”ESL Start OS” menu to start operating system.

Boot via NORFLASH

In this boot mode, kernel image, dtb file and rootfs file will be writen into NORFLASH. Before the kernel start, the kernel image, dtb fille and rootfs file will be loaded into RAM from NORFLASH.
Boot D02 to UEFI main menu. Select “Boot Manager”->”Eembedded Boot Loader(EBL)” and type the follow commands in EBL:

  1. Download Image binary file from FTP 

    1
    2
    3
    4
    # Download file from FTP server to target board's RAM
    provision <server IP> -u <ftp user name> -p <ftp password> -f <kernel image file> -a <download target address>
    # Write data into NORFLASH
    norwfmem <source address> <target address> <data length>

    e.g.:

    1
    2
    provision 192.168.1.107 -u sch -p aaa -f Image -a 0x100000
    norwfmem 0x100000 0x100000 0x1f00000

  2. Download rootfs file from FTP 

    1
    2
    3
    4
    # Download file from FTP server to target board's RAM
    provision <server IP> -u <ftp user name> -p <ftp password> -f <rootfs image> -a <download target address>
    # Write data into NORFLASH
    norwfmem <source address> <target address> <data length>

    e.g.:

    1
    2
    provision 192.168.1.107 -u sch -p aaa -f mini-rootfs-arm64.cpio.gz -a 0x100000
    norwfmem 0x100000 0x2000000 0x4000000

  3. Reboot D02 and press anykey except “enter” to enter UEFI Boot Menu

  4. Select “Boot Manager”->”FLASH Start OS” boot option and press “Enter”

To get all binaries mentioned above, please refer to Readme.md.

Boot via PXE

In this boot mode, the UEFI will get grub from PXE server.
The grub will get the configuration file from TFTP service configured by PXE server.

  1. Setup PXE environment on host
    Enable both DHCP and TFTP services on one of your host machines according to Setup_PXE_Env_on_Host.md.
  2. Reboot and press anykey except “enter” to enter UEFI main Menu
  3. Select “Boot Manager”->”EFI Network” and press “Enter”.
  4. After several seconds, D02 will boot by PXE automatically.

To config the grub.cfg to support PXE boot, please refer to Grub_Manual.md.

Boot via NFS

In this boot mode, the root parameter in grub.cfg menuentry will set to /dev/nfs and nfsroot will be set to the path of rootfs on NFS server. You can use "showmount -e <server ip address>" to list the exported NFS directories on the NFS server. You can use “showmount -e “ to list the exported NFS directories on the NFS server.
D02 supports booting via NFS, you can try it as following steps:

  1. Enable DHCP, TFTP and NFS service according to Setup_PXE_Env_on_Host.md.
  2. Get and config grub file to support NFS boot according to Grub_Manual.md.
  3. Reboot D02 and press anykey except “enter” to enter UEFI main Menu
  4. Select “Boot Manager”->”EFI Network” to and press enter key.

Boot via DISK(SAS/USB/SATA)

D02 board supports booting via SAS and USB disk by default, if you want to boot via SATA, there are two different methods for you, one is to plug SATA disk into PCIE-to-SATA convert card(model:PEC-2024) which connect to D02 board, another is to connect SATA disk into SATA interface on D02 board directly. Usually the first is more stable than the second, so we suggest you to use the first method.
For SAS and USB, the UEFI will directly get the grub from the EFI system partition on the hard disk. The grub will load the grub configuration file from the EFI system partition. So grubaa64.efi, grub.cfg, Image and different estuary release distributions are stored on disk. But for SATA boot mode, the kernel image will be loaded from NORFLASH into RAM on target board. The root parameter passed to the kernel will be specified in hip05-d02.dts and it will point to the root partition on SATA disk.

  1. Boot by PXE or NORFLASH(please refer to “#Boot via PXE” or “#Boot via NORFLASH”) to part and format hardware disk before booting D02 board
    Format hardware disk, e.g.:

    1
    2
    sudo mkfs.vfat /dev/sda1
    sudo mkfs.ext4 /dev/sda2

    Part hardware disk with "sudo fdisk /dev/sda" as follow:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    +---------+-----------+--------------+------------------+------------------+
    | Name    |   Size    |    Type      |   USB/SAS        |   SATA           |
    +---------+-----------+--------------+------------------+------------------+
    | sda1    |   200M    |  EFI system  |   EFI            |    NULL          |
    +---------+-----------+--------------+------------------+------------------+
    | sda2    |   10G     |    ext4      | linux filesystem | linux filesystem |
    +---------+-----------+--------------+------------------+------------------+
    | sda3    |   10G     |    ext4      | linux filesystem | linux filesystem |
    +---------+-----------+--------------+------------------+------------------+
    | sda4    |   10G     |    ext4      | linux filesystem | linux filesystem |
    +---------+-----------+--------------+------------------+------------------+
    | sda5    |rest space |    ext4      | linux swap       | linux swap       |
    +---------+-----------+--------------+------------------+------------------+

    Note: EFI partition must be a fat filesystem, so you should format sda1 with “sudo mkfs.vfat /dev/sda1″.

    Preprocess when the disk can’t be identified
    In case of the SATA disk is not be identified by D02, you can try the following step to process the disk. (it can be useful for some specfic disk such as seagate disk made by samsung).

    a. Find a PC or another board which can identify SATA disk.
    You should find a PC or another board which can identify this disk, and the system of PC or board should be linux system. For us,we can use D01 board.
    b. Use tool fdisk to process this disk

    format the disk firstly: sudo mkfs.ext4 /dev/sda

    add a gpt to this disk :
    fdisk /dev/sda
    g——-add a gpt partition

    add some EFI partition :
    n——-add a partition
    1——-the number of partition

    type “Enter” key —— First sector
    +200M———Last sector, size of partition
    t——-change the type of partition to EFI system

    add some anther partition ...
    save the change: w

    format EFI partition: sudo mkfs.vfat /dev/sda1

    Then this disk can be identified by D02 board.

  2. Download files and store them into hardware disk as below:
    (SAS/USB）Related files are placed as follow:

    1
    2
    3
    4
    5
    6
    7
    8
    9
    sda1: -------EFI
          |       |
          |      GRUB2------grubaa64.efi  //grub binary file
          |
          |-------------grub.cfg           //grub config file
          |
          |-------------Image          //kernel binary Image
    sda2: Ubuntu distribution
    sda3: Fedora distribution

    NOTE: The grubaa64.efi file must be put in /EFI/GRUB2 directory of dev/sda1(gpt partition), the distributions could be uncompressed in dev/sdaX(X can be 2,3,4,etc. exclude 1).

    (SATA)Related files are placed as follow:

    1
    2
    3
    4
     
    sda1: -------NULL
    sda2: Ubuntu distribution
    sda3: OpenSUSE distribution

    To get kernel image and dtb file, please refer to Readme.md.
    To get and config grub and grub.cfg, please refer to Grub_Manual.md.
    To get different distributions, please refer to Distributions_Guider.md.

  3. Boot the board via SAS/USB/SATA

Boot via SAS/USB

a. modify grub config file (https://github.com/open-estuary/estuary/blob/master/doc/Grub_Manual.4All.md)

e.g.: the context of grub.cfg file is modified as follow:

1
2
3
4
5
6
7
8
9
10
11
12
# Sample GRUB configuration file
#
# Boot automatically after 5 secs.
set timeout=5
# By default, boot the Estuary with Ubuntu filesystem
set default=ubuntu
# For booting GNU/Linux
menuentry "ubuntu" --id ubuntu {
search --no-floppy --fs-uuid --set=root <UUID>
linux /Image rdinit=/init pcie_aspm=off root=PARTUUID=<PARTUUID> rootwait rootfstype=ext4 rw console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000 ip=dhcp
      }

Note:

  1. <UUID> means the UUID of that partition which your EFI System is located in.
    <PARTUUID> means the PARTUUID of that partition which your linux distribution is located in.
    To see the values of UUID and PARTUUID, please use the command:$blkid.
  2. If you want to use another linux distribution, please refer above steps.

b. Reboot and press any key except “enter” into enter UEFI menu.
c. For USB: Select “Boot Manager”-> “EFI USB Device”-> to enter grub selection menu.
For SAS: Select “Boot Manager”-> “EFI Misc Device 1” to enter grub selection menu.
d. Press arrow key up or down to select grub boot option to decide which distribution should boot.

Boot via SATA

In this boot mode, there are two different methods for you, one is to plug SATA disk into PCIE-to-SATA convert card(model:PEC-2024) which connect to D02 board,another is to connect SATA disk into SATA interface on D02 board directly.

The first one: to plug SATA disk into PCIE-to-SATA convert card(model:PEC-2024) which connect to D02 board

a. Build kernel(please refer to [Readme.4D02.md] (https://github.com/open-estuary/estuary/blob/master/doc/Readme.4D02.md))
Modify arch/arm64/boot/dts/hisilicon/hip05-d02.dts file as follow:

1
bootargs = "rdinit=/init pcie_aspm=off root=/dev/sda2 rootdelay=10 rootfstype=ext4 rw console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000 ip=dhcp"

After build the linux kernel from source, burn Image into Nor Flash and dtb file into SPI Flash. About how to burn Image and dtb file , please refer to “Boot via NORFLASH” and “Upgrade DTB file”.

NOTE: according to above bootargs, it will boot ubuntu distribution in sda2, if you want to boot other different distribution, you should change “root=/dev/sdaX” item.
b. Reboot and press any key into enter UEFI menu.
c. Select “Boot Manager”->”FLASH Start OS” and then press Enter Key.

The second one: to connect SATA disk into SATA interface on D02 board directly

a. select sata mode for UEFI
After burn BIOS file(you can refer to UEFI_Manual.4D02.md), UEFI boot as sas mode by default.
You can switch between sata and sas by adding a commandline at EBL.
e.g.:

1
2
3
sataenable 0      //set into sas
sataenable 1      //set into sata
sataenable 2      //check the current setting: sas or sata

b. Modify arch/arm64/boot/dts/hisilicon/hip05-d02.dts file

  • Find the word “bootargs” and modify the value as follow: 

    1
    bootargs = "rdinit=/init pcie_aspm=off root=/dev/sda2 rootdelay=10 rootfstype=ext4 rw console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000 ip=dhcp"

  • Find the word “&sas0”, “&sas1” and delete as follow:
    &sas0 {
    status = “okay”;,
    };
    &sas1 {
    status = “okay”;
    };

c. Modify arch/arm64/boot/dts/hisilicon/hip05.dtsi file

Change the status’ value of node “ahci0: sata@b1002800” to “disabled” as follow:

1
2
3
4
ahci0: sata@b1002800 {
         ......
status = "disabled";      ---------> status = "okay";
     };

d. Build the kernel (please refer to [Readme.4D02.md] (https://github.com/open-estuary/estuary/blob/master/doc/Readme.4D02.md))
e. Burn Image, dtb file NorFlash. About how to burn, please refer to “Boot via NORFLASH”.
f. Reboot and press any key except “enter” to enter UEFI menu.
g. Select “Boot Manager”->”FLASH Start OS” and then press Enter Key.

Boot via ACPI

D02 also supports booting via ACPI, you can bring up this system which is similar with DTS mode, you must fix some point as follow:

  • Delete DTB file(comment out devicetree //hip05-d02.dtb as follow) and don’t burn DTB file
    e.g.: 

    1
    2
    3
    4
    5
    menuentry "D02 Ubuntu NFS" --id d02_ubuntu_nfs {
    set root=(tftp,192.168.1.107)
    linux /Image rdinit=/init pcie_aspm=off console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000 root=/dev/nfs rw nfsroot=192.168.1.107:/home/ftp/user/rootfs_ubuntu64 ip=dhcp
    # devicetree /<user>/hip05-d02.dtb
    }

  • Set the parameters of booting via ACPI
    you must add "acpi=force" property in "linux" line for “grub.cfg” file. If not, system will booted up with DTS by default.
    e.g.: 

    1
    2
    3
    4
    5
    # Booting from NFS with Ubuntu rootfs
    menuentry "D02 Ubuntu NFS(ACPI)" --id d02_ubuntu_nfs_acpi {
    set root=(tftp,192.168.1.107)
    linux /Image rdinit=/init pcie_aspm=off console=ttyS0,115200 earlycon=uart8250,mmio32,0x80300000 root=/dev/nfs rw nfsroot=192.168.1.107:/home/ftp/user/rootfs_ubuntu64 ip=dhcp acpi=force
    }

NOTE: you can get more information about setting grub.cfg from Grub_Manual.md.

热评文章