Vscode Block Comment Mac
General
Tutorials
Interfaces & Protocols
API Reference
ODrive
Can
•Config
•Error
•Protocol
•Endpoint
Axis
•LockinConfig
Config
•CalibrationLockin
•Error
•LockinState
•AxisState
•ThermistorCurrentLimiter
OnboardThermistorCurrentLimiter
•Config
OffboardThermistorCurrentLimiter
•Config
Motor
•CurrentControl
•GateDriver
•TimingLog
•Config
•Error
•ArmedState
•MotorType
Controller
Config
•Anticogging
•Error
•ControlMode
•InputMode
Encoder
•Config
•Error
•Mode
SensorlessEstimator
•Config
•Error
TrapezoidalTrajectory
•Config
Endstop
•Config
SystemStats
•Usb
•I2C
•Config
For ODrive Developers
Component Guides
Search extensions for: baerkins.acf-snippets-vscode; VS Code Marketplace link; Auto Comment Blocks. You can easily insert multi-line comments. Just type /. + Enter and you’re good to go. Search extensions for: kevinkyang.auto-comment-blocks; VS Code Marketplace link. I just updated my VSCode to the version you mentioned. The combinations work exactly as you described. It must be something that was changed on your computer. Go to File = Preferences = Keyboard Shortcuts (Or press CTRL + K and then CTRL + S) look for Remove Line Comment. In my settings it still says.
Help improve these docs: submit edits using the link in the top right.
If you need help, please search or ask the ODrive Community.
VSCode is the recommended IDE for working with the ODrive codebase. It is a light-weight text editor with Git integration and GDB debugging functionality.
Visual Studio Code Tips and Tricks 'Tips and Tricks' lets you jump right in and learn how to be productive with Visual Studio Code. You'll become familiar with its powerful editing, code intelligence, and source code control features and learn useful keyboard shortcuts. Type: Debugger Describe the bug OS and Version: Windows 10 2004 VS Code Version:1.47.3 C/C Extension Version: 0.29.0 A clear and concise description of what the bug is. How do disable messages.
Before doing the VSCode setup, make sure you’ve installed all of your prerequisites
Setup Procedure
- Clone the ODrive repository
- Open VSCode
- Install extensions. This can be done directly from VSCode (Ctrl+Shift+X)
- Required extensions:
- C/C++
ext install ms-vscode.cpptools
- Cortex-Debug
ext install marus25.cortex-debug
- Cortex-Debug: Device Support Pack - STM32F4
ext install marus25.cortex-debug-dp-stm32f4
- C/C++
- Recommended Extensions:
- Include Autocomplete
- Path Autocomplete
- Auto Comment Blocks
- Required extensions:
- Create an environment variable named
ARM_GCC_ROOT
whose value is the location of theGNU Arm Embedded Toolchain
(.e.gC:Program Files (x86)GNU Tools Arm Embedded7 2018-q2-update
) that you installed in the prerequisites section of the developer’s guide. This is not strictly needed for Linux or Mac, and you can alternatively use theCortex-debug: Arm Toolchain Path
setting in VSCode extension settings. - Relaunch VSCode
- Open the VSCode Workspace file, which is located in the root of the ODrive repository. It is called
ODrive_Workspace.code-workspace
. The first time you open it, VSCode will install some dependencies. If it fails, you may need to change your proxy settings.
You should now be ready to compile and test the ODrive project.
Building the Firmware
- Terminal -> Run Build Task (Ctrl+Shift+B)
A terminal window will open with your native shell. VSCode is configured to run the command make -j4
in this terminal.
Flashing the Firmware
- Terminal -> Run Task -> flash
A terminal window will open with your native shell. VSCode is configured to run the command make flash
in this terminal.
If the flashing worked, you can connect to the board using the odrivetool.
Debugging
An extension called Cortex-Debug has recently been released which is designed specifically for debugging ARM Cortex projects. You can read more on Cortex-Debug here: https://github.com/Marus/cortex-debug
Note: If developing on Windows, you should have arm-none-eabi-gdb
and openOCD
on your PATH.
Vscode Block Comment Machine
- Make sure you have the Firmware folder as your active folder
- Set
CONFIG_DEBUG=true
in the tup.config file - Flash the board with the newest code (starting debug session doesn’t do this)
- In the Run tab (Ctrl+Shift+D), select “Debug ODrive (Firmware)”
- Press Start Debugging (or press F5)
- The processor will reset and halt.
- Set your breakpoints. Note: you can only set breakpoints when the processor is halted, if you set them during run mode, they won’t get applied.
- Continue (F5)
- Stepping over/in/out, restarting, and changing breakpoints can be done by first pressing the “pause” (F6) button at the top the screen.
- When done debugging, simply stop (Shift+F5) the debugger. It will kill your openOCD process too.
Cleaning the Build
Vscode Comment Block Macos
This sometimes needs to be done if you change branches.
Vscode Block Comment Mac Download
- Open a terminal (View -> Integrated Terminal) and enter
make clean