By "look the same" i meant had the same length and structure.
All i can find is this:
https://www.st.com/resource/en/applicat ... ronics.pdf
https://www.st.com/resource/en/user_man ... ronics.pdf
Even if we knew which algorithm they used, we couldn't just brute-force it because we don't know what the output should look like.
Without exactly knowing what they use, we can see what is possible and going the way trying to decrypt this seems wrong.
About flashing the chip:
I couldn't get the original firmware because it read protected. If i had this all problems would be solved
I know its possible to re-flash the chip because i can connect it to STM32CubeProgrammer, erase the chip and write to it.
But developing our own software for the motor controller would be a big project. If we had some programmers here with enough time it could work, but it seems like most of us are more into electronics than programming.
If someone thinks he can get into STM32CubeMX / STM32CubeIDE programming for the motor controller, tell me.
https://www.st.com/en/embedded-software ... mcsdk.html
funbag wrote: ↑Fri Mar 20, 2020 1:45 pm
fernlop wrote: ↑Fri Mar 20, 2020 11:47 am
The "security code" that is sent always changes and i read about an encryption the stm32 used that generated an output that looks exactly like the codes we see. Bu i can't find the doc right now.
Would be interesting to see the doc! Assuming that codes look exactly the same.
fernlop wrote: ↑Fri Mar 20, 2020 11:47 am
I successfully reflashed the chip of the IOT, but that doesn't do anything now.
Reflashed with original firmware? Do you have the firmware dump?