(14-Aug-2017, 07:39 AM)unseen Wrote: The SP Racing F3 does not use DFU mode!

I flashed 2 evo boards for a friend and they installed themselves as dfu units on my system... But if it works without, even better. edit. Just realized it's not the same for evo- and older boards.

(14-Aug-2017, 04:32 PM)Adamski321 Wrote: I keep getting no response from boot loader?

Could it be that in configurator top right there's more than 1 com port to select?

(14-Aug-2017, 04:32 PM)Adamski321 Wrote: I keep getting no response from boot loader?

---

Just to make sure, this is my board: https://www.banggood.com/Upgrade-NAZE32-...ds=myorder

So is it the 'SPracingF3' FIRMWARE????

Yes, that board is a clone of the SP Racing F3 flight controller.

(14-Aug-2017, 04:35 PM)Adamski321 Wrote: If I have the STM32 drivers installed, will this affect my flashing? Should I uninstall them do you think?

You need to check in your Device Manager in Windows to see what driver is loaded and which COM port is allocated when you plug the board in.

That will tell you if it's using the correct drivers and also if you are selecting the correct port when flashing.

(14-Aug-2017, 06:12 PM)fftunes Wrote: I flashed 2 evo boards for a friend and they installed themselves as dfu units on my system... But if it works without, even better. edit. Just realized it's not the same for evo- and older boards.

Yeah, the F3 Evo is a completely different hardware design and uses VCP and DFU modes to configure and flash. The old SPR F3 has a CP2102 chip onboard and uses that for both configuration and flashing.

(15-Aug-2017, 07:40 AM)unseen Wrote: Yes, that board is a clone of the SP Racing F3 flight controller.


You need to check in your Device Manager in Windows to see what driver is loaded and which COM port is allocated when you plug the board in.

That will tell you if it's using the correct drivers and also if you are selecting the correct port when flashing.

I only have COM3 available. And I have it assigned to a Silicon Labs CP210x driver, which for all my research seems to be correct? Unless I am wrong?

---

I think I'll video everything I have installed, and what responses I get, then upload it to youtube and post a link here? Then hopefully someone may be able to diagnose an issue? thanks for the help everyone!

This works on F4 boards every time, worth a try:

Jump bootpads
connect board to configurator
close configurator
remove jumper from bootpads
open configurator
load firmware
flash firmware

Good luck!

(15-Aug-2017, 05:00 PM)Adamski321 Wrote: I only have COM3 available. And I have it assigned to a Silicon Labs CP210x driver, which for all my research seems to be correct? Unless I am wrong?

---

I think I'll video everything I have installed, and what responses I get, then upload it to youtube and post a link here? Then hopefully someone may be able to diagnose an issue? thanks for the help everyone!

That's how it should be.

I'm not sure what more I can say to help. If you have the right driver and you are selecting the correct port when trying to flash then it should just be a matter of getting the manual baud rate correct.

I trust you have tested the USB cable with another device (like a smartphone) to make sure that the cable is a proper data cable?

(15-Aug-2017, 08:22 PM)unseen Wrote: That's how it should be.

I'm not sure what more I can say to help. If you have the right driver and you are selecting the correct port when trying to flash then it should just be a matter of getting the manual baud rate correct.

I trust you have tested the USB cable with another device (like a smartphone) to make sure that the cable is a proper data cable?

I have a replacement board coming, kind of hoping this one was broken!

That is a link to a YouTube video I have created to demonstrate my problems! Any help is greatly appreciated!

After you plug in the USB and open Betaflight, DON'T attempt to "Connect". Just click on the flasher (third icon down) and try to flash. (Also, if that doesn't work on its own, you might try turning OFF full chip erase.)

(16-Aug-2017, 07:16 PM)sloscotty Wrote: After you plug in the USB and open Betaflight, DON'T attempt to "Connect". Just click on the flasher (third icon down) and try to flash. (Also, if that doesn't work on its own, you might try turning OFF full chip erase.)

Thanks but I have tried that and still no good ? Thanks though

---

(16-Aug-2017, 07:16 PM)sloscotty Wrote: After you plug in the USB and open Betaflight, DON'T attempt to "Connect". Just click on the flasher (third icon down) and try to flash. (Also, if that doesn't work on its own, you might try turning OFF full chip erase.)

Thanks but I have tried that and still no good ? Thanks though

"This video has been removed by the user"

????

(17-Aug-2017, 05:02 PM)unseen Wrote: "This video has been removed by the user"

????

Hold on, I'll post a link soon not sure what's gone on there.

Here's my problem

Looking at your vertical video, you have the correct driver installed and your boot pins are working properly. Pressing "Connect" while in bootloader mode will not work. Bootloader mode is for flashing only!

I also see that you have not selected "No reboot sequence". If you don't select this option, the first thing the Firmware Flasher tries to do is to reboot the flight controller into bootloader mode. As you have already forced it into bootloader mode by jumping the boot pins, the reboot operation fails.

Try exactly these steps:

1. Jump boot pins.
2. Connect USB to computer.
3. Start Betaflight Configurator and select "Firmware Flasher".
4. Select SPRACING F3 as the board.
5. Select the version you want to flash.
6. Press "Load Firmware (Online)".
7. Set "No reboot sequence".
8. Clear "Flash on connect".
9. Set "Full chip erase".
10. Set "Manual baud rate" and select 115200.
11. Press "Flash firmware".

If this still does not work, try selecting 256000 or 57600 in step 10 instead.

If you still don't have any luck, try a different USB cable. If you still don't have any luck, please record a new video showing what you do and turn the phone to landscape mode when recording the video so that we have a better chance of seeing what you are doing!