> For the complete documentation index, see [llms.txt](https://sdk.twelite.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.twelite.info/en/twelite-net-api-ref/twelite-net-guan-shu/toconet_vdebuginit.md).

# ToCoNet\_vDebugInit()

## Explanation

Initialisation of the TWELITE NET debug message output.

The specified [UART](/en/hw-api-ref/perifuraru/uart.md) output is used in common with the application's output, and debug messages are output during the application's output.

{% hint style="warning" %}
Set `TOCONET_DEBUG` to `1` in the [Makefile](/en/twelite-sdk-howto/birudonitsuite/makefile-nitsuite.md) and run the build.
{% endhint %}

{% hint style="danger" %}
The debug messages are intended for internal TWELITE NET development and the format of the output will not be disclosed. We may ask you to provide us with the output in order for us to analyse the problem.
{% endhint %}

## Argument

| Type                                                                      | Name   | Remark                                                       |
| ------------------------------------------------------------------------- | ------ | ------------------------------------------------------------ |
| [`tsFILE`](/en/hw-api-ref/perifuraru/uart/fprintf-raiburari/tsfile.md)`*` | `pSer` | Pointer to a structure defining the UART output destination. |

## Returns

None

## Sample code

```c
#include "serial.h"
#include "fprintf.h"

tsFILE sSerStream; // use for fprintf
tsSerialPortSetup sSerPort;

void initser() {
  //... setup serial port
  sSerPort.u8SerialPort = E_AHI_UART_0;
  //...
  SERIAL_vInitEx(&sSerPort, pUartOpt);
  
  // setup fprintf
  sSerStream.bPutChar = SERIAL_bTxChar; // lib function
  sSerStream.u8Device = E_AHI_UART_0; // UART0
  
  // setup TWELITE NET debug message.
  ToCoNet_vDebugInit(&sSerStream);
  ToCoNet_vDebugLevel(0); // start with no debug message.
}
```


---

# 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://sdk.twelite.info/en/twelite-net-api-ref/twelite-net-guan-shu/toconet_vdebuginit.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.