DarkFlippers/unleashed-firmware
1
1
Fork 0
mirror of https://github.com/DarkFlippers/unleashed-firmware.git synced 2024-12-20 20:01:54 +03:00
Code Issues Projects Releases Wiki Activity
6c768f2019
unleashed-firmware/.vscode
History
hedger 224d0aefe4
[FL-2733] multitarget support for fbt (#2209) 
* First part of multitarget porting
* Delete firmware/targets/f7/Inc directory
* Delete firmware/targets/f7/Src directory
* gpio: cli fixes; about: using version from HAL
* sdk: path fixes
* gui: include fixes
* applications: more include fixes
* gpio: ported to new apis
* hal: introduced furi_hal_target_hw.h; libs: added one_wire
* hal: f18 target
* github: also build f18 by default
* typo fix
* fbt: removed extra checks on app list
* api: explicitly bundling select mlib headers with sdk
* hal: f18: changed INPUT_DEBOUNCE_TICKS to match f7
* cleaned up commented out code
* docs: added info on hw targets
* docs: targets: formatting fixes
* f18: fixed link error
* f18: fixed API version to match f7
* docs: hardware: minor wording fixes
* faploader: added fw target check
* docs: typo fixes
* github: not building komi target by default
* fbt: support for `targets` field for built-in apps
* github: reworked build flow to exclude app_set; fbt: removed komi-specific appset; added additional target buildset check
* github: fixed build; nfc: fixed pvs warnings
* attempt to fix target id
* f7, f18: removed certain HAL function from public API
* apps: debug: enabled bt_debug_app for f18
* Targets: backport input pins configuration routine from F7 to F18

Co-authored-by: Aleksandr Kutuzov <alleteam@gmail.com>
2023-02-08 01:33:05 +09:00
..
example [FL-3080] fbt: PVS support (#2286) 2023-01-17 15:55:49 +03:00
.gitignore vscode: initial development configuration (#1520) 2022-08-04 01:32:31 +09:00
extensions.json [FL-2733] multitarget support for fbt (#2209) 2023-02-08 01:33:05 +09:00
ReadMe.md [FL-2059] Storage fixes for handling empty files (#1563) 2022-08-10 00:57:11 +09:00

ReadMe.md

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.