Important fail/warning to test and document

[datamafia]

I just bricked a FC w/ the most current GUI. Here's how I did it and how people should avoid and what seems to have happened.

Set Up

• OS: MaOSX 10.12.2 (16C67). New 15" MBP.
• FIRM: v1.3RC30
• GUI: v1.16.15

Procedure

1. I downloaded the bundle
2. installed the DMG
3. Closed other GUI
4. opened new GUI
5. noticed my machine was very laggy, especially track pad
6. held down boot button
7. added USB/power
8. entered firmware update, selected firmware, began process

Almost instantly I got an error 4 (not sure, I wish I screen captured the error). The flight controller bricked. Power still ran through as my RX that is powered by the FC was working.

And then I got a kernel panic and the machine force quit.

Symptoms of Brick:

• No lights
• not seen by OS
• not seen by GUI
• same for battery connected or USB

Issue

The silabs (?) driver and GUI required a restart. I reviewed the shutdown report and it was the USB and drivers that failed.

Fix

Restart after adding a new GUI.

I wanted to put this somewhere for others to find and ideally have it make it in the documentation somehow.

Post Mortem

Once restarted I flashed 2 spare KISS FC, one on older GUI and one on new GUI. No problems, both are functioning.

Did I miss a warning about reboot required?

[fedorcomander]

i assume all drivers are OK before using the gui. ;)