】Introduction

1. Introduction

The LicheeRV Nano is a mini-sized development board (measuring only 22.86*35.56mm), equipped with the SG2002 processor. It features a powerful core running at 1GHz (RISC-V/ARM options available) and a smaller core at 700MHz RISC-V, along with 256MB DDR3 memory, and an integrated 1Tops NPU. The board includes a wealth of interfaces such as MIPI-CSI, MIPI-DSI, SDIO, ETH, USB, SPI, UART, I2C, etc., allowing for the expansion of a wide variety of applications. Its through-hole/half-hole design facilitates easy mass production and soldering.

2. Specifications

3. Version Comparison

4. Hardware Resources

Datasheets, schematic diagrams, dimension drawings, and more can be found here: Click

• Board Specification
• Board Schematic
• Board Designator Drawing
• Board Dimensional Drawing
• 3D Model Files
• Core Board Packaging
• Board Chip Information
• http://cn.dl.sipeed.com/shareURL/LICHEE/LicheeRV_Nano/07_Datasheet)

5. Software Resources

• SDK LicheeRV-Nano-Build

6. SOPHGO Resources Summary

• Datasheet
• Compiler Toolchain Download
• Software SDK Download
• SDK Development Documentation Summary
• HDK Development Documentation Summary
• TPU SDK Development Resources Summary
• TDL SDK Development Guide: (Provides common AI model algorithms, application packaging based on TPU SDK)
• TDL SDK Development Resources Summary
• https://developer.sophgo.com/thread/556.html)
• Precautions
  】The beta version hardware (70405) NPU only supports operation at 0.5T, running at 1.0T does not guarantee the stability of the board.
  】The WIFI of the beta version hardware (70405) has not been fully optimized yet, resulting in lower speeds. We appreciate your understanding.
  】If purchasing a camera accessory or the WE version package, screws, soldering pillars, and a screwdriver are included in the package. To avoid burns during soldering, please refer to the Camera & WE Ethernet Module Installation Guide.
  】If purchasing 3-inch, 4-inch, or 10.1-inch screen accessories, a screen adapter board and ribbon cable are included in the package. Please refer to the Screen Installation Guide

】Unboxing Experience

1. LicheeRV Nano Package Introduction

The LicheeRV Nano is available in four versions based on networking capabilities:

• Standard Version (B): Comes without any networking accessories.
• Ethernet Version (E): Features an onboard 100M Ethernet port for wired network connections.
• WiFi Version (W): Equipped with an onboard WiFi6/BT5.2 module. By default, the BT5.2 functionality is not enabled. To activate Bluetooth capabilities, it's necessary to solder four 0201 resistors in the specified location or use a 2B pencil to create a short circuit in the designated area.

• The WiFi Ethernet (WE) version features an onboard WiFi 6/BT 5.2 module and comes with an Ethernet module that connects to the development board via standoffs and ribbon cables.

  We also offer the following accessory:

  • Camera

• The camera (model 3754) features non-short-circuiting screw holes on both sides for secure mounting. It is recommended to fix the standoffs to the fifth pad for optimal stability.

• 3-inch Display Screen

  
  

  • The display features a resolution of 480*845 and supports touch functionality. The package includes a touch screen adapter board and a ribbon cable for easy integration.
  • 5-inch Display Screen
  • 
    
  • This display boasts a resolution of 480*845 and does not support touch functionality. The ribbon cable can be directly connected to the LicheeRV Nano 31Pin screen interface for seamless integration.
  • 7-inch Display Screen
  • 
    
  • The display features a resolution of 800*1280 and supports touch functionality. The ribbon cable can be directly connected to both the LicheeRV Nano 31Pin screen interface and the 6Pin touch interface, ensuring easy setup and integration.
  • 10-inch Display Screen
  • 
    
  • The display features a resolution of 800*1280 and supports touch functionality. The package includes a touch adapter board and a ribbon cable for easy setup. The screen ribbon cable can be directly connected to the LicheeRV Nano 31Pin screen interface, ensuring seamless integration.
  • Raspberry Pi Camera Adapter Ribbon Cable (Coming Soon)
  • Raspberry Pi Standard 15Pin Camera to LicheeRV 22Pin CSI Camera Interface Adapter

• 1. Installation Guide

     1.1. Installing the WE Module

     1. Soldering the Ribbon Cable
     2. Solder the ribbon cable following the direction shown in the diagram below.
     3. Use a Multimeter to Test for Continuity

  ●Securing the Standoffs

  1. To avoid burns while soldering the standoffs, you can first screw them onto the Ethernet module.
  2. Insert the standoff into the fifth pad. It is advisable to apply solder paste to the pad beforehand to enhance the stability of the standoff after soldering.
  3. Use a soldering iron from the bottom side to solder.

• Assembly

  1. Insert the ribbon cable into the FPC connector of the Ethernet module and secure it.
  2. Secure the Ethernet module to the standoffs using screws.

1.2. Installing the Camera

• Securing the Standoffs
  1. Similar to the method mentioned above: first, screw the standoffs and screws onto the camera module.
  2. Insert the standoff into the fifth pad. To enhance the stability of the standoff after soldering, it is recommended to apply solder paste to the pad beforehand.
  3. Solder from the bottom side using a soldering iron.

• Assembly

  1. Connect the camera ribbon cable as shown in the diagram below.
  2. Secure with screws.
     

】Image Collection

1. Images Based on the Official SDK

Download here

2. Images Based on the Mainline Buildroot SDK (WORK-IN-PROGRESS)

Download here

3. Debian Sid Based image

Image Infomation and Downloads

】Flashing the Image

1. Linux

curl -O https://github.com/sipeed/LicheeRV-Nano-Build/releases/download/20240124/licheervnano-20230124.img.xz
# Replace sdX with your SD card's device node
xzcat https://github.com/sipeed/LicheeRV-Nano-Build/releases/download/20240124/licheervnano-20230124.img.xz | dd of=/dev/sdX conv=sync

2. Windows

Use 7zip for extraction:

https://www.7-zip.org/download.html

Use Rufus or Win32 Disk Imager to write to the SD card:

https://rufus.ie/

https://sourceforge.net/projects/win32diskimager/

】Peripheral

1. Connecting to the Board

1.1. UART0

Connect the UART port to the board at:

A17 A16 GND

Then use terminal software to connect to the serial port, with a baud rate of 115200.

1.2. USB CDC ACM Serial Port

When the board's USB Type-C port is connected to a computer, it will provide a USB CDC ACM serial port device (provided by Linux gadget).

Linux:

# Replace /dev/ttyACMX with the specific device, depending on your computer
picocom -b 9600 /dev/ttyACMX

Windows:

Press Win + R, enter devmgmt.msc, and press Enter.

Find the new device's serial port number under the serial port devices.

Then use PuTTY or HyperTerminal to connect.

1.3. USB RNDIS Network Port

When the board's USB Type-C port is connected to a computer, it will provide a USB RNDIS network card device (provided by Linux gadget).

The PC will automatically obtain an address using DHCP.

Replace the last digit of the automatically obtained IPv4 address with 1 to get the board's IPv4 address:

10.44.55.66 PC's IPv4 address
10.44.55.1  Board's IPv4 address

Then use ssh to connect: ssh root@board's IP address

Username: root
Password: root

On Windows system, some configurations need to be made.

Open Device Manager and find the following option.

Select "Update driver".

Select "Browse my computer for driver software".

Select "Let me pick from a list of available drivers on my computer".

In the device type list, select "Network adapters".

For manufacturer, select "Microsoft"; for model, select "Remote NDIS Compatible Device".

If this warning pops up, please click "OK".

After the update is successful, it will show as follows.

Then you can find the "Remote NDIS Compatible Device" item under the Network adapters list in Device Manager.

1.4. Ethernet Connection

Connect the Ethernet cable to the board; the board will automatically obtain an address using DHCP upon boot.

The board's image defaults to enabling the MDNS service.

Use the command:

avahi-browse -art | grep lpirvnano

to list devices in the broadcast domain with lpirvnano in their domain names.

Then use:

ssh root@lpirvnano-XXXX.local

to connect to the board.

2. Disabling the Boot Demo of the Image

# Clear rc.local
echo '#!/bin/sh' > /etc/rc.local
# Reboot
reboot

3. Audio

