• Welcome to RCCrawler Forums.

    It looks like you're enjoying RCCrawler's Forums but haven't created an account yet. Why not take a minute to register for your own free account now? As a member you get free access to all of our forums and posts plus the ability to post your own messages, communicate directly with other members, and much more. Register now!

    Already a member? Login at the top of this page to stop seeing this message.

Silent outrunner and ESC for less then $60

Thank you for the information "thumbsup" .
But what does it mean "no full firmware" ??? :shock:
What is the PB4 bootloader and what is the iflight firmware?
In your g-drive there is firmware for the iflight. Can i use this one?

cu
 
Last edited:
Thank you for the information "thumbsup" .
But what does it mean "no full firmware" ??? :shock:
What is the PB4 bootloader and what is the iflight firmware?
In your g-drive there is firmware for the iflight. Can i use this one?

cu

the I flight firmware in my drive is for tiny 1408 motors in a scx24 so you should only use it for that application, unless you flash the normal iflight target from github right away. other wise the esc and or motor will get really hot from too much power.
 
Now i have another problem. I can not connect to ST-Link. The STCube did not recognize my ST-Link. I powered my esc with 5V from ST-LINK USB i connect clock and Data to ESC, but no connection. On the ESC the LED is off. LED in Linker ist on.
 
Now i have another problem. I can not connect to ST-Link. The STCube did not recognize my ST-Link. I powered my esc with 5V from ST-LINK USB i connect clock and Data to ESC, but no connection. On the ESC the LED is off. LED in Linker ist on.


I have the exact same problem....
Didn't solve it yet but looks exactly the same.

I even open the ST-Link to check if the pin labels on the outside were matching the labels on the electronic board and yes, everything was matching.
 
Last edited:
I don't recall installing drivers in windows 10.
Mine only has a blue light on in the st-link usb tool.

Never trust the wraith led. It means nothing in am32.

I have burned up a few of the ST-link tools by plugging them in with a battery connected.
I think even just leaving it plugged in to the usb for a long time can burn them up, they get hot.
It could be broken?
 
I never had a battery on the ESC so that was not it.

When I open STM32Cube with no ST-Link connectec, on the right side, on the ST-Link configuration, it shows "No ST-Link" and blank on the frequency.
When I connect the ST-Link and refresh I have in Serial number "S", I have 4000hz on the frequency, 3.27v on the target voltage and firmware V2J37S7.

But, if I click "connect" on the top of this menu nothing happens and I still have the red dot and "not connected".
Same result if the ESC is connected or not to the ST-Link and same result if I connect the ST-Link and open the STM32Cube after.

I have downloaded and installed the latest drivers and same thing.
 
I dont know, This is what mine looks like, with some added text for explanation.
I have hade a dozen st-links and burned up half of them being stupid.
But I dont remember getting your error.
Mine are all the cheapest Chinese knockoffs money can buy.
None of mine are actual ST brand ST-links.


Pretty sure this is the driver


I had a different driver earlier that I didn't install myself, windows or the ST app handled it, that also worked fine.
I got this driver because of something to do with knockoff Arduino Nano boards.
It was probably totally unnecessary for that too.
and I doubt it will fix anything but no harm in trying I suppose.
 
Last edited:
I dont have this driver on my PC.
STCubeProg doenst Install this driver automatically.
I will Check this later and Install manual.
I got a second StLink today.
 
I didn't realize I left my Arduino plugged in so that's probably not a driver you need.

This one is it. It looks to be installed as part of windows 10. As all 3 driver files are provided by Microsoft.
 
Hi guys
this is my update.
the first ST-Link was broken :cry:. When you plug in USB there should be a blue LED. :ror:
the second one have this. I connect +3,3V and - from ST-Link to ESC + and - .
then connect swclk to clk on ESC,
then swdio to data on ESC.
Open CubeProg plug in USB and refresh ST-Link and voilà i can connect. "thumbsup"
I did the optionbyte and a full chip erase, all seems good.
But i can not flash firmware :cry: i tried many things most i can flash 10-30% then the connection lost.
After few hours i tried with +5v i can not connect...
So i plugged the USB start CubeProg connect with +3,3V OK, disconnect and switch wire to +5v(with connected USB) voilà i can connect.
Try to flash bootloader PB4v8 - OK
Try to flash Iflight 1.65.bin - OK
Try to flash Eeprom v1_7c00.bin from AlkaMotor - OK
Connect ESC to HGLRC F4 flightcontroller Dshot300, open ConfigTool 1.67 change Parameter according to Voodoobrew Video, save, finish.
Today i got my new Motor and will try out if it is running.
cu


BTW:
Is firmware iflight 1.65 special for crawler? If not did anybody know if there comes a special firmware for crawler?
 
Last edited:
When I read all the trouble people have with this I rather wait for a Holmes solution. I am a tinkerer but that here would break my nerves...seriously:lmao::mrgreen:
 
well I have no trouble with wraith32 and iflight both were successful on the first try and works perfect :ror:

Good for you but that is obviously not the case for many.:mrgreen:
Still have my hopes up to get something from HH
wxp2p3ga.jpg
[/URL][/IMG]
 
Back
Top