mirror of
https://gitee.com/bianbu-linux/openwrt-docs-en
synced 2025-04-18 19:34:54 -04:00
update openwrt development docs-en
This commit is contained in:
parent
d687a6ff82
commit
0fcf586ba3
12 changed files with 378 additions and 305 deletions
44
README.md
44
README.md
|
@ -5,52 +5,54 @@ sidebar_position: 1
|
|||
|
||||
# Intro
|
||||
|
||||
基于原生OpenWrt 23.05集成Spacemit Stone 系列芯片的 BSP,包含监管程序接口(OpenSBI)、引导加载程序(U-Boot/UEFI)、Linux 内核、根文件系统(包含各种中间件和库)以及示例等。其目标是为客户提供软路由和NAS方案支持,并且可以开发驱动或应用。
|
||||
BSP based on native OpenWrt 23.05(*bl-v2.0.y based on master*) integrated Spacemit Stone series chips, including supervisory program interface (OpenSBI), boot loader (U-Boot/UEFI), Linux kernel, root file system (including various middleware and libraries), and examples.Its goal is to provide customers with soft routing and NAS scheme support, and can develop drivers or applications.
|
||||
|
||||
## 主要组件
|
||||
## Main component
|
||||
|
||||
以下是OpenWrt的组件:
|
||||
Here are the components of OpenWrt::
|
||||
|
||||
- OpenSBI
|
||||
- U-Boot
|
||||
- Linux Kernel
|
||||
- mpp: Media Process Platform
|
||||
- FFmpeg (with Hardware Accelerated)
|
||||
|
||||
更多组件正在适配中
|
||||
More components are being adapted
|
||||
|
||||
- onnxruntime (with Hardware Accelerated)
|
||||
- ai-support: AI demo
|
||||
- ai-support: AI demo
|
||||
- k1x-vpu-firmware: Video Process Unit firmware
|
||||
- k1x-vpu-test: Video Process Unit test program
|
||||
- k1x-jpu: JPEG Process Unit API
|
||||
- FFmpeg (with Hardware Accelerated)
|
||||
- GStreamer (with Hardware Accelerated)
|
||||
|
||||
## 快速指南
|
||||
## Quick guide
|
||||
|
||||
- [下载和编译](openwrt_quickstart.md)
|
||||
- [设备管理](openwrt_device_management.md)
|
||||
- [方案管理](openwrt_solution_management.md)
|
||||
- [Download and compile](openwrt_quickstart.md)
|
||||
- [Device management](openwrt_device_management.md)
|
||||
- [Solution Management](openwrt_solution_management.md)
|
||||
|
||||
## 进阶指南
|
||||
## Advanced Develope guide
|
||||
|
||||
[系统开发指南](https://bianbu-linux.spacemit.com/category/%E5%BC%80%E5%8F%91%E6%8C%87%E5%8D%97)
|
||||
[system develope guide](https://bianbu-linux.spacemit.com/development_guide)
|
||||
|
||||
## 预编译
|
||||
## Precompile
|
||||
|
||||
[进迭OpenWrt源站点](https://archive.spacemit.com/openwrt/releases/23.05.2/)
|
||||
[Spacemit OpenWrt source site](https://archive.spacemit.com/openwrt/releases/[branch])
|
||||
|
||||
[BPI-F3、MUSE-Pi固件](https://archive.spacemit.com/openwrt/releases/23.05.2/targets/spacemit/DEVICE_debX/openwrt-spacemit-k1-sbc-debX-ext4-pack.zip)
|
||||
[BPI-F3、MUSE-Pi image](https://archive.spacemit.com/openwrt/releases/23.05.2/targets/spacemit/DEVICE_debX/openwrt-spacemit-k1-sbc-debX-ext4-pack.zip)
|
||||
|
||||
[MUSE-N1固件](https://archive.spacemit.com/openwrt/releases/23.05.2/targets/spacemit/DEVICE_MUSE-N1/openwrt-spacemit-k1-nas-MUSE-N1-ext4-pack.zip)
|
||||
[MUSE-N1 image](https://archive.spacemit.com/openwrt/releases/23.05.2/targets/spacemit/DEVICE_MUSE-N1/openwrt-spacemit-k1-nas-MUSE-N1-ext4-pack.zip)
|
||||
|
||||
## Supported device list
|
||||
|
||||
## 支持设备列表
|
||||
目前支持以下硬件设备:
|
||||
The following hardware devices are currently supported:
|
||||
|
||||
### SBC Solution
|
||||
|
||||
### SBC方案
|
||||
- BPI-F3
|
||||
- [MUSE Pi](supported_devices/muse_pi.md)
|
||||
|
||||
### NAS方案
|
||||
- [MUSE N1](supported_devices/muse_n1.md)
|
||||
### NAS Solution
|
||||
|
||||
- [MUSE N1](supported_devices/muse_n1.md)
|
||||
|
|
|
@ -4,31 +4,33 @@ sidebar_position: 3
|
|||
|
||||
# Device Management
|
||||
|
||||
本文档介绍如何通过EEPROM实现自适应设备(板型),包括如何添加新板型支持和实现自适应启动。
|
||||
The following document introduces how to achieve adaptive devices (board types) via EEPROM, including how to add support for new board types and implement adaptive booting.
|
||||
|
||||
后续文档描述的设备和板型等效
|
||||
In subsequent documentation, the terms "device" and "board type" are used interchangeably.
|
||||
|
||||
## 添加新设备
|
||||
以下以新增k1-x_MUSE-Pi板型为例说明
|
||||
## Adding a New Device
|
||||
|
||||
### kernel设备树
|
||||
The following uses the addition of the k1-x_MUSE-Pi board type as an example.
|
||||
|
||||
如参考deb1硬件设计,则拷贝k1-x_deb1.dts到如下文件,修改相应内容
|
||||
### Kernel Device Tree
|
||||
|
||||
```
|
||||
If you refer to the design of the deb1 hardware, copy `k1-x_deb1.dts` to the following file and modify the relevant content:
|
||||
|
||||
```sh
|
||||
target/linux/spacemit/dts/k1-x_MUSE-Pi.dts
|
||||
|
||||
```
|
||||
|
||||
对于新增的版型,dts文件均存放在以上目录。编译的时候打包进bootfs分区,uboot启动kernel前加载设备树文件。
|
||||
For the newly added board type, the .dts files are stored in the above directory. They are packed into the bootfs partition during compilation and loaded by U-Boot before the kernel boots.
|
||||
|
||||
### uboot设备树
|
||||
新增板型需要在uboot源码仓库修改,如下:
|
||||
### U-Boot Device Tree
|
||||
|
||||
1. 添加uboot设备树u-boot-2022.10/arch/riscv/dts/k1-x_MUSE-Pi.dts
|
||||
2. 修改Makefile,将k1-x_MUSE-Pi.dtb添加到里面,如下:(注意后缀改成dtb)
|
||||
To add a new board type, you need to modify the U-Boot source code repository as follows:
|
||||
|
||||
```
|
||||
1.Add the U-Boot device tree `u-boot-2022.10/arch/riscv/dts/k1-x_MUSE-Pi.dts`.
|
||||
2.Modify the Makefile to include k1-x_MUSE-Pi.dtb as follows: (Note that the suffix should be changed to .dtb).
|
||||
|
||||
```diff
|
||||
11 dtb-$(CONFIG_TARGET_SPACEMIT_K1X) += k1-x_evb.dtb k1-x_deb2.dtb k1-x_deb1.dtb k1-x_hs450.dtb \
|
||||
12 k1-x_kx312.dtb k1-x_MINI-PC.dtb k1-x_mingo.dtb k1-x_MUSE-N1.dtb \
|
||||
13 k1-x_MUSE-Pi.dtb k1-x_spl.dtb k1-x_milkv-jupiter.dtb \
|
||||
|
@ -36,14 +38,15 @@ target/linux/spacemit/dts/k1-x_MUSE-Pi.dts
|
|||
15
|
||||
```
|
||||
|
||||
3. 修改uboot-2022.10/board/spacemit/k1-x/configs/uboot_fdt.its,添加新节点。
|
||||
3.modify `uboot-2022.10/board/spacemit/k1-x/configs/uboot_fdt.its`, add new node:
|
||||
|
||||
```
|
||||
```diff
|
||||
@@ -46,15 +46,6 @@
|
||||
algo = "crc32";
|
||||
};
|
||||
};
|
||||
+ fdt_4 {
|
||||
|
||||
algo = "crc32";
|
||||
};
|
||||
};
|
||||
+ fdt_4 {
|
||||
+ description = "k1-x_MUSE-Pi";
|
||||
+ type = "flat_dt";
|
||||
+ compression = "none";
|
||||
|
@ -52,127 +55,127 @@ target/linux/spacemit/dts/k1-x_MUSE-Pi.dts
|
|||
+ algo = "crc32";
|
||||
+ };
|
||||
+ };
|
||||
};
|
||||
};
|
||||
|
||||
configurations {
|
||||
configurations {
|
||||
@@ -74,10 +65,5 @@
|
||||
loadables = "uboot";
|
||||
fdt = "fdt_3";
|
||||
};
|
||||
+ conf_4 {
|
||||
loadables = "uboot";
|
||||
fdt = "fdt_3";
|
||||
};
|
||||
+ conf_4 {
|
||||
+ description = "k1-x_MUSE-Pi";
|
||||
+ loadables = "uboot";
|
||||
+ fdt = "fdt_4";
|
||||
+ };
|
||||
};
|
||||
};
|
||||
};
|
||||
```
|
||||
|
||||
4. 修改uboot-2022.10/include/configs/k1-x.h,更新DEFAULT_PRODUCT_NAME,FSBL和u-boot将默认根据DEFAULT_PRODUCT_NAME加载dtb。如果板子有EEPROM记录product_name等信息,则优先级更高,FSBL和u-boot将使用EEPROM的信息实现自适应启动。
|
||||
4.Modify `uboot-2022.10/include/configs/k1-x.h` and update `DEFAULT_PRODUCT_NAME`. FSBL and U-Boot will, by default, load the dtb based on `DEFAULT_PRODUCT_NAME`. If the board has an EEPROM that records information such as product_name, then this takes precedence, and FSBL and U-Boot will use the information from the EEPROM to achieve adaptive booting.
|
||||
|
||||
```
|
||||
```diff
|
||||
@@ -25,7 +25,7 @@
|
||||
#define CONFIG_GATEWAYIP 10.0.92.1
|
||||
#define CONFIG_NETMASK 255.255.255.0
|
||||
#define CONFIG_GATEWAYIP 10.0.92.1
|
||||
#define CONFIG_NETMASK 255.255.255.0
|
||||
|
||||
-#define DEFAULT_PRODUCT_NAME "k1_deb1"
|
||||
+#define DEFAULT_PRODUCT_NAME "k1-x_MUSE-Pi"
|
||||
-#define DEFAULT_PRODUCT_NAME "k1_deb1"
|
||||
+#define DEFAULT_PRODUCT_NAME "k1-x_MUSE-Pi"
|
||||
|
||||
#define K1X_SPL_BOOT_LOAD_ADDR (0x20200000)
|
||||
#define DDR_TRAINING_DATA_BASE (0xc0829000)
|
||||
#define K1X_SPL_BOOT_LOAD_ADDR (0x20200000)
|
||||
#define DDR_TRAINING_DATA_BASE (0xc0829000)
|
||||
```
|
||||
|
||||
### 加入方案
|
||||
### Add Support for New Board
|
||||
|
||||
如是开发板形态,则修改openwrt/target/linux/spacemit/image/k1-sbc.mk,添加k1-x_MUSE-Pi板型支持
|
||||
If it is a development board form factor, modify `openwrt/target/linux/spacemit/image/k1-sbc.mk` to add support for the `k1-x_MUSE-Pi` board type.
|
||||
|
||||
```
|
||||
```sh
|
||||
DEVICE_DTS := k1-x_deb1 k1-x_MUSE-Pi
|
||||
|
||||
```
|
||||
|
||||
如果需要新增方案,请参考[方案管理](openwrt_solution_management.md)
|
||||
If you need to add a new configuration, please refer to[solution management](openwrt_solution_management.md)
|
||||
|
||||
## 支持单CS DDR
|
||||
## Support Single CS DDR
|
||||
|
||||
FSBL默认支持双CS DDR,修改`uboot-2022.10/arch/riscv/dts/k1-x_spl.dts`可以支持单CS DDR。
|
||||
By default, FSBL supports dual CS DDR. To enable support for single CS DDR, modify uboot-2022.10/arch/riscv/dts/k1-x_spl.dts.
|
||||
|
||||
```diff
|
||||
@@ -79,7 +79,7 @@
|
||||
ddr@c0000000 {
|
||||
/* dram data rate, should be 1200, 1600, or 2400 */
|
||||
datarate = <2400>;
|
||||
- cs-num = <2>;
|
||||
+ cs-num = <1>;
|
||||
u-boot,dm-spl;
|
||||
};
|
||||
ddr@c0000000 {
|
||||
/* dram data rate, should be 1200, 1600, or 2400 */
|
||||
datarate = <2400>;
|
||||
- cs-num = <2>;
|
||||
+ cs-num = <1>;
|
||||
u-boot,dm-spl;
|
||||
};
|
||||
```
|
||||
|
||||
如果设备有EEPROM,支持通过EEPROM实现自适应,待更新。
|
||||
If the device has an EEPROM, adaptive support can be achieved through the EEPROM. The corresponding key name is `ddr_cs_num`, which can be programmed using the titantools utility. For details on the flashing tool, please refer to the documentation at <https://developer.spacemit.com/documentation?token=O6wlwlXcoiBZUikVNh2cczhin5d>
|
||||
|
||||
## 通过EEPROM实现自适应
|
||||
## Adaptive Booting via EEPROM
|
||||
|
||||
通过进迭Titanflasher工具给板子eeprom写号,实现启动的自适应,即一个固件支持多个板子。
|
||||
Use the Titanflasher tool to program the EEPROM of the board, enabling adaptive booting, i.e., one firmware supports multiple boards.
|
||||
|
||||
系统启动时读取eeprom的信息,匹配uboot_fdt.its中信息,从而实现多板型支持。
|
||||
During system startup, the information in the EEPROM is read and matched with the information in uboot_fdt.its, thereby supporting multiple board types.
|
||||
|
||||
相关文件:
|
||||
Relevant Files:
|
||||
|
||||
```shell
|
||||
uboot-2022.10/arch/riscv/dts/k1-x_spl.dts
|
||||
uboot-2022.10/arch/riscv/dts/k1-x_*.dts
|
||||
```
|
||||
|
||||
### EEPROM支持列表
|
||||
### EEPROM Support List
|
||||
|
||||
- `atmel,24c02`
|
||||
|
||||
### 添加新EEPROM
|
||||
### Add New EEPROM
|
||||
|
||||
1. 修改`uboot-2022.10/arch/riscv/dts/k1-x_spl.dts`,更新EEPROM的I2C地址,例如新地址为`0xA0`。
|
||||
1.Modify `uboot-2022.10/arch/riscv/dts/k1-x_spl.dts`, Update the I2C address of the EEPROM, for example, the new address is `0xA0`.
|
||||
|
||||
```c
|
||||
@@ -121,7 +121,7 @@
|
||||
eeprom@50{
|
||||
compatible = "atmel,24c02";
|
||||
u-boot,dm-spl;
|
||||
- reg = <0x50>;
|
||||
+ reg = <0xA0>;
|
||||
bus = <6>;
|
||||
#address-cells = <1>;
|
||||
#size-cells = <1>;
|
||||
```
|
||||
```c
|
||||
@@ -121,7 +121,7 @@
|
||||
eeprom@50{
|
||||
compatible = "atmel,24c02";
|
||||
u-boot,dm-spl;
|
||||
reg = <0x50>;
|
||||
reg = <0xA0>;
|
||||
bus = <6>;
|
||||
#address-cells = <1>;
|
||||
#size-cells = <1>;
|
||||
```
|
||||
|
||||
2. 修改`uboot-2022.10/arch/riscv/dts/k1-x_*.dts`,添加新EEPROM的配置。
|
||||
2.Modify `uboot-2022.10/arch/riscv/dts/k1-x_*.dts`, add new eeprom config:
|
||||
|
||||
```c
|
||||
@@ -60,9 +60,9 @@
|
||||
pinctrl-0 = <&pinctrl_i2c2_0>;
|
||||
status = "okay";
|
||||
pinctrl-0 = <&pinctrl_i2c2_0>;
|
||||
status = "okay";
|
||||
|
||||
- eeprom@50{
|
||||
- compatible = "atmel,24c02";
|
||||
- reg = <0x50>;
|
||||
+ eeprom@A0{
|
||||
+ compatible = "atmel,24c04";
|
||||
+ reg = <0xA0>;
|
||||
vin-supply-names = "eeprom_1v8";
|
||||
status = "okay";
|
||||
};
|
||||
- eeprom@50{
|
||||
- compatible = "atmel,24c02";
|
||||
- reg = <0x50>;
|
||||
+ eeprom@A0{
|
||||
+ compatible = "atmel,24c04";
|
||||
+ reg = <0xA0>;
|
||||
vin-supply-names = "eeprom_1v8";
|
||||
status = "okay";
|
||||
};
|
||||
```
|
||||
|
||||
### 使用tlv_eeprom写号
|
||||
### Use tlv_eeprom command to write key
|
||||
|
||||
写号是指将`product_name`等信息写入EEPROM。目前,在EEPROM中的信息是按照TLV编码的,可以使用u-boot的`tlv_eeprom`命令写号。
|
||||
Writing to the EEPROM involves storing information such as `product_name`. Currently, the data in the EEPROM is encoded using TLV format, and you can use the `tlv_eeprom` command provided by u-boot to perform this operation.
|
||||
|
||||
1. PC接上设备的调试串口,设备启动时,在PC串口终端按下键盘的`s`键,直到进入u-boot shell。
|
||||
1. Connect your PC to the device's debug serial port. During boot-up, press the `s` key on the PC terminal to enter the u-boot shell.
|
||||
|
||||
```shell
|
||||
Autoboot in 0 seconds
|
||||
=>
|
||||
```
|
||||
|
||||
2. 烧写`product_name`,例如`k1-x_MUSE-Pi`。
|
||||
2. write `product_name`,such as `k1-x_MUSE-Pi`。
|
||||
|
||||
```shell
|
||||
=> tlv_eeprom set 0x21 k1-x_MUSE-Pi
|
||||
|
@ -180,18 +183,17 @@ uboot-2022.10/arch/riscv/dts/k1-x_*.dts
|
|||
Programming passed.
|
||||
```
|
||||
|
||||
`Programming passed.`表示写入成功。
|
||||
`Programming passed.` meaning write key success.
|
||||
|
||||
请以设备dts的文件名(不带后缀)命名,方便u-boot自动加载dtb。
|
||||
Use the name of the device’s DTS file (without the extension, e.g., k1-x_MUSE-Pi) to facilitate automatic loading of the DTB by u-boot.
|
||||
|
||||
3. `reset`检查是否可以加载`k1-x_MUSE-Pi`的dtb,正常的话u-boot有如下打印。
|
||||
3. reboot device and check if the `k1-x_MUSE-Pi` DTB can be loaded. If everything is normal, u-boot should print the following:
|
||||
|
||||
```shell
|
||||
product_name: k1-x_MUSE-Pi
|
||||
detect dtb_name: k1-x_MUSE-Pi.dtb
|
||||
Boot from fit configuration: k1-x_MUSE-Pi
|
||||
```
|
||||
|
||||
SDK还支持从EEPROM读取以下信息:
|
||||
The SDK also supports reading the following information from the EEPROM:
|
||||
|
||||
- Serial Number:`0x23`
|
||||
- Base MAC Address:`0x24`
|
||||
|
@ -201,4 +203,4 @@ SDK还支持从EEPROM读取以下信息:
|
|||
- Manufacturer:`0x2B`
|
||||
- SDK Version:`0x40`
|
||||
|
||||
其中MAC Address会更新到dtb,作为网卡物理地址。
|
||||
The MAC Address will be updated in the DTB and used as the network card’s physical address.
|
||||
|
|
|
@ -4,124 +4,262 @@ sidebar_position: 2
|
|||
|
||||
# Download and Build
|
||||
|
||||
以下文档基于ubuntu22.04描述
|
||||
The following document is based on Ubuntu 22.04.
|
||||
|
||||
## 环境准备
|
||||
## Environment Preparation
|
||||
|
||||
### 安装依赖
|
||||
### Installing Dependencies
|
||||
|
||||
```
|
||||
```sh
|
||||
sudo apt install build-essential clang flex bison g++ gawk \
|
||||
gcc-multilib g++-multilib gettext git libncurses-dev libssl-dev \
|
||||
python3-distutils rsync unzip zlib1g-dev file wget jq device-tree-compiler
|
||||
|
||||
```
|
||||
|
||||
## 下载代码
|
||||
## Download openwrt
|
||||
|
||||
The code repository has two branches:` bl-v1.0.y` and `bl-v2.0.y`, which correspond to `linux-6.1` and `linux-6.6`, respectively. The `bl-v2.0.y` branch will be primarily maintained going forward.
|
||||
|
||||
```sh
|
||||
git clone https://gitee.com/bianbu-linux/openwrt.git -b bl-v2.0.y
|
||||
|
||||
```
|
||||
git clone https://gitee.com/bianbu-linux/openwrt.git -b bl-v1.0.y
|
||||
```
|
||||
|
||||
## 拉取feeds
|
||||
|
||||
首次或想更新包时需要运行
|
||||
Use the following commands to run or update packages. Package updates will be downloaded from the OpenWRT official website, so ensure that your network is accessible. If there are any failures in downloading certain packages, you can re-run the commands:
|
||||
|
||||
```
|
||||
```sh
|
||||
cd openwrt
|
||||
./scripts/feeds update -a
|
||||
./scripts/feeds install -f -p spacemit_openwrt_feeds -a
|
||||
./scripts/feeds install -a
|
||||
```
|
||||
|
||||
## 固件编译
|
||||
## Firmware Compilation
|
||||
|
||||
V=s输出详细日志
|
||||
The optional parameter `V=s` in the compilation command provides detailed logs. Currently, there are two options for initiating the compilation process.
|
||||
|
||||
### SBC方案
|
||||
### SBC Solution
|
||||
|
||||
```
|
||||
```sh
|
||||
cp feeds/spacemit_openwrt_feeds/spacemit_k1_defconfig .config
|
||||
make -j12 V=s
|
||||
```
|
||||
|
||||
固件位于bin/targets/spacemit/DEVICE_debX/*.zip
|
||||
image would create at `bin/targets/spacemit/DEVICE_debX/*.zip`
|
||||
|
||||
### NAS方案
|
||||
### NAS Solution
|
||||
|
||||
```
|
||||
```sh
|
||||
cp feeds/spacemit_openwrt_feeds/spacemit_k1_nas_defconfig .config
|
||||
make -j12 V=s
|
||||
```
|
||||
固件位于bin/targets/spacemit/DEVICE_MUSE-N1/*.zip
|
||||
|
||||
### 清理
|
||||
image would create at `bin/targets/spacemit/DEVICE_MUSE-N1/*.zip`
|
||||
|
||||
全部清理,会把bin、build_dir、staging_dir、feeds、dl等目录删掉
|
||||
### Cleaning
|
||||
|
||||
```
|
||||
* The full cleanup command will delete directories such as `bin, build_dir, staging_dir, feeds, dl`, as well as the `.config` file, returning the code repository to its original state.
|
||||
|
||||
```sh
|
||||
make distclean
|
||||
```
|
||||
|
||||
局部清理,会把编译输出目录bin、build_dir、staging_dir删掉
|
||||
* The partial cleanup command will delete the build output directories such as `bin, build_dir, staging_dir`, but it will not remove the dl directory, the `.config` file, or other similar files.
|
||||
|
||||
```
|
||||
```sh
|
||||
make dirclean
|
||||
```
|
||||
|
||||
## 单包编译
|
||||
## single package compilation
|
||||
|
||||
以adb包为例说明
|
||||
### build uboot
|
||||
|
||||
### 编译
|
||||
* compile
|
||||
|
||||
```sh
|
||||
make package/boot/uboot-spacemit/compile V=s
|
||||
```
|
||||
|
||||
* clean
|
||||
|
||||
```sh
|
||||
make package/boot/uboot-spacemit/clean V=s
|
||||
```
|
||||
|
||||
### build opensbi
|
||||
|
||||
* compile
|
||||
|
||||
```sh
|
||||
make package/boot/opensbi-spacemit/compile V=s
|
||||
```
|
||||
|
||||
* clean
|
||||
|
||||
```sh
|
||||
make package/boot/opensbi-spacemit/clean V=s
|
||||
```
|
||||
|
||||
### build linux
|
||||
|
||||
* compile
|
||||
|
||||
```sh
|
||||
make target/linux/compile V=s
|
||||
```
|
||||
|
||||
* clean
|
||||
|
||||
```sh
|
||||
make target/linux/clean V=s
|
||||
```
|
||||
|
||||
### build adb package
|
||||
|
||||
The compilation process for other packages is similar to the following method.
|
||||
|
||||
* compile
|
||||
|
||||
```sh
|
||||
make package/utils/adb/compile V=s
|
||||
```
|
||||
|
||||
### 清理
|
||||
* clean
|
||||
|
||||
```
|
||||
```sh
|
||||
make package/utils/adb/clean V=s
|
||||
```
|
||||
|
||||
## 烧写
|
||||
## Flashing
|
||||
|
||||
固件*.zip,使用Titan Flasher工具刷写至设备板载存储介质
|
||||
Firmware `*.zip`: Use the Titan Flasher tool to flash it to the onboard storage of the device. For instructions on using the flashing tool, see<https://developer.spacemit.com/documentation?token=O6wlwlXcoiBZUikVNh2cczhin5d>
|
||||
|
||||
固件*sdcard.img,使用dd命令写至卡上,设备插卡上电即可实现卡启动
|
||||
Firmware `*sdcard.img`: Can be written to the card using the `dd` command. The device can boot from the card once it is inserted and powered on.
|
||||
|
||||
## 支持设备列表
|
||||
## Supported Devices List
|
||||
|
||||
### SBC方案
|
||||
### SBC Solutions
|
||||
|
||||
- BPI-F3
|
||||
- MUSE-Pi
|
||||
* BPI-F3
|
||||
* MUSE-Pi
|
||||
|
||||
### NAS方案
|
||||
### NAS Solutions
|
||||
|
||||
- MUSE-N1
|
||||
* MUSE-N1
|
||||
|
||||
## 软路由
|
||||
## Soft Router Functionality
|
||||
|
||||
在以上支持设备列表的板型默认开启软路由功能。系统开机后默认开启WiFi AP模式,其中:
|
||||
The soft router function is enabled by default on the board types in the supported devices list. When the system boots up, the WiFi AP mode is activated by default. Specifically:
|
||||
|
||||
SBC方案有线网卡eth1为lan口,eth2为wan
|
||||
For SBC solutions: The wired network card eth1 is the LAN port, and eth2 is the WAN port.
|
||||
|
||||
NAS方案有线网卡2.5G为wan,其它两个千兆口为lan
|
||||
For NAS solutions: The 2.5G wired network card is the WAN port, and the other two Gigabit ports are LAN ports.
|
||||
|
||||
- 热点名称:openWRT-AP
|
||||
- 热点密码:12345678
|
||||
- WiFi网关:192.168.1.1
|
||||
* Hotspot Name:openWRT-AP
|
||||
* Hotspot Password:12345678
|
||||
* WiFi Gateway:192.168.1.1
|
||||
|
||||
## FAQ
|
||||
|
||||
### 1. 内核编译链接pthread_once出错
|
||||
### Error with pthread_once during kernel compilation
|
||||
|
||||
基于ubuntu 20.04编译openwrt出现"pthread_once"的编译报错,可修改`linux-*/certs/Makefile`
|
||||
When compiling OpenWRT based on Ubuntu 20.04, an error with "pthread_once" may occur. This can be resolved by modifying the `linux-*/certs/Makefile`.
|
||||
|
||||
```C
|
||||
openwrt/build_dir/target-riscv64_riscv64_musl_*/linux-spacemit_*/linux-6.1.15/certs/Makefile
|
||||
最后一行改成:
|
||||
//openwrt/build_dir/target-riscv64_riscv64_musl_*/linux-spacemit_*/linux-6.1.15/certs/Makefile
|
||||
# Change the last line to:
|
||||
HOSTLDLIBS_extract-cert = -lcrypto -pthread
|
||||
```
|
||||
|
||||
### How to Update U-Boot/OpenSBI/Linux Versions
|
||||
|
||||
1.OpenWRT tracks the versions of the U-Boot/OpenSBI/Linux repositories hosted on <https://gitee.com/bianbu-linux>. OpenWRT periodically updates these repository versions.
|
||||
|
||||
2.If you need to manually update to the latest versions of U-Boot/OpenSBI/Linux, follow these steps:
|
||||
|
||||
* Confirm that the latest version tarball has been uploaded to<https://archive.spacemit.com/openwrt/dl/>,such as `linux-6.1-v1.0.15.tar.xz`
|
||||
|
||||

|
||||
|
||||
* Changing the Version Number in the Makefile
|
||||
|
||||
```diff
|
||||
diff --git a/package/boot/opensbi-spacemit/Makefile b/package/boot/opensbi-spacemit/Makefile
|
||||
index d4572af253..208d2fae6d 100644
|
||||
--- a/package/boot/opensbi-spacemit/Makefile
|
||||
+++ b/package/boot/opensbi-spacemit/Makefile
|
||||
@@ -16,7 +16,7 @@ else
|
||||
PKG_NAME:=opensbi
|
||||
PKG_RELEASE:=1
|
||||
PKG_VERSION:=1.3
|
||||
-PKG_SOURCE_VERSION:=1.0.5
|
||||
+PKG_SOURCE_VERSION:=v1.0.15
|
||||
|
||||
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION)-$(PKG_SOURCE_VERSION).tar.gz
|
||||
PKG_SOURCE_URL:=https://archive.spacemit.com/openwrt/dl/
|
||||
diff --git a/package/boot/uboot-spacemit/Makefile b/package/boot/uboot-spacemit/Makefile
|
||||
index 51e6e97fb7..c69173cfa8 100644
|
||||
--- a/package/boot/uboot-spacemit/Makefile
|
||||
+++ b/package/boot/uboot-spacemit/Makefile
|
||||
@@ -18,7 +18,7 @@ else
|
||||
PKG_NAME:=uboot
|
||||
PKG_RELEASE:=1
|
||||
PKG_VERSION:=2022.10
|
||||
-PKG_SOURCE_VERSION:=1.0.5
|
||||
+PKG_SOURCE_VERSION:=v1.0.15
|
||||
|
||||
PKG_SOURCE:=uboot-$(PKG_VERSION)-$(PKG_SOURCE_VERSION).tar.gz
|
||||
PKG_SOURCE_URL:=https://archive.spacemit.com/openwrt/dl/
|
||||
|
||||
diff --git a/target/linux/spacemit/Makefile b/target/linux/spacemit/Makefile
|
||||
index ac230af366..148e5a79b8 100644
|
||||
--- a/target/linux/spacemit/Makefile
|
||||
+++ b/target/linux/spacemit/Makefile
|
||||
@@ -20,7 +20,7 @@ CONFIG_EXTERNAL_KERNEL_TREE=$(TOPDIR)/../bsp-src/linux-6.1
|
||||
CONFIG_KERNEL_GIT_CLONE_URI=""
|
||||
else
|
||||
## download tar.xz from url.
|
||||
-LINUX_VERSION_CUSTOM:=linux-6.1-1.0.5
|
||||
+LINUX_VERSION_CUSTOM:=linux-6.1-v1.0.15
|
||||
LINUX_SOURCE:=$(LINUX_VERSION_CUSTOM).tar.xz
|
||||
LINUX_KERNEL_HASH:=skip
|
||||
endif
|
||||
|
||||
```sh
|
||||
* update kernel config
|
||||
|
||||
```sh
|
||||
make kernel_menuconfig
|
||||
```
|
||||
|
||||
* compile
|
||||
|
||||
There might be failures. If the compilation encounters errors, please correct them based on the error messages.
|
||||
|
||||
```sh
|
||||
make -j12 V=s
|
||||
```
|
||||
|
||||
### Change the Download Source to Spacemit
|
||||
|
||||
Spacemit maintains a set of pre-compiled packages that can be downloaded and installed by changing the source.
|
||||
|
||||
* Modify the software source address (based on device modifications):
|
||||
|
||||
`bl-v2.0.y` is a specific version tag. Please modify it according to your needs.
|
||||
If using the SBC solution, change `DEVICE_MUSE-N1` to `DEVICE_debX`.
|
||||
|
||||
```sh
|
||||
//vim /etc/opkg/distfeeds.conf
|
||||
|
||||
src/gz openwrt_base https://archive.spacemit.com/openwrt/releases/bl-v2.0.y/packages/riscv64_riscv64/base
|
||||
src/gz openwrt_luci https://archive.spacemit.com/openwrt/releases/bl-v2.0.y/packages/riscv64_riscv64/luci
|
||||
src/gz openwrt_packages https://archive.spacemit.com/openwrt/releases/bl-v2.0.y/packages/riscv64_riscv64/packages
|
||||
src/gz openwrt_routing https://archive.spacemit.com/openwrt/releases/bl-v2.0.y/packages/riscv64_riscv64/routing
|
||||
src/gz openwrt_telephony https://archive.spacemit.com/openwrt/releases/bl-v2.0.y/packages/riscv64_riscv64/telephony
|
||||
src/gz openwrt_spacemit_packages https://archive.spacemit.com/openwrt/releases/bl-v2.0.y/targets/spacemit/DEVICE_MUSE-N1/packages
|
||||
|
||||
```
|
||||
|
|
|
@ -2,86 +2,82 @@
|
|||
sidebar_position: 4
|
||||
---
|
||||
|
||||
|
||||
|
||||
# Solution Management
|
||||
|
||||
本文档介绍进迭OpenWrt SDK的方案管理,目前发行的SDK默认适配k1-sbc、k1-nas方案,
|
||||
每个方案支持多个板型,如k1-sbc方案支持k1-x_MUSE-Pi、k1-x_deb1板型,未来会持续更新。
|
||||
This document introduces the management of solutions for the OpenWrt SDK. Currently, the released SDK defaults to supporting the k1-sbc and k1-nas solutions. Each solution supports multiple board types; for example, the k1-sbc solution supports the k1-x_MUSE-Pi and k1-x_deb1 board types. Future updates will continue to be released.
|
||||
|
||||
## Solution Overview
|
||||
|
||||
Using the development board solution k1-sbc as an example, it typically involves the following configuration files, which will be introduced in subsequent chapters.
|
||||
|
||||
|
||||
## 方案总览
|
||||
以开发板方案k1-sbc为例,通常跟以下配置文件有关,后续章节逐一介绍
|
||||
```
|
||||
#方案配置
|
||||
```sh
|
||||
#Solution Configuration
|
||||
feeds/spacemit_openwrt_feeds/spacemit_k1_defconfig
|
||||
|
||||
#方案编译入口
|
||||
#olution Compilation Entry Point
|
||||
openwrt/target/linux/spacemit/Makefile
|
||||
|
||||
#方案定义
|
||||
#Solution Definition
|
||||
openwrt/target/linux/spacemit/k1-sbc/config-6.1
|
||||
openwrt/target/linux/spacemit/k1-sbc/target.mk
|
||||
openwrt/target/linux/spacemit/k1-sbc/base-files/
|
||||
|
||||
#方案设备树管理
|
||||
#Solution Device Tree Management
|
||||
openwrt/target/linux/spacemit/dts/
|
||||
|
||||
#方案启动参数
|
||||
#Solution Boot Parameters
|
||||
openwrt/target/linux/spacemit/image/env_k1-x.txt
|
||||
|
||||
#固件定义
|
||||
#Firmware Definition
|
||||
openwrt/target/linux/spacemit/image/k1-sbc.mk
|
||||
#方案的固件分区
|
||||
#Firmware Partitions for the Solution
|
||||
openwrt/target/linux/spacemit/image/partition_tables/partition_2M.json
|
||||
openwrt/target/linux/spacemit/image/partition_tables/partition_flash.json
|
||||
openwrt/target/linux/spacemit/image/partition_tables/partition_universal.json
|
||||
|
||||
#方案首次启动配置
|
||||
#Initial Setup Configuration for the Solution
|
||||
openwrt/target/linux/spacemit/base-files/etc/uci-defaults/
|
||||
|
||||
|
||||
```
|
||||
|
||||
### 方案配置
|
||||
### Configuration for the Solution
|
||||
|
||||
`feeds/spacemit_openwrt_feeds/spacemit_k1_defconfig`
|
||||
|
||||
k1-sbc方案的编译配置,用于指导OpenWrt的编译行为
|
||||
This is the build configuration for the k1-sbc solution, used to guide the compilation behavior of OpenWrt.
|
||||
|
||||
### Makefile for the Solution
|
||||
|
||||
### 方案Makefile
|
||||
`openwrt/target/linux/spacemit/Makefile`
|
||||
|
||||
SUBTARGETS添加方案名称
|
||||
Add the name of the solution to SUBTARGETS:
|
||||
|
||||
```
|
||||
```c
|
||||
...
|
||||
12 SUBTARGETS:=k1-nas k1-sbc
|
||||
...
|
||||
```
|
||||
|
||||
### Directory for the Solution
|
||||
|
||||
### 方案目录
|
||||
`openwrt/target/linux/spacemit/k1-sbc`
|
||||
|
||||
创建跟方案名称同名目录:k1-sbc,包含以下内容
|
||||
Create a directory with the same name as the solution: k1-sbc, containing the following:
|
||||
|
||||
* openwrt/target/linux/spacemit/k1-sbc/config-6.1
|
||||
* openwrt/target/linux/spacemit/k1-sbc/config-6.1
|
||||
|
||||
config-6.1为方案的kernel配置,编译kernel时合并openwrt/target/linux/generic/config-6.1 与本方案config-6.1,相同的配置选项以本方案为主
|
||||
`config-6.1` is the kernel configuration for this solution. When compiling the kernel, merge `openwrt/target/linux/generic/config-6.1` with this solution's `config-6.1`, giving priority to the options in this solution.
|
||||
|
||||
* openwrt/target/linux/spacemit/k1-sbc/target.mk
|
||||
* openwrt/target/linux/spacemit/k1-sbc/target.mk
|
||||
|
||||
定义方案的通用信息,如DEVICE_TYPE:=router(可选router、nas)。
|
||||
Defines general information for the solution, such as `DEVICE_TYPE:=router` (optional values include router, nas). This is defined by OpenWrt, where different device types include different default packages.
|
||||
|
||||
此为OpenWrt定义,不同device type默认包含不同软件包
|
||||
* openwrt/target/linux/spacemit/k1-sbc/base-files/
|
||||
|
||||
Contains configuration files to be packaged into the root file system, such as:
|
||||
|
||||
* openwrt/target/linux/spacemit/k1-sbc/base-files/
|
||||
|
||||
包含要打包进rootfs的配置文件,如下:
|
||||
```
|
||||
```sh
|
||||
openwrt/target/linux/spacemit/k1-sbc/base-files$ tree
|
||||
.
|
||||
├── etc
|
||||
|
@ -107,40 +103,41 @@ openwrt/target/linux/spacemit/k1-sbc/base-files$ tree
|
|||
8 directories, 11 files
|
||||
```
|
||||
|
||||
### Device Tree for the Solution
|
||||
|
||||
|
||||
### 方案设备树
|
||||
`openwrt/target/linux/spacemit/dts/`
|
||||
|
||||
不同板型的内核设备树,可参考[设备管理](openwrt_device_management.md)添加一个新板型支持
|
||||
Kernel device trees for different board types. You can refer to[device management](openwrt_device_management.md)to add support for a new board type.
|
||||
|
||||
### Partition Table for the Solution
|
||||
|
||||
### 方案分区表
|
||||
`openwrt/target/linux/spacemit/image/partition_tables/`
|
||||
|
||||
这里的分区表是多个方案通用。里面包含不同存储介质的分区表配置,
|
||||
The partition tables here are shared among multiple solutions. They contain configurations for different storage media.
|
||||
|
||||
也可自行添加跟板载存储介质容量一致的分区表,TitanFlasher工具烧写固件时自动匹配
|
||||
You can also add a partition table that matches the capacity of the onboard storage medium, which will be automatically matched when using the TitanFlasher tool to flash the firmware.
|
||||
|
||||
* partition_2M.json,用于nor刷机启动,一般与emmc/ssd等blk设备一起使用
|
||||
* partition_universal.json,用于blk设备的刷机启动,
|
||||
* partition_flash.json,用于spacemit Titanflasher工具制作卡量产
|
||||
* partition_2M.json,Used for NOR flash booting, typically paired with eMMC/SSD block devices.
|
||||
* partition_universal.json,Used for booting from block devices.
|
||||
* partition_flash.json,Used for mass production with the spacemit Titanflasher tool.
|
||||
|
||||
修改分区表可能会影响到系统正常启动,详细的修改方式请参考《启动》文档
|
||||
Modifying the partition table may affect the normal boot process of the system. For detailed modification procedures, please refer to the documentation on <https://bianbu-linux.spacemit.com/development_guide/boot>.
|
||||
|
||||
### Boot Parameters for the Solution
|
||||
|
||||
### 方案启动参数
|
||||
`openwrt/target/linux/spacemit/image/env_k1-x.txt`
|
||||
|
||||
uboot最高优先级环境变量,这里可以设定bootargs启动参数,loglevel等
|
||||
U-Boot environment variables with the highest priority. Here you can set boot arguments (bootargs), log level, etc.
|
||||
|
||||
默认的bootargs为:
|
||||
The default bootargs are:
|
||||
|
||||
```
|
||||
```sh
|
||||
commonargs=setenv bootargs earlycon=${earlycon} earlyprintk console=tty1 console=${console} loglevel=${loglevel} clk_ignore_unused swiotlb=65536 rdinit=${init}
|
||||
```
|
||||
|
||||
可在env_k1-x.txt中重定义earlycon/console/loglevel/init等环境变量
|
||||
```
|
||||
You can redefine environment variables such as `earlycon, console, loglevel, and init` in `env_k1-x.txt`.
|
||||
|
||||
```sh
|
||||
# Common parameter
|
||||
earlycon=sbi
|
||||
console=ttyS0,115200
|
||||
|
@ -150,25 +147,26 @@ loglevel=8
|
|||
|
||||
```
|
||||
|
||||
也可以直接重定义整个bootargs
|
||||
```
|
||||
Alternatively, you can redefine the entire bootargs.
|
||||
|
||||
```sh
|
||||
bootargs=earlycon=sbi console=ttyS0,115200 loglevel=4
|
||||
|
||||
```
|
||||
|
||||
### Firmware for the Solution
|
||||
|
||||
### 方案固件
|
||||
`openwrt/target/linux/spacemit/image/k1-sbc.mk`
|
||||
|
||||
制定方案的固件编译,如包含支持的板型、生成sdcard.img、spacemit.zip刷机包等,
|
||||
This Makefile configures the firmware compilation for the solution, including supported board types, generating sdcard.img, and creating the spacemit.zip flashing package.
|
||||
|
||||
比如不想生成sdcard.img,可去掉IMAGE/pack.zip中的sdcard-img。
|
||||
For example, if you do not want to generate sdcard.img, you can remove sdcard-img from `IMAGE/pack.zip`.
|
||||
|
||||
比如对本方案增加MUSE-Pi板型支持,则DEVICE_DTS增加k1-x_MUSE-Pi设备树名称,
|
||||
If you want to add support for the MUSE-Pi board type in this solution, then add the device tree name `k1-x_MUSE-Pi`to DEVICE_DTS.
|
||||
|
||||
且openwrt/target/linux/spacemit/dts/需有一份k1-x_MUSE-Pi.dts
|
||||
Additionally, there should be a file named `k1-x_MUSE-Pi.dts` in `openwrt/target/linux/spacemit/dts/`.
|
||||
|
||||
```
|
||||
```sh
|
||||
# SPDX-License-Identifier: GPL-2.0-only
|
||||
#
|
||||
# Copyright (C) 2024 Spacemit Ltd.
|
||||
|
@ -189,45 +187,42 @@ TARGET_DEVICES += debX
|
|||
|
||||
```
|
||||
|
||||
### Initial Setup for the Solution
|
||||
|
||||
### 方案首次启动
|
||||
`openwrt/target/linux/spacemit/base-files/etc/uci-defaults/`
|
||||
|
||||
UCI默认设置提供了一种使用UCI预配置您的镜像的方法。 要在设备首次启动时设置一些系统默认值,
|
||||
UCI default settings provide a method to preconfigure your image using UCI. To set some system defaults during the first boot of the device, create a script in this directory.
|
||||
|
||||
请在目录此中创建一个脚本。
|
||||
## Adding a New Solution
|
||||
|
||||
Using the k1-sbc solution as an example, the following modifications need to be made:
|
||||
|
||||
1.Modify the SUBTARGETS in `openwrt/target/linux/spacemit/Makefile` to include the solution name, such as `k1-sbc`.
|
||||
2.Add a new solution directory, such as `openwrt/target/linux/spacemit/k1-sbc/`, and include the following files:
|
||||
|
||||
## 新增方案
|
||||
以k1-sbc方案为例,需要修改以下内容:
|
||||
|
||||
1. 修改openwrt/target/linux/spacemit/Makefile中的SUBTARGETS,添加方案名称,如k1-sbc
|
||||
2. 新增方案目录,如openwrt/target/linux/spacemit/k1-sbc/,添加如下文件
|
||||
|
||||
```
|
||||
```sh
|
||||
openwrt/target/linux/spacemit/k1-sbc/config-6.1
|
||||
openwrt/target/linux/spacemit/k1-sbc/target.mk
|
||||
|
||||
```
|
||||
3. 新增固件编译和兼容板型 openwrt/target/linux/spacemit/image/k1-sbc.mk
|
||||
4. feeds/spacemit_openwrt_feeds/目录下新增编译配置,如k1-sbc方案spacemit_k1_defconfig
|
||||
|
||||
3.Add firmware compilation and compatible board configurations in `openwrt/target/linux/spacemit/image/k1-sbc.mk`.
|
||||
|
||||
### 新增板型
|
||||
每个方案下至少有一个或多个板型,新增板型支持可参考[设备管理](openwrt_device_management.md)
|
||||
4.In the `feeds/spacemit_openwrt_feeds/` directory, add new build configurations, such as `spacemit_k1_defconfig` for the `k1-sbc` solution.
|
||||
|
||||
### Adding Support for New Board Types
|
||||
|
||||
### uboot/opensbi编译配置
|
||||
如有需要增加uboot/opensbi新的编译配置,可参考修改以下内容
|
||||
Each solution should have at least one or more board types. For adding support for new board types, refer to[device management](openwrt_device_management.md)
|
||||
|
||||
### U-Boot/OpenSBI Compilation Configurations
|
||||
|
||||
If it is necessary to add new compilation configurations for U-Boot/OpenSBI, refer to the following modifications:
|
||||
|
||||
#### uboot
|
||||
|
||||
1. uboot源码仓库新增编译配置,如u-boot-2022.10/configs/k1_defconfig
|
||||
2. 修改openwrt/package/boot/uboot-spacemit/Makefile
|
||||
|
||||
```
|
||||
1. Add new compilation configurations in the U-Boot source repository, such as `u-boot-2022.10/configs/k1_defconfig`.
|
||||
2. Modify `openwrt/package/boot/uboot-spacemit/Makefile`:
|
||||
|
||||
```sh
|
||||
50 define Build/Configure
|
||||
51 $(MAKE) -C $(LOCAL_SOURCE_DIR) k1_defconfig
|
||||
52 endef
|
||||
|
@ -236,10 +231,10 @@ openwrt/target/linux/spacemit/k1-sbc/target.mk
|
|||
|
||||
#### opensbi
|
||||
|
||||
1. opensbi源码仓库新增编译配置,如opensbi-1.3/platform/generic/configs/k1_defconfig
|
||||
2. 修改package/boot/opensbi-spacemit/Makefile
|
||||
1. Add new compilation configurations in the OpenSBI source repository, such as `opensbi-1.3/platform/generic/configs/k1_defconfig`.
|
||||
2. Modify `openwrt/package/boot/opensbi-spacemit/Makefile`.
|
||||
|
||||
```
|
||||
```sh
|
||||
59 define Build/Compile
|
||||
60 $(eval $(Package/opensbi_$(BUILD_VARIANT))) \
|
||||
61 +$(MAKE_VARS) $(MAKE) -C $(LOCAL_SOURCE_DIR) \
|
||||
|
|
BIN
static/image.png
Normal file
BIN
static/image.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 242 KiB |
|
@ -1,8 +1,8 @@
|
|||
{
|
||||
"label": "支持的设备",
|
||||
"label": "support devices",
|
||||
"position": 5,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
"description": "OpenWrt支持设备列表"
|
||||
"description": "OpenWrt support devices list"
|
||||
}
|
||||
}
|
||||
|
|
|
@ -4,38 +4,4 @@ sidebar_position: 1
|
|||
|
||||
# MUSE N1
|
||||
|
||||
## **概述**
|
||||
|
||||
MUSE N1 开发板板型:
|
||||
|
||||
- MUSE N1 开发板采用 K1 芯片、P1 PMIC + 外挂 DCDC 的供电方案
|
||||
- 存储采用 LPDDR4X、eMMC
|
||||
- DC Power:USB TYPEC 供电
|
||||
- Ethernet:支持3路 RJ45 网络接口. 其中2路支持 10/100/1000M 以太网,1路支持 2.5G 网口
|
||||
- USB:1路USB 2.0 Host TYPEA 接口,1路 USB3.0 Device TypeC 功能
|
||||
- SDIO WIFI:WIFI 型号为 RTL8852BS,外置 SMA 天线,支持无线上网功能
|
||||
- PCIe2.0 2lane Interface:2路标准M.2 KEY M 接口,用于扩展 PCIe 设备
|
||||
|
||||
## **实物图**
|
||||
|
||||

|
||||
|
||||
## 刷机模式
|
||||
|
||||
对照实物图,进行下述操作:
|
||||
|
||||
- USB线一端连接板子Type-C口,一端连接PC。长按 S3 键不松手,然后按下 S2 REST键进入刷机模式
|
||||
|
||||
刷机工具使用参考《 [刷机工具使用手册](https://developer.spacemit.com/#/documentation?token=O6wlwlXcoiBZUikVNh2cczhin5d)》,刷机完成,按S2重启系统。
|
||||
|
||||
## 拨码开关
|
||||
|
||||
对照实物图,拨码开关功能由 SW1 进行控制。通过拨动 SW1 可使得开发板以下面两种模式启动:
|
||||
|
||||
- NAS 模式:如图所示放置 MUSE N1 开发板,SW1 三个子键全部往上拨为 NAS 模式。
|
||||
|
||||

|
||||
|
||||
- 快速U盘模式:如图所示放置 MUSE N1 开发板,SW1 三个子键全部往下拨为快速U盘模式。
|
||||
|
||||

|
||||
Refer to [MUSE N1](https://bianbu.spacemit.com/en/bianbu-nas/device_list/muse_n1/)
|
||||
|
|
|
@ -4,34 +4,4 @@ sidebar_position: 2
|
|||
|
||||
# MUSE Pi
|
||||
|
||||
## 概述
|
||||
|
||||
MUSE Pi 开发板板型:
|
||||
|
||||
- MUSE Pi 开发板采用 K1 芯片,集成8核 X60,符合 RISC-V 64GCVB 和 RVA22 标准设计
|
||||
- 存储采用 LPDDR4X 4266 SDRAM 8GB/16GB 和 EMMC 32GB/64GB
|
||||
- 电源:TypeC 接口支持 USB2.0 OTG 数据传输,支持 PD3.0 协议输入(12V)
|
||||
- Ethernet:支持2路 RJ45 接口 1000M 以太网
|
||||
- HDMI:支持 HDMI1.4 接口,最大可输出 1920x1080@60Hz
|
||||
- 卡启动:支持 TF 卡扩展存储,可用作系统启动存储,支持高速数据传输模式
|
||||
- 蓝牙:支持蓝牙5.0标准及低功耗模式(BLE)
|
||||
- Wi-Fi:支持双频(2.4GHz 和 5GHz)的 802.11ax Wi-Fi 无线网络连接
|
||||
- MIPI DSI:支持 4lane MIPI DSI 接口,最大可输出 1920x1080@60Hz
|
||||
- MIPI CSI:支持 2x4-lane MIPI CSI,支持 4lane+4lane 或 4lane+2lane+2lane 组合
|
||||
- PCIe:支持2路 PCIe x2,提供 10Gbps 通讯速率,快速扩展
|
||||
- 音频:支持立体声喇叭、耳机输出及双 MIC 录音
|
||||
- GPIO:兼容树莓派标准 26pin 接口
|
||||
- USB:支持1路 USB3.0 DRD,1路 USB2.0 Host
|
||||
|
||||
## 实物图
|
||||
|
||||

|
||||
|
||||
## 刷机模式
|
||||
|
||||
对照实物图,进行下述操作:
|
||||
|
||||
- USB线一端连接板子Type-C口,一端连接PC。长按 SW2 键不松手,然后按下SW4 REST键进入刷机模式
|
||||
|
||||
刷机工具使用参考《 [刷机工具使用手册](https://developer.spacemit.com/#/documentation?token=O6wlwlXcoiBZUikVNh2cczhin5d)》,刷机完成,按SW4 重启系统。
|
||||
|
||||
Refer to [MUSE N1](https://bianbu.spacemit.com/en/bianbu-nas/device_list/muse_pi)
|
||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 1.6 MiB |
Binary file not shown.
Before Width: | Height: | Size: 829 KiB |
Binary file not shown.
Before Width: | Height: | Size: 909 KiB |
Binary file not shown.
Before Width: | Height: | Size: 3 MiB |
Loading…
Add table
Reference in a new issue