> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/application-notes/application-note-xcp-driver-example.md).

# Application Note: XCP Driver Example

### Introduction

This application note is written to provide an overview of the Intrepid XCP C Code ECU driver and example Vehicle Spy Setup. It will describe all the files and resources provided by Intrepid to enable you to develop real-time XCP memory editing and monitoring for your ECU.

### Files Required for This Example: [Click Here to Download Files](https://cdn.intrepidcs.net/support/VehicleSpy/ICS_XCP_Driver_And_Example_Setup.zip)

There are several files provided in this example implementation to help you get started quickly. These files are:

1. ECU.omf This file is an example debugger file used as an input in creating an ASAP2 file.
2. ECU.a2l This file is the final ASAP2 file output from the Intrepid ASAP2 generator.
3. XCP\_Example.vs3 This file is an example Vehicle Spy 3 setup file for an example XCP ECU driver and simulation.
4. Intrepid\_XCP\_Driver.zip This file contains a complete Microsoft Visual Studio Project including the source code for the XCP simulator and XCP ECU driver example.
5. ASAP2.pdf ASAP2 file format specification for your reference.
6. XCP\_SPEC.zip Complete XCP specification for your reference.

[Click Here to Go to Training Videos Page](https://intrepidcs.com/learning-center/videos/)

Here you will find a video called **XCP Driver and Example Application Video.** It is a Windows Media Video that will take you through every step of creating the ASAP2 file to using it in Vehicle Spy with the XCP simulator. It is recommended that you view this video as the first step in learning about the Intrepid XCP support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/application-notes/application-note-xcp-driver-example.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.