Develop Testing Packages

Overview

This document shows how to build packages for develop testing for OTA

Author

Abhijit, Shan

Date

Nov 01, 2021

Version

7.4.0

Introduction

• Its to be used for building custom OTA packages.

• You can chose any successfully built package, it could be package that failed testing too

• You can provide your own custom zip file too

Note

At start custom zip is only supported for IHUB

OTA Package Window Layout

Note

Package secured format is only available from version 6.2+. Signature feature is only available from version 6.0+

• Blow is the overall window layout for 6.2+ version.

• For Package Signature please check Package Signature.

1. The ota package name input field (required).

2. The package priority (default PRIORITY_UPGRADE).

3. The upload to cloud controller (default False).

4. The package secured format (default PKCS7 Message).

   • For creating package before version DF91_00.27 please use (Encapsulated Message).

   • The signing algorithm is different for each secured format.

   • Encapsulated Message format is priority for all packages before version DF91_00.27.

   • PKCS7 Message format is priority for all packages from version DF91_00.27.

5. The package output path (required), please select the path with Folder button.

6. The package signing option (default False), this is only supporting PKCS7 format.

7. The package signature auto load fields, please using Folder button to load.

   • Select the signature key files folder.

   • The key files will be automatic loaded from the selected path.

   • Error will be showed if the files are incorrect.

8. The Assembly List selector, all selected assemblies will be included.

9. The Software List selector, for each assembly only the selected software will be included.

   • File Path field can be edited by double click.

   • Package Type field can be edited by double click.

10. The package Inheritance information editor.

11. The package Previous Inheritance information editor.

Process

• Select the Manifest to be used for custom package Package Window ‣ Select the package ‣ Select the Manifest ‣ Right Click ‣ Build Customised Package

• Select target ECUs and Software Components to be used in custom package.

  • Use left side Check Box to select the target ECU and Software, the default is checked for all level.

  • Click OK to start flashing

  • Select the correct inheritance for your packagage

  • For IHUB Only, in the File Path column you can give your own custom zip file. Please ensure you give the correct zip for correct start string. This file can be located on your own C drive too

  • At later stage we will add this facility for other ECU’s also

• If you want you can save this setting using the Save Debug Setting option

  • This gives you a chance to save settings to a *.p extension file, which you can give to others use later

• To load a previously saved setting, use the Load Debug Setting option

  • This will work even if you load a setting file you saved using a different manifest

  • It will try to match the assemblies and copy that info

  • It will copy the inheritance from that file

• To also upload the package after creation please select the Upload To Cloud

• Give the package the name you want, this would be the name of the generate OTA manifest

• Select the output location for the package

• Once ready click OK and wait for package to be built and be uploaded to cloud.

Note

The package is built locally and uses your computer resources and internet. Please ensure you do not unplug internet connection

• It generates two folders in the given output location new_style and old_style

  • new_style creates the new style package with .cpkg and .ec2 files

  • old_style creates the old style package with .pkg, .swpkg and .ec2 files

• If Upload To Cloud was selected it will try to upload only the new style package and its associated files

A gif showing how to build custom package