unleashed-firmware/.vscode
hedger 241b4ef6e4
[FL-3299] furi_crash: added C2 status; added fw-version gdb command (#2638)
* furi_crash: added C2 status
* debug: Added "fw-version" gdb command; vscode: updated configuration to use new command
* debug: added fw-info command to debug_other session
* Toolbox: versioned structure for Version
* debug: fw-version: no longer needs an ELF file loaded
* debug: flipperversion: removed unused variable
* debug_other: print running fw version

Co-authored-by: Aleksandr Kutuzov <alleteam@gmail.com>
2023-05-09 07:31:39 +09:00
..
example [FL-3299] furi_crash: added C2 status; added fw-version gdb command (#2638) 2023-05-09 07:31:39 +09:00
.gitignore vscode: initial development configuration (#1520) 2022-08-04 01:32:31 +09:00
extensions.json [FL-3300] API version in UI (#2649) 2023-05-08 20:11:23 +09:00
ReadMe.md [FL-2059] Storage fixes for handling empty files (#1563) 2022-08-10 00:57:11 +09:00

Visual Studio Code workspace for Flipper Zero

Setup

  • To start developing with VSCode, run ./fbt vscode_dist in project root. That should only be done once
  • After that, open firmware folder in VSCode: "File" > "Open folder"

For more details on fbt, see fbt docs.

Workflow

Commands for building firmware are invoked through Build menu: Ctrl+Shift+B.

To attach a debugging session, first build and flash firmware, then choose your debug probe in Debug menu (Ctrl+Shift+D).

Note that you have to detach debugging session before rebuilding and re-flashing firmware.