> For the complete documentation index, see [llms.txt](https://nxp.gitbook.io/rddrone-t1adapt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nxp.gitbook.io/rddrone-t1adapt/software/code-description-and-overview.md).

# Code description and overview

{% hint style="success" %}
Source code for the LPC MCU on this board is available through your local NXP sales representative. Please ask them to contact the NXP Mobile Robotics team
{% endhint %}

### Overview

The on board LPC MCU is used to configure the T1 and TX Ethernet PHYs for back to back operation. In addition it establishes if the T1 PHY should be the master on the T1 connection and will attempt a connection by resetting and alternating between Master and slave mode operation until the connection is made.&#x20;

Therefore if two T1ADAPT boards are connected they will automatically negotiate a T1 connection. There is no specific indication which one has assumed master role.&#x20;

The LPC MCU will also drive LEDs to indicate T1 data and link activity.&#x20;

The TX PHY drives it's own LINK and DATA LEDs independently of the MCU.&#x20;


---

# 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://nxp.gitbook.io/rddrone-t1adapt/software/code-description-and-overview.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.
