Some pin assignment reverts back to FW values and not being stored in Flash

[opelpanfan]

Bigger picture is in this post:
https://rusefi.com/forum/viewtopic.php?f=2&t=2147&p=42497#p42497

Now new issue.

Some pin assignments revert back to values set while compiling FW. For example, LED pin assignments (Running, Warning) and Primary CAN BUS pins reverts back after power cycle.

Values set, burned.

image.png (54.87 KiB) Viewed 2281 times

After power cycle

image.png (61.08 KiB) Viewed 2282 times

any suggestion what can it be?

[AndreyB]

This smells like "Overrides" - "Overrides" as in "overrule, overturn"

Code: Select all

void setBoardConfigOverrides(void) {
	setHellen176LedPins();
	setupVbatt();
	setSdCardConfigurationOverrides();

	engineConfiguration->clt.config.bias_resistor = 4700;
	engineConfiguration->iat.config.bias_resistor = 4700;

	engineConfiguration->canTxPin = GPIOD_1;
	engineConfiguration->canRxPin = GPIOD_0;
}

At the moment we have to help in the blind without a URL for you custom code fork. It's hard to help in the blind. At the moment we are having a case of Trabant

https://github.com/rusefi/rusefi/wiki/Hardware#q-this-is-all-very-cool-but-you-guys-do-not-have-a-plugplay-for-my-trabant-i-think-i-will-go-and-make-a-new-rusefi-board-just-for-my-trabant

[opelpanfan]

Thank you Andrey. Yes it smells like Trabant but had this hardware so use what I have. Sorry will try to keep posts as minimal as possible.