I have had the board for a few days, and I am recording some of the problems I encountered when I first started learning how to use it.
As soon as I got it, I powered on and ran the built-in buildroot system directly, but buildroot is not easy to play, I have to do everything myself. I changed to the official Ubuntu image, emm... How to say it, after all, it is still an A7 chip, it is too difficult for it, Ubuntu is not working well.
Fortunately, I saw a post in the tutorial about porting alpine shared by a big guy, so I followed it decisively and customized my own alphine system, which retained the simplicity of buildroot and had the package manager of Ubuntu.
1 : The build image directory cannot be burned using Rockchip's tool, and it says that oem.img cannot be found.
After searching the forum, I found that the official mentioned that WSL compiled and downloaded the firmware and prompted that oem.img did not exist - Luckfox Forums . The image compiled under the wsl environment will have problems when burning. The reason is that oem.img rootfs.img, etc. are soft links, only 1KB in size, and cannot be successfully burned in.
Use the official script to change the soft link object to the actual object.
#!/bin/bash
files=("output/image/oem.img"
"output/image/rootfs.img"
"output/image/userdata.img")
for file in "${files[@]}"; do
if [ -e "$file" ]; then
filename=$(basename "$file")
target=$(readlink -f "$file")
rm "$file"
mv "$target" "output/image/$filename"
echo "文件 '$filename' 已删除并重命名为 '$filename'"
else
echo "文件 '$file' 不存在"
fi
done
2: After startup, the 64M memory is actually only about 30M
Because the default configuration is for the camera, if you don't need the camera, go to your configuration file and change RK_BOOTARGS_CMA_SIZE to a smaller size. For example, mine is:
3.Nand boot method, rootfs space is too small, it is full without doing anything
Although nand has 128M, the official allocation is 10M for userdata and 30M for oem, which wastes 40M of space. Just kill it (I don’t know what the function of this oem partition is yet, please tell me if anyone knows)
4. When the kernel is compiled, the modules are not exported to /lib/modules
The official SDK is exported to OEM by default. I don't know why this is done. This also makes it impossible to load the driver directly through modprobe. You must manually go to the directory to insmod, and there is no way to automatically load the dependencies.
The make file in the sysdv directory is used to compile kernel, uboot, and rootfs. Here, we modify the kernel compilation part to make it compile the kernel and export the modules to the directory we specify (this directory is determined by ourselves, and it will be used when packaging the root file system later):
$(MAKE) -C $(KERNEL_DIR) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) INSTALL_MOD_PATH=$(KERNEL_DIR)/out/modules_install modules_install
5. Package the alpine root file system
For specific production methods, please refer to the official document: Alpine Linux Porting (2) | LUCKFOX WIKI
Here we assume that the alpine.tar.gz file has been successfully created and placed under sysdrv/source/alpine/
First, modify the makefile and remove the rootfs of the all project, which is the one packaged by default. Because we want to use our own rootfs instead of the official one, there is no need to package the rootfs to save time:
Then go to the configuration file BoardConfig-SPI_NAND-Buildroot-RV1103_Luckfox_Pico_Mini_B-IPC.mk and add an item:
# 配置自定义镜像目录
export RK_CUSTOM_ROOTFS=../sysdrv/source/alpine/alpine.tar.gz
The next step is to modify the packaging part in build.sh:
The entire packaging process is as follows:
1. Check whether there is a RK_CUSTOM_ROOTFS variable defined above. If so, it means that your own custom root file system is used.
2. Unzip the root file system
3. Copy the firmware and the modules exported above to the file system
4. Repackage into img image
6. WiFi support
The USB WiFi driver is not working yet (mainly due to insufficient voltage, try again when you have time)
sdio wifi, also refer to the official tutorial: [RV1103] RTL8723bs (SD card shape module) driver development - CSDN blog
But to be honest, that article is a bit complicated, and the configurations in it are mixed with a lot of the author's own configurations that have nothing to do with wifi, which makes it a bit confusing.
Taking the r8723bs sdio wifi module as an example, first activate 8723bs in the kernel configuration.
For more information on how to configure, please refer to the official example: Kernel Configuration | LUCKFOX WIKI , or simply modify the config file and add the following options:
Because 8723 uses sdio, the default kernel does not support sdio for sdmmc. You need to manually modify the device tree. You only need to add a sdio_pwrseq node and modify the function of sdmmc:
提升卡
变色卡
千斤顶
京公网安备 11010802033920号
