You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

After the code compilation and producing the .bin file (see details in User’s Manual, Volume 2) the developer needs to send the binary code to GrdUtil.exe for it to be processed and written into the dongle. The Loadable Code Settings dialog box serves this purpose.

This dialog box permits the:

  • Import of the previously compiled code from the .bin file
  • Conversion of the imported code into GCEXE format suitable for writing into a Guardant Code / Code Time dongle
  • Writing code in GCEXE format into the Flash memory of the dongle or exporting it into an external file

Further, this dialog box provides additional services that simplify working with the loadable code.

PICTURE

 

 

Clicking the Import code from a .bin file button located in the top right corner of the Loadable code settings page launches a dialog box for selecting the .bin file from the required project.

Upon importing, GrdUtil.exe reads from the project_name.bmap file settings describing the dongle’s memory occupied by the loadable code. After importing, the following appears in the dialog box:

Status indicatorPurpose
RAM in useIndicates the dongle’s RAM allocated for the loadable code, its start and end address
Flash in useIndicates the dongle’s Flash memory allocated for the loadable code, its start and end address as well as the number of the item storing the descriptor of the loadable code

Free memory is indicated by a green color, whereas the allocated memory – with blue. Addresses are displayed in hexadecimal format. 

Considering the confidentiality of the loadable code, it must not be transmitted “outside” in an open format.

Therefore, an effective routine for preparing code for writing into the dongle and the safe transfer of loadable code updates to end users was implemented in GrdUtil.exe.

GrdUtil.exe automatically converts the binary code into the .GCEXE file format containing:

  • AES-encrypted source code
  • AES session key (used previously for encrypting the source code) encrypted with the ECC160 No.1 public key
  • The .GCEXE file digital signature generated using the ECC160 No.2 private key

Whereas the counterpart of the ECC keys pairs, used during the binary code conversion, is stored in the loadable code descriptor (prot. item):

  • The ECC160 No.1private keyfor encryption
  • The ECC160 No.2 public keyfor the digital signature

This allows the dongle to successfully check, decrypt and execute loadable code upon addressing it.

Important information

Conversion of the code into GCEXE format is done with GrdUtil.exe utility automatically upon writing a mask into the dongle (or upon clicking the Export GCEXE button). This does not require any actions on the part of the developers for its execution, besides the setting of ECC160 key pair. 

 

 

 

  • No labels