rusefi
/
rusefi_documentation
mirror of https://github.com/rusefi/rusefi_documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Developing On Linux (markdown)

This commit is contained in:
Scott Smith 2021-11-19 15:13:01 -08:00
parent 8bde777bd9
commit 720702ae84
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Developing-On-Linux.md
View File

@ -43,7 +43,12 @@ https://github.com/xpack-dev-tools/openocd-xpack/releases
To get started, plug the ST-Link side of the dev board into your computer. Generally this should power the whole board.
OpenOCD can be left running in the background while you develop in other windows. It will provide a GDB server, a telnet connection for issuing commands, and a TCL interface. We'll just ignore the last one for now.
OpenOCD can be left running in the background while you develop in other windows. It will provide a GDB server, a telnet connection for issuing commands, and a TCL interface. We'll just ignore the last one for now. To start OpenOCD, you need to pass in a board configuration file. Luckily they exist for most any off the shelf board you care about.
```
sudo ~/openocd/xpack-openocd-0.11.0-2/bin/openocd -f ~/openocd/xpack-openocd-0.11.0-2/scripts/board/st_nucleo_h743zi.cfg
```
Adjust as necessary; you may need `sudo` if you don't normally have access to USB devices.
To reprogram, simply do:
```
@ -51,6 +56,10 @@ telnet localhost 4444
program build/rusefi.elf reset
exit
```
Or, if you prefer a one-liner:
```
(echo "program build/rusefi.elf reset"; echo exit) | nc localhost 4444
```
Conveniently, OpenOCD will retain a history of commands, allowing you to use up-arrows to retrieve previous commands.
On a nucleo-h743, I don't seem to get much indication this worked, but if you connect via gdb: