工程目录下创建ota目录
前后两版软件分别make otapackage -j48,每次分别拷贝用于升级的ota包到工程目录下的ota目录下,取名字为old和new两版zip
以下报错:
build01@build-pc:~/aml/mx/git_m6_1225$ ./build/tools/releasetools/ota_from_target_files -i ota/old.zip ota/new.zip ota/update.zip
unzipping target target-files...
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 951, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 903, in main
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/home/build01/aml/mx/git_m6_1225/build/tools/releasetools/common.py", line 114, in LoadInfoDict
raise ValueError("can't find recovery API version in input target-files")
ValueError: can't find recovery API version in input target-files
build01@build-pc:~/aml/mx/git_m6_1225$
原因是zip文件不对,不是升级用的zip(out/target/product/g18ref/g18ref-ota-20140628.zip),
而是out/target/product/g18ref/obj/PACKAGING/target_files_intermediates/g18ref-target_files-20140628.zip
正确的打印如下
build01@build-pc:~/aml/mx/git_m6_1225$ ./build/tools/releasetools/ota_from_target_files -i ota/old.zip ota/new.zip ota/update.zip
unzipping target target-files...
using device-specific extensions in device/amlogic/common
unzipping source target-files...
unable to load device-specific module; assuming none
Loading target...
Loading source...
3 diffs to compute
0.14 sec 297 / 280045 bytes ( 0.11%) system/etc/recovery-resource.dat
3.29 sec 251 / 6163076 bytes ( 0.00%) system/lib/libXXXjni.so
3.42 sec 249 / 6326752 bytes ( 0.00%) system/lib/libXXX.so
building image from target_files BOOT...
building image from target_files BOOT...
building image from target_files RECOVERY...
building image from target_files RECOVERY...
boot target: 4622336 source: 4620288 diff: 3542860
boot image changed; including.
recovery image changed; including as patch from boot.
Signing Whole File
done.
build01@build-pc:~/aml/mx/git_m6_1225$
总结
考虑签名不一样,只能在同一个账号下发布,而且每次备份升级软件的时候把差分源zip和ota升级zip一起备份,以备全新升级和制作差分包升级使用。
本站转载的文章为个人学习借鉴使用,本站对版权不负任何法律责任。如果侵犯了您的隐私权益,请联系我们删除。