[help needed] 1993 Miata 1.6l (stock so far)

[stefanst]

Hi,

I'm setting up a rusefi for one of our friends from the NJ Miatas group on FB- Jeff.
I'm trying to set this up to be a full stock-replacement and yet fully expandable.

And here comes the first problem:
I had good solid serial communication from the dev-console. But TS was losing connection and reconnecting every few seconds. So I tried to flash new FW. Couldn't get the STM utility or the "flasher" in the console to do anything. Tried programming via built-in micro-USB and via USART with external ftdi. No-go. Communication still worked.

Then I played with it some more. Now I can't get any serial comm going anymore. Neither via USART and internal Micro-USB. Discovery board is unplugged, Power LED is solid red. LD1 is flashing red (maybe 1s on/off). LD5 is solid red.

I'm probably missing something really simple. But what?

Edit: When I plug in the Micro-USB, I get a green light, but no serial port detected. If I use an external ftdi, I see it as a serial port, but still no comm.

[kb1gtt]

Have you updated the SWD programming chip on the discovery? That should be done when the discovery is by itself and powered via USB. As well remember that after it is flashed it will reboot and will probably take like 15 minutes for the drivers to install on windows as it times out trying to find them at Microsoft servers. Once it has the latest SWD firmware in the programming chip, let us know if it has any more communications problems.

[AndreyB]

Couldn't get the STM utility or the "flasher" in the console to do anything

Let's start by fixing this - it's just not right to play the uart flashing game.

Did you ever connect another discovery to this PC? Do you have ST drivers installed? Do you have the "installing drivers..." animated icon? Sometimes you see the "installing drivers..." animated icon for some ridiculous amount of time, but you have to wait and let it do it.

Switching to a different USB port would poke it to re-attempt the driver installation.

[stefanst]

Couldn't get the STM utility or the "flasher" in the console to do anything

Let's start by fixing this - it's just not right to play the uart flashing game.

Did you ever connect another discovery to this PC? Do you have ST drivers installed? Do you have the "installing drivers..." animated icon? Sometimes you see the "installing drivers..." animated icon for some ridiculous amount of time, but you have to wait and let it do it.

Switching to a different USB port would poke it to re-attempt the driver installation.

It's the same computer I am using for the '03, so I doubt that's it. I also tried re-installing the drivers. But of course there may have been one of those friendly Microsoft updates in the meantime. I'll try the other board tonight.

[AndreyB]

Do you want to get yourself couple of spare http://www.mouser.com/Search/ProductDetail.aspx?qs=mKNKSX85ZJejxc9JOGT45A%3d%3d ?

About the current state of the board - do you have the blue LED blinking?

[AndreyB]

Do you have latest ST Link console installed? Could it be that I've installed newer firmware into the board and you have older ST console which also means older incompatible drivers? That's a random theory nothing more.

I am on ST link console 4.0.0 at the moment.

[stefanst]

Blue LED is not blinking and I should have ordered spares last week when I had a Digikey order anyway. Damn.

STM Link utility is 4.0

stm_link_version.png (32.67 KiB) Viewed 7597 times

[AndreyB]

Blue LED is not blinking

Well, lack of serial communication is the least of your concurs - you have lack of firmware operation altogether. http://rusefi.com/wiki/index.php?title=Manual:Software:User/en#LEDs

[stefanst]

Do you want to get yourself couple of spare http://www.mouser.com/Search/ProductDetail.aspx?qs=mKNKSX85ZJejxc9JOGT45A%3d%3d ?

About the current state of the board - do you have the blue LED blinking?

3 replacement boards ordered.

I'll use my other one from the '03 in the meantime.

[tomiata]

Were you able to see any signs of life from the discovery board? I checked my new rev D board with Windows to check driver revisions.

discovery-revD.jpg (397.78 KiB) Viewed 7584 times

My windows STM USB driver version I have looks like:

st-link-debug-driver.jpg (51.77 KiB) Viewed 7584 times

And my STM debug embedded firmware version is:

st-link-upgrade.jpg (119.18 KiB) Viewed 7584 times

To check for signs of life, running only from power from STM mini USB as shown you should be able to connect to the STM Discovery. If the board is on a Frankenso in the car, I always do this with key off. If STLINK software does not connect, something is really wrong. If it connects ok, update rusefi firmware using STLINK. If you don't see flashing blue led after update, you can try wiping the rusefi config by grounding PB6 and reset. If no flashing blue LED after that, I think your board is toast.

[stefanst]

Grounding PB6 did the trick- thanks!

[AndreyB]

Interesting, so we are saying configuration was very invalid so that even blue led was not well.