Documentation available on:

􀁺 This document describes how to port the T-Kernel/Standard Extension to new hardware.
􀁺 Please refer to each of specifications as for the T-Kernel and T-Monitor. Also, refer to the each applicable specification
as for the spec of T-Engine and CPUs. And download the T-Kernel/Standard Extension source code.

1. Introduction
2. About the T-Kernel/Standard Extension Source Code

In original spec., Figures 1.1 to 1.6 show the expanded directory structures of the T-Kernel/SE main body, extension file system and standard C library that are included with the release package.

Those shown in sky blue are the parts that have been added in T-Kernel/SE. Others are the target CPU dependent part (yellow, indicated as MACHINE in the diagram; e.g., sh7727 or m32104) and the target system dependent part (orange, indicated as TE_MACHINE where TE denotes T-Engine type, which is mic or std or app; e.g., std_sh7727).  These directories are differentiated for each CPU and target system, so that when developing a new target system, the user needs to create new directories according to the target CPU and target system dependent parts.

3. Research on the T-Kernel/SE System-Dependent Parts
  3.1. Files

There is a table which lists the file names and outlines of each directory with respect to the files of the T-Kernel/SE system-dependent parts.
  3.2. Verification of the Source code

If the same CPU family as the system to be ported is supported by T-Kernel (non-SE), the files of that system may be reused without modification to some extent. (Number of files: approx. 100)

Note also that the facilities or features listed below need to be newly developed. (Number of files concerned: approx. 30)
(1) (ELF) binary reload facility (tkse/extension/memory/src directory)
(2) Memory management by MMU (tkse/extension/memory/src directory)
(3) Shared library and object facility (DLL or SO format) (tkse/lib/solib directory)

Furthermore, since no T-Kernel/SE documents are available that describe its implementation specification and internal structure, the contents of implementation in other system dependent parts may need to be consulted to know how to implement.

4. References