Hello Bernard, You are correct, I forgot to mention openssl configuration: export OPENSSL_CONF=/usr/lib/ssl/openssl.cnf As you did, envsetup script and lunch are needed, so for resign, command will look like: source build/envsetup.sh lunch celadon-userdebug export OPENSSL_CONF=/usr/lib/ssl/openssl.cnf ./build/tools/releasetools/ota_from_target_files --block -i out/dist/celadon-target_files-1.zip out/dist/celadon-target_files-2.zip out/dist/celadon-ota-1-to-2.zip Regards. Philippe P.S.: I won't be available in the coming 10 days, so please expect slower reply from my side on ota/resign topic. Yet don't hesitate to send any question in the mailing list, somebody might be able to reply, and worst case I will be happy to help when I will be back. I really hope that we can help you to be successful with Celadon! From: Bernard Carter [mailto:bernardc@nowmicro.com] Sent: Thursday, January 31, 2019 5:19 AM To: Regnier, Philippe <philippe.regnier(a)intel.com&gt;; celadon(a)lists.01.org Subject: RE: Re: [01.org Celadon] User Builds/Incremental Updates Thank you Philippe- Is there anything special one must setup to run ota-test-prepare? After I run "source build/envsetup.sh" and "lunch celadon-userdebug", any operation involving openssl results in a message about not finding its config file: Error: "Unable to load config info from /usr/local/ssl/openssl.cnf" I have modified scripts in the past to just include the config option, but I suspect I have something subtly wrong with my build environments (both Ubuntu 16.04). Thanks, Bernard From: Celadon <celadon-bounces@lists.01.org<mailto:celadon-bounces@lists.01.org>> On Behalf Of Regnier, Philippe Sent: Monday, January 28, 2019 6:44 AM To: celadon@lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org Celadon] User Builds/Incremental Updates Hello Bernard, For incremental update package, please use a command like this : ./build/tools/releasetools/ota_from_target_files --block -i out/dist/cel_apl_peak-target_files-1.zip out/dist/cel_apl_peak-target_files-2.zip out/dist/cel_apl-ota-1-to-2.zip Input : out/dist/cel_apl_peak-target_files-1.zip and out/dist/cel_apl_peak-target_files-2.zip Output: out/dist/cel_apl-ota-1-to-2.zip File names and paths can be modified. For signing your binaries with a production key, it is possible to use scripts: ./device/intel/build/test/ota-test-prepare -s -t out/dist/cel_apl_peak-target_files-1.zip A Output in ota directory will be targetfiles-A.zip, flashfiles-A.zip and ota-A.zip . Keys used for Celadon are stored in directories: TESTKEYS: device/intel/build/testkeys PRODKEYS: device/intel/build/testkeys/production-test If you don't want to use the resign script it is also possible to replace the test keys currently used with your own keys (yet, I have never tried it) I hope it helps. Philippe