LibrePilot Forum
General Category => General Discussion => Topic started by: stubtoe on February 24, 2017, 12:12:35 am
-
Hello
I have the Mini CC3D Nano Flight controller and require it to be put into Boot-loader Mode so that I can Flash iNav Firmware onto it.
I notice that it has 4 soldered pads labeled 'O' 'K' and '-' '+' which if any are the Bootloader pads... thx joe
-
When changing brands of firmware or bootloaders, the Nano can be flashed either through the USB connection, usually using dfu-util.
https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+DFU
To change brands and flash a bootloader on the CC3D, you probably need to use MainPort and stm32flash. There is a also a "flash loader demo" that runs under Windows.
http://www.southquay3d.com/index.php?route=news/article&news_id=9
If you are putting non-LP firmware on it you will not be using the LP GCS to do it.
-
Hi... TheOrtherCliff
I've browsed through your links, thanks, and they seem to follow my Flashing procedure I used for my CC3D EVO Brd ( 35mm sq brd ) which used the Main Port + an FTDI adapter to flash the iNav Firmware, but it required me too short out the Bootloader pins/tabs momentarily before plugging in the FTDI adapter
So may I ask, where are the BL tabs on the much smaller Mini CC3D Nano brd (27x17mm brd)... I'm attempting to send pic's of both sides of brd...may not work!?
As I explained in the previous post there were 4 tabs O # K # - # + you can see them in the pic's if you get them
-
Googling
mini cc3d sbl
lead to this post.
http://www.southquay3d.com/index.php?route=news/article&news_id=9
Go down about 25% of the article and you will see a small white board on the right that is your board.
-
Go down about 25% of the article and you will see a small white board on the right that is your board.
The board in this thread is definitively not a CC3D Atom but a Chinese derivative without output servo pins.
@stubtoe Try following the pcb trace starting from pin 44, that the BOOT0 pin, your picture is too blurred to be used here.
This pin need to be connected to the +3.3V for bootloader mode. (see JP7 to the left in schematic)
(https://forum.librepilot.org/index.php?action=dlattach;topic=3136.0;attach=5393)
(https://forum.librepilot.org/index.php?action=dlattach;topic=3136.0;attach=5395)
-
On this board there's no easy way to put it in dfu mode. Pin 44 is connected directly to ground instead of through a resistor like the original cc3d. This means you can't just jumper the pin to 3.3v to get bootloader mode, you'd have to unsolder the pin f5soh mentioned and lift it or possibly cut a trace going to it
The easiest way is to do what the factory does, use a STLinkV2.
O = SWDIO
K = SWCLK
+ = +3.3v
- = ground
Something like this stlink clone from Banggood http://www.banggood.com/STM8-STM32-Emulator-Simulator-Programmer-Downloader-For-ST-LINK-V2-With-4Pin-Cable-p-1080420.html?p=SO28133399239201512V (http://www.banggood.com/STM8-STM32-Emulator-Simulator-Programmer-Downloader-For-ST-LINK-V2-With-4Pin-Cable-p-1080420.html?p=SO28133399239201512V) would work or there are lots of small stlinkV2 clones on eBay.
-
What a pain!
SBL is bad enough for the average user. :o
-
STLink flashing procedure is explained here :
https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+ST-Link
-
Hi Fella's
I was thinking about the post that TheOtherCliff had sent regarding the BL pads on the white FC brd pic - it was not my CC3D brd - but was a little hesitant to contradict him.
Im V pleased that you all have come up with solutions which I will pursue tomorrow and will report back...thanks...joe
I have by googling/poking/prodding/messing around, been able to load/Flash CleanFlight CC3D.bin Ver 1.10.0 (not sure why ''.bin''' rather than ''.hex'' !!??) via LibrePilot GSC using the Main Port - - and the Mini usb as the power input.
My aim is to Load/Flash iNav onto the Mini CC3D brd if at all possible...joe
-
Hello again, sorry for the delay
My CC3D Atom is no-more I bricked it when I tried to lift mcu pin44 leg and it broke of short - but did confirm ''hwh's'' statement that it was grounded, actually by a hidden track under the MCU. So thats one FC not to bother me.
But have a similar problem now with an OpenPilot revC CC3D EVO,
I cannot recover/rescue LibrePilot FW, methinks it is a Driver Issue !?
Observations:-
• Device Manager Port shows - STM32 Virtual COM Port (Port 22)
• GCS Connections Dropdown Box! shows - Serial COM22 ( should this showup as Copter
Control Virtual Post ??)
• On shorting the Bootloader pads then applying power to a PWM output the green LED is
steady the Blue LED goes out - should this show as 'slow fading'
My intention is to flash iNav 1.6.1 but failing that I would be more than happy with LibrePilot lates FW.
•• Isn't it always bothersome (pita) really navigating Bootloader Mode mthx...joe ••
-
Hi Fella's
To cut a long story long my CC3D Evo FC now works - it always did - meaning when it was connected to my HP Win10 Laptop it did.
When connected to my Desktop the CC3D would not connect/communicate with CF or iNav Configurator nor LibrePilot GCS.
So...looking in Device Manager of the Laptop showed me what driver enabled the FC too communicate with the CC3D - jotting down the Driver Ver No 10.0.14343.0 and asking Professor Google it turns out out to be.. a Win10 Media Creation Tool (what the hell is that all about) - downloaded about 5MB of data to the desktop - plugged in the CC3D ''Eureka'' ;D I then found it had iNav 1.5.1 installed. :-[
So.... I had previously used my laptop to configure the CC3D - thus by knowing that comms between CC3D and Desktop was unavailable to me due to my limited knowledge of computer manipulation and the fact that my ''little grey cells'' are a failing me. I had switched my allegiance too my Laptop.
Well Fella's all seems well at the moment, sorry for taking up your precious time but it's a good feeling for the likes of an old fogie to poke and prod a problem and finally get a measure of success, eventually...joe
-
Hello again especially 'TheOtherCliff'
I think I can understand now why there's not been many posts concerning my Bootloader Mode thread - I've been a little slow in picking up on the excellent ''Sticky Thread'' by TheOtherCliff namely - Unblocking: Bootloader/resurrection FW if you had non LP or CP FW on it. It must have covered all possible communicative combinations, but my magic fingers and failing 'little gey cells' have let me down.
I've read all of it and tried most of the steps to try and revert back to LP from iNav 1.5.1 on my CC3D Evo, me heads been agog with all the info, so I've finally given up for a while until I'm in reciept of the ST-Link gizmo, which hopefully may make things easier - arrive's around 27Mar - until then...joe
-
Ok Fella's
Received the ST-Link V2 - Wot to do now - I have iNav 1.5.1 installed - so please would someone take me through the proceedure of reverting back to LibrePilot
I've downloaded - STM32 ST-Link Utility V4.0.0 setup exe but do not see the STM32 ST-LINK Utility menu which updates the ST-Link donge firmware!!?? wot to do ...joe
-
post #7 ^^
-
Hello f5soh
I'm not sure what the hell I've been doing these last 24hours trying to find the ''ST-LINK Utility'' kept getting ''ST-Link Utility setup Mainenance Program ie (modify, repair, remove radio button thingy's !!? ) thinking this was - (am not sure but I think you call it) - the SW GUI Interface for programming ST controllers as depicted in the How To Recover Board, using the ST-Link, which you pointed me too - post7.
Eventually found the ST-Link Utility program in the Win10 Sart-up menu !? but going through the steps to 'Connect' to the device - I get - No ST-Link device detected
So f5soh is it now a question of another 'Win10' expletive mismatch with drivers or some such geeky thing, please help...joe
-
I never used Windows10, i only use WinXP and wrote the tutorial linked above.
I cannot help more than that, sorry.
You should register and download the needed ST program files from ST website.
https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+ST-Link#RecoverboardusingST-Link-Softwaresetup
-
Hello again f5soh
So you wrote a proceedure with a Steam Machine and expected it to work on a Win10 ::) :D - I too have a Steam Machine (XP) but that also has not been very helpfull in my quest to get ST-LINK v2 recognized - f5soh you must have ''The Knowledge'' I hope you don't loose it.
Anyone else out there that has other than an XP, ZX80 or a Cray that can help me - or even want to :'( ;)...joe
Yer know Folks it's an interesting learning curve, having to deal with these darn Bootloaders and such, 'Poirot' would be most proud'
-
Luckily Windows is not the only operating system in the world :)
-
Although I'm not fond of Windows10 it works just fine on it.
Below are captures from a brand new stlink clone that I just opened the package. The device manager/driver info, before firmware upgrade, after firmware upgrade, and connected to a revo.
The last picture shows two different stlink clones that look alike but notice the pinout printed on them, they're different and the wiring needs to be adjusted.
-
Morning hwh
You me and f5sh no like Win10 should have stuck with Win7.
I think your onto something, managed to change the ST-Link driver version as shown in your (pic1) to V 1.1.0.0. - tbh not sure how this came about, duh! with zadig maybe, don't want to mess around to find out, how, just yet.
So now my desktop recognizes the STLink dongle - yippee - but now the dongle does not see the Target = CC3D Evo :'( >:(
Hopefully I have attached a couple of screen shots - (don't see these in the preview to confirm) - anyway we're making headway and 'me little grey cells' is working overtime - an interesting exercise...joe
-
Hi hwh
More Pic's of wiring setup of ST-Link & CC3D Evo, may help with, wot to do next...joe
-
Try powering the board after you connect the STLink
This mean power the board using the output port or usb port
https://librepilot.atlassian.net/wiki/display/LPDOC/Recover+board+using+ST-Link#RecoverboardusingST-Link-FlashBootloaderwithSTLinkUtility
-
The only difference I see is you have the reset pin tied to 3.3v and I have it connected to my stlink RST pin so it can control the cpu. I'm not sure if that's necessary or not. Our webpage shows it being left disconnected so that must work for some people.
-
Here we go again on the BootLoader Merry-Go-Round
f5soh - Yes! powering the brd after connecting the ST-Link did the trick
hwh - the switched-link was to put the brd in BL mode if needed
Hey Fella's - hit another brick wall during the - Board's Firmware Update proceedure - due to it timing out. Attached a series of screenshots to which you budding Poirot detective's may shed some light on this ongoing saga...joe
-
Hello All
AN update - still not solved the problem with the CC3D Evo essentially now it's timing out during FW update!!?? :-\ - I'm not giving up on it , just put it to one side, in me head and on the bench. My Nemesis. :-[
Ordered another CC3D Evo a New Version I understand from (Banggood) - loaded with OpenPilot, I think, I do hope the move to LibrePilot is not going to be too challenging, can someone confirm this.
Wish me luck...joe
-
Hello Again
Good news - at last - been at it off and on for the last 2wks - truly - trying to get my CC3D Evo working/recognized by my Win10 Desktop.
Finally for the umpteenth time browsing through the Manual >Firmware Tab >Troubleshooting > Windows drive issues noticed the similarities of my problem in Symptoms >> then worked through the 11 steps of Possible solutions - Eureka... Rx data thingies lit up, phew! all is working Yippee.
Device Manager observation's - I expected the 'Driver' ( is that correct) to appear in - Ports (COM & LPT) dropdown but it appeared in USB devices dropdown list as 'CopterControl' - - why this is is where I get flummoxed.
Please note that when the CC3D is plugged into my Win10 Laptop the 'driver' appears as 'CopterControl Virtual COM Port (Com6)'
Comment:- if you please... bootloaders and drivers associated with the various Firmware platforms are a minefield, but I do hope in the near future with the immergence of more powerfull processors F3,4>>7,8 we may see a Plug & Play accross FW platforms...joe