They definitely could go wrong after flashing the wrong firmware, but that can't be done accidentally, there's a warning and a checkbox has to be set to flash incorrect firmware.

If you connect via C2 interface and prior to doing anything else make a flash memory dump, I may be able to compare for differences and artifacts to find out what happened.
To reach the C2 pads you don't need to desolder anything. Have you identified them already btw?

(07-Feb-2017, 07:23 AM)AndreyM Wrote: They definitely could go wrong after flashing the wrong firmware, but that can't be done accidentally, there's a warning and a checkbox has to be set to flash incorrect firmware.

If you connect via C2 interface and prior to doing anything else make a flash memory dump, I may be able to compare for differences and artifacts to find out what happened.
To reach the C2 pads you don't need to desolder anything. Have you identified them already btw?

Haven't identified the C2 interface on my escs yet but have looked around online and have an idea what I'll be looking for. To make the connection and do the flash dump can that be done from an arduino or do I need to get a USB connecting tool?

I use a Arduino UNO R3 clone, any Arduino should work.

So looking at my ESCs I have found the four "solder pads" but they are super tiny. Do I need to solder to these things or can I rig up some way to just hold jump cables to them?

Can't get a picture just yet.

On the plus side, I'm learning.

You need only 2 of them, I usually just touch pads with a 2-pin header connector. But it's a bit hard to ensure good contact when you're trying to operate BLHeliSuite at the same moment, so you may be better off soldering to these 2 pads.

Really sorry to keep being after you for help but I'm new to all this. 

Got the wrapper off my ESC. My issue now is I have no clue how I'm making the connection. Where on the ESC and where on the Uno? I'm finding a lot of how-to videos but they're all using three wires. 

I think I'm looking at the four round pads, right?

Maybe I see why I'm confused. These are the same board as mine. http://www.banggood.com/4X-Racerstar-RS2...mds=search

I see in their setup they have a ground wire paired up with the data wire. Mine don't have this.

Four round pads are left-to-right GND, VCC, C2CK, C2D.
You need only the last two. On Uno, C2CK goes to D11, C2D to D12. I've taken this info from here: https://github.com/4712/BLHeliSuite/blob...pinout.pdf

Well the UNO got set up properly but I can't connect to the ESC. I expect it's either my holding the wires or something in the jury-rigged harness I put together. Either way I'm going to see if I can't get someone to help me out tomorrow then I'll report back.

Did you connect power to your ESCs? Show a photo.
Did you flash your UNO to BLHeli Box?

Uno is flashed to BLHeli 4-way interface. BLHeli says it connects to the interface. We tried again with and without my makeshift harness. My daughter was cycling the power so I could concentrate on keeping the leads on the pads. Still no luck.

Connection made on BLHeli


Leads on the Uno


Connection on the ESC - Near pin is black lead from UNO ~11, far pin is blue lead from UNO 12


Aislin hits read setup and plugs in the battery while I hold the connector to the ESC. This is the result.


This is the 'harness'


Also tried it with just normal leads.

You have SiLabs BLHeli bootloader programmer interface selected, it should be c2 (4way-if).

Alright, I've made some progress but regrettably was not able to work out how to pull down the flash files for you.
Good news is I have four working ESCs again. 

Ended up using four leads on the Arduino Uno: Gnd, 3.3v, 11, 12 and connected to the ESCs without using the flight battery. This let me verify the connection was on the right pins with an LED inline with the ground. 

It took a few tries to get everything steady enough to connect. On connecting and reading the setup we got this message. 


Went with yes which brought us here:


To here:


Took a few tries, disconnects and reconnects as we would get this message a lot (would that error file be helpful?):


But finally was able to hold the connection flat enough and steady enough that we got a Flash complete message. Disconnected then pulled it all up in BLHeli Configurator through the FC interface and am now seeing all four ESC and signs of life in all four motors. 

Tried to throttle up through the transmitter but didn't get a response so I'm assuming there is some configuration I need to work out still but will get back to it tomorrow.

Hoping to fly again soon.

Glad you solved it. Make sure you really need G_L firmware and not G_H.

(15-Feb-2017, 10:16 PM)AndreyM Wrote: Glad you solved it. Make sure you really need G_L firmware and not G_H.

Someone with the same drone as mine said his were set with C-H-15 from the factory but G-L-20 is what comes up by default when I connected and I can't find C-H or G-H software in the program list. Is this something I have to download? Where would one look to verify what is actually intended to be used?

This list says C-H-15 as well https://github.com/blheli-configurator/b...ledge-Base and looks like the entry for the Eachine Wizard was only added 10 days ago.