You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And I am not start thinking about the mobile app. But for start, looking at the bootloader option of STM8. Seems that if bootloader is enable on the options bytes (which I think it is not on the original firmware), the user can flash the firmware using the UART -- this would mean that users would need to use only 1 first time the STLinkV2 to erase the original firmware and enable the UART bootloader, after they could flash our firmware by UART...
And if we have a mobile app, the app could flash the firmware, so the user would just need to hit a button to update the firmware -- but this could work on the mobile app or even the Java tool :-)
And I am not start thinking about the mobile app. But for start, looking at the bootloader option of STM8. Seems that if bootloader is enable on the options bytes (which I think it is not on the original firmware), the user can flash the firmware using the UART -- this would mean that users would need to use only 1 first time the STLinkV2 to erase the original firmware and enable the UART bootloader, after they could flash our firmware by UART...
And if we have a mobile app, the app could flash the firmware, so the user would just need to hit a button to update the firmware -- but this could work on the mobile app or even the Java tool :-)
For the interested, here is the ST documentastion for the STM8 bootloader: https://opensourceebikefirmware.bitbucket.io/EmbeddedFiles/9-STM8_bootloader.pdf
The text was updated successfully, but these errors were encountered: