Monday, June 13, 2016

Eachine Blade 185 Recover Bootload boot Naze32 unbrick EB185

This happened soon after I had my EB185 hooked up to the laptop for the first time. I've been asked by a top forum contributor to document it. I had just installed CleanFlight and was running it for the first time ever. I was very unfamiliar with it (being my first exposure to Naze32 and CF) but quad seemed to be calibrated and working. The 3D model in CF was responding on the laptop screen as I moved the quad on desk.

I thought I needed to change the uart ports to be more like in EB185 manual. Well, you do ... but I mis-interpreted what they were talking about. After I inadvertently changed UART-1 Data away from MSP/115200 (by changing something else on that line) ... I could no longer Connect to quad. Basically, it appeared to be bricked.

As it turns out, the Naze32 is supposedly un-brickable. All you have to do is carefully short test-point Boot/Boot0 to 3.3volts, and plug-in it's power at the same time. The problem is that on the EB185, the Boot signal is not brought out to an easy to access test-point pad. So, in this case, you must use Pin#5 on STM32F chip itself.

Understanding what must be done, it seemed pretty hard to hold a probe on a single STM32F pin without it slipping and shorting to a nearby one ... not to mention holding a short while connecting power. Luckily, I ohmed-out Pin#5 and found it goes directly to the top solder-leg of the resistor right by it on the PCB.




Therefore, I carefully shorted these 2 points (marked in above pic in violet color) with a pair of sharp tweezers, while simultaneously connecting USB cable coming from laptop. Windows laptop detects Naze32 device in "Devices and Printers", but no sound from quad. Carefully lift and remove tweezers shorting the 2 points. At this point you should be done. It should connect now or the next time you reset the power (or re-connect USB).

I started CleanFlight and Flashed to: 1.12.1 NAZE 2016-4-10 (Stable). Recalibrated and reprogrammed. Good as new and back on-track. Note to self : Never do that again! Hope this helps.

27 comments:

  1. Thanks a bunch for your tip!!!

    I made the exact same mistake than you and I had given up hope to unbrick it ever again as I could not find which pads to short in order to hard reboot it.

    Your trick worked perfectly!!

    ReplyDelete
    Replies
    1. Excellent. Glad I could help.

      Delete
    2. i have tried to short that board out 5 or 6 times and i am still getting the same result. any suggestions?? i am so lost.

      Delete
    3. Maybe a different Revision board? Either try Pin#5 on STM32F chip itself. Or, with no power ... use ohm meter and verify that pin goes to that side of SMT resistor.

      Delete
    4. Spent hours trying to fix the connection issue. Tweezers are the key. I got a good connection and all is working again. Thanks again

      Delete
  2. polished my turd brick into shiny again. Thanks for this!

    ReplyDelete
  3. Do you know if there is any chance to get the telemetry data of the Naze on the Taranis via SBUS (FRSky X4R receiver). I found following info but actually not

    ReplyDelete
    Replies
    1. I couldn't get it to work either, but I'm not that familiar with Naze32. Post back here if you find a way.

      Delete
  4. Hi,

    I ttied it, for some reason it doesnt work. I short the 2 points, I connect the USB to the PC and there is no sound from the quad, it tries to connect to the PC but fails, same thing if I remove the shor and try to reconnect - it beeps but cant connect to the PC.
    Any thoughts on what am I doing wrong?

    Thanks.

    ReplyDelete
    Replies
    1. Not really. I just know what I posted, and only had to do it the one time. First step it to get Windows to detect it as a working USB Device. Once that is working, only then can you attempt a CleanFlight connection. Good Luck.

      Delete
  5. This comment has been removed by the author.

    ReplyDelete
    Replies
    1. Hi everyone, My drone just arrived, I removed it from the packaging, plugged the Receiver futaba and I connected it on the PC with the cleanfligth and opened normally I checked the option receicever mode "RX_serial" and on the switch it is 1 on and 2 off, Serial receiver provider is sbus, identifier RX is UART1 desable and UART2 enable. After performing this configuration "saved" and turned off the drone and then turned it on again. Now the PC recognizes the port and speed but does not connect in the cleanflight. What to do ???? It only beeps and does not open more in the cleanflight.

      Delete
    2. Mine has done exactly the same with FrSky S-Bus RX.

      Delete
  6. Thank You Very Much Tesla !!! Its working again !!

    ReplyDelete
  7. Thanks a BUNCH! You don't know how close I was to throwing this thing in the fireplace after bricking it. You save the day after I spent 6 hours searching the web for answers and ideas.
    Everybody made is sound so easy "just short the Boot tabs" Yea, right! Eachine forgot to provide the "Boot Tabs".
    I'm back in business again. #MAGA

    ReplyDelete
    Replies
    1. You are welcome. Glad to hear it worked. I'm trying to keep this blog online to help others. This has turned out to be a popular post.

      Delete
  8. I thank you. I can now get back to other issues I have with my 185. 3 volt LDO failed in the first five minutes of first flight. took awhile to fix that out. then did the UART-1 thing switching to Sbus. Now I need to figure out why motor 3 not spinning. think if I do get it in the air agian. full speed into a tree ha ha. thanks again

    ReplyDelete
    Replies
    1. You are welcome. Glad I could help. Yeah, I'm very careful when I fly mine. Turns out, it is pretty fragile (I guess the PCB?). Wish I would have known that when I bought it. The Blade-185 is ok, but I fly my Tyrant-180 more.

      Delete
  9. this will save all some time!

    Step 1 Make sure no boot sequence is clicked and full erase

    Step 2

    make sure you keep the board shorted whilst flashing once flashed then release the short and then connect to cleanflight/betaflight

    Step 3 you will need to do a second flash to newer firmware and your all back to normal.

    Hope this helps save the hours I spent on this fix.

    ReplyDelete
  10. what CF or BF Version does EB185 suupport?

    ReplyDelete
    Replies
    1. Does the latest version of http://cleanflight.com/ not work? That's the version I used last time I flew it. It's a Google Chrome App. I run it on Windows.

      Delete
  11. ok let me check
    CL 2.1.0 sees to be the latest stable version in CL

    ReplyDelete
    Replies
    1. That should work. I would be surprised if the developer purposely removed support for the (now) older flight-controllers like Naze32-Rev6.

      Delete
  12. ótimo trabalho! você realmente me ajudou bastante!!!!

    ReplyDelete
    Replies
    1. You are welcome. English is better for me.

      Delete

The stupid spammers have now forced me to approve each Comment before it appears (but I am usually pretty quick about it).