# Debug View

Minicube64 has a debug view that can be toggled easily by pressing tab.

![](/files/-MbQxYJtnAgCnYCN1CXk)

It displays the state of the program updating in realtime, so you can see what it is doing and can help identify any problems.

The top right is a window that shows the main output of the program.

Across the top indicates the state of the various registers, from left to right:

| Name                           | Showing  |
| ------------------------------ | -------- |
| Current program counter        | `0x021D` |
| Stack pounter \[SP]            | `0xFF`   |
| Accumulator \[A]               | `0x00`   |
| X register                     | `0x40`   |
| Y register                     | `0x1F`   |
| `VIDEO` register \[VP]         | `0x02`   |
| `INPUT` Controller input \[P1] | `0x00`   |

Down the left side is the currently executing code as it appears to the emulator.

The middle right square represents the 256 bytes of the zero-page. Here you should see what any active values are doing.

{% hint style="info" %}
For readability any values in zero-page that are `0x00` are currently shown as `--`
{% endhint %}

{% hint style="danger" %}
Processor flags are not currently visible in debug view.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://aeriform.gitbook.io/minicube64/debug-view.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.