Loading README.md +1 −5 Original line number Diff line number Diff line Loading @@ -60,10 +60,6 @@ west build -b robomaster_board_c samples/motor/dji_m3508_demo A sample debug configuration is also provided. To apply it, run the following command: ```shell west build -b $BOARD samples/motor/dji_m3508_demo ``` Once you have built the application, run the following command to flash it: ```shell Loading @@ -88,7 +84,7 @@ The OpenOCD (On-Chip Debugger) project conveniently provides a rules file that d 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 sudo cp ~/zephyr-sdk-*/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: Loading Loading
README.md +1 −5 Original line number Diff line number Diff line Loading @@ -60,10 +60,6 @@ west build -b robomaster_board_c samples/motor/dji_m3508_demo A sample debug configuration is also provided. To apply it, run the following command: ```shell west build -b $BOARD samples/motor/dji_m3508_demo ``` Once you have built the application, run the following command to flash it: ```shell Loading @@ -88,7 +84,7 @@ The OpenOCD (On-Chip Debugger) project conveniently provides a rules file that d 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 sudo cp ~/zephyr-sdk-*/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: Loading
