[DOm007]

My Revolution board was working completely fine with several hundred flights using a Next release when it stopped working while changing flight batteries. It seems to be stuck in the bootloader more. I'm able to get to the rescue settings and flash the bu_revolution.opfw but if I try to manually upgrade or upgrade and flash the firmware it times out while trying to boot after uploading the firmware.

If I flash with TauLabs the board works. But reverting back to the Next release or 15.09 it loops the bootloader process.

I make sure to only have either the Next Release or 15.09 installed at one time and never both installed at the same time. Currently have the Next Release installed.

Can someone please help me? I'm stuck and at a complete loss. And I hate being grounded. I need my FPV addiction.

Revolution
Device ID: 903
HW Revision: 3
Flash access: RW
BL version: 6
Max code size: 655260

Board name: Revolution
Firmware tag: 15.09
Firmware date: 2015-10-21 19:14
Git commit hash: c3f2fd0b
CRC: 734612222

Won't let me attach the UAV log file so here's a link to it.

https://drive.google.com/file/d/0B4NViVM0fVrWZjBsWW8zODNpcEE/view?usp=drivesdk

Sent from my SM-N920T using Tapatalk

[DOm007]

Firmware Screenshot.

[DOm007]

And I know no file is loaded, but I can't seem to get one to save on the FC.

Sent from my SM-N920T using Tapatalk

[DOm007]

Shorted the SBL pad, did the dfu script, tried both the bootloader and entire flash, rescued with the resurrect fw, booted, and still cycles the bootloader. Upgrading firmware still times out.

Sent from my SM-N920T using Tapatalk

[Brian]

Have you tried clearing settings?  You should be able to do that from the firmware tab in rescue mode.

[Mateusz]

I am not sure if this is the cause, but it could be hardware failure (sensor or other peripherial) that LP firmware fails to initialize and reboots, while other firmware may no simply check for that.

One could boot-up other firmware and check if all sensors are healthy and functional ? Maybe someone else has better suggestion...
Could as well be something else...

[DOm007]

Have you tried clearing settings?  You should be able to do that from the firmware tab in rescue mode.

Yes, I've tried erasing the settings but nothing happens. It fits day reading when flashing files or when trying to upgrade and erase.

Sent from my SM-N920T using Tapatalk

[DOm007]

I am not sure if this is the cause, but it could be hardware failure (sensor or other peripherial) that LP firmware fails to initialize and reboots, while other firmware may no simply check for that.

One could boot-up other firmware and check if all sensors are healthy and functional ? Maybe someone else has better suggestion...
Could as well be something else...

TauLabs shows all sensors as being healthy or all green.

Sent from my SM-N920T using Tapatalk

[Mateusz]

Can you try flashing resurrect image Cliff posted on forum?  Ef with sbl. It should clean up SPI external flash. Maybe electrostatic discharge caused some bad blocks...

[DOm007]

Are you flashing the right image ? bu = bootloader update, after that you need to flash actual compatible firmware (fw file).
TauLabs uses different bootloader that boots only their firmware afaik.

I only loaded TauLabs to test if it was working and if the sensors are healthy.

I only use LibrePilot and rescued with like bu_revolution.opfw or fw_revolution.opfw and _resurrect2-1509.opfw files.

Sent from my SM-N920T using Tapatalk

[DOm007]

Can you try flashing resurrect image Cliff posted on forum?  Ef with sbl. It should clean up SPI external flash. Maybe electrostatic discharge caused some bad blocks...

I did the jumper with the SBL pad and made sure the blue light was off and flashed it. Then removed the jumper and flashed the resurrect fw. But when it came to erasing the board nothing happens and it cycles the bootloader again.

Sent from my SM-N920T using Tapatalk

[TheOtherCliff]

bu is actually a program that must be run, so:
flash bu
run bu (important to run it!)
flash resurrection fw (use 1509 resurrection fw if you running 1509 and you can just leave that on the FC if you want.)
run resurrection fw

It should be running at that point and you can update firmware if desired.

If it isn't running, start with FC unplugged, press Rescue button, plug in FC, wait, press Erase Settings, answer yes, wait for 15 seconds while it erases, press Boot.

[DOm007]

bu is actually a program that must be run, so:
flash bu
run bu (important to run it!)
flash resurrection fw (use 1509 resurrection fw if you running 1509 and you can just leave that on the FC if you want.)
run resurrection fw

It should be running at that point and you can update firmware if desired.

If it isn't running, start with FC unplugged, press Rescue button, plug in FC, wait, press Erase Settings, answer yes, wait for 15 seconds while it erases, press Boot.

When you say run you mean boot, correct?

Sent from my SM-N920T using Tapatalk

[DOm007]

I'm sorry but I still can't get it working. When I flash bu and boot, I got rescue and I have to physically unplug the USB and plug it back in as the open file is grayed out. Then I flash the 1509 resurrection and boot. It then goes through the bootloader cycle. And the same if I try and do the erase it just cycles.

Sent from my SM-N920T using Tapatalk

[Mateusz]

//Update

Revo has two flash chips:
- STM32F405 is the main micro-controller 1Mb flash
- SPI flash for storing logs and configuration 2Mb flash

Revo has two bootloaders

[ STM32 Bootloader ] [ LP or TL bootloadr] [ LP or TL Firmware]

STM32 Bootloader you have access to when you short SBL pads and that can brick board if you flash wrong firmware.
Second bootloader is safe and can only boot firmware that matches it (LP boots LP, TL boots TL).

You have also different images of firmware
EF = Entire flash (LP bootloader + LP firmware)
BU = Bootloader updater (LP program that goes in place of firmware and flashes LP bootloader if it boots).
BF = Bootloader firmware (actuall LP bootloader alone)
FW = Firmware (actuall firmware alone)

1) Make sure your STM32 flash has correct images loaded up by using SBL method to flash ef*.bin image.
This makes sure both firmware and bootloader are right and compatible (less complicated way).
I am saying this because I don't know if TL bootloader will actually boot LP bu image. So just easiest is to use EF and done.

2) Revo has watchdog that reboots board if something fails or times-out on initialization. This can be flash or sensor.
Sensor you checked that all work and return values (mag, baro, accel, gyro). So what's left is SPI flash.
SPI flash may have different format for LP and TL. If TL have written to it, or when you were connecting battery you could have touched flash and cause electrostatic discharge (guessing) which could corrupt flash (potentially bad block).
In that case you need to flash ressurection image https://forum.librepilot.org/index.php?topic=208.0 to fix the potential problem.

There is a reason why Revo cycles, it cant initialize due to something failing. I hope providing this level of detail is helpful for you in figuring out what's wrong.