[help needed] Rusefi Prometheus/F405 - Start with project

[Mari232]

Hi

I have started with rusEFI Prometheus with stm32f405 this month.
The board is in 95% complete, i don't have only bluetooth module and a few pull_up resistors.

I have a problem with software to make it run properly.

What i observed in hardware:
1. when i turn on the board, MCU sents "y" on UART
2. TX is pulled up after the message was send.
3. about 200ms the TX line goes permanently LOW.

The oscillator is working
All voltages are good.
I checked the soldering 3 times.

What i observed in software:
I'm using master from andreika-git/rusefi
I debug the MCU using Chibi Studio and the program stops on sr5ReadDataTimeout in tunerstudio_io.cpp
also it always run the firmwareError(CUSTOM_ERR_6126, "Unexpected channel situation");

Except that, the efifeatures.h from board catalog dont initiate properly, TS_UART_DMA_MODE should be TRUE, but in debug it's FALSE, i think other definitions from efifeatures.h also can be wrong.

I'm beginner in programming and i don't know what should i do now. Someone can help me?

Thanks!

[AndreyB]

Very few people use Prometheus and there is a good chance that master just does not have a valid configuration. UART implementation is not in a great state right now - while it works, it's really fragile in terms of configuration, very easy to make config invalid

I would suggest working with https://github.com/rusefi/rusefi - I've actually just made errors in this error just a bit more helpful. Great job isolating it at "Unexpected channel situation" now you need to figure out what goes wrong exactly.

Can you get a discovery board to have a reference? Have you tried official precompiled binaries from https://rusefi.com/build_server/ ?

[Mari232]

Hi!
Thanks for the answer.

I would have to buy a discovery board to have a reference..
I tried official precompiled binaries 10 minutes ago.. the same result, "y" on TX and 200ms of high state.

I will try to debug official rusefi code but i think the effect will be the same.

[AndreyB]

Someone with Prometheus hardware would have to debug it. There is a chance that you are one of two or three people on this planet with both Prometheus hardware and debugging skills. There is a chance that you would have to fix this (probably configuration) defect.

If I would be doing it I would be reducing the gap between rusEFI default config and Prometheus - these days those configs are doing more or less similar things but for historical reasons via potentially different configurations.

[Mari232]

Hi

Yesterday I resolve the problem with communication and now UART is working (i do some changes in efifeatures.h and mcuconf.h from /config/stm32f4ems/ directory)

Now i have two questions:

1. I have firmware signature mismatch in Tuner Studio, can I do something easy to make to disable this?

2. I have also a problem with rusefi.ini file for the prometeus, some configuration of the pins can only use "Analog 3O" or "Injector 3Z". What is the best way to make rusefi.ini for prometheus usable?

Thanks for previous help

[AndreyB]

I think first step would be to share the changes which have helped you so that everyone can benefit from your efforts. can you make a github pull request? or just publish a patch?