From 86c97d39dd43c2c5f1ce08a5a4d1619927b8f832 Mon Sep 17 00:00:00 2001 From: Rob Meades Date: Wed, 15 Mar 2023 14:18:25 +0000 Subject: [PATCH] Documentation update only: editorial change to DATABASE.md. --- port/platform/common/automation/DATABASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/port/platform/common/automation/DATABASE.md b/port/platform/common/automation/DATABASE.md index be3577bb..35a841fd 100644 --- a/port/platform/common/automation/DATABASE.md +++ b/port/platform/common/automation/DATABASE.md @@ -1,7 +1,7 @@ # Instance Matrix The table below defines the instances of test hardware available on the `ubxlib` test farm and how each one is currently configured. It is parsed and used by the functions in [u_data.py](u_data.py) to know what to do so please always ensure that it is a properly formatted Markdown format table. The columns of the table are: -- a unique instance ID: the first digit of the instance ID represents either a physical thing (a board connected via a COM port/debugger, or a distinct process (e.g. run Lint)), the remaining digits represent variants, e.g. using different SDKs on a board; the second/third digit(s) of the instance ID must be used consistently (e.g. for NRF52840 variant 0 is always the nRF5 SDK, variant 1 is always the Zephyr SDK, etc.), +- a unique instance ID: the first digit of the instance ID represents either a physical thing (a board connected via a COM port/debugger) or a distinct process (e.g. run Lint), the remaining digits represent variants, e.g. using different SDKs on a board; the second/third digit(s) of the instance ID must be used consistently (e.g. for NRF52840 variant 0 is always the nRF5 SDK, variant 1 is always the Zephyr SDK, etc.), - the duration field should be the approximate expected duration of the instance in minutes, used when working out how to spread the test load, - the MCU field must match a unique MCU name from one of the [port/platform](/port/platform)`//mcu/` directories (e.g. `esp32`), - some platforms (e.g. Zephyr and Arduino) require a board-level definition as well as an MCU; this may be provided in the "board" column,