ORBIT 0.10.B: Bluetooth MIDI build

Download orbit-ble.fwsc for the M-VAVE FM-1. This is the Bluetooth MIDI
variant of ORBIT 0.10.0 and includes all of its changes: MIDI
clock out, quiet drum GRID editing with black-key recording, and the OCT- +
OCT+ controller tap. Both builds use the FM-1_900 installation identity.

Bluetooth MIDI

• Turn the radio on with MENU > SYSTEM > BLUETOOTH. It's off after
  every restart and advertises as ORBIT FM-1.
• Everything ORBIT sends over USB MIDI also goes out over Bluetooth: notes,
  controller mode and, new in this release, MIDI clock with START/STOP
  when GLO > SYSTEM > SYNC = OUT. Outgoing SysEx isn't sent.
• To follow a Bluetooth MIDI clock instead, set SYNC = USB. Bluetooth
  input shares the USB route.

Bluetooth now starts after other firmware

Some FM-1 units showed FAILED: NO RF TRIM IN FLASH. Bluetooth needs the
radio calibration that the stock firmware stores in flash, and other
firmware that used the same area for the FM6 bank or a user sample had
erased it. ORBIT can't rerun the radio calibration itself, because the SDK
routine waits forever for a hardware flag on this board.

0.10.B looks for the calibration in this order: the stock record, the copy
ORBIT kept from an earlier start, and then built-in recovery values, which
ORBIT saves in its own settings area. The stock record always wins when
it's present, and ORBIT never writes over it. The recovery values aren't
calibrated for your unit, so range may be shorter. They haven't been tested
yet on an FM-1 whose stock calibration was erased. The only remaining
startup error is FAILED: RF READ FAIL, when flash can't be read.

Unchanged from 0.9.B

• Melodic built-in samples are replaced by same-named FM voices; PERC drum
  samples and USR samples remain. See the
  complete sound list.
• The delay line is about 0.74 seconds, or 0.37 seconds per side in PING.
• FM6 bank and USR4 writes over a stock radio calibration are refused.

Tested

Development builds with these changes were installed on an FM-1. The
device owner confirmed Bluetooth operation, the new clock out and the new
controls. Bluetooth latency, worst-case radio/audio load and stack
high-water remain unmeasured. The SAMPLE/GRAIN static-cost baselines are
still exceeded by this variant, unchanged from 0.9.B. See the
validation record.

Compare both sound builds in the
web emulator. Its audio comes
from the firmware C engine; it doesn't emulate Bluetooth.

The Bluetooth integration is ported from Hortator 4e40f27 by DEADACTIVE,
with felucca-ble/Felucca credits and SHA-256-pinned JieLi SDK inputs. See
LICENSING.