Milk-V Duo is an ultra-compact embedded development platform based on the CV1800B chip. It can run Linux and RTOS, providing a reliable, low-cost, and high-performance platform for professionals, industrial ODMs, AIoT enthusiasts, DIY hobbyists, and creators.
- CPU: CVITEK CV1800B (C906@1Ghz + C906@700MHz)
- Dual RV64 Core up to 1GHz
- 64MB RAM
- Provides 10/100Mbps Ethernet via optional add-on board
├── build // compilation scripts and board configs
├── build.sh // one-click compilation script
├── buildroot-2021.05 // buildroot source code
├── freertos // freertos system
├── fsbl // fsbl firmware in prebuilt form
├── install // temporary images stored here
├── isp_tuning // camera effect parameters
├── linux_5.10 // linux kernel
├── middleware // self-developed multimedia framework
├── device // configuration files for milkv
├── opensbi // opensbi library
├── out // final image for SD card
├── ramdisk // prebuilt ramdisk
└── u-boot-2021.10 // u-boot source code
Tip
For the compilation and use methods of the SDK, you can also go to our official documentation for better information and eading experience. In addition, our official documentation website is also open source. If you are interested in enriching the content of the documentation or translating it into other languages, you can go to this repository submit your PR, and we will give out exquisite gifts to contributors from time to time.
Prepare the Compilation Environment. Using a local Ubuntu system, the officially supported compilation environment is Ubuntu Jammy 22.04.x amd64 only!
If you are using other Linux distributions, we strongly recommend that you use the Docker environment to compile to reduce the probability of compilation errors.
The following describes the compilation methods in the two environments.
Install the packages that compile dependencies:
sudo apt install -y pkg-config build-essential ninja-build automake autoconf libtool wget curl git gcc libssl-dev bc slib squashfs-tools android-sdk-libsparse-utils jq python3-distutils scons parallel tree python3-dev python3-pip device-tree-compiler ssh cpio fakeroot libncurses5 flex bison libncurses5-dev genext2fs rsync unzip dosfstools mtools tcl openssh-client cmake expect libconfuse2git clone https://github.com/milkv-duo/duo-buildroot-sdk.git --depth=1Execute one-click compilation script build.sh：
cd duo-buildroot-sdk/
./build.shYou will see tips on how to use the compiled script:
# ./build.sh
Usage:
./build.sh - Show this menu
./build.sh lunch - Select a board to build
./build.sh [board] - Build [board] directly, supported boards as follows:
milkv-duo-sd
milkv-duo-spinand
milkv-duo-spinor
milkv-duo256m-sd
milkv-duo256m-spinand
milkv-duo256m-spinor
milkv-duos-emmc
milkv-duos-sdListed at the bottom is the list of currently supported target versions.
As shown in the prompt, there are two ways to compile the target version.
The first method is to execute ./build.sh lunch to bring up the interactive menu, select the version number to be compiled, and press Enter:
# ./build.sh lunch
Select a target to build:
1. milkv-duo-sd
2. milkv-duo-spinand
3. milkv-duo-spinor
4. milkv-duo256m-sd
5. milkv-duo256m-spinand
6. milkv-duo256m-spinor
7. milkv-duos-emmc
8. milkv-duos-sd
Which would you like:The second method is to put the name of the target version after the script and compile it directly. For example, if you need to compile the image of milkv-duo, the command is as follows:
# ./build.sh milkv-duoAfter a successful compilation, you can find the generated SD card burning image milkv-duo-*-*.img in the out directory.
Note: The first compilation will automatically download the required toolchain, which is approximately 840MB in size. Once downloaded, it will be automatically extracted to the host-tools directory in the SDK directory. For subsequent compilations, if the host-tools directory is detected, the download will not be performed again.
If you have not executed the one-click compilation script, you need to manually download the toolchain host-tools and extract it to the SDK root directory:
tar -xf host-tools.tar.gz -C /your/sdk/path/Then enter the following commands in sequence to complete the step-by-step compilation. Replace [board] and [config] in the command with the version that needs to be compiled. The currently supported board and corresponding config are as follows:
milkv-duo256m-sd cv1812cp_milkv_duo256m_sd
milkv-duo256m-spinand cv1812cp_milkv_duo256m_spinand
milkv-duo256m-spinor cv1812cp_milkv_duo256m_spinor
milkv-duo-sd cv1800b_milkv_duo_sd
milkv-duos-emmc cv1813h_milkv_duos_emmc
milkv-duo-spinand cv1800b_milkv_duo_spinand
milkv-duo-spinor milkv-duo-spinor
milkv-duos-sd cv1813h_milkv_duos_sd
source device/[board]/boardconfig.sh
source build/milkvsetup.sh
defconfig [config]
clean_all
build_all
pack_sd_imageFor example, if you need to compile the image of milkv-duo, the step-by-step compilation command is as follows:
source device/milkv-duo/boardconfig.sh
source build/milkvsetup.sh
defconfig cv1800b_milkv_duo_sd
clean_all
build_all
pack_sd_imageGenerated firmware location:
Duo: install/soc_cv1800b_milkv_duo_sd/[board].img
Duo256M: install/soc_cv1812cp_milkv_duo256m_sd/[board].img
Duos: install/soc_cv1813cp_milkv_duos_sd/[board].img
Docker support is required on hosts running Linux systems. For how to use Docker, please refer to the official documentation or other tutorials.
We put the SDK source code on the Linux host system and call the Docker image environment provided by Milk-V to compile it.
git clone https://github.com/milkv-duo/duo-buildroot-sdk.git --depth=1cd duo-buildroot-sdkdocker run -itd --name duodocker -v $(pwd):/home/work milkvtech/milkv-duo:latest /bin/bashDescription of some parameters in the command:
duodockerDocker name, you can use the name you want to use.$(pwd)The current directory, here is the duo-buildroot-sdk directory that was 'cd' to in the previous step.-v $(pwd):/home/workBind the current code directory to the /home/work directory in the Docker image.milkvtech/milkv-duo:latestThe Docker image provided by Milk-V will be automatically downloaded from hub.docker.com for the first time.
After Docker runs successfully, you can use the docker ps -a command to view the running status:
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8edea33c2239 milkvtech/milkv-duo:latest "/bin/bash" 2 hours ago Up 2 hours duodockerdocker exec -it duodocker /bin/bash -c "cd /home/work && cat /etc/issue && ./build.sh [board]"Note that the ./build.sh [board] at the end of the command is the same as the previous usage in the one-click compilation instructions in Ubuntu 22.04. Use ./build.sh can see how to use the command, use ./ build.sh lunch can bring up the interactive selection menu, use ./build.sh [board] to directly compile the target version, [board] can be replaced with:
milkv-duo-sd
milkv-duo-spinand
milkv-duo-spinor
milkv-duo256m-sd
milkv-duo256m-spinand
milkv-duo256m-spinor
milkv-duos-emmc
milkv-duos-sd
Description of some parameters in the command:
duodockerThe name of the running Docker must be consistent with the name set in the previous step."*"In quotes is the shell command to be run in the Docker image.cd /home/workSwitch to the /home/work directory. Since this directory has been bound to the host's code directory during runtime, the /home/work directory in Docker is the source code directory of the SDK.cat /etc/issueDisplays the version number of the image used by Docker. It is currently Ubuntu 22.04.3 LTS and is used for debugging../build.sh [board]Execute one-click compilation script.
For example, if you need to compile the image of milkv-duo, the command is as follows:
docker exec -it duodocker /bin/bash -c "cd /home/work && cat /etc/issue && ./build.sh milkv-duo"After successful compilation, you can see the generated SD card burning image [board]-*-*.img in the out directory.
If you have not executed the one-click compilation script, you need to manually download the toolchain host-tools and extract it to the SDK root directory:
tar -xf host-tools.tar.gz -C /your/sdk/path/Step-by-step compilation requires logging into Docker to operate. Use the command docker ps -a to view and record the ID number of the container, such as 8edea33c2239.
Enter Docker:
docker exec -it 8edea33c2239 /bin/bashEnter the code directory bound in Docker：
root@8edea33c2239:/# cd /home/work/Then enter the following commands in sequence to complete the step-by-step compilation. Replace [board] and [config] in the command with the version that needs to be compiled. The currently supported board and corresponding config are as follows:
milkv-duo256m-sd cv1812cp_milkv_duo256m_sd
milkv-duo256m-spinand cv1812cp_milkv_duo256m_spinand
milkv-duo256m-spinor cv1812cp_milkv_duo256m_spinor
milkv-duo-sd cv1800b_milkv_duo_sd
milkv-duos-emmc cv1813h_milkv_duos_emmc
milkv-duo-spinand cv1800b_milkv_duo_spinand
milkv-duo-spinor milkv-duo-spinor
milkv-duos-sd cv1813h_milkv_duos_sd
source device/[board]/boardconfig.sh
source build/milkvsetup.sh
defconfig [config]
clean_all
build_all
pack_sd_imageFor example, if you need to compile the image of milkv-duo, the step-by-step compilation command is as follows:
source device/milkv-duo/boardconfig.sh
source build/milkvsetup.sh
defconfig cv1800b_milkv_duo_sd
clean_all
build_all
pack_sd_imageGenerated firmware location:
Duo: install/soc_cv1800b_milkv_duo_sd/[board].img
Duo256M: install/soc_cv1812cp_milkv_duo256m_sd/[board].img
Duos: install/soc_cv1813cp_milkv_duos_sd/[board].img
Generated firmware location: install/soc_cv1800b_milkv_duo_sd/milkv-duo.img.
After compilation is completed, you can use the exit command to exit the Docker environment:
root@8edea33c2239:/home/work# exitThe generated firmware can also be seen in the host code directory.
After compilation is completed, if the above Docker running environment is no longer needed, you can stop it first and then delete it:
docker stop 8edea33c2239
docker rm 8edea33c2239If you want to try to compile this SDK in an environment other than the above two environments, the following are things you may need to pay attention to, for reference only.
Note：cmake minimum version requirement is 3.16.5.
Check the version of cmake in the system:
cmake --versionFor example, the version of cmake installed using apt in the Ubuntu 20.04 is:
cmake version 3.16.3
The minimum requirement of this SDK is not met. Manual installation of the latest version 3.27.6 is needed:
wget https://github.com/Kitware/CMake/releases/download/v3.27.6/cmake-3.27.6-linux-x86_64.sh
chmod +x cmake-3.27.6-linux-x86_64.sh
sudo sh cmake-3.27.6-linux-x86_64.sh --skip-license --prefix=/usr/local/When manually installed, cmake is located in /usr/local/bin. To check its version, use the command cmake --version, which should display:
cmake version 3.27.6
If you wish to perform the compilation with WSL, there's an small issue building the image. The $PATH, due Windows interoperability, has Windows environment variables which include some spaces between the paths.
To solve this problem you need to change the /etc/wsl.conf file and add the following lines:
[interop]
appendWindowsPath = false
After that, you need to reboot the WSL with wsl.exe --reboot. Then you able to run the ./build.sh script or the build_all line in the step-by-step compilation method.
To rollback this change in /etc/wsl.conf file set appendWindowsPath as true. To reboot the WSL, can you use the Windows PowerShell command wsl.exe --shutdown then wsl.exe, after that the Windows environment variables become avaliable again in $PATH.
Note: Writing the image to the microSD card will erase the existing data on the card. Remember to back up important data before burning!!!
- To write the generated image to a microSD card on Windows, you can use tools like
balenaEtcher,Rufus, orWin32 Disk Imager. - To write the generated image to a microSD card on Linux, use the
ddcommand. Please make sure to carefully confirm that theofdevice/dev/sdXcorresponds to the microSD card you want to burn:sudo dd if=milkv-duo-*-*.img of=/dev/sdX conv=fsync status=progress
- Insert the microSD card into the microSD card slot of the Milk-V Duo.
- Connect the serial cable (optional).
- Power on, the Duo will boot up and enter the system normally.
- If a serial cable is connected, you can view the boot logs in the serial console (
mobarXterm,Xshellor others). After entering the system, you can use the serial console to log in to the terminal and execute relevant Linux commands.
- Using a serial cable.
- Using a USB network (CDC-NCM).
- Using the Ethernet interface (requires the IO-Board).
The username and password for logging into the Duo terminal are as follows:
root
milkv
If you want to disable the LED blinking feature on the Duo, you can execute the following command in the Duo terminal:
mv /mnt/system/blink.sh /mnt/system/blink.sh_backup && syncThis means renaming the LED blinking script, and after restarting the Duo, the LED will no longer blink.
If you want to restore LED blinking, rename it back to its original name and restart the device:
mv /mnt/system/blink.sh_backup /mnt/system/blink.sh && syncNote that when using the IO-Board, the USB network (CDC-NCM) is not available, Please use the Ethernet interface on the IO-Board.
If you need to assign a fixed MAC address to the Ethernet port of the IO-Board, please execute the following command(Replace the MAC address in the command with the MAC address you want to set, and please note that MAC addresses of different devices within the same network segment must not be duplicated):
echo "pre-up ifconfig eth0 hw ether 78:01:B3:FC:E8:55" >> /etc/network/interfacesthen reboot the board.
Enable the 4 USB ports on the IO-Board:
ln -sf /mnt/system/usb-host.sh /mnt/system/usb.sh
syncthen reboot the board.
For example, if a USB flash drive is connected to the USB port on the IO-Board, you can use the command ls /dev/sd* to check if the device is detected.
To mount the USB drive and view its contents in the system (taking /dev/sda1 as an example):
mkdir /mnt/udisk
mount /dev/sda1 /mnt/udiskVerify if the contents in the /mnt/udisk directory match the expectations:
ls /mnt/udiskThe command to unmount a USB flash drive:
umount /mnt/udiskTo restore the functionality of the USB network (CDC-NCM) when not using the IO-Board, you can follow these steps:
ln -sf /mnt/system/usb-ncm.sh /mnt/system/usb.sh
syncthen reboot the board.
-
Why is only a single core being displayed?
The CV1800B chip adopts a dual-core design. Currently, the Linux system runs on one of the cores, while the other core is used for running a real-time system. For the use of this core, please see official documentation.
-
Why does it only show 28M when viewing the RAM?
Because a portion of the RAM is allocated to ION, which is the memory used when running algorithms with the camera. If you're not using the camera, you can modify the value of this ION_SIZE to 0 and then recompile to generate the image(Duo 256M: ION_SIZE).
- CV181x/CV180x MMF SDK Development Documents (English and Chinese): MultiMedia Framework Software Development Document.
- CV Series Chip TPU SDK Development Documentation Compilation (Chinese): CV series chip TPU SDK development data summary.
