> For the complete documentation index, see [llms.txt](https://bananapi.gitbook.io/bpi-open-debugger-burn-board/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bananapi.gitbook.io/bpi-open-debugger-burn-board/zh/openuartusemicrocontrolle.md).

# Open Debugger Uart use of STC microcontroller programming interface

To illustrate, here using the model for STC 89C516RD + microcontroller

1.Uart in the Open Debugger interface and connection with the STC microcontroller as STC microcontroller requires a cold start, do not use Open Debugger VCC supply to STC, and then open the STC-ISP software, select the model and serial microcontroller, as.

![](/files/-M2HWyfVVmzTqMhZW5sx)

2.Disconnect the power microcontroller, and then point detection MCU option, and then give the power microcontroller, the microcontroller will read out information.

![](/files/-M2HWyfXsrRAp_osmfZN)

3.Then point to open the program file, select STC microcontroller firmware to be programmed, then the microcontroller power, and then point to download / Programming.

![](/files/-M2HWyfZSNg-yry_pVnD)

4.Download/programmed, to give the power microcontroller, programmed to be completed.

![](/files/-M2HWyfaHMVOxH-QqFJe)

5.If the power for a long time did not respond, check the cable is connected right, or attempt to re-power. Note: Open Debugger UART interface through RXD / TXD pin on the microcontroller power supply, causing power outages can not completely downloaded. TxD pins in microcontroller series with a diode (then positive), so that the microcontroller can be powered down completely cold start.


---

# 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://bananapi.gitbook.io/bpi-open-debugger-burn-board/zh/openuartusemicrocontrolle.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.