...

Test Management Interface

Anchor10036181003618NDIT requires a connection with the target to configure the tests. There are two connection protocols available: RS-232 or TCP/IP (Ethernet). The use of TCP/IP requires a functional Ethernet driver and TCP/IP stack. It is common to start with RS-232, when a UART is available. Anchor

10036191003619Upon starting NDIT, the following dialog box appears: Anchor10036201003620 Image Removed

...

Image Added

Figure 8-1 Test management interface setup dialog

...

anchor10289741028974

The connection setup options are as followed:

Anchor10289761028976Connection type Anchor10036281003628

RS-232
COM port (ex: COM1).
Baud rate (8 bits, no parity, 1 stop bit and no flow control)

...

...

TCP/IP
Command port (UDP or TCP port)
The test station and target exchange commands and return results on this port. It must match the port number defined in app_cfg.h (#define NDIT_PORT).

Anchor10036341003634Transport protocol Anchor10036351003635

TCP or UDP. Either one of the protocol can be chosen as long as the

...

target’s TCP/IP implementation supports it.

Anchor10036381003638Target IP Anchor10036391003639

The target IP address must be the one used by App_TCPIP_Init() in app.c in order for the test station to reach the target board. This parameter is also used when the NDIT is setup for RS-232 communication.

...

1005380Network Anchor10036411003641

The network interface used to communicate with the target. By default, the first IPv4 network interface found is used. In order for the tests to work, the target has to be reachable via the selected network interface.

Anchor10036421003642Once you click ‘OK’ ‘OK’ the NDIT main window (see next section) appears, and your chosen connection settings are stored and will be reloaded at the next startup of NDIT.