The LicheeRV Nano supports recording and playback. Standard ALSA tools can be used for recording, playback, and other operations.

3.1. Recording

First, set the microphone volume, range: 0-24

amixer -Dhw:0 cset name='ADC Capture Volume' 24

After setting, start recording:

arecord -Dhw:0,0 -d 3 -r 48000 -f S16_LE -t wav test.wav & > /dev/null &

3.2. Playback

./aplay -D hw:1,0 -f S16_LE test.wav

4. I2C

I2C1 and I2C3 are brought out on the pin header, and devices can be connected to them.

Before using, you need to correctly set the PINMUX:

shell# I2C1
devmem 0x030010D0 32 0x2
devmem 0x030010DC 32 0x2
# I2C3
devmem 0x030010E4 32 0x2
devmem 0x030010E0 32 0x2

Then you can use i2c-tools to operate the i2c peripherals. The image is already pre-installed.

5. ADC

An ADC route is brought out on the pin header, using ADC1.

First, select the ADC channel, here taking ADC1 as an example:

echo 1 > /sys/class/cvi-saradc/cvi-saradc0/device/cv_saradc

Read the value of ADC1:

cat /sys/class/cvi-saradc/cvi-saradc0/device/cv_saradc

6. LCD

Connect the screen's ribbon cable to the board's MIPI interface, paying attention to the wire order.

Create or edit the uEnv.txt file in the first partition of the sdcard, add or modify the panel field:

Note: The image will have the first partition already mounted in the /boot directory and can be used directly in the terminal:

cd /boot
touch uEnv.txt
vi uEnv.txt
# Use 'i' to enter edit
# Use 'Esc',':wq' to save and quit

7-inch screen:

panel=zct2133v1

5-inch screen:

panel=st7701_dxq5d0019b480854

3-inch screen:

panel=st7701_d300fpc9307a

2.3-inch screen:

panel=st7701_hd228001c31

If you want to use the framebuffer function, create a file named fb in the first partition of the sd card:

touch /boot/fb

Then load the driver:

/etc/init.d/S04fb start

Adjusting the Backlight Brightness:

echo 0 > /sys/class/pwm/pwmchip8/pwm2/enable
echo 5000 > /sys/class/pwm/pwmchip8/pwm2/duty_cycle # 50%
echo 1 > /sys/class/pwm/pwmchip8/pwm2/enable

# some example:
#echo 2000 > /sys/class/pwm/pwmchip8/pwm2/duty_cycle # 20%
#echo 4000 > /sys/class/pwm/pwmchip8/pwm2/duty_cycle # 40%
#echo 7000 > /sys/class/pwm/pwmchip8/pwm2/duty_cycle # 70%
#echo 9000 > /sys/class/pwm/pwmchip8/pwm2/duty_cycle # 90%

7. Touch Screen

Connect the touchscreen ribbon to the board's touchscreen interface, paying attention to the wire sequence.

Then execute:

/opt/touch.sh # Load the touchscreen driver

Followed by:

echo 2 | evtest

Touching the screen will display specific coordinates in the terminal.

For reading coordinates and touch events, refer to the input section in /opt/src/vendortest.

8. WIFI

Install the antenna onto the WIFI module's antenna connector.

Then write the AP's SSID and password into the /etc/wpa_supplicant.conf file:

network={
        ssid="ssid"
        psk="password"
}

After that, execute:

/opt/wifi.sh

To verify if the network is available:

ping your gateway address

If available, you can add it to the boot script:

echo '/opt/wifi.sh' >> /etc/rc.local

9. Camera

Install the camera onto the camera mount, paying attention to the wire sequence.

Then execute:

/mnt/system/usr/bin/sample_vio 6 # Real-time display of camera images on the screen
# Type 255 to exit the program

/mnt/system/usr/bin/sensor_test # Camera test program that can be used to dump single YUV images.

When using the 70405 (beta) boards:

touch /boot/alpha # Beta version
# rm /boot/alpha  # Official version
cd /mnt/data
cp sensor_cfg.ini.alpha sensor_cfg.ini   # Beta version
# cp sensor_cfg.ini.beta sensor_cfg.ini  # Official version

10. Button

To view button events, use the command:

echo 1 | evtest

Then press the USER button, and you will see the corresponding event report in the terminal.

