Introduction

Binary Images can be programmed directly via the external REST API or stored on the Cuica for later use. The following limits apply to the Binary Images Bank:

• Maximum 125 MB per Binary Image
• Maximum 100 Binary Images in the Bank

All operations can be performed using the web interface, the Cuica CLI app, or directly in the REST API. The related REST API endpoints can be found in the DUT section of the OpenAPI specification and corresponding documentation.

Bypassing the Binary Images Bank

It is possible to bypass the Binary Images Bank and directly access the Cuica’s programming functionality. This is useful for quick testing or when the mechanism to automate programming of the DUT is external to the Cuica.

Adding Binary Images

When adding a new Binary Image, a label and an optional version are associated with it. After uploading the Binary Image to the Cuica, the system attempts to determine the architecture (e.g., elf) and machine type (e.g., ARM). Various checksums (CRC32, MD5, SHA1, SHA256) are calculated for the newly imported Binary Image and can later be viewed to validate its integrity.

Tagging Binary Images

To facilitate grouping and filtering during DELETE and GET operations, Binary Images may be tagged with up to 20 unique strings.

Replacing Binary Images

To maintain the relationship between Test Suites and an instance of a Binary Image, the Binary Image data itself can be replaced. This allows existing Test Suites to use updated Binary Images without requiring a rebuild. When a Binary Image is replaced, the original SHA256 checksum is retained, and the Binary Image record in the bank is marked as modified.

Deleting Binary Images

Binary Images can be removed individually, by tag, or all at once.