1
0
Fork 0
mirror of https://github.com/betaflight/betaflight-configurator.git synced 2025-07-23 00:05:22 +03:00
Commit graph

4860 commits

Author SHA1 Message Date
mikeller
2902db5c39 Hide the 'factory band' VTX table setting for VTX types that do not support it. 2020-02-19 23:06:30 +13:00
Michael Keller
855ab72e03
Merge pull request #1882 from mikeller/fix_loop_speed_selection
Fixed loop speed dropdowns for firmware versions with 32kHz gyro support.
2020-02-17 23:57:36 +13:00
Michael Keller
8f7634c3f4
Merge pull request #1881 from betaflight/dependabot/npm_and_yarn/yarn-1.22.0
Bump yarn from 1.19.1 to 1.22.0
2020-02-17 23:56:34 +13:00
mikeller
b889ed3de5 Fixed loop speed dropdowns for firmware versions with 32kHz gyro support. 2020-02-16 11:33:24 +13:00
Michael Keller
44cb725932
Merge pull request #1880 from rvdveen/low-capacity-warning
Add support for the 'mah capacity exceeded' osd warning
2020-02-15 23:41:52 +13:00
Roy van der Veen
eb8a50016f Add support for the 'mah capacity exceeded' osd warning 2020-02-15 10:22:49 +01:00
dependabot[bot]
22848779d6
Bump yarn from 1.19.1 to 1.22.0
Bumps [yarn](https://github.com/yarnpkg/yarn) from 1.19.1 to 1.22.0.
- [Release notes](https://github.com/yarnpkg/yarn/releases)
- [Changelog](https://github.com/yarnpkg/yarn/blob/master/CHANGELOG.md)
- [Commits](https://github.com/yarnpkg/yarn/compare/v1.19.1...v1.22.0)

Signed-off-by: dependabot[bot] <support@github.com>
2020-02-14 23:47:25 +00:00
Michael Keller
021e4fbcc1
Merge pull request #1879 from McGiverGim/osd_camera_frame
Add OSD Camera Frame element
2020-02-13 13:08:49 +13:00
Miguel Angel Mulero Martinez
6e2682ea43 Add OSD Camera Frame element 2020-02-11 15:21:46 +01:00
Michael Keller
682472e1b0
Merge pull request #1873 from mikeller/add_bind_button
Added bind button for receivers that support it.
2020-02-08 20:47:37 +13:00
mikeller
0a92e90427 Added message to acknowledge binding. 2020-02-08 19:19:39 +13:00
Michael Keller
2eae917b77
Merge pull request #1874 from mikeller/move_macos_azure_build_to_10_15
Moved MacOS azure build to 10.15 because 10.13 has been deprecated.
2020-02-08 14:56:17 +13:00
Michael Keller
719491635e
Merge pull request #1872 from etracer65/rename_acc_calib_arming_disabled
Rename ACC_CALIB arming disabled message to NO_ACC_CAL
2020-02-08 14:55:59 +13:00
Michael Keller
50ae3de4da
Merge pull request #1876 from mikeller/improve_analytics_naming
Improved naming of event categories, 'Firmware' is now 'Flashing'.
2020-02-08 14:06:57 +13:00
Michael Keller
a27ffbd453
Merge pull request #1875 from McGiverGim/fix_throttle_preview
Fix throttle preview refresh
2020-02-08 13:23:24 +13:00
mikeller
d4271042f0 Improved naming of event categories, 'Firmware' is now 'Flashing'. 2020-02-07 10:09:21 +13:00
Michael Keller
abb3429b96
Merge pull request #1869 from Asizon/DynamicNotchMaxHz
Coordination with new Dynamic Notch improvements
2020-02-07 09:51:40 +13:00
Michael Keller
41876c7281
Merge pull request #1870 from McGiverGim/hide_32k_notice
Remove 32k notice
2020-02-07 09:13:39 +13:00
Asizon
5486b7e78e Remove whitespaces 2020-02-06 09:58:44 +01:00
Miguel Angel Mulero Martinez
10916a5cfc Fix throttle preview refresh 2020-02-06 09:44:14 +01:00
Asizon
e3041286a3 Add Dynamic Notch Max Hz
Remove white spaces

Remove white space2

Revert and add suggested changes

Some cosmetic changes

MinHz Changes

Fix MinHz Max
2020-02-06 09:27:44 +01:00
Miguel Angel Mulero Martinez
7881bd3673 Remove 32k notice 2020-02-06 09:09:56 +01:00
mikeller
7cfbd098d8 Moved MacOS azure build to 10.15 because 10.13 has been deprecated. 2020-02-06 17:17:21 +13:00
Michael Keller
c2575935fc Added bind button for receivers that support it. 2020-02-06 15:41:47 +13:00
Bruce Luckcuck
01e35c2ecb Rename ACC_CALIB arming disabled message to NO_ACC_CAL 2020-02-05 18:07:15 -05:00
Michael Keller
2925646d82
Merge pull request #1868 from McGiverGim/gyro_native_sampling
Work with gyro native sampling
2020-02-05 23:21:43 +13:00
Miguel Angel Mulero Martinez
9394d5901c Work with gyro native sampling 2020-02-04 16:42:39 +01:00
Michael Keller
55aab38680
Merge pull request #1867 from bluehallu/patch-1
Update MacOS instructions
2020-01-28 21:18:17 +13:00
Michael Keller
53f4ad6489
Merge pull request #1865 from fiam/agh_fix_1864
Fix problems introduced in #1851
2020-01-28 00:02:54 +13:00
Michael Keller
111190638e
Merge pull request #1863 from mikeller/add_dfu_exit_button
Added button to exit DFU.
2020-01-27 19:27:12 +13:00
bluehallu
edd650fcc0
Update MacOS instructions
Trying to run the command before installing results in 

```
sudo xattr -rd com.apple.quarantine /Applications/Betaflight\ Configurator.app
Password:
xattr: No such file: /Applications/Betaflight Configurator.app
```
2020-01-26 21:20:56 +00:00
Alberto García Hierro
2b1c2e5732 Fix problems introduced in #1851
- Clear to in-memory ports array when reading MSP2_COMMON_SERIAL_CONFIG,
like MSP_CF_SERIAL_CONFIG does. Take the opportunity to move the
`SERIAL_CONFIG.ports = [];` statement to the very first line of both
handler blocks, so it's more evident.
- Remove accidentally duplicated line in the payload serializer
for MSP_SET_CF_SERIAL_CONFIG, which then I copied and pasted to
MSP2_COMMON_SET_SERIAL_CONFIG. This was sending the msp_baudrate
twice, causing all baudrates after it to be misinterpreted.

Fixes #1864
2020-01-26 10:49:55 +00:00
mikeller
d293d6b1e7 Added button to exit DFU. 2020-01-26 22:59:54 +13:00
Michael Keller
4475586e59
Merge pull request #1862 from McGiverGim/update_catalan_translation
Update Catalan translation
2020-01-26 12:50:11 +13:00
Michael Keller
cee091f103
Merge pull request #1851 from fiam/agh_cf_serial_config
[MSP] Use MSP2_COMMON[_SET]_SERIAL_CONFIG for configuring ports
2020-01-26 12:48:05 +13:00
Michael Keller
d022cb827e
Merge pull request #1861 from jflyper/bfcdev-h7-rev-v-erase-weirdness-workaround
Workaround for H7 Rev.V weirdness on erase beyond 1MB
2020-01-25 20:04:14 +13:00
Miguel Angel Mulero Martinez
f18390c203 Update Catalan translation 2020-01-24 19:30:56 +01:00
jflyper
8ac29e0563 Workaround for H7 Rev.V weirdness on erase beyond 1MB
H743 Rev.V (probably other H7 Rev.Vs also) remains in dfuDNBUSY state after the specified delay time.

STM32CubeProgrammer deals with behavior with an undocumented procedure as follows.

  1. Issue DFU_CLRSTATUS, which ends up with (14,10) = (errUNKNOWN, dfuERROR)
  2. Issue another DFU_CLRSTATUS which delivers (0,2) = (OK, dfuIDLE)
  3. Treat the current erase successfully finished.

Here in this PR, we call clarStatus to get to the dfuIDLE state when dfuDNBUSY is detected after timeout.

---
Below is the complete description of the problem reported at ST community
(https://community.st.com/s/question/0D50X0000C0w7U9SQI/weird-stm32h743zi-revv-usb-dfu-erase-behavior-beyond-1mb-page-8)

Weird STM32H743ZI Rev.V USB DFU erase behavior beyond 1MB (sector 8)

Summary

I'm observing errors and what looks like a non-standard error recovery procedure for all sectors beyond 1MB (sectors 8 through 15) during sector erase on STM32H743ZI Rev.V (Nucleo-H743ZI2) under STM32CubeProgrammer.

Is this behavior documented anywhere?

Description

For sector erase start to sector 2 erase, a log from the STM32CubeProgrammer looks like this.

13:05:04:121 : Flash sector erase ...
13:05:04:121 : DFU status = 0
13:05:04:121 : DFU State = 9
13:05:04:121 : Status: 0, State: 9
13:05:04:121 : sending an abort request
13:05:04:122 : DFU status = 0
13:05:04:122 : DFU State = 2
13:05:04:122 : sending a page erase request @: 0x08000000
13:05:04:122 : data: 4100000008
13:05:05:025 : DFU status = 0
13:05:05:025 : DFU State = 4
13:05:05:026 : DFU status = 0
13:05:05:027 : DFU State = 5
13:05:05:027 : erasing sector 0000 @: 0x08000000 done
13:05:05:027 : DFU status = 0
13:05:05:027 : DFU State = 5
13:05:05:027 : Status: 0, State: 5
13:05:05:027 : sending a page erase request @: 0x08020000
13:05:05:027 : data: 4100000208
13:05:05:932 : DFU status = 0
13:05:05:932 : DFU State = 4
13:05:05:933 : DFU status = 0
13:05:05:934 : DFU State = 5
13:05:05:934 : erasing sector 0001 @: 0x08020000 done
13:05:05:935 : DFU status = 0
13:05:05:936 : DFU State = 5
13:05:05:936 : Status: 0, State: 5
...

I notice that sector erase requests are followed by what seems like a pair of GETSTATUS results, with (status, state) being (0, 4) and (0,5) and then declared as erase done.
States 4 and 5 are probably dfuDNBUSY and dfuDNLOAD-IDLE respectively.
All sectors within the first 1MB (sectors 0 through 7) behaves the same.

But for sectors beyond 1MB, it looks like this.

13:05:11:397 : DFU status = 0
13:05:11:397 : DFU State = 5
13:05:11:397 : Status: 0, State: 5
13:05:11:397 : sending a page erase request @: 0x08100000
13:05:11:397 : data: 4100001008
13:05:11:413 : DFU status = 0
13:05:11:413 : DFU State = 4
13:05:11:414 : DFU status = 0
13:05:11:414 : DFU State = 4
13:05:13:419 : sending a clear status request
13:05:13:421 : DFU status = 14
13:05:13:421 : DFU State = 10
13:05:13:421 : an error occured after sending the clear status request
13:05:13:421 : Status: errUNKNOWN, State: dfuERROR
13:05:13:421 : DFU status = 14
13:05:13:422 : DFU State = 10
13:05:13:422 : sending a clear status request
13:05:13:422 : DFU status = 0
13:05:13:422 : DFU State = 2
13:05:13:422 : DFU status = 0
13:05:13:422 : DFU State = 2
13:05:13:422 : erasing sector 0008 @: 0x08100000 done

Notice that GETSTATUS results are now (0,4) and (0,4), followed by CLEARSTATUS returning (14,10) which is attributed as dfuERROR, and then another CLEARSTATUS (may be two?) that returned (0,2). This particular sector erase process is treated as successful, but it looks like that the process has never confirmed the successful completion of the erase operation but forced clear an error caused by the preceding clear.

(status, state) in the process are probably:
(14, 10) = (errUNKNOWN, dfuERROR)
(0, 2) = (OK, dfuIDLE)

Btw, sector erase succeeds with (0,4) (0,5) on STM32H743ZI Rev.Y (Nucleo-H743ZI) for all sectors 0 through 15 under STM32CubeProgrammer.
2020-01-22 18:27:13 +09:00
Michael Keller
577ce99c1d
Merge pull request #1857 from nicolas-van/patch-1
Changed installation procedure for Linux user
2020-01-17 02:30:22 +13:00
Michael Keller
672923e810
Merge pull request #1849 from McGiverGim/fix_vtx_powerlevel
Fix VTX when PowerLevel tag is empty
2020-01-17 01:40:35 +13:00
Michael Keller
c85198a661
Merge pull request #1850 from McGiverGim/sonar_clean_vtx_js
Sonar clean vtx.js
2020-01-17 01:38:08 +13:00
Michael Keller
14ab7639ca
Update Basque translation (#1848)
Update Basque translation
2020-01-16 23:21:54 +13:00
Alberto García Hierro
b9b84e1c87 Change all console.log() calls to use string interpolation 2020-01-15 09:34:18 +00:00
Alberto García Hierro
35cb6a5e70 Change all shadowed variables use let/const
Otherwise sonarcloud complains about the shadowed variables
in the previous commit. Not ammending it into the previous one
to make review easier.
2020-01-15 09:34:18 +00:00
Alberto García Hierro
2defc901a9 [MSP] Use MSP2_COMMON[_SET]_SERIAL_CONFIG for configuring ports
Configurator side of https://github.com/betaflight/betaflight/pull/9332
2020-01-15 09:33:50 +00:00
Nicolas Vanhoren
05ac30e101
Update README.md 2020-01-13 12:36:10 +01:00
Nicolas Vanhoren
54db304758
Update README.md 2020-01-13 12:35:03 +01:00
Nicolas Vanhoren
ace1becd21
Changed installation procedure for Linux user
That's just the same recommandation with more explanation as the old one was not very precise.
2020-01-13 09:26:24 +01:00
Miguel Angel Mulero Martinez
d8e3b9ee44 Sonar clean vtx.js 2020-01-02 15:11:00 +01:00
Miguel Angel Mulero Martinez
de2ce14ca7 Fix VTX when PowerLevel tag is empty 2020-01-02 12:43:52 +01:00