Skip to content
bionic24 edited this page Jan 22, 2013 · 3 revisions

There are two techniques, both of which finish up the same way, but the Halt method is more user-friendly whereas the Rescue method will work with bricked boards

#Halt method

  • Start the GCS
  • Go to the Bootloader tab
  • Press the Halt button
  • Wait until the GCS shows that the board is connected
  • Click Open... button
  • Choose the appropriate firmware. Tau Labs firmwares are prefaced by fw_ and end with .tlfw. For instance, if you are flashing the FlyingF3, this will be in builds/fw_flyingf3/fw_flyingf3.tlfw.
  • Click on Flash button
  • Once flashing is completed, power cycle or click the Boot button

#Rescue method

  • Start the GCS
  • Go to the Bootloader tab
  • Press the Rescue button
  • When the dialog requests, connect the USB port
  • The blue led should now be constantly on.
  • The GCS should now show that the board is connected
  • Click Open... button
  • Choose the appropriate firmware. Tau Labs firmwares are prefaced by fw_ and end with .tlfw. For instance, if you are flashing the FlyingF3, this will be in builds/fw_flyingf3/fw_flyingf3.tlfw.
  • Click on Flash button
  • Once flashing is completed, power cycle or click the Boot button

You're done, GCS should now be showing data from the board.

Note: The STM32F3Discovery board has 2 onboard mini-usb connectors. The USB connector marked USB USER is used to connect the board to the Ground Control Software (GCS).

Clone this wiki locally