 | Services - tools - models - for embedded software development |
|---|
| Services - tools - models - for embedded software development |
|---|
 |  | |
None of the peripherals are modeled—all external ports are tied off to appropriate values.
The behavior of ORPSoC is tracked through use of the OpenRISC 1000
l.nop instruction. These are incorporated in the
test applications as shown in Table 3.2
|
Opcode |
Action |
|---|---|
|
|
End simulation, with the value in GPR 3 as return code. |
|
|
Report the value in GPR 3. |
|
|
Print the value in GPR 3 as a character |
Table 3.2.
l.nop usage with the example ORPSoC platform
All other l.nop argument values are ignored.
The test bench implements a monitor function to detect a new
l.nop instruction. It implements the appropriate
functionality.
| |  | |
| 3.2. Interrupt Assignment |  | 3.4. Test Software Application |