Commit a2638a9e authored by Wenxi XU's avatar Wenxi XU
Browse files

Update file README.md

parent 75e543c0
Loading
Loading
Loading
Loading
+18 −0
Original line number Diff line number Diff line
@@ -78,6 +78,24 @@ Then you can have your motors running!

详细的文档请参考`Documents`文件夹

### 常见问题
如果flash时提示找不到compatible CMSIS_DAP device, 参照以下做法: 
Flashing a board requires permission to directly access the board hardware, usually managed by installation of the flashing tools. On Linux systems, if the west flash command fails, you likely need to define udev rules to grant the needed access permission.

Udev is a device manager for the Linux kernel and the udev daemon handles all user space events raised when a hardware device is added (or removed) from the system. We can add a rules file to grant access permission by non-root users to certain USB-connected devices.

The OpenOCD (On-Chip Debugger) project conveniently provides a rules file that defined board-specific rules for most Zephyr-supported arm-based boards, so we recommend installing this rules file by downloading it from their sourceforge repo, or if you’ve installed the Zephyr SDK there is a copy of this rules file in the SDK folder:

copy the rules file from the Zephyr SDK folder:
```shell
sudo cp ${ZEPHYR_SDK_INSTALL_DIR}/sysroots/x86_64-pokysdk-linux/usr/share/openocd/contrib/60-openocd.rules /etc/udev/rules.d
```
Then, ask the udev daemon to reload these rules:

sudo udevadm control --reload

Unplug and plug in the USB connection to your board, and you should have permission to access the board hardware for flashing. Check your board-specific documentation (Supported Boards and Shields) for further information if needed.

```
好无聊逗逗梅总吧
    嘬嘬嘬𐃆 ˒˒ ͏