The h8 blue board has a strange issue when flashed with "Keil", and it needs specific workarounds.
Also, the board pads are mislabeled,
the pad marked CLK is actually DAT, and viceversa.
Windows:
This only affects the blue board and the Keil program (windows)
The actual flashing instructions are similar to those for the CG023 and other stm32 based quads, in
this thread
An error comes up after the st-link is disconnected from the usb port . This results in a "communication error" popup.
To clear,
1. disconnect the st-link from usb and reconnect
2. Use the
st-link utility (
mirror) , connect to the board, and then disconnect, using the toolbar buttons or menu items
At this point the board should be flashable again in keil, until the usb is disconnected again.
Alternatives to the st-link utility:
You could also clear the error in other ways:
1: Flash any other non-blue quad using the st-link
2: Run the ST-LinkUpgrade.exe utility present in your keil folder, and upgrade the st-link
3: Use openocd to connect to a board
4: (included in above instructions) Use the st-link utility to connect to a board
Note: the board needs to be powered by a battery while flashing / erasing.
Sorry about this, the bug is beyond my control.
Hex file:
The hex file compiled by keil can be found in the "Objects" folder , h8blue.hex , and can be flashed with st-utility if needed
Linux:
Use instructions in file
INSTALL.md . There should not be any issues except that the board pads are mislabelled. Gcc compiles somewhat larger, and as such you may need to turn off some features and watch file size, as the defaults are not always checked to fit compilation by gcc. You can see compilation status at
travisCI
Code: (
github)
Video of the procedure by
gioy808 (
rcgroups)
Video by
ArbitraryNotion: (
rcgroups)
Flashing using the st-utility only (
post)
Binary location(use only if you have trouble compiling your own) (
github)
Devo telemetry setup:
RCG Post