777a4d109d
* Threads: application id * Unit tests: appsdata getter test * Unit tests: moar test cases for appsdata getter * Unit tests: remove folders after test * Storage: dir_is_exist, migrate, + unit_tests * Plugins: migration * Storage: common_exists, moar unit_tests 4 "common_migrate", "common_migrate" and "common_merge" bugfixes * Storage: use FuriString for path handling * Storage API: send caller thread id with path * Storage: remove StorageType field in storage file list * Storage: simplify processing * Storage API: send caller thread id with path everywhere * Storage: /app alias, unit tests and path creation * Storage, path helper: remove unused * Examples: app data example * App plugins: use new VFS path * Storage: file_info_is_dir * Services: handle alias if the service accepts a path. * App plugins: fixes * Make PVS happy * Storage: fix storage_merge_recursive * Storage: rename process_aliases to resolve_path. Rename APPS_DATA to APP_DATA. * Apps: use predefined macro instead of raw paths. Example Apps Data: README fixes. * Storage: rename storage_common_resolve_path to storage_common_resolve_path_and_ensure_app_directory * Api: fix version * Storage: rename alias message * Storage: do not create app folders in path resolving process in certain cases. --------- Co-authored-by: Astra <93453568+Astrrra@users.noreply.github.com> Co-authored-by: Aleksandr Kutuzov <alleteam@gmail.com> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| applications | ||
| applications_user | ||
| assets | ||
| debug | ||
| documentation | ||
| firmware | ||
| furi | ||
| lib | ||
| scripts | ||
| site_scons | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .pvsconfig | ||
| .pvsoptions | ||
| CODE_OF_CONDUCT.md | ||
| CODING_STYLE.md | ||
| CONTRIBUTING.md | ||
| fbt | ||
| fbt_options.py | ||
| fbt.cmd | ||
| firmware.scons | ||
| LICENSE | ||
| ReadMe.md | ||
| SConstruct | ||
Flipper Zero Firmware
- Flipper Zero Official Website. A simple way to explain to your friends what Flipper Zero can do.
- Flipper Zero Firmware Update. Improvements for your dolphin: latest firmware releases, upgrade tools for PC and mobile devices.
- User Documentation. Learn more about your dolphin: specs, usage guides, and anything you want to ask.
Contributing
Our main goal is to build a healthy and sustainable community around Flipper, so we're open to any new ideas and contributions. We also have some rules and taboos here, so please read this page and our Code of Conduct carefully.
I need help
The best place to search for answers is our User Documentation. If you can't find the answer there, check our Discord Server or our Forum.
I want to report an issue
If you've found an issue and want to report it, please check our Issues page. Make sure the description contains information about the firmware version you're using, your platform, and a clear explanation of the steps to reproduce the issue.
I want to contribute code
Before opening a PR, please confirm that your changes must be contained in the firmware. Many ideas can easily be implemented as external applications and published in the Flipper Application Catalog (coming soon). If you are unsure, reach out to us on the Discord Server or the Issues page, and we'll help you find the right place for your code.
Also, please read our Contribution Guide and our Coding Style, and make sure your code is compatible with our Project License.
Finally, open a Pull Request and make sure that CI/CD statuses are all green.
Development
Flipper Zero Firmware is written in C, with some bits and pieces written in C++ and armv7m assembly languages. An intermediate level of C knowledge is recommended for comfortable programming. C, C++, and armv7m assembly languages are supported for Flipper applications.
Requirements
Supported development platforms:
- Windows 10+ with PowerShell and Git (x86_64)
- macOS 12+ with Command Line tools (x86_64, arm64)
- Ubuntu 20.04+ with build-essential and Git (x86_64)
Supported in-circuit debuggers (optional but highly recommended):
- Flipper Zero Wi-Fi Development Board
- ST-Link
- J-Link
Flipper Build System will take care of all the other dependencies.
Cloning source code
Make sure you have enough space and clone the source code:
git clone --recursive https://github.com/flipperdevices/flipperzero-firmware.git
Building
Build firmware using Flipper Build Tool:
./fbt
Flashing firmware using an in-circuit debugger
Connect your in-circuit debugger to your Flipper and flash firmware using Flipper Build Tool:
./fbt flash
Flashing firmware using USB
Make sure your Flipper is on, and your firmware is functioning. Connect your Flipper with a USB cable and flash firmware using Flipper Build Tool:
./fbt flash_usb
Documentation
- Flipper Build Tool - building, flashing, and debugging Flipper software
- Applications, Application Manifest - developing, building, deploying, and debugging Flipper applications
- Hardware combos and Un-bricking - recovering your Flipper from the most nasty situations
- Flipper File Formats - everything about how Flipper stores your data and how you can work with it
- Universal Remotes - contributing your infrared remote to the universal remote database
- Firmware Roadmap
- And much more in the documentation folder
Project structure
applications- applications and services used in firmwareassets- assets used by applications and servicesfuri- Furi Core: OS-level primitives and helpersdebug- debug tool: GDB plugins, an SVD file, etc.documentation- documentation generation system configs and input filesfirmware- firmware source codelib- our and 3rd party libraries, drivers, etc.scripts- supplementary scripts and python libraries home
Also, see ReadMe.md files inside those directories for further details.
Links
- Discord: flipp.dev/discord
- Website: flipperzero.one
- Forum: forum.flipperzero.one
- Kickstarter: kickstarter.com