9. Implementing a Custom Test

Using the Connectivity Production Line Tool, it is possible to create a custom test for a DUT. This guide will provide a basic understanding of how to create a custom test using the Connectivity Production Line Tool.

9.1. Custom test overview

Before a custom test is implemented, it is important to understand the basic structure of a custom test. The custom test is implemented in a similar manner as many of the built-in tests. Many built-in tests are pieces of code that are executed on the DUT itself. In the industry, this is known as a Built-In Self-Test (BIST). The BIST software is called by the PLT via the DUT connection (see Section 6 for more info about the DUT connection). The BIST then responds with the test result so the Connectivity Production Line Tool can determine if the DUT passed or failed the test. The built-in tests used by the Connectivity Production Line Tool are implemented in device-specific software such as prod_test_xxx.bin (for DA1453x devices).

9.2. Where the custom test is implemented

Specifically for the purpose of implementing a custom test, all Renesas Electronics Coorporation BIST software comes with a placeholder test step where a custom test can be implemented. But, while the standard BIST software is pre-configured and included in the Connectivity Production Line Tool software package, the custom test software must be created by the user. Thus, the source code must be obtained. The exact location of the source code depends on the DUT and the software package used. Please refer to the table below to find where the BIST source code can be found.

9.3. Structure

The exact implementation of the custom test step varies from SDK to SDK. Which is why this guide only covers the general structure which is the same across all SDKs. The custom test step for SDK6 devices can be found by searching for dialog_commands_custom_action_handler. Regardless of which SDK is used, the custom test step is always triggered by a opcode command and returns a value.

9.3.1. command

The custom test operation, like any other test operation, is called using an HCI command. The HCI command used for this is in the vendor-specific section of the HCI command specification. For SDK6, 0xFE00 is used to trigger the custom test, but the exact value differs per product/SDK. When triggering the custom test using the HCI command, a value is passed along with the HCI command. This value can be chosen by the user, making it possible to have multiple custom tests in the same BIST software.

9.3.2. return value

The custom test step returns a value to the Connectivity Production Line Tool to indicate if the test passed or failed. The return value is two bytes, where 0x00 indicates that the test passed and any positive value indicates that the test failed. The return value is sent back to the Connectivity Production Line Tool using the HCI command response.

9.4. Enabling the custom test

To enable the custom test, the Connectivity Production Line Tool must be configured to use the custom test. This is done by enabling the custom test in the configuration GUI. See Figure 40 below for details. The HCI vendor specific custom data is the value chosen in Section 9.3.1.