*** [U5 SBC/Hisilicon/Linaro] Bero, Linaro LMG / LHG 최신 커널과 함께 AOSP TV 8.1, Gemini PDA, Android를 보여줍니다.

안녕하십니까 ?  EddyLab입니다.

U5PVR의 CPU인 Hisilicon CV200 기반 오픈소스를 약3년째 리서치를 하고 있습니다.  ^^

이는 U5 SBC를 기반으로 

네이티브 리눅스 부팅을 위한 자료를 모으고 있습니다. 

하기 내용은 Linaro프로젝트에서 96보드로 적용된 동일 Hisilicon CV200 관련

기술 내용을 보실 수 있습니다.

2018년 Linaro프로젝트에서는

Hisilicon CV200 기반으로 안드로이드 8.1을 올렸고,

독립 부팅 리눅스 데비안을 부팅 시켜 놓은 단계까지 왔습니다.

그러나, 아직 Hisilicon CV200의 GPU관련으로는

진행단계라고 하는 것 같네요...

차근차근 나가다보면, 좋은 결과가 있을 것으로 보여집니다. 

Bero, Linaro LMG / LHG 해킹 룸에서 최신 커널과 함께 AOSP TV 8.1, Gemini PDA, Android를 보여줍니다.

Charbax - 2018 년 3 월 24 일 게시자

Linaro Mobile Group (Android)과 Linaro Home Group (TV Boxes)의 Bero (Bernhard Rosenkränzer)와 그의 동료는 Linaro Connect의 해킹 룸에서 금요일 AOSP TV를 포함한 데모 금요일을 준비하고 있습니다 (대부분의 Android TV는 일부 최신 커널 버전으로 안드로이드 폰에 리눅스 커널을 업데이트) 7.1에서 실행되고 베로 또한 그가 구입 한 쌍둥이 PDA 놀라운 키보드 전화 (쌍둥이 자리 PDA 리눅스 지원에 내 비디오를 볼 부팅 멀티 리눅스에 대한 자신의 의견을 제공 여기 )

http://armdevices.net/2018/03/24/bero-of-linaro-lmg-lhg-aosp-tv-8-1-gemini-pda/

Bernhard Rosenkränzer

현재 Rosenkränzer는에서 작동 리나 , ^[3] 향상을 위해 최선을 다하고 조직 리눅스 에 ARM의 프로세서. 그는 또한 작동하는 데 사용 ROSA 연구소 , ^[4] 회사가 자신의 사용자 정의 브랜드 제공 맨드리바 리눅스를 러시아 정부에 대해. 이 작업의 일환으로 Ark Linux가 OpenMandriva 에 병합되었습니다 .

2012 년에는 Bionic (소프트웨어) 을 수정 하고 툴 체인을보다 잘 사용 하여 Linaro의 Android 빌드 속도를 높이는 작업에 참여했습니다 . ^[5]

2017 년 그는 AArch64 기반 데스크탑 및 노트북 컴퓨터의 프로토 타입 제작 및 데모 작업을 처음 으로 수행했습니다. ^[6]

https://en.wikipedia.org/wiki/Bernhard_Rosenkr%C3%A4nzer

Linaro Debian (Developer) and AOSP

https://www.96boards.org/documentation/enterprise/poplar/build/

96boards-poplar/Documentation

https://github.com/96boards-poplar/Documentation/

96boards-poplar/Documentation

https://github.com/96boards-poplar/Documentation/tree/master/debian

Building Poplar Debian System Recovery Media From Source

The instructions that follow describe the process for creating a USB flash drive suitable for use in recovering a Poplar system from a "bricked" state. The USB memory stick must be at least 2 GB.

Using prebuilt image files

Step 1: Download images

Download prebuilt images from https://releases.linaro.org (coming soon! Until then, please build from source using the instructions in the Building the image files from source section below.

Step 2: Prepare the images directory

Follow Step 7 in the Build everything section of debian_build_instructions.md to place the images to the TFTP directory.

Step 3: Recover board

Follow the prepare a USB flash drive section below until the end of the document.

In the Step 3: Copy "fastboot.bin" to the drive section, you can use https://github.com/96boards-poplar/l-loader/raw/master/installer/fastboot.bin rather than build the "fastboot.bin" file yourself.

Building the image files from source

Follow the instructions in debian_build_instructions.md to create image suitable for use in a Poplar system, with the following exceptions:

Step 1: Build ARM Trusted Firmware components for recovery.

Add POPLAR_RECOVERY=1 to the end of the make command, as shown below:

    cd ${TOP}/arm-trusted-firmware
    make distclean
    make CROSS_COMPILE=${CROSS_64} all fip DEBUG=1 PLAT=poplar SPD=none \
        BL33=${TOP}/u-boot/u-boot.bin POPLAR_RECOVERY=1

Step 2: Build "l-loader" for recovery

Add RECOVERY=1 to the end of the make command, as shown below:

    cp ${TOP}/arm-trusted-firmware/build/poplar/debug/bl1.bin atf/
    cp ${TOP}/arm-trusted-firmware/build/poplar/debug/fip.bin atf/
    make clean
    make CROSS_COMPILE=${CROSS_32} RECOVERY=1

Once you are done with Step 7 in the Build everything section, come back to this document.

To allow recovery of a Poplar board in a "bricked" state, prepare a USB flash drive.

Step 1: Identify your USB flash drive device