11. HelloWorld

For information on compiling programs using the vendor's toolchain, visit:

https://github.com/sipeed/LicheeRV-Nano-Build/blob/v4.1.0/build/boards/cv181x/cv1812cp_licheerv_nano_sd/readme.md#compile-program-use-vendors-toolchain

】MMF Deveiopment Guide

1. Overview

This document is used to introduce the method of using SDK to develop MMF, to provide a development idea for developers who want to start developing MMF but can't get started.
MMF full name is Multimedia Framework, an framework that offers a unified API format for video input/output, audio input/output, image signal processing, and hardware encoding/decoding, allowing users to quickly implement multimedia-related functions by calling these APIs.

2. Build MMF development environment

Please refer to the method introduced in LicheeRV Nano->System Development->cvi_mmf_sdk to build the MMF development environment.

Or follow the instructions below:

Copy code
# Download dependencies
sudo apt install pkg-config build-essential ninja-build automake autoconf libtool wget curl git gcc libssl-dev bc slib squashfs-tools android-sdk-libsparse-utils android-sdk-ext4-utils jq cmake python3-distutils tclsh scons parallel ssh-client tree python3-dev python3-pip device-tree-compiler libssl-dev ssh cpio squashfs-tools fakeroot libncurses5 flex bison

# Download SDK and toolchain
git clone https://github.com/sipeed/LicheeRV-Nano-Build.git
wget https://sophon-file.sophon.cn/sophon-prod-s3/drive/23/03/07/16/host-tools.tar.gz
tar xvf host-tools.tar.gz

# Compile all examples with the build_middleware command
cd LicheeRV-Nano-Build
git checkout v4.1.0-licheervnano
ln -s ../host-tools ./
source build/cvisetup.sh
defconfig cv1812cp_licheerv_nano_sd
build_middleware

The above instructions describe how to install the MMF-related compilation environment and how to compile the MMF examples provided by the SDK.

• Note: You may fail to compile sample_cvg. If you do not need this example, try again after deleting the LicheeRV-Nano-Build/middleware/v2/sample/cvg folder. If you need this demo, try compiling with build_all, which requires compiling the entire SDK, so the compilation time will be longer.

3. Development Document

Please refer to the LicheeRV Nano->Board Introduction to find most of the document.

For MMF applications, pay attention to the following document:

• Media Processing Software Development Reference
• SDK LicheeRV-Nano-Build

4. Connecting to the Development Board via Network

The purpose of connecting to the development board via network is to upload the firmware we compiled to the board.

Please refer to the methods in LicheeRV Nano->peripheral to get the IP address of the development board. Any one of the three methods can be implemented: Ethernet connection, WIFI connection, or USB RNDIS connection.

5. Compiling and Running an Example

MMF will use the hardware directly, so incorrect operation can lead to system crash, and you must be careful to pay attention to details when developing MMF. The suggestion is to modify your own program by using the examples.

Compile and run sample_vio example:

# Ensure that the basic MMF compilation environment has been set up and that build_middleware has been compiled once
# Compile sample_vio
cd middleware/v2/sample/vio
make

# Upload to the development board (account root, password cvitek)
scp sample_vio root@xxx.xxx.xxx.xxx:/root  # xxx.xxx.xxx.xxx is the board's IP address

# Log into the development board
ssh root@xxx.xxx.xxx.xxx

# If you need to use the display, you need to run fb_load.sh to make sure the driver is loaded (it only needs to be executed once)
/opt/fb_load.sh

# Run the example
cd ~
./sample_vio

The instructions above explain how to compile a specific MMF example, and how to upload and run the example on the development board. Developers can modify the example based on their applications to eventually develop the functionality they desire.

6. Have an unsolvable problem?

1. Please remain patient and carefully review the development document to see if anything was overlooked. For example, check if the input parameters are correct, whether resources have been properly released, etc.
2. Post your problem on maixhub or GitHub. Please organize the functionality you want to achieve, the problems you encountered, the solutions you tried, and the ways to reproduce them, by the way, many times can be solved in the process of organizing your thoughts.

】Support

Monday-Friday (9:30-6:30) Saturday (9:30-5:30) -China time
Email: services01@spotpear.com