Nezha d1-h test microbench

Burning the firmware

PhoenixSuit： be based on Windows System burning tool , It is the most commonly used burning tool , Through the data line PC Connect with the development board , Burn the firmware on the development board , Support partition burning , Suitable for development and small-scale production . It is recommended that developers use this tool to upgrade firmware during development .

PhoenixSuit Brief introduction

The following mainly introduces the use of PhoenixSuit The method of burning ,LiveSuit and PhoenixUSBpro The method of burning is similar .

PhoenixSuit Download address ：

Firmware burning tool PhoenixSuit

At the same time, it is necessary to install Quanzhi USB drive , Download link ：

Full ambition USB drive

* Enterprise developers are installing APST At the same time, it will also install Quanzhi USB drive , No need to install it separately

The specific steps are as follows ：

（1） open PhoenixSuit, When the device is powered on, start and insert USB And PC Connected time ,PhoenixSuit You will be prompted to recognize the device ;

（2） Click on  

One touch brush machine - Browse

Select the firmware to burn ;

（3） Click on  

Upgrade now

, At this point will pass USB Send restart command to the device , The device will restart with the burn mark , And enter the burn mode in the restart phase ;

（4） The device returns to boot Will automatically burn when , You can see PhoenixSuit The progress bar of is moving ;

（5） Success in writing , Equipment to restart .

Empty equipment burning

When the device burns for the first time （ That is, there is no system in the equipment ）,PC Open the burning tool , Device insertion USB, The burning tool will automatically pop up the burning prompt , Press YES Button to burn （ It is necessary to select the firmware to be burned at the firmware in advance ）.

Hold down fel Key burning

There is a fel Key ,PC After turning on the burning tool ,

Hold down fel Press the key and insert USB Access to electricity

, At this time, it will also enter the burning mode like empty device burning .

* Tips ： When PC After recognizing the device pop-up prompt , It can be loosened fel key , Don't keep pressing

Firmware burning of existing equipment

For devices that have burned firmware , In the development process , It can be on the serial port or ADB The terminal inputs the burn restart command  

reboot efex

Restart the device , At this time, the device will restart and automatically enter the burn mode during startup , The subsequent burning process is the same as  

PhoenixSuit Brief introduction

 .

* Serial port and ADB See for the debugging method ： 

USB And serial port debugging

RootFS

The way we introduce here is simple , You only need one  X86  The computer , Put on  Docker  Just go , Now let's demonstrate .

Simple preparation

We recommend the unified experimental environment for this activity  

Linux Lab Disk

  For example （ Please install other environments by yourself  Docker）.

Linux Lab Disk  Has supported  6  Mainstream  Linux  Distribution version , Include  Ubuntu, Kali, Mint ( mint ) , Deepin, Manjaro, Fedora  etc. , Here, choose any one  Kali  Version to do experiments .

First, open the desktop  

Cloud Lab Manager

, And install  

qemu-user-static

, With  Ubuntu, Kali, Mint ( mint ) , Deepin  Version as an example , Except for the slightly different software installation commands , Everything else is the same .

$ sudo apt install -y qemu-user-static jq

Then go directly to  Linux Lab  Working directory of ：

$ pwd~/Develop/cloud-lab$ cd labs/linux-lab

Query supported  RISC-V Linux  Distribution version

And then retrieve  Docker  What has been supported in  riscv64  Distribution version ：

$ docker search riscv64 | grep ^riscv64/riscv64/debian Debian is a Linux distribution that's compos… 1riscv64/busybox Busybox base image. 0riscv64/alpine A minimal Docker image based on Alpine Linux… 0riscv64/ubuntu Ubuntu is a Debian-based Linux operating sys… 0

You can see that there is already  busybox, debian, alpine ( The mountain )  and  ubuntu, Next, let's say  ubuntu  For example , First look at the supported  tags：

$ ../../tools/docker/tags riscv64/ubuntu"latest""devel""jammy""jammy-20220315""22.04""rolling""impish""impish-20220316""21.10""focal"

You can see , The latest has supported  Ubuntu 22.04  了 .

Choose any one to download

Choose here  

22.04

  download ：

$ tools/root/docker/extract.sh riscv64/ubuntu:22.04LOG: Pulling riscv64/ubuntu:22.0422.04: Pulling from riscv64/ubuntu779c5da60b92: Pull completeDigest: sha256:4de0b5a51c63b54d27ad151217f6cefaa4114a5db33abce6f47fc6a1f2c3bc2bStatus: Downloaded newer image for riscv64/ubuntu:22.04docker.io/riscv64/ubuntu:22.04LOG: Running riscv64/ubuntu:22.04WARNING: The requested image's platform (linux/riscv64) does not match the detected host platform (linux/amd64) and no specific platform was requestedLOG: Creating temporary rootdir: /home/kali/Develop/cloud-lab/labs/linux-lab/prebuilt/fullroot/tmp/riscv64-ubuntu-22.04LOG: Extract docker image to /home/kali/Develop/cloud-lab/labs/linux-lab/prebuilt/fullroot/tmp/riscv64-ubuntu-22.04[sudo] password for kali:LOG: Removing docker container2b3b9d005682e664f40f4ff80ce483e3673828eaafef51809757e2d91b2ba090LOG: Chroot into new rootfsLinux linux-lab-host 5.10.0-kali9-amd64 #1 SMP Debian 5.10.46-4kali1 (2021-08-09) riscv64 riscv64 riscv64 GNU/LinuxUbuntu Jammy Jellyfish (development branch) \n \l

Experience your goal at top speed  Linux  System

And then through  chroot  function ：

$ tools/root/docker/chroot.sh riscv64/ubuntu:22.04LOG: Chroot into /home/kali/Develop/cloud-lab/labs/linux-lab/prebuilt/fullroot/tmp/[email protected]:/#[email protected]:/# uname -aLinux linux-lab-host 5.10.0-kali9-amd64 #1 SMP Debian 5.10.46-4kali1 (2021-08-09) riscv64 riscv64 riscv64 GNU/[email protected]:/# uname [email protected]:/# exit

If you don't want to persist and save the running results , Then it can be used directly  

tools/root/docker/run.sh

, Discard when used up ！

test

git clone https://gitee.com/tinylab/riscv-linux
cd riscv-linux/test/microbench
make logging PRODUCT='D1-H-nezha' O=0
make logging PRODUCT='D1-H-nezha' O=1

result

Run on (1 X 1008 MHz CPU )
Load Average: 1.43, 1.21, 1.10
-------------------------------------------------------------------------
Benchmark Time  CPU Iterations
-------------------------------------------------------------------------
BM_nop  10.1 ns  10.0 ns  69957559
BM_ub  10.2 ns  10.0 ns  69873414
BM_bnez  10.1 ns  10.0 ns  69937321
BM_beqz  10.1 ns  10.0 ns  69938862
BM_load_bnez  12.2 ns  12.0 ns  58255983
BM_load_beqz  12.2 ns  12.0 ns  58298861
BM_cache_miss_load_bnez  24.3 ns  12.0 ns  58107258
BM_cache_miss_load_beqz  24.3 ns  12.0 ns  58252024
BM_branch_miss_load_bnez  24.2 ns  12.0 ns  58267620
BM_branch_miss_load_beqz  24.3 ns  12.0 ns  58236516
BM_cache_branch_miss_load_bnez  24.4 ns  12.0 ns  58232276
BM_cache_branch_miss_load_beqz  24.7 ns  12.0 ns  58142354

Reference documents

Experience in two minutes  RISC-V Linux  System release  -  Taixiao technology  (tinylab.org)