Home
last modified time | relevance | path

Searched refs:DUT (Results 1 – 13 of 13) sorted by relevance

/Zephyr-latest/scripts/tests/twister/
Dtest_hardwaremap.py16 DUT,
24 DUT(platform='p1', id=1, serial='s1', product='pr1', connected=True),
25 DUT(platform='p2', id=2, serial='s2', product='pr2', connected=False),
26 DUT(platform='p3', id=3, serial='s3', product='pr3', connected=True),
27 DUT(platform='p4', id=4, serial='s4', product='pr4', connected=False),
28 DUT(platform='p5', id=5, serial='s5', product='pr5', connected=True),
29 DUT(platform='p6', id=6, serial='s6', product='pr6', connected=False),
30 DUT(platform='p7', id=7, serial='s7', product='pr7', connected=True),
31 DUT(platform='p8', id=8, serial='s8', product='pr8', connected=False)
102 d = DUT(**kwargs)
Dtest_handlers.py38 DUT
1278 dut = DUT()
/Zephyr-latest/tests/drivers/uart/uart_elementary/
DKconfig16 UART baudrate for DUT_AUX that is intentionally different from DUT
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dhardwaremap.py36 class DUT: class
248 device = DUT(
298 new_dut = DUT(platform=plat,
362 s_dev = DUT(platform="unknown",
/Zephyr-latest/boards/adi/max78002evkit/doc/
Dindex.rst225 | | | | 1-2 | | | DUT ADC VREF is supplied by precision external…
260 | | | | Closed | | | USB-UART bridge connected to DUT UART0 (RTS an…
262 | | | | Open | | | USB-UART bridge disconnected from DUT UART0 …
281 | | | | Closed | | | USB-UART bridge connected to DUT UART1 (no HW …
283 | | | | Open | | | USB-UART bridge disconnected from DUT UART1 …
323 | | | | 2-1 | | | DUT USB XCVR VDDB powered from VBUS regulated …
/Zephyr-latest/boards/adi/max78000evkit/doc/
Dindex.rst170 | | | | 1-2 | | | DUT LDO powers VDDIOH …
246 | JP21 | DUT I | +---------------+ | +-------------------------------------------…
247 | | | | 1-2 | | | DUT 3V3 total current monitor point …
/Zephyr-latest/tests/drivers/can/host/
DREADME.rst10 host PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
18 * A CAN fixture creating a CAN bus between the host PC and the DUT.
/Zephyr-latest/tests/bluetooth/classic/sdp_c/
DREADME.rst10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
/Zephyr-latest/tests/kernel/timer/timer_behavior/
DREADME48 to account for expected drift in the test and between the DUT and the external
/Zephyr-latest/doc/develop/test/
Dpytest.rst110 the core of pytest harness plugin. It is required to launch DUT (initialize logging, flash device,
129 It calls ``wait_for_promt`` method, to not start scenario until DUT is ready. The shell fixture
Dtwister.rst844 If the scope is set to ``function``, DUT is launched for every test case
845 in python script. For ``session`` scope, DUT is launched only once.
/Zephyr-latest/boards/adi/max32672evkit/doc/
Dindex.rst220 | JP15 | LDO DUT | +-----------+ | +---------------------------------------------------…
/Zephyr-latest/doc/releases/
Drelease-notes-3.7.rst556 * Twister now supports ``--flash-before`` parameter that allows flashing DUT before