Replies: 1 comment 1 reply
-
@niclask I'd like to give some generic pointers first. One is the documentation chapter about Updating Sub-Devices, the other one is the chapter about Handling Board Variants. If deciding to have the MCU firmware as part of the rootfs, then the compatibility should be checked and resolved there. In case you decide that variant support would be the way to go, you can simply put an image for the variant to support into the bundle. RAUC will reject the update if it does not have an image for the board's current variant. Does that already solve your question? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a use-case that looks like:
An embedded system running Linux that is connected, with a UART, to a MCU. During the update both Linux and MCU have to be updated. Right now there is only one hardware version. In the future there might be a few more hardware versions depending on when the MCU hits end of life. Then the MCU will be replaced with another one which will require a new HEX file. The hardware version will be changed. The update will now contain two HEX files to support both MCUs.
What is the recommended way to handle the compatibility check?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions