Multirotor, multicopter and quadcopter discussion - The Drone thread

Something happened with the comms during the flash, it timed out and I cant connect to the naze. Trying to recover, when I plug in i just get a blue LED.


Looking at unbricking this, it says to use the bootloader pins?/pads?

Argh cant get any comms to the bootloader, I am trying to put a bit of solder between the two boot pads on the board, how do you do this?

EDIT: managed to get it back, phew :) but having issues when trying to flash to betaflight, keep getting

"STM32 - timed out, programming failed" which then bricks and I have to recover back to cleanflight by jumping the bootloader pins, which is a pain to try and recover.


Going to leave it for tonight, if anyone got any tips on what to use thats easy to short the two pads, let me know, tried a bit of solder trying to contact them but its not working well at all
 
Last edited:
You can flash Betaflight with the pins bridged, instead of recovering to cleanflight.

You are using the correct .hex file right? Silly question I know, but different flight controllers have different amounts of flash memory on the CPU
 
Yep for the naze

I'm.finding it difficult to find something that will bridge the boot pads on the board. Whilst that worked the first time with a bit of unheated solder metal. I flashed back to cleanflight. Tried again with betaflight failed again.

Now I cant connect to boot loader.

I need to try and make sure I'm using a decent metal and have decent contact on both the pads on the board when I'm trying to bridge/short them. Any tips? Seen online some people have been using tweezers or plyers?

Trying to do it without having to take the frame apart
 
Anyone? going to try and make a prong out of a paper clip but use a solder wire loop.

Hopefully this will be good enough to bridge the two boot pads
 
On the way to work this morning, I saw a car which had a company slogan on the side of it for offering drone services to do flights over construction projects. Do people actually pay for these services? Seems like someone got a new toy for xmas and thought to make a job of it! lol
 
On the way to work this morning, I saw a car which had a company slogan on the side of it for offering drone services to do flights over construction projects. Do people actually pay for these services? Seems like someone got a new toy for xmas and thought to make a job of it! lol

Of course they do. You do realise that the vast majority of vertical tracking shots or aerial footage you see on the BBC these days is shot from drones?
For newsreel stuff and documentaries most people are flying an S900 or S1000 with a Panasonic GH4 or Canon 5D MK3 slung underneath. I've even seen Inspires and Phantoms being used in BBC shows. In fact, a documentary I was watching last night about the migrant crisis had aerial shots that were quite clearly shot with a GoPro, probably slung underneath a Phantom 2.

Hollywood is also using larger craft to fly RED Epics and similar.

There is a big industry for aerial photography and the UK is leading the world with it's regulation. We were one of the first countries to have in place a system of qualification and regulation for the control of SUASs.

Talk to Russ on this forum. He's a qualified SUAS operator and his business do a lot of aerial work.
 
Anyone? going to try and make a prong out of a paper clip but use a solder wire loop.

Hopefully this will be good enough to bridge the two boot pads

I just use the tip of a flat blade screwdriver that is big enough to bridge the gap.

Are you using the latest version of cleanflight configurator (1.2.1) and all the STM32 drivers installed ok?

I would;

1) Bridge connectors on bootpads, flash back to latest cleanflight

2) Confirm the naze is working as intended

3) Try flashing cleanflight without the bootpads bridged

4) If that works, flash betaflight.

Have you flashed a local firmware before and it worked?
 
I'm going to mod my transmitter to hopefully increase its range...shall I just yoink an aerial cable from an old router or should I purchase something more specific?
 
I just use the tip of a flat blade screwdriver that is big enough to bridge the gap.

Are you using the latest version of cleanflight configurator (1.2.1) and all the STM32 drivers installed ok?

I would;

1) Bridge connectors on bootpads, flash back to latest cleanflight

2) Confirm the naze is working as intended

3) Try flashing cleanflight without the bootpads bridged

4) If that works, flash betaflight.

Have you flashed a local firmware before and it worked?



I will have another attempt at bridging, going to try a few different metals/tools.

The solder wire worked once, but its bendy so doesnt contact properly, I did try a screwdriver but didnt work.

Once I get it back on cleanflight, I will make sure all drivers are installed/will re-install then try again


EDIT: tried paperclip which I knew had good contact, didnt work, still getting "no response from the bootloader, programming failed"
 
Last edited:
Right managed to flash it back to cleanflight

I am going to try and use a spare laptop and do this with a different windows install just incase its a driver issue when it tries to flash to betaflight

I have heard baseflight is better to use at flashing ? rather than using cleanflight, as clearly there is an issue flashing to betaflight here
 
Right managed to flash it back to cleanflight

I am going to try and use a spare laptop and do this with a different windows install just incase its a driver issue when it tries to flash to betaflight

I have heard baseflight is better to use at flashing ? rather than using cleanflight, as clearly there is an issue flashing to betaflight here

I think the issue is either with your hardware or the way you're doing it tbh. A large amount of people flash Betaflight through cleanflight without a hitch!
 
27mhz, 35mhz, 72mhz, 2.4ghz, DSR etc?

Either video transmitter from quad to goggles or the radio you use to fly it :)

If it's the 'radio' itself then depending on the model you might gain some range.

Oh, it's 2.4ghz :p

I've just seen a few articles on changing them so figured I'd give it a go considering I have a spare TX now, seems easy enough :)
 
Same again on another laptop,

installed the latest STM32 drivers, cleanflight configurator 1.2.1

loaded local firmware (betaflight_2.5.3NAZE.hex) and flash

get a "STM32 - timed out, programming failed"


If I try to flash with cleanflight from a local cleanflight hex file, again it fails, but if I flash firmware (online) it works

Tried a reboot of laptop, it started flashing betaflight, then failed.


So it seems contained to an issue flashing from local files, I will leave it for now until I can find out whats going on.
 
Last edited:
Back
Top Bottom