Hi,
On my project I have a factory partition and 2 OTA partition that mean there should be two binary one for the factory and one for the OTA. If I seperate the project it's working correctly. But when I try to use only one repo for both I have some issue. Is there some guideline how should be the repo architect when we have 1 factory and 2 OTA
Architect 1 Factory 2 OTA
-
- Posts: 9986
- Joined: Thu Nov 26, 2015 4:08 am
Re: Architect 1 Factory 2 OTA
Why do you want to generate two different binaries with the same project?
Normally, you'd have the factory partition be either 1. the firmware that is 'known-good' and well-tested the moment the physical product leaves your factory, or 2. a barebones firmware that only serves to act as a fallback OTA updater. In case 1, you'd simply save your 'golden' binary somewhere and use versioning to tag its source version so you can look back at it, but you wouldn't need to recompile it so it wouldn't have to be a different project. In case 2, you'd make a separate project that potentially only shares some custom components with the main code.
Normally, you'd have the factory partition be either 1. the firmware that is 'known-good' and well-tested the moment the physical product leaves your factory, or 2. a barebones firmware that only serves to act as a fallback OTA updater. In case 1, you'd simply save your 'golden' binary somewhere and use versioning to tag its source version so you can look back at it, but you wouldn't need to recompile it so it wouldn't have to be a different project. In case 2, you'd make a separate project that potentially only shares some custom components with the main code.
Who is online
Users browsing this forum: Bing [Bot] and 93 guests