-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GDI4: configuration persistence is flaky #212
Comments
shit I have GD32F103CBT6 C77979 chip https://lists.gnupg.org/pipermail/gnuk-users/2018-March/000021.html
tried with but that did not help |
test project works same good on both stm32 and GD32 - now I am confused, that must be some silly error specifically in GDI4 firmware? |
@dron0gus actually NO, looks like different behavior between stm32 and GD32. Do you have GDf103 and stm32f103 handy? |
@dron0gus actually I got even stm32 to not behave as I expect - just much much less often expected behavior: UART shows incrementing counter, counter is persisted with reset/power cycle actual behavior: stm32 would rarely reset counter to zero, gd32 would often reset to zero. neither chip gives me reliable persistent counter |
stm32
|
gd32
|
simpler code comment
we use master here
simpler code comment
See 97b1435
I have configuration update counter logged into UART console
at the moment rusEFI requests calibration modifications via CAN bus and I see counter going up
problem: on "reset" too often I see values roll back to previous configuration in 80% of the cases
8000 10 HAPPY
here
10
is configuration version.The text was updated successfully, but these errors were encountered: