Melis Yuzuki PI-Lizard Test Report

Test Environment

Operating System Information

• SDK Links:
  • Global - Google Drive: https://drive.google.com/drive/folders/1_HAZRddR69hRMZAVrxFrPZXFFQiV3vE0?usp=share_link
  • Recommended for users in Chinese mainland - Baidu Netdisk: https://pan.baidu.com/s/115gVK-8Pt-vJi8jn2AWMYw?pwd=7n4q Password: 7n4q
• Reference Installation Document:
  • https://dongshanpi.com/YuzukiHD-Lizard/01-BoardIntroduction/
  • https://tina.100ask.net/SdkModule/Linux_E907_DevelopmentGuide-01/

Hardware Information

• Yuzuki PI-Lizard Development Board

Installation Steps

Extracting the SDK

After downloading the SDK, merge the package files and extract:

cat tina-v853-open.tar.gz.* > tina-v853-open.tar.gz
tar -xzvf tina-v853-open.tar.gz

Since the default SDK doesn’t support this development board, you need to add the necessary configurations separately to the tina-v853-open SDK. First, clone the patch repository for this development board and then overwrite it:

git clone  https://github.com/DongshanPI/Yzukilizard-v851s-TinaSDK
cp -rfvd Yzukilizard-v851s-TinaSDK/* tina-v853-open/

System Configuration and Compilation

After downloading the SDK, configure the environment:

cd tina-v853-open
source build/envsetup.sh
lunch

Choose the appropriate scheme.

If you encounter issues, try using bash instead of zsh or other shell environments

Configure E906 to start RTOS:

cconfigs
cd ../default/
vim boot_package_nor.cfg

--- boot_package_nor.cfg.bak    2024-05-09 15:59:28.706860360 +0800
+++ boot_package_nor.cfg        2024-05-09 16:40:10.476852456 +0800
@@ -4,6 +4,7 @@
 item=optee,                  optee.fex
 item=u-boot,                        u-boot-spinor.fex
 item=dtb,                    sunxi.fex
+item=melis-elf,              riscv.fex
 ;item=logo,                   bootlogo.bmp.lzma
 ;item=shutdowncharge,         bempty.bmp.lzma
 ;item=androidcharge,          battery_charge.bmp.lzma

vim boot_package.cfg

--- boot_package.cfg.bak        2024-05-09 16:39:35.356852125 +0800
+++ boot_package.cfg    2024-05-09 16:40:01.263519036 +0800
@@ -4,6 +4,7 @@
 item=optee,                  optee.fex
 item=u-boot,                 u-boot.fex
 item=dtb,                    sunxi.fex
+item=melis-elf,              riscv.fex
 ;item=logo,                   bootlogo.bmp.lzma
 ;item=shutdowncharge,         bempty.bmp.lzma
 ;item=androidcharge,          battery_charge.bmp.lzma

Configure the kernel:

ckernel
m kernel_menuconfig

Include Device Drivers under Mailbox Hardware Support; Include Device Drivers → Mailbox Hardware Support under sunxi Mailbox and sunxi rv32 standby driver:

--- .config.old 2024-05-09 16:42:29.690187100 +0800
+++ .config     2024-05-09 16:45:57.840189075 +0800
@@ -3174,7 +3174,12 @@
 # CONFIG_SH_TIMER_MTU2 is not set
 # CONFIG_SH_TIMER_TMU is not set
 # CONFIG_EM_TIMER_STI is not set
-# CONFIG_MAILBOX is not set
+CONFIG_MAILBOX=y
+CONFIG_SUNXI_MBOX=y
+CONFIG_SUNXI_RV32_STANBY=y
+# CONFIG_PLATFORM_MHU is not set
+# CONFIG_ALTERA_MBOX is not set
+# CONFIG_MAILBOX_TEST is not set
 CONFIG_IOMMU_API=y
 CONFIG_IOMMU_SUPPORT=y
 
@@ -3192,6 +3197,7 @@
 # Remoteproc drivers
 #
 # CONFIG_STE_MODEM_RPROC is not set
+# CONFIG_SUNXI_RPROC is not set
 
 #
 # Rpmsg drivers
@@ -3304,6 +3310,7 @@
 # Firmware Drivers
 #
 CONFIG_ARM_PSCI_FW=y
+# CONFIG_ARM_SCPI_PROTOCOL is not set
 # CONFIG_FIRMWARE_MEMMAP is not set
 # CONFIG_FW_CFG_SYSFS is not set
 CONFIG_HAVE_ARM_SMCCC=y

mkernel -j

If a linker error regarding yyloc redefinition occurs: This is due to GCC version being higher than 10. Change YYLTYPE yyloc to extern YYLTYPE yyloc in scripts/dtc/dtc-parser.tab.c

Configure RTOS:

mmelis menuconfig

Build and Package

make -j$(nproc)
p

Logging into the System

Connect to UART3 to observe the serial port output.

Expected Results

The system should boot normally and provide serial port output.

Actual Results

CFT

Boot Log

Screen recording:

Test Criteria

Successful: The actual result matches the expected result.

Failed: The actual result does not match the expected result.

Test Conclusion

CFT