Page 2
SiFive does not assume any liability rising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation indirect, incidental, spe- cial, exemplary, or consequential damages.
The FE310-G002 is the second revision of the General Purpose Freedom E300 family. The FE310-G002 is built around the E31 Core Complex instantiated in the Freedom E300 plat- form and fabricated in the TSMC CL018G 180nm process. This manual serves as an architec- tural reference and integration guide for the FE310-G002.
1.3 Interrupts The FE310-G002 includes a RISC-V standard platform-level interrupt controller (PLIC), which supports 52 global interrupts with 7 priority levels. The FE310-G002 also provides the standard RISC‑V machine-mode timer and software interrupts via the Core-Local Interruptor (CLINT). Interrupts are described in Chapter 8. The CLINT is described in Chapter 9. The PLIC is...
1.8 Hardware Serial Peripheral Interface (SPI) There are 3 serial peripheral interface (SPI) controllers. Each controller provides a means for serial communication between the FE310-G002 and off-chip devices, like quad-SPI Flash mem- ory. Each controller supports master-only operation over single-lane, dual-lane, and quad-lane protocols.
GPIO output pins and can also be used to generate several forms of internal timer interrupt. The PWM peripherals are described in Chapter 20. 1.10 I²C The FE310-G002 has an I²C controller to communicate with external I²C devices, such as sen- sors, ADCs, etc. The I²C is described in detail in Chapter 21.
Page 16
JTAG Joint Test Action Group Loosely Integrated Memory. Used to describe memory space delivered in a SiFive Core Complex but not tightly integrated to a CPU core. Physical Memory Protection PLIC Platform-Level Interrupt Controller. The global interrupt controller in a RISC-V system.
The core caches instructions from executable addresses, with the exception of the Instruction Tightly Integrated Memory (ITIM), which is further described in Section 3.1.1. See the FE310-G002 Memory Map in Chapter 4 for a description of executable address regions that are denoted by the attribute X.
Chapter 5 Boot Process The FE310-G002 supports booting from several sources, which are controlled using the Mode Select ( ) pins on the chip. All possible values are enumerated in Table 5. MSEL[1:0] MSEL Purpose loops forever waiting for debugger...
Table 7: Target of the reset vector 5.1.1 Mask ROM (MROM) MROM is fixed at design time, and is located on the peripheral bus on FE310-G002, but instruc- tions fetched from MROM are cached by the core’s I-cache. The MROM contains an instruction at address...
AON block (Chapter 13) or the PRCI block (Section 6.2). 6.1 Clock Generation Overview Figure 2: FE310-G002 clock generation scheme Figure 2 shows an overview of the FE310-G002 clock generation scheme. Most digital clocks on the chip are divided down from a central high-frequency clock produced from either hfclk the PLL or an on-chip trimmable oscillator.
The PRCI registers are generally only made visible to machine-mode software. The AON block contains registers with similar functions, but only for the AON block units. Table 8 shows the memory map for the PRCI on the FE310-G002. Offset Name...
Page 31
Figure 3: Controlling the FE310-G002 PLL output frequency. field encodes the reference clock divide ratio as a 2-bit binary value, where the pllr[1:0] value is one less than the divide ratio (i.e., =4).
Table 15: lfclkmux: Low-Frequency Clock Mux Control and Status 6.9 Clock Summary Table 16 summarizes the major clocks on the FE310-G002 and their initial reset conditions. At external reset, the AON domain is clocked by either the LFROSC or...
Chapter 7 Power Modes This chapter describes the different power modes available on the FE310-G002. The FE310-G002 supports three power modes: Run, Wait, and Sleep. 7.1 Run Mode Run mode corresponds to regular execution where the processor is running. Power consump- tion can be adjusted by varying the clock frequency of the processor and peripheral bus, and by enabling or disabling individual peripheral blocks.
Page 36
HFROSC at the default setting, and must reconfigure clocks to run from an alternate clock source (HFXOSC or PLL) or at a different setting on the HFROSC. Because the FE310-G002 has no internal power regulator, the PMU’s control of the power sup- plies is through chip outputs, .
Instruction Set Manual, Volume II: Privileged Architecture, Version 1.10. 8.1 Interrupt Concepts The FE310-G002 supports Machine Mode interrupts. It also has support for the following types of RISC‑V interrupts: local and global. Local interrupts are signaled directly to an individual hart with a dedicated interrupt value. This...
A summary of the fields related to interrupts in mstatus the FE310-G002 is provided in Table 17. Note that this is not a complete description of mstatus as it contains fields unrelated to interrupts. For the full description of...
Page 40
See Table 18 for a description of the register. See Table 19 for a description of the mtvec field. See Table 23 for the FE310-G002 interrupt exception code values. mtvec.MODE Mode Direct When operating in direct mode all synchronous exceptions and asynchronous interrupts trap to address.
8.4 Interrupt Priorities Individual priorities of global interrupts are determined by the PLIC, as discussed in Chapter 10. FE310-G002 interrupts are prioritized as follows, in decreasing order of priority: • Machine external interrupts • Machine software interrupts • Machine timer interrupts...
Chapter 9 Core-Local Interruptor (CLINT) The CLINT block holds memory-mapped control and status registers associated with software and timer interrupts. The FE310-G002 CLINT complies with The RISC‑V Instruction Set Manual, Volume II: Privileged Architecture, Version 1.10. 9.1 CLINT Memory Map Table 24 shows the memory map for CLINT on SiFive FE310-G002.
Architecture, Version 1.10 and supports 52 interrupt sources with 7 priority levels. 10.1 Memory Map The memory map for the FE310-G002 PLIC control registers is shown in Table 25. The PLIC memory map has been designed to only require naturally aligned 32-bit memory accesses.
10.2 Interrupt Sources The FE310-G002 has 52 interrupt sources. These are driven by various on-chip devices as listed in Table 26. These signals are positive-level triggered. In the PLIC, as specified in The RISC‑V Instruction Set Manual, Volume II: Privileged Architec-...
10.3 Interrupt Priorities Each PLIC interrupt source can be assigned a priority by writing to its 32-bit memory-mapped register. The FE310-G002 supports 7 levels of priority. A priority value of 0 is priority reserved to mean "never interrupt" and effectively disables the interrupt. Priority 1 is the lowest active priority, and priority 7 is the highest.
WARL field, where the FE310-G002 supports a maximum threshold of 7. threshold The FE310-G002 masks all PLIC interrupts of a priority less than or equal to . For threshold example, a value of zero permits all interrupts with non-zero priority, whereas a threshold value of 7 masks all interrupts.
Chapter 11 Error Device The error device is a TileLink slave that responds to all requests with a TileLink error. It has no registers. The entire memory range discards writes and returns zeros on read. Both operation acknowledgments carry an error indication. The error device serves a dual role.
Chapter 12 One-Time Programmable Memory (OTP) Peripheral This chapter describes the operation of the One-Time Programmable Memory (OTP) Controller. Device configuration and power-supply control is principally under software control. The con- troller is reset to a state that allows memory-mapped reads, under the assumption that the con- troller’s clock rate is between 1 MHz and 37 MHz.
Chapter 13 Always-On (AON) Domain The FE310-G002 supports an always-on (AON) domain that includes real-time counter, a watchdog timer, backup registers, low frequency clocking, and reset and power-management circuitry for the rest of the system. Figure 5 shows an overview of the AON block.
13.3 AON Reset Unit An AON reset is the widest reset on the FE310-G002, and resets all state except for the JTAG debug interface. An AON reset can be triggered by an on-chip power-on reset (POR) circuit when power is first...
The Real-Time Clock is described in detail in Chapter 16. 13.9 Backup Registers The backup registers provide a place to store critical data during sleep. The FE310-G002 has 32 32-bit backup registers. 13.10 Power-Management Unit (PMU) The power-management unit (PMU) sequences the system power supplies and reset signals when transitioning into and out of sleep mode.
Chapter 14 Watchdog Timer (WDT) The watchdog timer (WDT) is used to cause a full power-on reset if either hardware or software errors cause the system to malfunction. The WDT can also be used as a programmable periodic interrupt source if the watchdog functionality is not required. The WDT is implemented as an upcounter in the Always-On domain that must be reset at regular intervals before the count reaches a preset threshold, else it will trigger a full power-on reset.
Chapter 15 Power-Management Unit (PMU) The FE310-G002 power-management unit (PMU) is implemented within the AON domain and sequences the system’s power supplies and reset signals during power-on reset and when tran- sitioning the "mostly off" (MOFF) block into and out of sleep mode.
Chapter 16 Real-Time Clock (RTC) The real-time clock (RTC) is located in the always-on domain, and is clocked by a selectable low-frequency clock source. For best accuracy, the RTC should be driven by an external 32.768 kHz watch crystal oscillator, but to reduce system cost, can be driven by a factory- trimmed on-chip oscillator.
This chapter describes the operation of the General Purpose Input/Output Controller (GPIO) on the FE310-G002. The GPIO controller is a peripheral device mapped in the internal memory map. It is responsible for low-level configuration of actual GPIO pads on the device (direction, pull up-enable, and drive value ), as well as selecting between various sources of the controls for these signals.
The UART peripheral does not support hardware flow control or other modem control signals, or synchronous serial data transfers. 18.2 UART Instances in FE310-G002 FE310-G002 contains two UART instances. Their addresses and parameters are shown in Table 54. Instance Num-...
SPI flash device and instead return immediately. Hardware interlocks ensure that the current transfer completes before mode transitions and control register updates take effect. 19.2 SPI Instances in FE310-G002 FE310-G002 contains three SPI instances. Their addresses and parameters are shown in Table...
Chapter 20 Pulse Width Modulator (PWM) This chapter describes the operation of the Pulse-Width Modulation peripheral (PWM). 20.1 PWM Overview Figure 10 shows an overview of the PWM peripheral. The default configuration described here has four independent PWM comparators ( –...
PWM 3 compare register 0x2C pwmcmp3 Table 89: SiFive PWM memory map, offsets relative to PWM peripheral base address 20.4 PWM Count Register ( pwmcount The PWM unit is based around a counter held in . The counter can be read or written pwmcount over the TileLink bus.
Chapter 21 Inter-Integrated Circuit (I²C) Master Interface The SiFive Inter-Integrated Circuit (I²C) Master Interface is based on OpenCores® I²C Master Core. Download the original documentation at https://opencores.org/project,i2c. All I²C control register addresses are 4-byte aligned. 21.1 I²C Instance in FE310-G002 FE310-G002 contains one I²C instance.
Chapter 22 Debug This chapter describes the operation of SiFive debug hardware, which follows The RISC‑V Debug Specification 0.13. Currently only interactive debug and hardware breakpoints are sup- ported. 22.1 Debug CSRs This section describes the per-hart trace and debug registers (TDRs), which are mapped into...
Debug ROM. The debugger may use it as described in The RISC‑V Debug Specifi- cation 0.13. 22.2 Breakpoints The FE310-G002 supports eight hardware breakpoint registers per hart, which can be flexibly shared between debug mode and machine mode. When a breakpoint register is selected with...
– 0x300 0x3FF The FE310-G002 has 16 32-bit words of program buffer for the debugger to direct a hart to exe- cute arbitrary RISC-V code. Its location in memory can be determined by executing aiupc instructions and storing the result into the program buffer.
The specific behavior of the flags is not further documented here. 22.3.4 Safe Zero Address In the FE310-G002, the debug module contains the address in the memory map. Reads to this address always return 0, and writes to this address have no impact. This property allows a "safe"...
Chapter 23 Debug Interface The SiFive FE310-G002 includes the JTAG debug transport module (DTM) described in The RISC‑V Debug Specification 0.13. This enables a single external industry-standard 1149.1 JTAG interface to test and debug the system. The JTAG interface is directly connected to input pins.
The JTAG DTM implements the BYPASS and IDCODE instructions. On the FE310-G002, the IDCODE is set to 0x20000913 23.5 JTAG Debug Commands The JTAG DEBUG instruction gives access to the SiFive debug module by connecting the debug scan register between jtag_TDI jtag_TDO...
Chapter 24 References Visit the SiFive forums for support and answers to frequently asked questions: https://forums.sifive.com [1] A. Waterman and K. Asanovic, Eds., The RISC-V Instruction Set Manual, Volume I: User- Level ISA, Version 2.2, May 2017. [Online]. Available: https://riscv.org/specifications/ [2] ——, The RISC-V Instruction Set Manual Volume II: Privileged Architecture Version 1.10,...
Need help?
Do you have a question about the FE310-G002 and is the answer not in the manual?
Questions and answers