advertisement
PPC405CR – AMCC
®
PowerPC
®
32-bit RISC
Processor
Summary
This document provides information on Altium Designer's Wishbone wrapper support for the discrete AMCC
®
PPC405CR – an embedded PowerPC
®
405 32-bit RISC processor.
Core Reference
CR0161 (v2.0) March 11, 2008
Altium Designer's PPC405CR component is a 32-bit Wishbone-compatible RISC processor.
Although placed in an Altium Designer-based FPGA project just like any other 32-bit processor component, the PPC405CR is essentially a Wishbone-compliant wrapper that allows communication with, and use of, the discrete PowerPC 405 processor encapsulated within the AMCC PPC405CR device. You can think of the wrapper as being the 'means' by which to facilitate use of external memory and peripheral devices – defined within an FPGA – with the discrete processor.
Most instructions are 32-bits wide and execute in a single clock cycle. In addition to fast register access, the PPC405CR features a user-definable amount of zero-wait state block RAM, with true dual-port access
The PPC405CR wrapper can be used in FPGA designs targeting any physical FPGA device – you are not constrained to a particular vendor or platform.
Features
• 5-stage pipelined RISC processor
• Internal Harvard architecture with simplified external memory access
• 4GByte address space
• Wishbone I/O and memory ports for simplified peripheral connection
• Full Viper-based software development tool chain – C compiler/assembler/source-level debugger/profiler
• C-code compatible with other Altium Designer 8-bit and 32-bit Wishbone-compliant processors, for easy design migration.
For further information on PPC405CR features, refer to the following documents, available from www.amcc.com/Embedded :
• PPC405CR Data Sheet (DS2007)
• PPC405CR Embedded Processor User's Manual.
Available Devices
The PPC405CR device can be found in the FPGA Processors integrated library (FPGA Processors.IntLib), located in the
\Library\Fpga folder of the installation.
CR0161 (v2.0) March 11, 2008 1
PPC405CR – AMCC PowerPC 32-bit RISC Processor
RISC Processor Background
RISC, or Reduced Instruction Set Computer, is a term that is conventionally used to describe a type of microprocessor architecture that employs a small but highly-optimized set of instructions, rather than the large set of more specialized instructions often found in other types of architectures. This other type of processor is traditionally referred to as CISC, or
Complex Instruction Set Computer.
History
The early RISC processors came from research projects at Stanford and Berkeley universities in the late 1970s and early 1980s.
These processors were designed with a similar philosophy, which has become known as RISC. The basic design architecture of all RISC processors has generally followed the characteristics that came from these early research projects and which can be summarized as follows:
• One instruction per clock cycle execution time: RISC processors have a CPI (clock per instruction) of one cycle. This is due to the optimization of each instruction on the CPU and a technique called pipelining. This technique allows each instruction to be processed in a set number of stages. This in turn allows for the simultaneous execution of a number of different instructions, each instruction being at a different stage in the pipeline.
• Load/Store machine with a large number of internal registers: The RISC design philosophy typically uses a large number (commonly 32) of registers. Most instructions operate on these registers, with access to memory made using a very limited set of Load and Store instructions. This limits the need for continuous access to slow memory for loading and storing data.
• Separate Data Memory and Instruction Memory access paths: Different stages of the pipeline perform simultaneous accesses to memory. This Harvard style of architecture can either be used with two completely different memory spaces, a single dual-port memory space or, more commonly, a single memory space with separate data and instruction caches for the two pipeline stages.
Over the last 20-25 years, RISC processors have been steadily improved and optimized. In one sense, the original simplicity of the RISC architecture has been lost – replaced by super-scalar, multiple-pipelined hardware, often running in the gigahertz range.
“Soft” FPGA Processors
With the advent of low-cost, high-capacity programmable logic devices, there has been something of a resurgence in the use of processors with simple RISC architectures. Register-rich FPGAs, with their synchronous design requirements, have found the ideal match when paired with these simple pipelined processors.
As a result, most 32-bit FPGA soft processors are adopting this approach. They could even be considered as “Retroprocessors”.
Why use “Soft” Processors?
There are a number of benefits to be gained from using soft processors on reconfigurable hardware. The following sections explore some of the more significant of these benefits in more detail.
Field Reconfigurable Hardware
For certain specific applications, the ability to change the design once it is in the field can be a significant competitive advantage.
Applications in general can benefit from this ability also. It allows commitment to shipping early in the development cycle. It also allows field testing to be used to help drive the latter part of the design cycle without requiring new “board-spins” based on the outcome. This is very similar to the way in which alpha, beta, pre-release and release cycles currently drive the closure of software products.
The ability to update embedded software in a device in the field has long been an advantage enjoyed by designers of embedded systems. With FPGAs, this has now become a reality for the hardware side of the design. For end-users, this translates as “Field Upgradeable Hardware”.
Faster Time to Market
FPGAs offer the fastest time to market due to their programmable nature. Design problems, or feature changes, can be made quickly and simply by changing the FPGA design – with no changes in the board-level design.
2 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Improving and Extending Product Life-Cycles
Fast time to market is usually synonymous with a weaker feature set – a traditional trade-off. With FPGA-based system designs you can have the best of both worlds. You can get your product to market quickly with a limited feature set, then follow-up with more extensive features over time, upgrading the product while it is already in the field.
This not only extends product life-cycles but also lowers the risk of entry, allowing new protocols to be added dynamically and hardware bugs to be fixed without product RMA.
Creating Application-Specific Coprocessors
Algorithms can easily be moved between hardware and software implementations. This allows the design to be initially implemented in software, later off-loading intensive tasks into dedicated hardware, in order to meet performance objectives.
Again, this can happen even after commitment to the board-level design.
Implementing Multiple Processors within a Single Device
Extra processors can be added within a single FPGA device, simply by modifying the design with which the device is programmed. Once again, this can be achieved after the board-level design has been finalized and a commitment to production made.
Lowering System Cost
Processors, peripherals, memory and I/O interfaces can be integrated into a single FPGA device, greatly reducing system complexity and cost. Once the FPGA-based embedded application moves to 32-bit, cost becomes an even more powerful driver.
As large FPGAs become cheaper, both Hybrids and soft cores move into the same general cost area as dedicated processors.
At the heart of this argument is also the idea that once you have paid for the FPGA, any extra IP that you place in the device is free functionality.
Avoiding Processor Obsolescence
As products mature, processor supply may become an increasing problem, particularly where the processor is one of many variants supplied by the semiconductor vendor. Switching to a new processor usually requires design software changes or logical hardware changes.
With FPGA implementations, the design can be easily moved to a different device with little or no change to the hardware logic and probably no change to the application software. Peripherals are created dynamically in the hardware, so lack of availability of specific processor variants is never a problem.
The PPC405CR
Altium Designer's support for the AMCC PPC405CR offers you the best of both worlds – allowing you to create designs that themselves reside within an FPGA device, whilst incorporating the processing power of the PowerPC 405 on the physical
PPC405CR device. Your design may simply provide an extension of the PPC405CR to external memory and peripheral devices, the interfacing to which is specified in the design downloaded to the FPGA. Alternatively, you may have a hybrid design, making use not only of a physical processor, but also one or more 'soft' processors defined within your FPGA design and resident on the target FPGA device. Performance critical code might typically be handled by the physical processor.
The PPC405CR is a 32-bit RISC machine that follows the classic RISC architecture previously described. It is a load/store machine with 32 general purpose registers.
All instructions are 32-bits wide and most execute in a single clock cycle.
The PPC405CR also features a user-definable amount of zero-wait state block RAM, with true dual-port access.
Wishbone Bus Interfaces
The PPC405CR uses the Wishbone bus standard. This standard is formally described as a
“System-on-Chip Interconnection Architecture for Portable IP Cores”. The current standard is the
Revision B.3 Specification , a copy of which is included as part of the software installation and can be found by navigating to the Documentation Library » Designing with FPGAs section of the Knowledge Center panel.
The Wishbone standard is not copyrighted and resides in the public domain. It may be freely copied and distributed by any means. Furthermore, it may be used for the design and production of integrated circuit components without royalties or other financial obligations.
Remember that the PPC405CR is the 'Wishbone wrapper' placed in your FPGA design. The actual embedded PowerPC processor resides in the physical
PPC405CR device – external to the FPGA device to which that design is targeted.
CR0161 (v2.0) March 11, 2008 3
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Wishbone OpenBUS Processor Wrappers
To normalize access to hardware and peripherals, each of the 32-bit processors supported in Altium Designer has a Wishbone
OpenBUS-based FPGA core that 'wraps' around the processor. This enables peripherals defined in the FPGA to be used transparently with any type of processor. An FPGA OpenBUS wrapper around discrete, hard-wired peripherals also allows them to be moved seamlessly between processors.
The OpenBUS wrappers can be implemented in any FPGA and allow the designer to implement FPGA-based portable cores, taking advantage of the device driver system in Altium Designer for both FPGA-based soft-core peripherals as well as connections to off-chip discrete peripherals and memory devices.
Processor Abstraction System
Use of OpenBUS wrappers creates a plug-in processor abstraction system that normalizes the interface to interrupt systems and other hardware specific elements. The system provides an identical interface to the processor's interrupt system, whether soft or hard-vectored. This allows different processors to be used transparently with identical source code bases.
Design Migration
With each 32-bit processor encased in a Wishbone OpenBUS wrapper, an embedded software design can be seamlessly moved between soft-core processors, hybrid hard-core processors and discrete processors.
The Wishbone OpenBUS wrapper around the PPC405CR processor makes it architecturally similar to the other 32-bit processors included with Altium Designer, both in terms of its memory map and its pinout. This allows for easy migration from the PPC405CR to any of the following devices:
• TSK3000A – 32-bit RISC processor, device and vendor-independent. (Refer to the TSK3000A 32-bit RISC Processor core reference).
• PPC405A – 'hard' PowerPC
®
32-bit RISC processor immersed on the Xilinx Virtex-II Pro. (Refer to the PPC405A 32-bit
RISC Processor core reference).
• MicroBlaze
™
– 32-bit RISC processor targeted to Xilinx FPGA platforms. (Refer to the MicroBlaze 32-bit RISC Processor core reference).
• Nios
®
II – 32-bit RISC processor targeted to Altera FPGA platforms. (Refer to the Nios II 32-bit RISC Processor core reference).
• ARM
®
720T_LH79520 – Sharp Bluestreak
®
LH79520 with built-in ARM720T 32-bit RISC microprocessor. (Refer to the
ARM720T_LH79520 – Sharp LH79520 SoC with ARM720T 32-bit RISC Processor core reference).
Altium Designer also features Wishbone-compliant versions of its TSK52x 8-bit processor. These Wishbone variants, along with true C-code compatibility between these and the PPC405CR, allow designs to be easily moved between the 8- and 32-bit worlds.
For further information on the TSK52x, refer to the TSK52x MCU core reference.
4 CR0161 (v2.0) March 11, 2008
Architectural Overview
Symbol
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Figure 1. PPC405CR symbol.
As can be seen from Figure 1 (previous), the PPC405CR wrapper that is placed in an FPGA design essentially has three interfaces. The Wishbone External Memory and Peripheral I/O interfaces are identical to those of all other 32-bit processors supported by Altium Designer.
The third interface provides for connection to the physical PPC405CR itself. More specifically, it caters for:
• Data bus, Address bus and control signals to/from the PPC405CR's External Bus Controller (EBC)
• Clock, Reset and Interrupt signals.
The corresponding signals from the physical PPC405CR must be hardwired to the desired pins of the physical FPGA device. To wire from the PPC405CR Wishbone wrapper to the physical pins of the FPGA device requires the use of the relevant port-plugin
.
CR0161 (v2.0) March 11, 2008 5
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Pin Description
Table 1. PPC405CR pin description
6
CLK_I
RST_I
INT_I
ME_STB_O
ME_CYC_O
ME_ACK_I
ME_ADR_O
ME_DAT_I
ME_DAT_O
ME_SEL_O
ME_WE_O
ME_CLK_O
ME_RST_O
IO_STB_O
IO_CYC_O
Control Signals
I Rise
PPC_SYS_CLK output.
I High
PPC_SYS_RESET output.
Interrupt Signals
I 32 physical device on the PER_IO_IRQ bus (see
Wishbone External Memory Interface Signals
O High data transfer cycle
O High bus cycle. This signal remains asserted until the end of the bus cycle, where such a cycle can include multiple data transfers
I High signal goes High, an external Wishbone slave memory device has finished execution of the requested action and the current bus cycle is terminated
O 32 connected Wishbone slave memory device for writing to/reading from
O 4
ME_DAT_O line during a Write cycle and from where on the
ME_DAT_I line data is accessed during a Read cycle. Each of the data ports is 32-bits wide with 8-bit granularity, meaning data transfers can be 8-, 16- or 32-bit. The four select bits allow targeting of each of the four active bytes of a port, with bit 0 corresponding to the low byte (7..0) and bit 3 corresponding to the high byte (31..24)
O Level Write enable signal. Used to indicate whether the current local bus cycle is a Read or Write cycle.
0 = Read
1 = Write
O Rise for connecting to the CLK_I input of a slave memory device. Though not part of the standard Wishbone interface, this signal is provided for convenience when wiring your design
O High slave memory device. This signal goes High when an external reset is issued to the processor on its RST_I pin. When this signal goes
Low, the reset cycle has completed and the processor is active again. Though not part of the standard Wishbone interface, this signal is provided for convenience when wiring your design
Wishbone Peripheral I/O Interface Signals
O High data transfer cycle
O High bus cycle. This signal remains asserted until the end of the bus cycle, where such a cycle can include multiple data transfers
CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
IO_ACK_I
IO_ADR_O
IO_DAT_I
IO_DAT_O
IO_SEL_O
I High signal goes High, an external Wishbone slave peripheral device has finished execution of the requested action and the current bus cycle is terminated
O 24 of a connected Wishbone slave peripheral device for writing to/reading from
IO_WE_O
IO_CLK_O
IO_RST_O
O 4
IO_DAT_O line during a Write cycle and from where on the
IO_DAT_I line data is accessed during a Read cycle. Each of the data ports is 32-bits wide with 8-bit granularity, meaning data transfers can be 8-, 16- or 32-bit. The four select bits allow targeting of each of the four active bytes of a port, with bit 0 corresponding to the low byte (7..0) and bit 3 corresponding to the high byte (31..24)
O Level Write enable signal. Used to indicate whether the current local bus cycle is a Read or Write cycle.
0 = Read
1 = Write
O Rise for connecting to the CLK_I input of a slave peripheral device.
Though not part of the standard Wishbone interface, this signal is provided for convenience when wiring your design
O High slave peripheral device. This signal goes High when an external reset is issued to the processor on its RST_I pin. When this signal goes Low, the reset cycle has completed and the processor is active again. Though not part of the standard Wishbone interface, this signal is provided for convenience when wiring your design
Physical PPC405CR Interface Signals
PER_DATA
PER_ADDR
PER_WEB
I 4/Low are used to configure the width of the data transfer between the
PPC405CR'S External Bus Controller and the external memory/peripheral. Data transfers can be 8-, 16- or 32-bit. The four select bits allow targeting of each of the four active byte lanes, with bit 0 corresponding to the low byte (7..0) and bit 3 corresponding to the high byte (31..24)
PER_CS
PER_OE
PER_RESET
PPC_SYS_RESET
PER_CLK
PPC_SYS_CLK
PPC_DMA_REQ
O Low the RST_I line).
O Rise connected from the CLK_I line).
O High initiated by hardware) memory-to-memory transfers. The processor's
DMA Controller will acknowledge the request using PER_CS(0).
CR0161 (v2.0) March 11, 2008 7
PPC405CR – AMCC PowerPC 32-bit RISC Processor
PER_READY
PERBLAST
PER_RNW
PPC_IO_IRQ
O High processor to perform device-paced transfers.
I Low during the last transfer of a burst access.
I Level is being read or written.
0 = Write
1 = Read
O 7/High when handled by the physical device's Universal Interrupt Controller
(see
Configuring the Processor from the Schematic Design
The architecture of the PPC405CR can be configured after placement on the schematic sheet. Simply right-click and choose the command to configure the processor from the pop-up menu that appears (e.g. Configure U_PPC405CR (PPC405CR) for a processor with designator U_PPC405CR). Alternatively, click on the Configure button, available in the Component Properties dialog for the processor.
The Configure (32-bit Processors) dialog will appear as shown in Figure 2.
Figure 2. Options to configure the architecture of the PPC405CR.
The drop-down field at the top-right of the dialog enables you to choose the type of processor you want to work with. As the pinouts for the Wishbone interfaces between the 32-bit processors are the same, you can easily change the processor used in your design without having to extensively rewire the external interfaces.
As you select the processor type, the Configure (32-bit Processors) dialog will change accordingly to reflect the architectural options available. The symbol on the schematic will also change to reflect the type of processor and configuration options chosen.
For the PPC405CR, a single architectural option is available that allows you to define the size of the internal memory for the processor. This memory, also referred to as ‘Low’ or ‘Boot’ memory is implemented using true dual port FPGA Block RAM and will contain the boot part of a software application and the interrupt and exception handlers.
Speed-critical (or latency-sensitive) parts of an application should also be placed in this memory space.
The following memory sizes are available to choose from:
8 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
• 1KB (256 x 32-bit Words)
• 2KB (512 x 32-bit Words)
• 4KB (1K x 32-bit Words)
• 8KB (2K x 32-bit Words)
• 16KB (4K x 32-bit Words)
• 32KB (8K x 32-bit Words)
• 64KB (16K x 32-bit Words)
• 128KB (32K x 32-bit Words)
• 256KB (64K x 32-bit Words)
• 512KB (128K x 32-bit Words)
• 1MB (256K x 32-bit Words)
Your configuration choice will be reflected in the Current Configuration region of the processor’s schematic symbol (Figure 3).
Note: There are no options to remove MDU or Debug Hardware for the
PPC405CR. These architectural features are permanently installed in the actual
PowerPC processor within the physical PPC405CR device.
For further information with respect to real-time debugging of the processor, refer
to the On-Chip Debugging section of this reference.
Figure 3. Current configuration settings for the processor.
CR0161 (v2.0) March 11, 2008 9
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Memory & I/O Management
The PPC405CR uses 32-bit address buses providing a 4GByte linear address space. All memory access is in 32-bit words, which creates a physical address bus of 30-bits.
Memory space is broken into three main areas, as illustrated in Figure 4. Memory and peripheral I/O devices placed and wired
Before detailing the nature of each of these memory regions, it is worthwhile discussing the difficulties with mapping devices into this memory, and the solution that Altium Designer brings to the problem.
FFFF_FFFFh
FF00_0000h
FEFF_FFFFh
Peripheral I/O
Defining the Memory Map
An area that can be difficult to manage in an embedded software development project is the mapping of memory and peripherals into the processor’s address space.
The memory map, as it is often called, is essentially the bridge between the hardware and software projects – the hardware team allocating each of the various memory and peripheral devices their own chunk of the processor’s address space, the software team then writing their code to access the memory and peripherals at the given locations.
To help manage the process of allocating devices into the space there are a number of features available to both the hardware designer and the embedded software developer in Altium Designer.
External Memory
This discussion is based around the PPC405CR processor, however the overall approach can be applied to any of the 32-bit processors available in Altium Designer.
0100_0000h
00FF_FFFFh
Building the Bridge between the Hardware and Software
Internal Memory
Defining the memory map on the hardware (FPGA project) side is essentially a 3 stage process:
0000_0000h
Figure 4. Memory organization in the PPC405CR
•
Place the peripheral or memory
•
Define its addressing requirements (this is most easily done using a Wishbone Interconnect device)
•
Bring that definition into the processor’s configuration, which can then be accessed by the embedded tools
Figures 5 and 6 show examples of memory and peripheral devices mapped into the addressable memory and IO ranges for the
PPC405CR respectively.
10 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Figure 5. Memory devices mapped into the PPC405CR's address space.
Figure 6. Peripheral devices mapped into the PPC405CR's address space.
CR0161 (v2.0) March 11, 2008 11
PPC405CR – AMCC PowerPC 32-bit RISC Processor
The adjacent flow chart shows the process that was followed to build this memory map in the FPGA project. This flow chart is only a guide, during the course of development it is likely that you will jump back and forth through this process as you build up the design.
Dedicated System Interconnect Components
This process of being able to quickly build up the design and resolve the processor to memory & peripheral interface is possible because of specialized interconnection components, including the
Wishbone Interconnect, the Wishbone Dual Master and the Wishbone Multi-Master.
These three components solve the common system interconnect issues that face the designer, these being:
•
Interfacing multiple peripheral and memory blocks to a processor (handled by the Wishbone
Interconnect component)
•
Allowing two or more system components, that must each be able to control the bus, to share access to a common resource (provided by the Wishbone Dual Master or Wishbone Multi-
Master components)
Use of the Wishbone Interconnection Architecture for all parts of the system that connect to the processor contributes to the system’s ‘building block’ behavior. The Wishbone standard resolves data exchange between system components – supporting popular data transfer bus protocols, while defining clocking, handshaking and decoding requirements (amongst others).
With the lower-level physical interface requirements being resolved by the Wishbone interface, the other challenge is the structural aspects of the system – defining where components sit in the address space, providing address decoding, and allocating and interfacing interrupts to the processor.
For more information on the Wishbone Interconnect component, refer to the WB_INTERCON
Configurable Wishbone Interconnect core reference.
For more information on the Wishbone Dual Master component, refer to the WB_DUALMASTER
Configurable Wishbone Dual Master core reference.
For more information on the Wishbone Multi-Master component, refer to the
WB_MULTIMASTER Configurable Wishbone Multi-Master core reference.
Place Processor
Place Wishbone
Interconnect
Place peripheral component on schematic
(peripheral 1)
(peripheral 2)
(peripheral n)
Configure
Wishbone
Interconnect
(Add and Setup P1)
(Add and Setup P2)
(Add and Setup Pn)
Configure Processor to see Peripherals
(import settings from WB intercon)
Configuring the Processor
Each configurable component has its own configuration dialog, including the different processors.
The processor has separate commands and dialogs to configure memory and peripherals, but it does support mapping peripherals into memory space (and the memory into peripheral space), if required.
An important feature to point out is the Import from Schematic button in the processor’s Configure dialogs, clicking this will read in the settings from the Interconnects attached to the processor. This lets you quickly build the memory map, as shown in the figure earlier. You now have the memory map defined in the hardware, this data is stored with the processor component.
Peripheral memory map ready for embedded project
(repeat process for memory)
The flow of connecting and mapping the peripherals (or memory) to the processor
The processor’s Configure dialogs include options to generate assembler and C hardware description files that can be included in your embedded project, simplifying the task of declaring peripheral and memory structures in your embedded code. You can also ‘pull’ the memory map configurations directly into the embedded project by enabling the Automatically import when
compiling FPGA project option in the Configure Memory tab of the Options for Embedded Project dialog.
For more information on mapping physical memory devices and I/O peripherals into the processor's address space, refer to the application note Allocating Address Space in a 32-bit Processor .
Division of Memory Space
As illustrated previously (Figure 4), the PPC405CR's 4GB address space is divided into three distinct areas (or ranges). Memory and peripheral devices defined within the FPGA design are mapped into these regions, as detailed in the following sections.
Internal Memory
The internal "Low" or "Boot" RAM is built using true dual-port FPGA block RAM memory. As such, it can be read or written on both sides, simultaneously, in a single cycle.
12 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
This memory still has the standard limitation of load delay slots, because the load from memory happens further down the pipeline, after the Execute stage. As a result, any operation that requires loaded data in the cycle immediately after the load will cause the processor to insert a load stall, holding the first half of the pipeline for one cycle while the data becomes available.
Other than this single limitation, the RAM block is as fast as the internal processor registers themselves.
The size of the RAM can vary between 1KB and 16MB, dependent on the availability of embedded block RAM in the target
FPGA device used. Memory size is configured in the Internal Processor Memory region of the Configure (32-bit Processors)
dialog (see the Configuring the Processor from the Schematic Design section).
Covering the processor's address space between 0000_0000h and 00FF_FFFFh, it will contain the reset and interrupt vectors, as well as any speed or latency-sensitive code or data.
External Memory
The PPC405CR wrapper's Wishbone External Memory Interface is used by both the instruction and data sides of the processor and provides access to the majority of the address space of the processor. It covers the address space between 0100_0000h and FF00_0000h – 1.
External Memory Interface Time-out
A simple time-out mechanism for the interface handles the case when attempting to access an address that does not exist, or if the addressed target slave device is not operating correctly. This mechanism ensures that the processor will not be ‘locked’ indefinitely, waiting for an acknowledgement on its ME_ACK_I input.
After the ME_STB_O output is taken High a timer built-in to Altium Designer's PPC405CR wrapper is started and the physical
PPC405CR processor, which normally times out after 16 cycles, is requested to wait. If, after 4096 cycles of the external clock signal (CLK_I), an acknowledge signal fails to appear from the addressed slave memory device, the wait request to the
PPC405CR is dropped, the processor times out normally and the current data transfer cycle is forcibly terminated.
The ACK_O signal from a slave device should not be used as a ‘long delay’ hand-shaking mechanism. Where such a mechanism needs to be implemented, either use polling or interrupts.
Peripheral I/O
The PPC405CR wrapper's Wishbone Peripheral I/O Interface is a one-way Wishbone Master, handling I/O in a very similar way to external memory. The port can be used to communicate with any Wishbone Slave peripheral device and covers the address space between FF00_0000h and FFFF_FFFFh. This address space of 16MB allows a physical address bus size of 24 bits.
Although the space for peripheral I/O is 16MB, the top 256 bytes is reserved for hardwired boot code (see next section). Any access to addresses in the range FFFF_FF00h to FFFF_FFFFh over the Wishbone Peripheral I/O interface will be ignored.
System Boot Code
The region of processor address space from FFFF_FF00h to FFFF_FFFFh is reserved for system boot (or startup) code. After a reset, the processor will try to fetch its first instruction from address FFFF_FFFCh, as this is the reset vector for the PPC405CR.
In order to make the physical processor compatible with the standard Wishbone memory layout – employed for all 32-bit processors in Altium Designer – the memory controller in the physical device needs to be configured accordingly. This entails use of the following hardwired instructions within the Wishbone wrapper around the processor, the result of which is to configure the physical processor's memory controller, then branch to address 0000_0000h in the boot RAM (block RAM) containing the user code.
_START:
; EBC Access Parameters
0xFFFF_FFC0 li %R4,EBC0_B1AP
0xFFFF_FFC4 mtdcr PeripheralControl_Address,%R4
0xFFFF_FFC8 lis %R4 ,@MSH(EBC_FastBRAM)
0xFFFF_FFCC ori %R4,%R4,@LSH(EBC_FastBRAM)
0xFFFF_FFD0 mtdcr PeripheralControl_Data,%R4
; EMC Configuration Registers
0xFFFF_FFD4 li %R4,EBC0_B1CR
While addresses in the range FFFF_FF00h to
FFFF_FFFFh are reserved for the hardwired boot code, only addresses from FFFF_FFC0h to
FFFF_FFFFh are actually used.
0xFFFF_FFD8 mtdcr PeripheralControl_Address,%R4
0xFFFF_FFDC lis %R4 ,@MSH(EBC_16MB_32Bit_RAM_000)
0xFFFF_FFE0 ori %R4,%R4,@LSH(EBC_16MB_32Bit_RAM_000)
CR0161 (v2.0) March 11, 2008 13
PPC405CR – AMCC PowerPC 32-bit RISC Processor
0xFFFF_FFE4 mtdcr PeripheralControl_Data,%R4
; Memory controller now configured. Now jump out to address 0000_0000h,
; fetch whatever is in block RAM and proceed with user application.
0xFFFF_FFE8 ba 0x00000000
; the following nops are for alignment only. They are required as the last
; instruction (b _START) has to be placed at the processor's reset vector
; address.
0xFFFF_FFEC nop
0xFFFF_FFF0 nop
0xFFFF_FFF4 nop
0xFFFF_FFF8 nop
; The processor will fetch the following instruction first after a reset and
; will branch to _START label so we can configure memory controller prior to
; giving control to the user code at address 0000_0000h in block RAM.
0xFFFF_FFFC b _START ; jbranch to 0xFFFF_FFC0
Peripheral I/O Interface Time-out
A simple time-out mechanism for the interface handles the case when attempting to access an address that does not exist, or if the addressed target slave device is not operating correctly. This mechanism ensures that the processor will not be ‘locked’ indefinitely, waiting for an acknowledgement on its IO_ACK_I input.
After the IO_STB_O output is taken High a timer built-in to Altium Designer's PPC405CR wrapper is started and the physical
PPC405CR processor, which normally times out after 16 cycles, is requested to wait. If, after 4096 cycles of the external clock signal (CLK_I), an acknowledge signal fails to appear from the addressed slave peripheral device, the wait request to the
PPC405CR is dropped, the processor times out normally and the current data transfer cycle is forcibly terminated.
The ACK_O signal from a slave peripheral should not be used as a ‘long delay’ hand-shaking mechanism. Where such a mechanism needs to be implemented, either use polling or interrupts.
For more information on connection of slave physical memory and peripheral I/O devices to the processor's Wishbone interfaces, refer to the application note Connecting Memory and Peripheral Devices to a 32-bit Processor .
Data Organization
Data organization refers to the ordering of the data during transfers. There are two general types of ordering:
• BIG ENDIAN – the most significant portion of an operand is stored at the lower address
• LITTLE ENDIAN – the most significant portion of an operand is stored at the higher address.
The physical PPC405CR supports both of these, but by default operates in Big Endian mode only. Little Endian mode is not implemented.
Words, Half-Words and Bytes
The PPC405CR operates on the following data sizes:
There are dedicated load and store instructions for these three data types.
PPC405CR.
14 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Word-0 Word-1
31 24 23 16 15 8 7 0 31 24 23 16 15 8 7 0
Half-0 Half-1 Half-2 Half-3
15 8 7 0 15 8 7 0 15 8 7 0 15 8 7 0
Byte-0 Byte-1 Byte-2 Byte-3 Byte-4 Byte-5 Byte-6 Byte-7
7 0 7 0 7 0 7 0 7 0 7 0 7 0 7 0
Figure 7. Organization of data types for the PPC405CR (Big Endian).
Physical Interface to Memory and Peripherals
The PPC405CR's physical interface to the outside world is always 32 bits wide. Since the addressing has a byte-level resolution, this means that up to four "packets" of data (bytes) can be loaded or stored during a single memory access. To accommodate this requirement all memory accesses (8-bit, 16-bit and 32-bit) are handled in a specific way.
Each 32-bit read and write can be considered as a read or write through four "byte-lanes". These byte-lanes are marked as valid by the corresponding bits in the PER_WEB[3..0] and subsequent SEL_O[3..0] signal of the relevant Wishbone interface
(External Memory or Peripheral I/O). Each of these bits will be active if the byte data in that lane is valid. This allows a single byte to be written to 32-bit wide memory without needing to use a slower read-modify-write cycle.
The instructions of the PPC405CR require that all 32-bit load/store operations be aligned on 4-byte boundaries and all 16-bit load/store operations be aligned on 2-byte boundaries. Byte operations (8-bit) can be to any address.
To complete a byte load or store, the PPC405CR will position the byte data in the correct byte-lane and set the
PER_WEB/SEL_O signal for that lane active. The memory hardware must then only enable writing on the relevant 8-bits of data from the 32-bit word.
When reading, the PPC405CR will put the relevant 8- or 16-bit value into the LSB's of the 32-bit word. What happens with the remaining bits depends on the operation:
• for an unsigned read, the processor will pad-out the remaining 24 or 16 bits respectively with zeroes
• for a byte load/store, the processor will sign-extend from bit 8
• for a half-word load/store, the processor will sign-extend from bit 16.
Peripheral I/O
For memory I/O the process described happens transparently, because memory devices are always seen by the processor as
32 bits wide. Even when connecting to small 8- or 16-bit physical memories, the interfacing Memory Controller device will, as far as the processor is concerned, make the memory look like it is 32 bits wide.
For peripheral devices, the process is not so simple. 32-bit wide peripheral devices behave like memory devices, although they may or may not support individual byte-lanes. These devices should therefore be accessed using the 32-bit LW and SW instructions. For C-code, this means declaring the interface to the device as 32 bits wide, for example:
#define Port32 (*(volatile unsigned int*) Port32_Address)
This will result in the software using LW and SW instructions to access the device.
If the 32-bit peripheral does support byte-lanes (i.e. it has a SEL_I[3..0] input), then smaller accesses can be performed using the 8-bit LBU and SB or 16-bit LHU and SH instructions.
For smaller devices, there needs to be translation of the 8- or 16-bit values into the relevant byte-lanes in the processor. This is automatically handled by the Wishbone Interconnect device if it is used to access slave peripheral I/O devices. There is, however, some hardware penalty for this since it requires an extra 4:1 8-bit multiplexer for 8-bit devices or a 2:1 16-bit multiplexer for 16-bit devices.
16-bit peripheral devices should be accessed using the 16-bit LHU and SH instructions. For C-code, this means declaring the interface to the device as 16 bits wide, for example:
#define Port16 (*(volatile unsigned short*) Port16_Address)
This will result in the software using LHU and SH instructions to access the device.
CR0161 (v2.0) March 11, 2008 15
PPC405CR – AMCC PowerPC 32-bit RISC Processor
8-bit peripheral devices should be accessed using the 8-bit LBU and SB instructions. For C-code, this means declaring the interface to the device as 8 bits wide, for example:
#define Port8 (*(volatile unsigned char*) Port8_Address)
This will result in the software using LBU and SB instructions to access the device.
There are some trade-offs that may need to be considered when deciding whether to use 8-, 16- or 32-bit wide devices. It may require significantly less hardware to implement a single 32-bit wide I/O port than it would to implement four separate 8-bit ports.
If however, the natural format of the data packets is 8-bits and hardware size is not a constraint, then it may be better to use 8bit ports since there will be no need to use software to break up a 32-bit value into smaller components.
If you are only accessing 8-bits at any one time, then software may also execute faster when using 8-bit wide peripherals, since there is need for extra instructions to extract the 8-bit values from the 32-bit values.
Hardware Description
For detailed information about the hardware and functionality of the PPC405CR processor, including internal registers, refer to the following document, available from the AMCC website:
• PPC405CR Embedded Processor User's Manual
Clocking
The signal PPC_SYS_CLK sent from the processor wrapper to the physical processor itself is simply the internally-routed CLK_I signal. On the physical device side, the PPC_SYS_CLK signal (arriving as SysClk) is fed into a PLL. The generated PER_CLK signal is then sent back into the FPGA, where it is used to correctly clock signals to/from the wrapper.
PPC_SYS_CLK – and therefore CLK_I – must be within the range 25MHz to 66MHz, in order for the PLL to achieve stable locking.
Reset
The signal PPC_SYS_RESET sent from the processor wrapper to the physical processor itself (arriving as SysReset) is simply the internally-routed RST_I signal. A system reset of the FPGA can therefore also be used to reset the physical processor as well.
Conversely, the physical processor can issue a reset of the system, the required signal of which (ExtReset) is passed into the
FPGA, ultimately arriving at the wrapper on the PER_RESET line.
Interrupts
Although the PPC405CR wrapper has provision for 32 interrupt lines, the physical PowerPC device supports only 7 external interrupts. The least significant 7 lines of the INT_I bus are connected through to the PPC_IO_IRQ bus.
These external interrupts are handled by a Universal Interrupt Controller (UIC) – part of the physical PPC405CR device, but external to the embedded PowerPC 405 processor itself. They appear as interrupts 25 to 31. The interrupt handler combines these signals into a single signal sent to the processors Noncritical interrupt input.
Interrupts generated by Altium Designer Wishbone peripherals have positive polarity and are level sensitive. You will need to program the processor's UIC Polarity Register (UIC0_PR) with '1's (positive polarity) for the corresponding external interrupt bits. You will also need to ensure that the corresponding bits in the UIC Trigger Register (UIC0_TR) are set to '0' (level sensitive). Bear in mind that the internal registers use reverse-bit logic, so the external interrupts (bits 25-31) are the rightmost 7 bits in the register.
Detailed information on the operation of the PPC405CR's Interrupt Controller can be found in the Interrupt Controller
Operations section of the PPC405CR Embedded Processor User's Manual.
16 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Wishbone Communications
The following sections detail the standard handshaking that takes place when the processor communicates to a slave peripheral or memory device connected to the relevant Wishbone interface port. Both of the PPC405CR wrapper's Wishbone ports can be configured for 8-, 16- or 32-bit data transfer, depending on the width of the data bus supported by the connected slave device.
Configuration is achieved using the relevant IO_SEL_O or ME_SEL_O output, which defines where on the corresponding
DAT_O and DAT_I lines the data appears when writing and reading respectively.
Writing to a Slave Wishbone Peripheral Device
Data is written from the host processor (Wishbone Master) to a Wishbone-compliant peripheral device (Wishbone Slave) in accordance with the standard Wishbone data transfer handshaking protocol. This data transfer cycle can be summarized as follows:
• The host presents an address on its IO_ADR_O output for the register it wants to write to and valid data on its IO_DAT_O output. It then asserts its IO_WE_O output to specify a Write cycle
• The host defines where the data will be sent on the IO_DAT_O line using its IO_SEL_O signal
• The slave device receives the address at its ADR_I input and prepares to receive the data
• The host asserts its IO_STB_O and IO_CYC_O outputs, indicating that the transfer is to begin. The slave device, monitoring its STB_I and CYC_I inputs, reacts to this assertion by latching the data appearing at its DAT_I input into the requested register and asserting its ACK_O signal – to indicate to the host that the data has been received
• The host, monitoring its IO_ACK_I input, responds by negating the IO_STB_O and IO_CYC_O signals. At the same time, the slave device negates the ACK_O signal and the data transfer cycle is naturally terminated.
Reading from a Slave Wishbone Peripheral Device
Data is read by the host processor (Wishbone Master) from a Wishbone-compliant peripheral device (Wishbone Slave) in accordance with the standard Wishbone data transfer handshaking protocol. This data transfer cycle can be summarized as follows:
• The host presents an address on its IO_ADR_O output for the register it wishes to read. It then negates its IO_WE_O output to specify a Read cycle
• The host defines where it expects the data to appear on its IO_DAT_I line using its IO_SEL_O signal
• The slave device receives the address at its ADR_I input and prepares to transmit the data from the selected register
• The host asserts its IO_STB_O and IO_CYC_O outputs, indicating that the transfer is to begin. The slave device, monitoring its STB_I and CYC_I inputs, reacts to this assertion by presenting the valid data from the requested register at its DAT_O output and asserting its ACK_O signal – to indicate to the host that valid data is present
• The host, monitoring its IO_ACK_I input, responds by latching the data appearing at its IO_DAT_I input and negating the
IO_STB_O and IO_CYC_O signals. At the same time, the slave device negates the ACK_O signal and the data transfer cycle is naturally terminated.
Writing to a Slave Wishbone Memory Device
Data is written from the host processor (Wishbone Master) to a Wishbone-compliant memory device or memory controller
(Wishbone Slave) in accordance with the standard Wishbone data transfer handshaking protocol. This data transfer cycle can be summarized as follows:
• The host presents an address on its ME_ADR_O output for the address in memory that it wants to write to and valid data on its ME_DAT_O output. It then asserts its ME_WE_O output to specify a Write cycle
• The host defines where the data will be sent on the ME_DAT_O line using its ME_SEL_O signal
• The slave device receives the address at its ADR_I input and prepares to receive the data
• The host asserts its ME_STB_O and ME_CYC_O outputs, indicating that the transfer is to begin. The slave device, monitoring its STB_I and CYC_I inputs, reacts to this assertion by storing the data appearing at its DAT_I input at the requested address and asserting its ACK_O signal – to indicate to the host that the data has been received
• The host, monitoring its ME_ACK_I input, responds by negating the ME_STB_O and ME_CYC_O signals. At the same time, the slave device negates the ACK_O signal and the data transfer cycle is naturally terminated.
CR0161 (v2.0) March 11, 2008 17
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Reading from a Slave Wishbone Memory Device
Data is read by the host processor (Wishbone Master) from a Wishbone-compliant memory device or memory controller
(Wishbone Slave) in accordance with the standard Wishbone data transfer handshaking protocol. This data transfer cycle can be summarized as follows:
• The host presents an address on its ME_ADR_O output for the address in memory that it wishes to read. It then negates its
ME_WE_O output to specify a Read cycle
• The host defines where it expects the data to appear on its ME_DAT_I line using its ME_SEL_O signal
• The slave device receives the address at its ADR_I input and prepares to transmit the data from the selected memory location
• The host asserts its ME_STB_O and ME_CYC_O outputs, indicating that the transfer is to begin. The slave device, monitoring its STB_I and CYC_I inputs, reacts to this assertion by presenting the valid data from the requested memory location at its DAT_O output and asserting its ACK_O signal – to indicate to the host that valid data is present
• The host, monitoring its ME_ACK_I input, responds by latching the data appearing at its ME_DAT_I input and negating the
ME_STB_O and ME_CYC_O signals. At the same time, the slave device negates the ACK_O signal and the data transfer cycle is naturally terminated.
Wishbone Timing
timing diagrams are presented assuming point-to-point connection of the Master and Slave interfaces, with only signals on the
Master side of the interface shown. Note that cycle speed can be throttled by the Slave device inserting wait states (represented as WSS on the diagrams) before asserting its acknowledgement line (ACK_I input at the Master side).
Figure 8. Timing diagrams for single Wishbone Write (left) and Read (right) cycles
18 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Placing a PPC405CR in an FPGA Design
Figure 9 shows an example of how a PPC405CR is used within an FPGA design, making peripheral devices and memory (not shown) available to the physical processor.
Figure 9. Wiring up the PPC405CR wrapper in an FPGA design.
Memory and peripheral I/O devices are wired to the wrapper's Wishbone External Memory and Peripheral I/O interfaces in the same way as for any other 32-bit processor.
The signals in the wrapper's external interface – the interface to the physical processor itself – must be wired to ports that are mapped accordingly to the required pins of the physical FPGA device in which the FPGA design will be programmed. You must ensure that the relevant signals from the discrete processor device are wired to these FPGA device pins.
Facilitating Communications
The host computer is connected to the PPC405CR using the IEEE 1149.1 (JTAG) standard interface. You must ensure that the physical JTAG lines are appropriately routed between the physical devices on your board.
Verification that the JTAG signals are indeed propagating through the intended physical devices as required is obtained by the respective physical devices appearing on the Hard Devices chain within the Devices view (View » Devices View). Figure 10 illustrates this for a board containing an AMCC PPC405CR and a Xilinx Spartan 3 FPGA (XC321000-4FG456C).
CR0161 (v2.0) March 11, 2008 19
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Figure 10. Detected physical devices appearing in the Hard Devices JTAG chain.
As the physical PPC405CR processor does not reside within an FPGA, communications between the host computer and the
PPC405CR are carried out through the Hard Devices JTAG chain. This is a departure from the normal way of communicating with FPGA-based, debug-enabled devices, such as the 'soft' processors and virtual instruments, whereby communication is carried out through the Soft Devices JTAG chain, and in accordance with the Nexus 5001 standard.
For further information on the JTAG communications, refer to the PC to NanoBoard Communications article.
Additional 'Soft' Devices in Your Design
If your design incorporates FPGA-based 'soft' processors and virtual instruments, in addition to the discrete PPC405CR processor, these devices will appear in the Soft Devices chain of the Devices view. The Soft Devices chain is determined when the design has been implemented within the target FPGA device. It is not a physical chain, in the sense that you can see no external wiring – the connections required between the Nexus-enabled devices are made internal to the FPGA itself. Figure 11 shows an example of devices presented in this chain.
Figure 11. Nexus-enabled processor (TSK3000A) and virtual instruments appearing in the Soft Devices chain.
Enabling the Soft Devices JTAG Chain
In order to communicate with soft devices in a design (processors and/or virtual instruments) you must enable the Soft Devices
JTAG chain within the design. This is done by placing a JTAG Port (NEXUS_JTAG_CONNECTOR) and corresponding Soft Nexus-
Chain Connector (NEXUS_JTAG_PORT) on the top schematic sheet of the design, as shown in Figure 12.
If your design incorporates just the discrete PPC405CR, with no additional 'soft' devices, then these Nexus JTAG devices are not required.
Figure 12. Implementing the soft devices chain within the design.
These devices can be found in the FPGA NB2DSK01 Port-Plugin (FPGA NB2DSK01 Port-Plugin.IntLib) and FPGA
Generic (FPGA Generic.IntLib) integrated libraries respectively, both of which are located in the \Library\Fpga folder of the installation.
20 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Downloading Your Design
Download of a design which incorporates a discrete processor such as the PPC405CR is performed in two stages:
• Download of the FPGA design to the target physical FPGA device. This includes downloading the respective embedded code to any 'soft' processors used within the design. Click on the FPGA device in the Hard Devices chain to access the process flow required to facilitate this part of the download, as illustrated in the following image. The standard process flow is followed when programming the FPGA device – Compile, Synthesize, Build and Program.
• Download of the embedded code targeted to the discrete PPC405CR device. Click on the PPC405CR device in the Hard
Devices chain to access the process flow required to download the embedded software to the processor, as illustrated below.
Notice that the process flow consists of compilation and download only.
CR0161 (v2.0) March 11, 2008 21
PPC405CR – AMCC PowerPC 32-bit RISC Processor
On-Chip Debugging
To facilitate real-time debugging of the processor, the PPC405CR includes On-Chip Debug hardware that can be accessed using the standard JTAG interface.
With this hardware, the following set of additional functional features are provided:
• Reset, Go, Halt processor control
• Single or multi-step debugging
• Read-write access for internal processor registers
• Read-write access for memory and I/O space
• Unlimited software breakpoints.
Accessing the Debug Environment
Debugging of the embedded code within a PPC405CR processor is carried out by starting a debug session. Prior to starting the session, you must ensure that the FPGA design has been downloaded to the target FPGA device and the embedded code has been downloaded to the physical PPC405CR device (see
).
You can have multiple debug sessions running simultaneously
– one per embedded software project associated with a processor in the design.
To start a debug session for the embedded code running in the PPC405CR, simply right-click on the icon for the physical device in the Hard Devices region of the Devices view, and choose the
Debug command from the pop-up menu that appears.
The embedded project for the software running in the processor will initially be recompiled and the debug session will commence. The relevant source code document (either Assembly or C) will be opened and the current execution point will be set to the first line of executable code (see Figure
13).
To start a debug session for the embedded code running in a
'soft' processor in the design, simply right-click on the icon for that processor, in the Soft
Devices region of the view, and choose the Debug command from the menu.
Figure 13. Starting an embedded code debug session.
22 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
The debug environment offers the full suite of tools you would expect to see in order to efficiently debug the embedded code.
These features include:
• Stepping into and over at both the source (*.C) and instruction (*.asm) level
• Reset, Run and Halt code execution
• Run to cursor
All of these and other feature commands can be accessed from the Debug menu or the associated Debug toolbar.
Various workspace panels are accessible in the debug environment, allowing you to view/control code-specific features, such as
Breakpoints, Watches and Local variables, as well as information specific to the processor in which the code is running, such as memory spaces and registers.
These panels can be accessed from the View » Workspace Panels » Embedded sub menu, or by clicking on the Embedded button at the bottom of the application window and choosing the required panel from the subsequent pop-up menu.
Figure 14. Workspace panels offering code-specific information and controls
Figure 15. Workspace panels offering information specific to the parent processor.
CR0161 (v2.0) March 11, 2008 23
PPC405CR – AMCC PowerPC 32-bit RISC Processor
Full-feature debugging is of course enjoyed at the source code level – from within the source code file itself. To a lesser extent, debugging can also be carried out from a dedicated debug panel for the processor. To access
this panel, first double-click on the icon representing the physical PPC405CR device, in the Hard Devices region of the view. The Instrument Rack –
Hard Devices panel will appear, with the PPC405CR device added to the rack (Figure 16).
Any 'soft' core processor that you have included in the design will appear, when double-clicked, as an
Instrument in the Instrument Rack
– Soft Devices panel (along with any other Nexus-enabled devices).
Figure 16. Accessing debug features from the processor's instrument panel
and to a lighter extent control, debugging of the processor and its embedded code, notably with respect to the registers and memory.
One key feature of the debug panel is that it enables you to specify (and therefore change) the embedded code (HEX file) that is downloaded to the processor, quickly and efficiently.
Figure 17. Processor debugging using the associated processor debug panel
1
The debug panels for each of the debug-enabled processors are standard panels and, as such, can be readily accessed from the View »
Workspace Panels » Instruments sub menu, or by clicking on the Instruments button at the bottom of the application window and choosing the required panel – for the processor you wish to debug – from the subsequent pop-up menu.
24 CR0161 (v2.0) March 11, 2008
PPC405CR – AMCC PowerPC 32-bit RISC Processor
For more information on the content and use of processor debug panels, press F1 when the cursor is over one of these panels.
For further information regarding the use of the embedded tools for the PPC405CR, see the Using the PowerPC Embedded
Tools guide.
For comprehensive information with respect to the embedded tools available for the PowerPC, see the PowerPC Embedded
Tools Reference .
Instruction Set
For detailed information with respect to the instruction set for the PPC405, including instruction encoding and an alphabetical listing of all instructions by mnemonic, refer to the Instruction Set section of the PPC405CR Embedded Processor User's
Manual. This document is available from the AMCC website.
Revision History
Date Version No.
Revision
04-Oct-2006
11-Mar-2008
1.0
2.0
Initial document release.
Updated for Altium Designer Summer 08
Software, hardware, documentation and related materials:
Copyright © 2008 Altium Limited.
All rights reserved. You are permitted to print this document provided that (1) the use of such is for personal use only and will not be copied or posted on any network computer or broadcast in any media, and (2) no modifications of the document is made. Unauthorized duplication, in whole or part, of this document by any means, mechanical or electronic, including translation into another language, except for brief excerpts in published reviews, is prohibited without the express written permission of Altium Limited. Unauthorized duplication of this work may also be prohibited by local statute. Violators may be subject to both criminal and civil penalties, including fines and/or imprisonment. Altium, Altium
Designer, Board Insight, Design Explorer, DXP, LiveDesign, NanoBoard, NanoTalk, P-CAD, SimCode, Situs, TASKING, and Topological
Autorouting and their respective logos are trademarks or registered trademarks of Altium Limited or its subsidiaries. All other registered or unregistered trademarks referenced herein are the property of their respective owners and no trademark rights to the same are claimed.
CR0161 (v2.0) March 11, 2008 25
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project