1
0
Fork 0
mirror of https://github.com/betaflight/betaflight-configurator.git synced 2025-07-15 12:25:15 +03:00
Commit graph

15 commits

Author SHA1 Message Date
Tomas Chmelevskij
03690e087f chore: add comman dangle rule for multiline 2021-12-18 08:21:05 +01:00
Mark Haslinghuis
682539f11b
Rebase of stm32.js 2021-08-31 06:47:43 +02:00
Mark Haslinghuis
c0cda1f735
Detect board in firmware_flasher patch 2021-07-28 03:34:09 +02:00
Mark Haslinghuis
7af9fb28a9 Verify board from firmware before flashing 2021-06-20 03:00:50 +02:00
Tomas Chmelevskij
616c2e796d chore: add semi rule to the linter and run --fix
Adds semicolon to the linter rules.
2021-02-14 07:37:03 +01:00
Miguel Angel Mulero Martinez
fd35031e6f Replace API versions by constants 2020-10-15 08:58:18 +02:00
Miguel Angel Mulero Martinez
24010a2e2a Move FC global vars inside FC object 2020-07-06 09:23:58 +02:00
Miguel Angel Mulero Martinez
c8b4958e8c Fix critical and major bugs from Sonar in JS files 2019-11-05 13:15:44 +01:00
mikeller
6999656097 Added dialog to offer resetting to custom defaults. 2019-09-15 00:54:39 +12:00
Hydra
4c0e9f06e5 Replace legacy firmware reboot sequence with MSP based sequence.
This allows two things:
1. good user experience when flashing devices that use FLASH
bootloaders.  previously users would have to use `bl flash` or enter
flash bootloader manually.
2. arbitrary setting of cli reboot character without breaking ability to
reboot flash via configurator.

Squashed commits:
* Extract MSPConnector from code in stm32.js to allow reuse.
* Use reboot_baud when connecting via MSP.
* Ensure GUI connect is unlocked after connect failures.
* Support legacy reboot method for old firmware.
* Don't treat MSPConnector as a singleton.
* Fix `port` usage in handlers.
* Add short delay after closing serial port before re-opening it again.
2019-08-24 22:11:35 +02:00
Miguel Angel Mulero Martinez
58657ac345 Refactor flashing progress bar code 2019-07-04 20:39:29 +02:00
Bruce Luckcuck
cc4406a748 Fix Firmware Flasher progress bar color indicators
There was previous logic in place to display a visual indicator for the status of the firmware flash using different colors for the progress bar. Unfortunately the logic was never working, or was broken at some point. The progress bar color would remain the default even if the flashing failed, making it difficult to recognize there was a problem.

Fixed to display the progress bar in green for success, red for failed, and blue for other "action required" types of failures. The logic was already there to try and display the red and blue indicators but they weren't working.
2019-04-14 20:04:02 -04:00
mikeller
058e72811c Fixed exception thrown when flashing. 2018-12-02 23:22:32 +13:00
Miguel Angel Mulero Martinez
1de9efd590 i18n stm32 driver 2018-01-29 09:28:11 +01:00
Bas Delfos
24c81375a4 Move src files 2018-01-24 22:50:40 +01:00
Renamed from js/protocols/stm32.js (Browse further)