Phantom on 4.1.1 decided to upgrade to 4.1.7 (last 4.1 version).
Flashed with "full chip erase " deselected and "no reboot sequence" deselected.

The "Flashing" yellow bar is now stuck at around 50% and nothing happens.
FC only has one red LED on.

What can I do?

Here is the log on top of BetaFlight

[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- Serial port [color=var(--accent)]successfully[/color] opened with ID: 6[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- MultiWii API version: 1.42.0[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- Flight controller info, identifier: BTFL, version: 4.1.1[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- Running firmware released on: Nov 15 2019 12:55:17[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- Board: MATEKF411(STM32F411), version: 0[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- Unique device ID: 0x2e00423439510a38313437[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- Craft name: PhantomRJA[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:40 -- Arming Disabled[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:43:42 -- CLI mode detected[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:27 -- Serial port [color=var(--accent)]successfully[/color] closed[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:29 -- Using cached builds information for jobs.[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:29 -- Using cached release information for firmware releases.[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:30 -- Using cached release information for firmware releases.[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:50 -- MultiWii API version: 1.42.0[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:50 -- Device - [color=var(--error)]Rebooting to ROM BOOTLOADER[/color][/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:51 -- USB device [color=var(--accent)]successfully[/color] opened with ID: 1[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:51 -- Detected device with total flash size 512 KiB[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:51 -- Read protection not active[/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:44:59 -- Erased 496 kB of flash [color=var(--accent)]successfully[/color][/color]
[color=rgba(255, 255, 255, 0.6)]2020-10-04 @ 10:45:26 -- USB device [color=var(--accent)]successfully[/color] closed[/color]

First of all, try a different USB cable.

Ok well yeah think I've bricked the FC

After reading a few (misguided) advice I clicked on the exit DFU and fumbled with the cables and now the FC does not come up as a USB device anymore so cannot connect to it anymore.

I'm starting to get disheartened by my ignorance and clumsiness

Mac OS over here. Can connect to my othertwo FCs without problems.

(04-Oct-2020, 10:03 AM)SnowLeopardFPV Wrote: First of all, try a different USB cable.

Hi Snow,
changed USB cable but no comm device comes up and only one red LED on the FC ...

Guess I might be needing to press the boot button on the FC? How is the VTX board connected to the FC one? I just need to pull it upwards to disconnect it and access the FC board?

So I managed to disassemble the stack.
Pressed the boot button on the FC.
Started BF and found DFU as one of the ports (the usual port does not appear anymore)

Tried reflashing. Does the erasing fine, then writes to about 50% and stops there ... bummer ...

Could it be that it is not measuring the amount of the FC memory?

Is it expected that the usual comm port does not come up until the flash is succesfull and I only see that DFU port?

That's weird. I updated mine the other day with no issues. I'd be surprised if it's an issue with the FC.

Are you using a Mac or a Windows machine? Do you have another computer you can try it on?

Mac only household. Have another Mac to try but don't quite expect things to be any different.

Is it expected I'm not seeing the usual comm port I connect to in Betaflight while the FC is in this state?

(04-Oct-2020, 10:53 AM)rjalex Wrote: Is it expected I'm not seeing the usual comm port I connect to in Betaflight while the FC is in this state?

You won't see a normal COM port while the FC is in boot mode. I'm not a Mac user so I'm not familiar with how the ports work on a Mac. All I know is that you don't need any drivers installed like you do under Windows.

Here is the full sequence in a video ....



hope this gives you a clue

When I click on that link I just get...

"Sorry, we couldn’t find that page"

OMG maybe I got it Don't know why but seemingly was flashing with the wrong target ????

Now flashed with MatekF411 and it succeeded !!!!

Is this the problem I had? OMG ashamed to have caused this commotion

Now I have a diff and diff all from 4.1.1 but have flashed the latest 4.2.3 ... in this situation can I apply the 4.1 diffs to the new 4.2? If not how to restore a good setting to the new 4.2.3 Phantom?

Thanks again

Video link fixed but also 99.99% irrelevant now

Yes, that will almost certainly have been the issue, especially if you were trying to flash a target that had a larger binary size than the available flash memory inside the STM F411 MCU.