Using the µVision Socket Interface: Introduction

| Using the µVision Socket Interface Application Note 198 Control and monitor µVision via the built-in TCP/IP interface

- Main Page
- Usage and Description
- Reference

All Data Structures Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
Introduction

The uVision Socket Interface (UVSOCK) enables third-party applications (Clients) to control and monitor uVision. The interface is implemented over TCP/IP and can be used locally on the PC running uVision or remotely from another PC on the network.

UVSOCK can be used with the:

- Client Interface (UVSC) (recommended method) where uVision is controlled via a familiar, easy to use C-API interface. The UVSC-Tester application exemplifies such a client.
- Direct Interface (UVSOCK) where uVision is controlled via TCP/IP directly. Recommended when running the Client on an operating system other than Microsoft Windows.

UVSOCK is communicating over messages with the client. Refer to UVSOCK Messaging for details.

Clients can:

- Access the uVision Device Database
- Configure a project
- Build a project
- Debug a project and use the advanced debugging features of the Real-Time Agent

# Application Note Structure

The application note is delivered in a zip-file containing a client tester, precompiled DLLs for clients, source code, and this documentation. The source code and the DLLs were built with Visual Studio 2015.

The table lists the structure of the application note.

Folder | Content | Description
--- | --- | ---
UVSOCK | various | root folder of application note
\bin | UVSC.dll | Client DLL for 32-bit operating systems
| UVSC.lib | Client Library for 32-bit operating systems
| UVSC_Tester.exe | Client example application for 32-bit operating systems
| UVSC64.dll | Client DLL for 64-bit operating systems
| UVSC64.lib | Client Library for 64-bit operating systems
| UVSC_Tester64.exe | Client example application for 64-bit operating systems
\doc | documentation | This documentation
\src | targetver.h | Header file needed by the compiler to retrieve system information
| UVSOCK.h | Header file for the UVSOCK interface
\src\UVSC | various | Visual Studio solution files and source code for a Client application
\src\UVSC\UVSC_DLL | UVSC_C.h | Header file for the Client application (used in the Tester example)
\src\UVSC\UVSC_Tester | source code | Source code for the Client application (Tester example)
\src\UVSC\UVSOCK_Log | source code | Source code for creating the UVSC_Tester Message window logging UVSOCK messages. Only needed for the UVSC-Tester application.
\src\UVSC\UVSOCK_Tester | source code | Source code for Client application running on operating systems other than Microsoft Windows

# Requirements

One of the following Keil products is required:

- MDK-ARM Microcontroller Development Kit V3.22 (or greater)
- C51 Development Tools V8.14a (or greater)
- C166 Development Tools V6.12 (or greater)
- C251 Development Tools V4.54 (or greater)

Note
  Real-Time Agent has been deprecated starting with MDK-ARM version 4.60. For later MDK-ARM versions, use the ITM channel 0 for Serial Window output or the Debug (printf) Viewer. Refer to UV_DBG_SERIAL_PUT and UV_DBG_SERIAL_OUTPUT; DEPRECATED: UV_DBG_SERIAL_GET