mirror of
https://github.com/sipeed/sipeed_wiki.git
synced 2026-09-11 00:22:49 -05:00
docs: checked grammar of the English translation for the RV_Nano, changed some of the sentence structure so it flows better
This commit is contained in:
Stan
@@ -3,7 +3,7 @@ title: LicheeRV Nano
|
||||
keywords: riscv, licheerv,nano
|
||||
---
|
||||
|
||||
## Introduction
|
||||
## 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.
|
||||
|
||||
@@ -32,7 +32,7 @@ The LicheeRV Nano is a mini-sized development board (measuring only 22.86*35.56m
|
||||
|
||||
|
||||
|
||||
## Version Comparison
|
||||
## Version Comparison
|
||||
|
||||
| **Specification** | **Basic System** | **Microphone/Speaker** | **Ethernet** | **WiFi6/BT5** |
|
||||
| :------------------: | :--------------: | :--------------------: | :----------: | :-----------: |
|
||||
@@ -52,7 +52,7 @@ Datasheets, schematic diagrams, dimension drawings, and more can be found here:
|
||||
- [3D Model Files](http://cn.dl.sipeed.com/shareURL/LICHEE/LicheeRV_Nano/06_3D_file)
|
||||
- [Core Board Packaging](http://cn.dl.sipeed.com/shareURL/LICHEE/LicheeRV_Nano/05_PCB_Lib)
|
||||
- [Board Chip Information](http://cn.dl.sipeed.com/shareURL/LICHEE/LicheeRV_Nano)
|
||||
- http://cn.dl.sipeed.com/shareURL/LICHEE/LicheeRV_Nano/07_Datasheet)
|
||||
- [Board Chip Datasheet](http://cn.dl.sipeed.com/shareURL/LICHEE/LicheeRV_Nano/07_Datasheet)
|
||||
|
||||
## Software Resources
|
||||
|
||||
@@ -68,10 +68,10 @@ Datasheets, schematic diagrams, dimension drawings, and more can be found here:
|
||||
- [TPU SDK Development Resources Summary](https://developer.sophgo.com/thread/473.html)
|
||||
- [TDL SDK Development Guide: (Provides common AI model algorithms, application packaging based on TPU SDK)](https://doc.sophgo.com/cvitek-develop-docs/master/docs_latest_release/CV180x_CV181x/zh/01.software/TPU/TDL_SDK_Software_Development_Guide/build/TDLSDKSoftwareDevelopmentGuide_zh.pdf)
|
||||
- [TDL SDK Development Resources Summary](https://developer.sophgo.com/thread/473.html)
|
||||
- https://developer.sophgo.com/thread/556.html)
|
||||
- [TDL SDK Development Resources](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.
|
||||
- The NPU on the beta version hardware (70405) only supports operation at 0.5T; running at 1.0T does not guarantee the stability of the board.
|
||||
- The WiFi on 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](https://wiki.sipeed.com/hardware/zh/lichee/RV_Nano/2_unbox.html).
|
||||
- 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](https://wiki.sipeed.com/hardware/zh/lichee/RV_Nano/2_unbox.html)
|
||||
|
||||
|
||||
@@ -69,13 +69,15 @@ The LicheeRV Nano is available in four versions based on networking capabilities
|
||||
|
||||
●Securing the Standoffs
|
||||
|
||||
1. To avoid burns while soldering the standoffs, you can first screw them onto the Ethernet module.
|
||||
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.
|
||||
|
||||
|
||||
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.
|
||||
3. Use a soldering iron from the bottom side to solder.
|
||||
|
||||
|
||||
|
||||
@@ -96,11 +98,11 @@ The LicheeRV Nano is available in four versions based on networking capabilities
|
||||
|
||||
|
||||
|
||||
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.
|
||||
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.
|
||||
3. Solder from the bottom side using a soldering iron.
|
||||
|
||||
|
||||
|
||||
@@ -110,6 +112,6 @@ The LicheeRV Nano is available in four versions based on networking capabilities
|
||||
|
||||
|
||||
|
||||
2.Secure with screws.
|
||||
2. Secure with screws.
|
||||
|
||||
|
||||
@@ -10,6 +10,6 @@ The image is compressed using xz. After decompression, use tools like Rufus, Win
|
||||
|
||||
[Download here](https://github.com/0x754C/sipeed-toolchain/releases)
|
||||
|
||||
## Debian Sid Based image
|
||||
## Debian Sid Based Image
|
||||
|
||||
[Image Information and Downloads](https://github.com/Fishwaldo/sophgo-sg200x-debian)
|
||||
|
||||
@@ -13,11 +13,11 @@ keywords: riscv, licheerv,nano
|
||||
|
||||
### UART0
|
||||
|
||||
Connect the UART serial port to the GND, `A16 (TX)`, and `A17 (RX)` of the board
|
||||
Connect the UART serial port to the GND, `A16 (TX)`, and `A17 (RX)` of the board.
|
||||
|
||||
Then use terminal software to connect to the serial port, with a baud rate of 115200.
|
||||
|
||||
UART0 is also brought out on SBU1/2 on the USB interface. You can use the USB TypeC adapter to bring out RX0 and TX0.
|
||||
UART0 is also brought out on SBU1/2 on the USB interface. You can use the USB Type-C adapter to bring out RX0 and TX0.
|
||||
|
||||
#### Disable UART0 output log
|
||||
|
||||
@@ -72,7 +72,7 @@ consoledev=/dev/ttyX
|
||||
|
||||
### UART1 UART2 UART3
|
||||
|
||||
By default, the pins of UART1 and 2 are used to connect to the UART Bluetooth chip:
|
||||
By default, the pins of UART1 and UART2 are used to connect to the UART Bluetooth chip:
|
||||
|
||||
```
|
||||
mmio_write_32(0x03001070, 0x1); // GPIOA 28 UART1 TX
|
||||
@@ -120,7 +120,7 @@ devmem 0x030010D8 32 0x5 # GPIOP 20 UART3 RX
|
||||
devmem 0x030010DC 32 0x5 # GPIOP 21 UART3 RTS
|
||||
```
|
||||
|
||||
Serial port usage in Linux system:
|
||||
Serial port usage in a Linux system:
|
||||
|
||||
C:
|
||||
|
||||
@@ -266,8 +266,8 @@ I2C1 and I2C3 are brought out on the pin header, and devices can be connected to
|
||||
|
||||
Before using, you need to correctly set the PINMUX:
|
||||
|
||||
```
|
||||
shell# I2C1
|
||||
```shell
|
||||
# I2C1
|
||||
devmem 0x030010D0 32 0x2
|
||||
devmem 0x030010DC 32 0x2
|
||||
# I2C3
|
||||
@@ -279,7 +279,7 @@ Then you can use i2c-tools to operate the i2c peripherals. The image is already
|
||||
|
||||
## ADC
|
||||
|
||||
An ADC route is brought out on the pin header, using ADC1.
|
||||
An ADC channel is brought out on the pin header, using ADC1.
|
||||
|
||||
First, select the ADC channel, here taking ADC1 as an example:
|
||||
|
||||
|
||||
@@ -8,8 +8,8 @@ update:
|
||||
---
|
||||
|
||||
## 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.
|
||||
This document introduces how to use the SDK to develop with MMF, providing a starting point for developers who want to begin MMF development.
|
||||
MMF stands for Multimedia Framework, a framework that offers a unified API 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.
|
||||
|
||||
## Build MMF development environment
|
||||
Please refer to the method introduced in `LicheeRV Nano->System Development->cvi_mmf_sdk` to build the MMF development environment.
|
||||
@@ -17,7 +17,6 @@ Please refer to the method introduced in `LicheeRV Nano->System Development->cvi
|
||||
Or follow the instructions below:
|
||||
|
||||
```shell
|
||||
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
|
||||
|
||||
@@ -37,22 +36,23 @@ 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.
|
||||
## Development Document
|
||||
Please refer to the `LicheeRV Nano->Board Introduction` to find most of the document.
|
||||
- Note: Compiling sample_cvg may fail. 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.
|
||||
|
||||
For MMF applications, pay attention to the following document:
|
||||
## Development Documentation
|
||||
Please refer to `LicheeRV Nano->Board Introduction` to find most of the documentation.
|
||||
|
||||
For MMF applications, pay attention to the following documents:
|
||||
|
||||
- [Media Processing Software Development Reference](https://doc.sophgo.com/cvitek-develop-docs/master/docs_latest_release/CV180x_CV181x/en/01.software/MPI/Media_Processing_Software_Development_Reference/build/html/index.html)
|
||||
- [SDK LicheeRV-Nano-Build](https://github.com/sipeed/LicheeRV-Nano-Build)
|
||||
|
||||
## 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.
|
||||
The purpose of connecting to the development board via the network is to upload the firmware you 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.
|
||||
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 used: Ethernet connection, WiFi connection, or USB RNDIS connection.
|
||||
|
||||
## 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.
|
||||
MMF accesses hardware directly, so incorrect usage can lead to a system crash. Pay careful attention to details when developing with MMF. It is recommended to base your program on the provided examples.
|
||||
|
||||
Compile and run sample_vio example:
|
||||
|
||||
@@ -78,5 +78,5 @@ cd ~
|
||||
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.
|
||||
|
||||
## 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](https://maixhub.com/discussion) 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.
|
||||
1. Please remain patient and carefully review the development documentation 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](https://maixhub.com/discussion) or GitHub. Please describe the functionality you want to achieve, the problems you encountered, the solutions you tried, and the steps to reproduce them. Many issues can be resolved in the process of organizing your thoughts.
|
||||
Reference in New Issue
Block a user