forked from flipperdevices/flipperzero-firmware
-
-
Notifications
You must be signed in to change notification settings - Fork 562
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
with small changes - Extra checks added for otg power - Included firmware binaries are packed into fap, will be unpacked on first launch, second launch will be fast
- Loading branch information
Showing
165 changed files
with
31,858 additions
and
60 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,30 +1,35 @@ | ||
App( | ||
appid="esp_flasher", | ||
name="ESP Flasher", | ||
fap_version=(1,4), | ||
fap_version=(1, 4), | ||
apptype=FlipperAppType.EXTERNAL, | ||
entry_point="esp_flasher_app", | ||
requires=["gui"], | ||
stack_size=4 * 1024, | ||
order=90, | ||
fap_file_assets="packedfws", | ||
fap_icon="wifi_10px.png", | ||
fap_category="GPIO", | ||
fap_private_libs=[ | ||
Lib( | ||
name="esp-serial-flasher", | ||
fap_include_paths=["include"], | ||
sources=[ | ||
"src/esp_loader.c", | ||
"src/esp_targets.c", | ||
"src/md5_hash.c", | ||
"src/protocol_common.c", | ||
"src/protocol_uart.c", | ||
"src/slip.c" | ||
], | ||
cincludes=["lib/esp-serial-flasher/private_include"], | ||
cdefines=["SERIAL_FLASHER_INTERFACE_UART=1", "MD5_ENABLED=1", "SERIAL_FLASHER_WRITE_BLOCK_RETRIES=10"], | ||
), | ||
], | ||
Lib( | ||
name="esp-serial-flasher", | ||
fap_include_paths=["include"], | ||
sources=[ | ||
"src/esp_loader.c", | ||
"src/esp_targets.c", | ||
"src/md5_hash.c", | ||
"src/protocol_common.c", | ||
"src/protocol_uart.c", | ||
"src/slip.c", | ||
], | ||
cincludes=["lib/esp-serial-flasher/private_include"], | ||
cdefines=[ | ||
"SERIAL_FLASHER_INTERFACE_UART=1", | ||
"MD5_ENABLED=1", | ||
"SERIAL_FLASHER_WRITE_BLOCK_RETRIES=10", | ||
], | ||
), | ||
], | ||
cdefines=["SERIAL_FLASHER_INTERFACE_UART=1"], | ||
fap_icon_assets="assets", | ||
) |
Binary file removed
BIN
-1.38 KB
non_catalog_apps/flipperzero-esp-flasher/assets/DolphinCommon_56x48.png
Binary file not shown.
Binary file removed
BIN
-1.77 KB
non_catalog_apps/flipperzero-esp-flasher/assets/KeyBackspaceSelected_16x9.png
Binary file not shown.
Binary file removed
BIN
-1.79 KB
non_catalog_apps/flipperzero-esp-flasher/assets/KeyBackspace_16x9.png
Binary file not shown.
Binary file removed
BIN
-7.04 KB
non_catalog_apps/flipperzero-esp-flasher/assets/KeyKeyboardSelected_10x11.png
Binary file not shown.
Binary file removed
BIN
-7.58 KB
non_catalog_apps/flipperzero-esp-flasher/assets/KeyKeyboard_10x11.png
Binary file not shown.
Binary file removed
BIN
-1.81 KB
non_catalog_apps/flipperzero-esp-flasher/assets/KeySaveSelected_24x11.png
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-1.11 KB
non_catalog_apps/flipperzero-esp-flasher/assets/WarningDolphin_45x42.png
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
47 changes: 47 additions & 0 deletions
47
...apps/flipperzero-esp-flasher/lib/esp-serial-flasher/.github/ISSUE_TEMPLATE/bug_report.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
name: Bug report | ||
description: Report a problem with esp-serial-flasher operation | ||
labels: ['Type: Bug'] | ||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
* Please ensure you are using the latest version of `esp-serial-flasher`. | ||
* Try using one of the examples from the `examples` directory and following the example documentation. | ||
* If your board is a custom design, consider using our [free-of-charge schematic and PCB review service](https://www.espressif.com/en/contact-us/circuit-schematic-pcb-design-review). | ||
* If still experiencing issues, please provide as many details as possible below about your hardware and software setup. | ||
- type: input | ||
id: port | ||
attributes: | ||
label: Port | ||
description: Which port are you experiencing the issue with? | ||
placeholder: ex. ESP, STM32 | ||
validations: | ||
required: true | ||
- type: input | ||
id: target | ||
attributes: | ||
label: Target chip | ||
description: Which chip are you trying to flash? | ||
placeholder: ex. ESP8266, ESP32, ESP32-C3 | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: other-hw | ||
attributes: | ||
label: Hardware Configuration | ||
description: What dev boards/custom PCB are you using, how are the chips connected, which baudrate are you trying to flash with? | ||
validations: | ||
required: true | ||
id: output | ||
- type: textarea | ||
attributes: | ||
label: Log output | ||
description: Enable tracing with SERIAL_FLASHER_DEBUG_TRACE and provide the full log. | ||
render: plain | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: more-info | ||
attributes: | ||
label: More Information | ||
description: Provide any additional information relevant to the issue. |
34 changes: 34 additions & 0 deletions
34
...flipperzero-esp-flasher/lib/esp-serial-flasher/.github/ISSUE_TEMPLATE/feature_request.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
name: Feature request | ||
description: Suggest an idea for this project | ||
labels: ['Type: Feature Request'] | ||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
* We welcome any ideas or feature requests! It's helpful if you can explain exactly why the feature would be useful. | ||
* Please check if the feature has already been suggested in [existing issues](https://github.com/espressif/esp-serial-flasher/issues) or [pull requests](https://github.com/espressif/esp-serial-flasher/pulls). | ||
* Please provide enough context so that the reasoning behind the suggestion can be understood. | ||
- type: textarea | ||
id: problem-related | ||
attributes: | ||
label: Is your feature request related to a problem? | ||
description: Please provide a clear and concise description of what the problem is. | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: solution | ||
attributes: | ||
label: Describe the solution you'd like | ||
description: Please provide a clear and concise description of a solution of the described problem or usecase. | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: alternatives | ||
attributes: | ||
label: Describe alternatives you've considered | ||
description: Please provide a clear and concise description of any alternative solutions or features you've considered. | ||
- type: textarea | ||
id: context | ||
attributes: | ||
label: Additional context | ||
description: Please add any other context here. |
Oops, something went wrong.