> For the complete documentation index, see [llms.txt](https://docs.excl.ornl.gov/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.excl.ornl.gov/system-overview/emu.md).

# emu

## Description

![](/files/-MeQUcAK0zTrNOXEV1ws)

EMU-Chick System is composed of 8x nodes that are connected via RapidIO Interconnect.

Each node has:

* 8x nodelets, array of DRAMs
* A stationary core (SC)
* Migration engine, PCI-Express interfaces, and an SSD.
* 64-byte channel 64GB of DRAM, divided into eight 8-byte narrow-channel-DRAMs (NC-DRAM

Each nodelet has:

* 2x Gossamer cores (GC)
* 64 concurrent in-order, single-issue hardware threads

## Access

* The path to access to each individual EMU node is: `login.excl.ornl.gov` ⇒ `emu-gw` ⇒ `emu` ⇒ {`n0`-`n7`}
* `emu-gw` is an x86-based gateway node.
* The `emu` is the system board controller (sbc) and individual nodes are accessed only via this host.
* Connections to `emu` from the `emu-gw` are via preset ssh keys that are created during account creation. If you can't log in, your user account/project do not have access to EMU systems.

## Development Workflow

* The EMU software development kit (SDK) is installed under /usr/local/emu on emu-gw, which is an x86 based system. Compilation and simulation should be performed on this machine.
* The official EMU programming guide is located under /usr/docs.
* emu and emu-gw mount home directories, so you should have no difficulty accessing your projects. Please use `$HOME` (or `${HOME}`) as your home directory in scripts, as the mount location of your home directory, may change.

## Other Resources

This document will be updated with additional documentation references and user information as it becomes available.

## Contact

Please send assistance requests to <excl-help@ornl.gov>.


---

# 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.excl.ornl.gov/system-overview/emu.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.