Insert the USB flash drive into your host system, and identify your USB device:

	grep . /sys/class/block/sd?/device/model

If you recognize the model name as your USB flash device, then you know which "sd" device to use. Here is an example:

	/sys/class/block/sdh/device/model:Patriot Memory
	                 ^^^

I had a Patriot Memory USB flash drive, and the device name I will want is "/dev/sdh" (based on "sdh" above). Record this name:

	USBDISK=/dev/sdh	# Make sure this is *your* device

The instructions that follow assume your USB flash drive needs to be formatted "from scratch." Once formatted, all that is required is to copy fastboot.bin to the first partition on the drive, and then properly eject the medium before removing the USB drive.

Step 2: Format the flash drive using MBR partitioning.

THIS IS VERY IMPORTANT. The following commands will COMPLETELY ERASE the contents of whatever device you specify here. So be sure USBDISK defines the flash device you intend to erase.

You will need superuser access. First, unmount anything mounted on that device:

    sudo umount ${USBDISK}?

Next, clobber any existing partitioning information that might be found at the beginning of the device:

    sudo dd if=/dev/zero of=${USBDISK} bs=2M count=1 status=none

Create a DOS MBR partition table on the USB flash drive with a single partition, and format that partition using FAT32.

    {   echo label:dos
	echo 1: start=8 size=62496KiB type=0x0c
	echo write
    } | sudo sfdisk --label dos ${USBDISK}
    sudo mkfs.fat -F 32 ${USBDISK}1

Step 3: Copy "fastboot.bin" to the drive

Finally, mount that partition and copy fastboot.bin into it. Once the partition has been unmounted and the device has been ejected, the USB stick can be removed.

    cd ${TOP}/recovery/recovery_files
    mkdir -p /tmp/usbdisk
    sudo mount -t vfat ${USBDISK}1 /tmp/usbdisk

    sudo cp fastboot.bin /tmp/usbdisk

    sudo umount /tmp/usbdisk
    rmdir /tmp/usbdisk
    sudo eject ${USBDISK}

(For a previously-formatted drive, simply inserting it will cause it be mounted automatically--normally under /media/...somewhere.)

Remove the USB flash drive from your host system.

De-brick a Poplar board in a "bricked" state

If a Poplar board is in a "bricked" state, it can be booted using the USB flash drive prepared above.

Step 1: Prepare the Poplar board for power-on

• The Poplar board should be powered off. You should have a cable from the Poplar's micro USB based serial port to your host system so you can connect and observe activity on the serial port. For me, the board console shows up as /dev/ttyUSB0 when the USB cable is connected. The serial port runs at 115200 baud. I use this command to see what's on the console:

      screen /dev/ttyUSB0 115200

Step 2: Insert the USB flash drive on the Poplar board

• There are a total of 4 USB connectors on the Poplar board. Two are USB 2.0 ports, they are stacked on top of each other. Insert the USB memory stick into one of these two.

• There is a "USB_BOOT" button on the board. It is one of two buttons on same side of the boards as the stacked USB 2.0 ports. To boot from the memory stick, this button needs to be depressed at power-on. You only need to hold it for about a second; keeping it down a bit longer does no harm.

• Next you will be powering on the board, but you need to interrupt the automated boot process. To do this, be prepared to press a key, perhaps repeatedly, in the serial console window until you find the boot process has stopped.

Step 3: Boot the Poplar board from the USB flash drive

• Power on the Poplar board (while pressing the USB_BOOT button), and interrupt its automated boot with a key press. This should lead to a poplar# prompt.

• If the board does not power up properly, something is wrong with the images built or USB flash drive created. The console log should give some details regarding the error.

Re-flash images onto the Poplar board eMMC

Follow Steps 3-4 of the Flash images onto the Poplar board eMMC section in debian_build_instructions.md to re-flash working images onto the board.

Additional information about the recovery files

The following paragraphs provide some more information about the files found in the recovery_files directory.

fastboot.bin

When this file is placed in the first partition of a USB memory stick formatted with a FAT32 file system, that memory stick can be used to boot the Poplar board. This is useful if the board has become "bricked" and is otherwise unusable.

install, install-layout, install-partition1, install-partitionX

These are human-readable versions of installer scripts used by U-Boot. The top-level installer is install; it loads and executes the other install scripts. Each install script has a corresponding ".scr" file (e.g., install.scr), which is the file that U-Boot actually uses. install-layout installs the Master Boot Record and the Extended Boot Records required for partitions 5 and above. install-partitionX contains commands to install the contents of just one partition.

Each install*.scr file can be loaded into U-Boot and run. If the top-level install.scr is used, it will execute all the others. Otherwise, partial installs can be performed by, for example, loading and running install-layout.scr to re-write the boot records, or install-partition2.scr to re-write only partition 2.

mbr.bin.gz, ebr5.bin.gz, ebr6.bin.gz

These are the Master Boot Record and Extended Boot Records for partitions 5 and 6. They are compressed. They are normally loaded and flashed to eMMC using install-layout.

partition1.1-of-1.gz, partition3.1-of-4.gz, etc.

These are files that contain (parts of) the contents of the partitions. The contents of an entire partition can't fit entirely in memory, so large partitions are broken into pieces. Each piece is compressed. The install script for the partition takes care of uncompressing each part before writing it to eMMC.

https://github.com/96boards-poplar/Documentation/blob/master/debian/debian_recovery.md