Drop brewfile, drop makefile, update readme and documentation (#2205)
* Drop brewfile, drop makefile, update readme * Minor grammar and consistency fixes * ReadMe: add more documentation links, cleanup layout * ReadMe: cleanup and contribution section. Roadmap: update. * Docs: Lots of minor fixes Co-authored-by: Anna Prosvetova <anna@prosvetova.me> Co-authored-by: Astra <astra@astrra.space>
This commit is contained in:
あく
GitHub
parent
727f043747
commit
d7735a1efb
BIN
.github/assets/dark_theme_banner.png
vendored
Normal file
BIN
.github/assets/dark_theme_banner.png
vendored
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
BIN
.github/assets/light_theme_banner.png
vendored
Normal file
BIN
.github/assets/light_theme_banner.png
vendored
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
6
Brewfile
6
Brewfile
@ -1,6 +0,0 @@
|
||||
cask "gcc-arm-embedded"
|
||||
brew "protobuf"
|
||||
brew "gdb"
|
||||
brew "open-ocd"
|
||||
brew "clang-format"
|
||||
brew "dfu-util"
|
||||
21
Makefile
21
Makefile
@ -1,21 +0,0 @@
|
||||
$(info +-------------------------------------------------+)
|
||||
$(info | |)
|
||||
$(info | Hello, this is Flipper team speaking! |)
|
||||
$(info | |)
|
||||
$(info | We've migrated to new build system |)
|
||||
$(info | It's nice and based on scons |)
|
||||
$(info | |)
|
||||
$(info | Crash course: |)
|
||||
$(info | |)
|
||||
$(info | `./fbt` |)
|
||||
$(info | `./fbt flash` |)
|
||||
$(info | `./fbt debug` |)
|
||||
$(info | |)
|
||||
$(info | More details in documentation/fbt.md |)
|
||||
$(info | |)
|
||||
$(info | Also Please leave your feedback here: |)
|
||||
$(info | https://flipp.dev/4RDu |)
|
||||
$(info | or |)
|
||||
$(info | https://flipp.dev/2XM8 |)
|
||||
$(info | |)
|
||||
$(info +-------------------------------------------------+)
|
||||
187
ReadMe.md
187
ReadMe.md
@ -1,134 +1,115 @@
|
||||
<picture>
|
||||
<source media="(prefers-color-scheme: dark)" srcset="/.github/assets/dark_theme_banner.png">
|
||||
<source media="(prefers-color-scheme: light)" srcset="/.github/assets/light_theme_banner.png">
|
||||
<img
|
||||
alt="A pixel art of a Dophin with text: Flipper Zero Official Repo"
|
||||
src="/.github/assets/light_theme_banner.png">
|
||||
</picture>
|
||||
|
||||
# Flipper Zero Firmware
|
||||
|
||||
[](http://flipperzero.one/discord)
|
||||
- [Flipper Zero Official Website](https://flipperzero.one). A simple way to explain to your friends what the Flipper Zero can do
|
||||
- [Flipper Zero Firmware Update](https://update.flipperzero.one). Improvements for your dolphin: latest firmware releases, upgrade tools for PC and Mobile devices
|
||||
- [User Documentation](https://docs.flipperzero.one). Learn more about your dolphin: specs, usage guides, and everything that you wanted to ask
|
||||
|
||||
|
||||
# Contributing
|
||||
|
||||
Welcome to [Flipper Zero](https://flipperzero.one/)'s Firmware repo!
|
||||
Our goal is to create nice and clean code with good documentation, to make it a pleasure for everyone to work with.
|
||||
Our main goal is to build a healthy, sustainable community around the Flipper and be 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](/CODE_OF_CONDUCT.md) carefully.
|
||||
|
||||
# Clone the Repository
|
||||
## I need help
|
||||
|
||||
The best place to search for answers is our [User Documentation](https://docs.flipperzero.one). If you can't find the answer there, you can check our [Discord Server](https://flipp.dev/discord) or our [Forum](https://forum.flipperzero.one/).
|
||||
|
||||
## I want to report an issue
|
||||
|
||||
If you've found an issue and want to report it, please check our [Issues](https://github.com/flipperdevices/flipperzero-firmware/issues) page. Make sure that the description contains information about the firmware version you're using, your platform, and the proper 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, you can ask on the [Discord Server](https://flipp.dev/discord) or the [Issues](https://github.com/flipperdevices/flipperzero-firmware/issues) page, and we'll help you find the right place for your code.
|
||||
|
||||
Also, please read our [Contribution Guide](/CONTRIBUTING.md), and our [Coding Style](/CODING_STYLE.md), and ensure that your code is compatible with our project [License](/LICENSE).
|
||||
|
||||
Finally, open a [Pull Request](https://github.com/flipperdevices/flipperzero-firmware/pulls) and ensure that CI/CD statuses are all green.
|
||||
|
||||
# Development
|
||||
|
||||
The 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. For Flipper applications, we support C, C++, and armv7m assembly languages.
|
||||
|
||||
## 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](https://shop.flipperzero.one/products/wifi-devboard)
|
||||
- ST-Link
|
||||
- J-Link
|
||||
|
||||
Everything else will be taken care of by Flipper Build System.
|
||||
|
||||
## Cloning Source Code
|
||||
|
||||
Ensure that you have enough space and clone source code with Git:
|
||||
|
||||
You should clone with
|
||||
```shell
|
||||
$ git clone --recursive https://github.com/flipperdevices/flipperzero-firmware.git
|
||||
git clone --recursive https://github.com/flipperdevices/flipperzero-firmware.git
|
||||
```
|
||||
|
||||
# Read the Docs
|
||||
## Building
|
||||
|
||||
Check out details on [how to build firmware](documentation/fbt.md), [write applications](documentation/AppsOnSDCard.md), [un-brick your device](documentation/KeyCombo.md) and more in `documentation` folder.
|
||||
Build firmware using Flipper Build Tool:
|
||||
|
||||
# Update firmware
|
||||
|
||||
[Get Latest Firmware from Update Server](https://update.flipperzero.one/)
|
||||
|
||||
Flipper Zero's firmware consists of two components:
|
||||
|
||||
- Core2 firmware set - proprietary components by ST: FUS + radio stack. FUS is flashed at factory, and you should never update it.
|
||||
- Core1 Firmware - HAL + OS + Drivers + Applications.
|
||||
|
||||
They both must be flashed in the order described.
|
||||
|
||||
## With offline update package
|
||||
|
||||
With Flipper attached over USB:
|
||||
|
||||
`./fbt flash_usb`
|
||||
|
||||
Just building the package:
|
||||
|
||||
`./fbt updater_package`
|
||||
|
||||
To update, copy the resulting directory to Flipper's SD card and navigate to `update.fuf` file in Archive app.
|
||||
|
||||
## With STLink
|
||||
|
||||
### Core1 Firmware
|
||||
|
||||
Prerequisites:
|
||||
|
||||
- Linux / macOS
|
||||
- Terminal
|
||||
- [arm-gcc-none-eabi](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads)
|
||||
- openocd
|
||||
|
||||
One-liner: `./fbt firmware_flash`
|
||||
|
||||
## With USB DFU
|
||||
|
||||
1. Download latest [Firmware](https://update.flipperzero.one)
|
||||
|
||||
2. Reboot Flipper to Bootloader
|
||||
- Press and hold `← Left` + `↩ Back` for reset
|
||||
- Release `↩ Back` and keep holding `← Left` until blue LED lights up
|
||||
- Release `← Left`
|
||||
|
||||
3. Run `dfu-util -D full.dfu -a 0`
|
||||
|
||||
# Build on Linux/macOS
|
||||
|
||||
Check out `documentation/fbt.md` for details on building and flashing firmware.
|
||||
|
||||
## macOS Prerequisites
|
||||
|
||||
Make sure you have [brew](https://brew.sh) and install all the dependencies:
|
||||
```sh
|
||||
brew bundle --verbose
|
||||
```
|
||||
|
||||
## Linux Prerequisites
|
||||
|
||||
The FBT tool handles everything, only `git` is required.
|
||||
|
||||
### Optional dependencies
|
||||
|
||||
- openocd (debugging/flashing over SWD)
|
||||
- heatshrink (compiling image assets)
|
||||
- clang-format (code formatting)
|
||||
- dfu-util (flashing over USB DFU)
|
||||
- protobuf (compiling proto sources)
|
||||
|
||||
For example, to install them on Debian, use:
|
||||
```sh
|
||||
apt update
|
||||
apt install openocd clang-format-13 dfu-util protobuf-compiler
|
||||
```
|
||||
|
||||
heatshrink has to be compiled [from sources](https://github.com/atomicobject/heatshrink).
|
||||
|
||||
## Compile everything
|
||||
|
||||
```sh
|
||||
```shell
|
||||
./fbt
|
||||
```
|
||||
|
||||
Check `dist/` for build outputs.
|
||||
## Flashing Firmware using an in-circuit debugger
|
||||
|
||||
Use **`flipper-z-{target}-full-{suffix}.dfu`** to flash your device.
|
||||
Connect your in-circuit debugger to the Flipper and flash firmware using Flipper Build Tool:
|
||||
|
||||
## Flash everything
|
||||
|
||||
Connect your device via ST-Link and run:
|
||||
```sh
|
||||
./fbt firmware_flash
|
||||
```shell
|
||||
./fbt flash
|
||||
```
|
||||
|
||||
## Flashing Firmware using USB
|
||||
|
||||
Ensure that your Flipper is working, connect it using a USB cable and flash firmware using Flipper Build Tool:
|
||||
|
||||
```shell
|
||||
./fbt flash_usb
|
||||
```
|
||||
|
||||
## Documentation
|
||||
|
||||
- [Flipper Build Tool](/documentation/fbt.md) - building, flashing, and debugging Flipper software
|
||||
- [Applications](/documentation/AppsOnSDCard.md), [Application Manifest](/documentation/AppManifests.md) - developing, building, deploying, and debugging Flipper applications
|
||||
- [Hardware combos and Un-bricking](/documentation/KeyCombo.md) - recovering your Flipper from most nasty situations
|
||||
- [Flipper File Formats](/documentation/file_formats) - everything about how Flipper stores your data and how you can work with it
|
||||
- [Universal Remotes](/documentation/UniversalRemotes.md) - contributing your infrared remote to the universal remote database
|
||||
- [Firmware Roadmap](/documentation/RoadMap.md)
|
||||
- And much more in the [Documentation](/documentation) folder
|
||||
|
||||
# Links
|
||||
|
||||
* Discord: [flipp.dev/discord](https://flipp.dev/discord)
|
||||
* Website: [flipperzero.one](https://flipperzero.one)
|
||||
* Kickstarter page: [kickstarter.com](https://www.kickstarter.com/projects/flipper-devices/flipper-zero-tamagochi-for-hackers)
|
||||
* Forum: [forum.flipperzero.one](https://forum.flipperzero.one/)
|
||||
- Discord: [flipp.dev/discord](https://flipp.dev/discord)
|
||||
- Website: [flipperzero.one](https://flipperzero.one)
|
||||
- Forum: [forum.flipperzero.one](https://forum.flipperzero.one/)
|
||||
- Kickstarter: [kickstarter.com](https://www.kickstarter.com/projects/flipper-devices/flipper-zero-tamagochi-for-hackers)
|
||||
|
||||
# Project structure
|
||||
|
||||
- `applications` - Applications and services used in firmware
|
||||
- `assets` - Assets used by applications and services
|
||||
- `furi` - Furi Core: os level primitives and helpers
|
||||
- `furi` - Furi Core: OS-level primitives and helpers
|
||||
- `debug` - Debug tool: GDB-plugins, SVD-file and etc
|
||||
- `documentation` - Documentation generation system configs and input files
|
||||
- `firmware` - Firmware source code
|
||||
- `lib` - Our and 3rd party libraries, drivers, etc.
|
||||
- `scripts` - Supplementary scripts and python libraries home
|
||||
|
||||
Also pay attention to `ReadMe.md` files inside those directories.
|
||||
Also, pay attention to `ReadMe.md` files inside those directories.
|
||||
|
||||
@ -1,63 +1,63 @@
|
||||
# Flipper Application Manifests (.fam)
|
||||
|
||||
All components of Flipper Zero firmware — services, user applications, system settings — are developed independently. Each component has a build system manifest file, named `application.fam`, which defines basic properties of that component and its relations to other parts of the system.
|
||||
All components of Flipper Zero firmware — services, user applications, and system settings — are developed independently. Each component has a build system manifest file, named `application.fam`, which defines the basic properties of that component and its relations to other parts of the system.
|
||||
|
||||
When building firmware, **`fbt`** collects all application manifests and processes their dependencies. Then it builds only those components that are referenced in the current build configuration. See [fbt docs](./fbt.md#firmware-application-set) for details on build configurations.
|
||||
When building firmware, **`fbt`** collects all application manifests and processes their dependencies. Then it builds only those components referenced in the current build configuration. See [fbt docs](./fbt.md#firmware-application-set) for details on build configurations.
|
||||
|
||||
## Application definition
|
||||
|
||||
Properties of a firmware component are declared in a form of a Python code snippet, forming a call to App() function with various parameters.
|
||||
A firmware component's properties are declared in a Python code snippet, forming a call to App() function with various parameters.
|
||||
|
||||
Only 2 parameters are mandatory: ***appid*** and ***apptype***, others are optional and may only be meaningful for certain application types.
|
||||
Only 2 parameters are mandatory: ***appid*** and ***apptype***; others are optional and may only be meaningful for certain application types.
|
||||
|
||||
### Parameters
|
||||
|
||||
* **appid**: string, application id within the build system. Used for specifying which applications to include in build configuration and to resolve dependencies and conflicts.
|
||||
* **appid**: string, application id within the build system. Used to specify which applications to include in the build configuration and resolve dependencies and conflicts.
|
||||
|
||||
* **apptype**: member of FlipperAppType.* enumeration. Valid values are:
|
||||
|
||||
| Enum member | Firmware component type |
|
||||
|--------------|--------------------------|
|
||||
| SERVICE | System service, created at early startup |
|
||||
| SYSTEM | Application not being shown in any menus. Can be started by other apps or from CLI |
|
||||
| APP | Regular application for main menu |
|
||||
| PLUGIN | Application to be built as a part of firmware an to be placed in Plugins menu |
|
||||
| SYSTEM | Application is not being shown in any menus. It can be started by other apps or from CLI |
|
||||
| APP | Regular application for the main menu |
|
||||
| PLUGIN | Application to be built as a part of the firmware and to be placed in the Plugins menu |
|
||||
| DEBUG | Application only visible in Debug menu with debug mode enabled |
|
||||
| ARCHIVE | One and only Archive app |
|
||||
| SETTINGS | Application to be placed in System settings menu |
|
||||
| SETTINGS | Application to be placed in the system settings menu |
|
||||
| STARTUP | Callback function to run at system startup. Does not define a separate app |
|
||||
| EXTERNAL | Application to be built as .fap plugin |
|
||||
| METAPACKAGE | Does not define any code to be run, used for declaring dependencies and application bundles |
|
||||
|
||||
* **name**: Name that is displayed in menus.
|
||||
* **entry_point**: C function to be used as application's entry point. Note that C++ function names are mangled, so you need to wrap them in `extern "C"` in order to use them as entry points.
|
||||
* **entry_point**: C function to be used as the application's entry point. Note that C++ function names are mangled, so you need to wrap them in `extern "C"` to use them as entry points.
|
||||
* **flags**: Internal flags for system apps. Do not use.
|
||||
* **cdefines**: C preprocessor definitions to declare globally for other apps when current application is included in active build configuration.
|
||||
* **requires**: List of application IDs to also include in build configuration, when current application is referenced in list of applications to build.
|
||||
* **conflicts**: List of application IDs that current application conflicts with. If any of them is found in constructed application list, **`fbt`** will abort firmware build process.
|
||||
* **cdefines**: C preprocessor definitions to declare globally for other apps when the current application is included in the active build configuration.
|
||||
* **requires**: List of application IDs to include in the build configuration when the current application is referenced in the list of applications to build.
|
||||
* **conflicts**: List of application IDs that the current application conflicts with. If any of them is found in the constructed application list, **`fbt`** will abort the firmware build process.
|
||||
* **provides**: Functionally identical to ***requires*** field.
|
||||
* **stack_size**: Stack size, in bytes, to allocate for application on its startup. Note that allocating a stack that is too small for an app to run will cause system crash due to stack overflow, and allocating too much stack space will reduce usable heap memory size for apps to process data. *Note: you can use `ps` and `free` CLI commands to profile your app's memory usage.*
|
||||
* **icon**: Animated icon name from built-in assets to be used when building app as a part of firmware.
|
||||
* **order**: Order of an application within its group when sorting entries in it. The lower the order is, the closer to the start of the list the item is placed. *Used for ordering startup hooks and menu entries.*
|
||||
* **stack_size**: Stack size, in bytes, to allocate for application on its startup. Note that allocating a stack too small for an app to run will cause a system crash due to stack overflow, and allocating too much stack space will reduce usable heap memory size for apps to process data. *Note: you can use `ps`, and `free` CLI commands to profile your app's memory usage.*
|
||||
* **icon**: Animated icon name from built-in assets to be used when building the app as a part of the firmware.
|
||||
* **order**: Order of an application within its group when sorting entries in it. The lower the order is, the closer to the start of the list the item is placed. *Used for ordering startup hooks and menu entries.*
|
||||
* **sdk_headers**: List of C header files from this app's code to include in API definitions for external applications.
|
||||
* **targets**: list of strings, target names, which this application is compatible with. If not specified, application is built for all targets. Default value is `["all"]`.
|
||||
* **targets**: list of strings, target names, which this application is compatible with. If not specified, the application is built for all targets. The default value is `["all"]`.
|
||||
|
||||
|
||||
#### Parameters for external applications
|
||||
|
||||
The following parameters are used only for [FAPs](./AppsOnSDCard.md):
|
||||
|
||||
* **sources**: list of strings, file name masks, used for gathering sources within app folder. Default value of `["*.c*"]` includes C and C++ source files. Application cannot use `"lib"` folder for their own source code, as it is reserved for **fap_private_libs**.
|
||||
* **fap_version**: tuple, 2 numbers in form of (x,y): application version to be embedded within .fap file. Default value is (0,1), meaning version "0.1".
|
||||
* **sources**: list of strings, file name masks used for gathering sources within the app folder. The default value of `["*.c*"]` includes C and C++ source files. Applications cannot use the `"lib"` folder for their own source code, as it is reserved for **fap_private_libs**.
|
||||
* **fap_version**: tuple, 2 numbers in the form of (x,y): application version to be embedded within .fap file. The default value is (0,1), meaning version "0.1".
|
||||
* **fap_icon**: name of a .png file, 1-bit color depth, 10x10px, to be embedded within .fap file.
|
||||
* **fap_libs**: list of extra libraries to link application against. Provides access to extra functions that are not exported as a part of main firmware at expense of increased .fap file size and RAM consumption.
|
||||
* **fap_category**: string, may be empty. App subcategory, also works as path of FAP within apps folder in the file system.
|
||||
* **fap_libs**: list of extra libraries to link the application against. Provides access to extra functions that are not exported as a part of main firmware at the expense of increased .fap file size and RAM consumption.
|
||||
* **fap_category**: string, may be empty. App subcategory, also determines the path of the FAP within apps folder in the file system.
|
||||
* **fap_description**: string, may be empty. Short application description.
|
||||
* **fap_author**: string, may be empty. Application's author.
|
||||
* **fap_weburl**: string, may be empty. Application's homepage.
|
||||
* **fap_icon_assets**: string. If present, defines a folder name to be used for gathering image assets for this application. These images will be preprocessed and built alongside the application. See [FAP assets](./AppsOnSDCard.md#fap-assets) for details.
|
||||
* **fap_icon_assets**: string. If present defines a folder name to be used for gathering image assets for this application. These images will be preprocessed and built alongside the application. See [FAP assets](./AppsOnSDCard.md#fap-assets) for details.
|
||||
* **fap_extbuild**: provides support for parts of application sources to be built by external tools. Contains a list of `ExtFile(path="file name", command="shell command")` definitions. **`fbt`** will run the specified command for each file in the list.
|
||||
Note that commands are executed at the firmware root folder's root, and all intermediate files must be placed in a application's temporary build folder. For that, you can use pattern expansion by **`fbt`**: `${FAP_WORK_DIR}` will be replaced with the path to the application's temporary build folder, and `${FAP_SRC_DIR}` will be replaced with the path to the application's source folder. You can also use other variables defined internally by **`fbt`**.
|
||||
Note that commands are executed at the firmware root folder's root, and all intermediate files must be placed in an application's temporary build folder. For that, you can use pattern expansion by **`fbt`**: `${FAP_WORK_DIR}` will be replaced with the path to the application's temporary build folder, and `${FAP_SRC_DIR}` will be replaced with the path to the application's source folder. You can also use other variables defined internally by **`fbt`**.
|
||||
|
||||
Example for building an app from Rust sources:
|
||||
|
||||
@ -71,16 +71,16 @@ Example for building an app from Rust sources:
|
||||
),
|
||||
```
|
||||
|
||||
* **fap_private_libs**: list of additional libraries that are distributed as sources alongside the application. These libraries will be built as a part of the application build process.
|
||||
* **fap_private_libs**: a list of additional libraries distributed as sources alongside the application. These libraries will be built as a part of the application build process.
|
||||
Library sources must be placed in a subfolder of "`lib`" folder within the application's source folder.
|
||||
Each library is defined as a call to `Lib()` function, accepting the following parameters:
|
||||
|
||||
- **name**: name of library's folder. Required.
|
||||
- **fap_include_paths**: list of library's relative paths to add to parent fap's include path list. Default value is `["."]` meaning library's source root.
|
||||
- **sources**: list of filename masks to be used for gathering include files for this library. Paths are relative to library's source root. Default value is `["*.c*"]`.
|
||||
- **cflags**: list of additional compiler flags to be used for building this library. Default value is `[]`.
|
||||
- **cdefines**: list of additional preprocessor definitions to be used for building this library. Default value is `[]`.
|
||||
- **cincludes**: list of additional include paths to be used for building this library. Paths are relative to application's root. Can be used for providing external search paths for this library's code - for configuration headers. Default value is `[]`.
|
||||
- **fap_include_paths**: list of library's relative paths to add to parent fap's include path list. The default value is `["."]` meaning the library's source root.
|
||||
- **sources**: list of filename masks to be used for gathering include files for this library. Paths are relative to the library's source root. The default value is `["*.c*"]`.
|
||||
- **cflags**: list of additional compiler flags to be used for building this library. The default value is `[]`.
|
||||
- **cdefines**: list of additional preprocessor definitions to be used for building this library. The default value is `[]`.
|
||||
- **cincludes**: list of additional include paths to be used for building this library. Paths are relative to the application's root. This can be used for providing external search paths for this library's code - for configuration headers. The default value is `[]`.
|
||||
|
||||
Example for building an app with a private library:
|
||||
|
||||
@ -103,10 +103,10 @@ Example for building an app with a private library:
|
||||
],
|
||||
```
|
||||
|
||||
For that snippet, **`fbt`** will build 2 libraries: one from sources in `lib/mbedtls` folder, and another from sources in `lib/loclass` folder. For `mbedtls` library, **`fbt`** will add `lib/mbedtls/include` to the list of include paths for the application and compile only the files specified in `sources` list. Additionally, **`fbt`** will enable `MBEDTLS_ERROR_C` preprocessor definition for `mbedtls` sources.
|
||||
For `loclass` library, **`fbt`** will add `lib/loclass` to the list of include paths for the application and build all sources in that folder. Also **`fbt`** will disable treating compiler warnings as errors for `loclass` library specifically - that can be useful when compiling large 3rd-party codebases.
|
||||
For that snippet, **`fbt`** will build 2 libraries: one from sources in `lib/mbedtls` folder and another from sources in `lib/loclass` folder. For the `mbedtls` library, **`fbt`** will add `lib/mbedtls/include` to the list of include paths for the application and compile only the files specified in the `sources` list. Additionally, **`fbt`** will enable `MBEDTLS_ERROR_C` preprocessor definition for `mbedtls` sources.
|
||||
For the `loclass` library, **`fbt`** will add `lib/loclass` to the list of the include paths for the application and build all sources in that folder. Also, **`fbt`** will disable treating compiler warnings as errors for the `loclass` library, which can be useful when compiling large 3rd-party codebases.
|
||||
|
||||
Both libraries will be linked into the application.
|
||||
Both libraries will be linked with the application.
|
||||
|
||||
|
||||
## .fam file contents
|
||||
|
||||
@ -2,49 +2,47 @@
|
||||
|
||||
# Where we are (0.x.x branch)
|
||||
|
||||
Our goal for 0.x.x branch is to build stable usable apps and API.
|
||||
First public release that we support in this branch is 0.43.1. Your device most likely came with this version.
|
||||
You can develop applications but keep in mind that API is not final yet.
|
||||
Our goal for 0.x.x branch is to build stable, usable apps and API.
|
||||
The first public release in this branch is 0.43.1.
|
||||
|
||||
## What's already implemented
|
||||
|
||||
**System and HAL**
|
||||
|
||||
- Furi Core
|
||||
- Furi HAL
|
||||
- Loading applications from SD
|
||||
|
||||
**Applications**
|
||||
|
||||
- SubGhz: all most common protocols, reading RAW for everything else
|
||||
- 125kHz RFID: all most common protocols
|
||||
- NFC: reading/emulating Mifare Ultralight, reading MiFare Classic and DESFire, basic EMV, basic NFC-B,F,V
|
||||
- NFC: reading/emulating Mifare Ultralight, reading MiFare Classic and DESFire, basic EMV, basic NFC-B/F/V
|
||||
- Infrared: all most common RC protocols, RAW format for everything else
|
||||
- GPIO: UART bridge, basic GPIO controls
|
||||
- iButton: DS1990, Cyfral, Metacom
|
||||
- Bad USB: Full USB Rubber Ducky support, some extras for windows alt codes
|
||||
- U2F: Full U2F specification support
|
||||
|
||||
**Extras**
|
||||
**External applications**
|
||||
|
||||
- BLE Keyboard
|
||||
- Bluetooth
|
||||
- Snake game
|
||||
|
||||
**System and HAL**
|
||||
|
||||
- Furi Core
|
||||
- Furi HAL
|
||||
|
||||
# Where we're going (Version 1)
|
||||
|
||||
Main goal for 1.0.0 is to provide first stable version for both Users and Developers.
|
||||
The main goal for 1.0.0 is to provide the first stable version for both Users and Developers.
|
||||
|
||||
## What we're planning to implement in 1.0.0
|
||||
|
||||
- Loading applications from SD (tested as PoC, work scheduled for Q2)
|
||||
- More protocols (gathering feedback)
|
||||
- User documentation (work in progress)
|
||||
- FuriCore: get rid of CMSIS API, replace hard real time timers, improve stability and performance (work in progress)
|
||||
- FuriHal: deep sleep mode, stable API, examples, documentation (work in progress)
|
||||
- Application improvements (a ton of things that we want to add and improve that are too numerous to list here)
|
||||
|
||||
## When will it happen and where I can see the progress?
|
||||
## When will it happen, and where can I see the progress?
|
||||
|
||||
Release 1.0.0 will most likely happen around the end of Q3
|
||||
Release 1.0.0 will most likely happen around the end of 2023Q1
|
||||
|
||||
Development progress can be tracked in our public Miro board:
|
||||
|
||||
Loading…
Reference in New Issue
Block a user