SuperH Specific Information

18. SuperH Specific Information#

This chapter discusses the SuperH architecture dependencies in this port of RTEMS. The SuperH family has a wide variety of implementations by a wide range of vendors. Consequently, there are many, many CPU models within it.

Architecture Documents

For information on the SuperH architecture, refer to the following documents available from VENDOR (http://www.XXX.com/):

  • SuperH Family Reference, VENDOR, PART NUMBER.

18.1. CPU Model Dependent Features#

This chapter presents the set of features which vary across SuperH implementations and are of importance to RTEMS. The set of CPU model feature macros are defined in the file cpukit/score/cpu/sh/sh.h based upon the particular CPU model specified on the compilation command line.

18.1.1. Another Optional Feature#

The macro XXX

18.2. Calling Conventions#

18.2.1. Calling Mechanism#

All RTEMS directives are invoked using a XXX instruction and return to the user application via the XXX instruction.

18.2.2. Register Usage#

The SH1 has 16 general registers (r0..r15).

  • r0..r3 used as general volatile registers

  • r4..r7 used to pass up to 4 arguments to functions, arguments above 4 are passed via the stack)

  • r8..13 caller saved registers (i.e. push them to the stack if you need them inside of a function)

  • r14 frame pointer

  • r15 stack pointer

18.2.3. Parameter Passing#

XXX

18.3. Memory Model#

18.3.1. Flat Memory Model#

The SuperH family supports a flat 32-bit address space with addresses ranging from 0x00000000 to 0xFFFFFFFF (4 gigabytes). Each address is represented by a 32-bit value and is byte addressable. The address may be used to reference a single byte, word (2-bytes), or long word (4 bytes). Memory accesses within this address space are performed in big endian fashion by the processors in this family.

Some of the SuperH family members support virtual memory and segmentation. RTEMS does not support virtual memory or segmentation on any of the SuperH family members. It is the responsibility of the BSP to initialize the mapping for a flat memory model.

18.4. Interrupt Processing#

Although RTEMS hides many of the processor dependent details of interrupt processing, it is important to understand how the RTEMS interrupt manager is mapped onto the processor’s unique architecture. Discussed in this chapter are the MIPS’s interrupt response and control mechanisms as they pertain to RTEMS.

18.4.1. Vectoring of an Interrupt Handler#

Upon receipt of an interrupt the XXX family members with separate interrupt stacks automatically perform the following actions:

  • TBD

A nested interrupt is processed similarly by these CPU models with the exception that only a single ISF is placed on the interrupt stack and the current stack need not be switched.

18.4.2. Interrupt Levels#

TBD

18.5. Symmetric Multiprocessing#

SMP is not supported.

18.6. Thread-Local Storage#

Thread-local storage is not implemented.

18.7. Board Support Packages#

18.7.1. System Reset#

An RTEMS based application is initiated or re-initiated when the processor is reset. When the processor is reset, it performs the following actions:

  • TBD

18.7.2. Processor Initialization#

TBD