[quote='Taddy',index.php?page=Thread&postID=10420#post10420]Hier habe ich noch etwas gefunden. aus dem bersetzer.
MTK entry
MTK for MediaTek companies to provide GSM software program. It includes five parts:
-- "L1 agreement
-- "Device Driver
-- "Protocol Stack
-- "MMI
-- "WAP application
MediaTek offers three tools:
-- "Catcher
-- "META
-- "MCT
The following three components of the software program:
1. MS Executable Software, which is the software running on the MS, includes the following modules
-- OS: Nucleus OS.
-- L1 Protocol Stack: GSM physical layer.
-- Drivers: device driver, like SIM, UART, GPIO, etc.
-- L2/L3 protocol stack: GSM protocol stack layer.
-- MMI: man-machine interface.
-- WAP: Wireless application protocol.
-- JAVA: J2ME Software
2. The Mobile Engineering Testing Architecture, also known as META
3. Catcher
-- "OS
MediaTek used Nucleus OS real-time operating system. KAL OS layer to MediaTek's software and the Nucleus operating system interface. For many of its mandate to provide system service functions, such as timer, queue, memory management, events and so on.
-- "Drivers
MCU peripherals driver, as follows:
SIM: Subscriber Identity Module
UART: Universal Asynchronous Receiver / Transmitter
SPI: Serial Port Interface
LCD: Liquid Crystal Display
GPIO: General Purpose Input / Output
GPT: General Purpose Timer
RTC: Real Time Clock
WDT: Watch Dog Timer
PWM: Pulse Width Modulation
Alerter
Keypad
PMIC: Power Management IC
BMT: Battery Charging Management task
AUX task: Auxiliary task
ADC Sched.: Analog to Digital Converter Scheduler
USB task: The USB 1.1 protocol and driver
IrDA task: The IrDA and driver
Camera: Camera driver for integrating with 3rd party camera module
MSDC: Memory card driver, supporting SD, MMC cards and Memory Stick
JPEG Decoder: Software for controlling hardware JPEG decoder
-- "L2/L3/L4 Protocol Stack
This part consists of a large number of GSM / GPRS demand and provide an excellent GSM / GPRS platform to the application. Local MMI and remote PC through AT commands can facilitate the use of the software platform. Detail is structured as follows:
RMI: remote MMI, such as PC terminal can be used with the AT command protocol stack through a serial communications.
FMI: Feature rich MMI, described in the above section. This is the production co-worked with Pixtel.
L4: Layer 4. L4 is a task through which FMI and / or RMI communicate with PS. L4 task includes several sub-modules.
ATCI: AT command interpreter. Interprets the AT commands from PC side and commands the L4C to do the relative actions.
L4A: L4 adaptation layer for FMI. The SAP between FMI and L4A is primitive base.
L4C: L4 control entity. Handles all applications request and response.
UEM: User equipments adaptation. Adaptation for drivers, like Keypad, LED, GPIO, Audio ... etc..
PHB: Phone book management. Handles the phone books related processing, like: sorting ... etc..
SMU: SIM management unit. Handle the security management, and STK.
CSM: Circuit switching protocol stack management.
RAC: Registration access control.
SMSAL: Short message service application layer.
TCM: Terminal context management.
NVRAM: Non-volatile RAM. This is adaptation layer to flash memory.
SIM: Subscriber identity module. Handle SIM behavior as ETSI 11.11 description.
DATA: Circuit switched data service. Data task includes several sub-modules.
FAX: Group 3 Facsimile.
TDT: Transparent circuit switching data.
L2R: Layer 2 relay protocol for non-transparent circuit switching data.
RLP: Radio link protocol for non-transparent circuit switching data.
CC: Circuit-switched call control.
SS: Supplementary service.
SMS: Short message service.
SM: Session management.
MM / GMM: Mobility management / GPRS mobility management.
SNDCP: Subnetwork dependent convergence protocol.
LLC: Logical link control.
RR: Radio resource management. RR task includes several sub-modules.
RRM: Handles cell selection and PLMN selection.
RMPC: Handles the procedures in Idle / Dedicated state including the surrounding cell scheme and measurement reporting.
LAPDM: Handles the procedure defined in GSM layer 2.
RLC: Radio link control protocol.
MAC: Medium access control protocol.
MPAL: Adaptation layer for RR and L1A.
PPP: Point to Point protocol layer. This is client PPP layer.
-- "MMI
This includes user interface framework, applications, and communications and protocol stack.
Ramework: This covers that
OSL: OS adaptation layer
Task: communication with L4 task.
File system: communication with storage device.
GUI: This covers that
Theme
UI component
Category screen
Font
Editor
T9 or Ezi input method.
Access LCD driver.
Customization tool.
Application
Phonebook
Messages (SMS, EMS 4.0, CB)
Call history
Setting. (Phone setting, network setting, and security setup)
Five kinds of user profiles
Fun and games
Organizers
Services
Shortcuts
In call management.
Interrupt events, like charging, alarm.
-- "WAP
2. How to Build
Reference Document: wcr - MTK_MakeBuild_Design_Customer_040930.pdf
-- "Build Environment
Operating system: Windows 2000, Windows XP. Recommend Windows 2000 with SP2 or later.
Compiler: ADS (Arm Developer Suite) v1.2.
Perl Analysis: ActivePerl. Recommends ActivePerl 5.6.1 version
-- "Make.bat
It will parse command line to determine project name, platform, and action. Meanwhile, checking \ make directory exist or not and checking command line argument is legal or not. After checking, to execute build script GSM2.mak build script to perform action.
Use:
Usage: Make [custom = customername] [module] "
Custom = Monza
Project = GPRS (GSM only)
Action = new (clean, scan, compile, link) (default)
= Update (scan, compile, link)
= Remake (compile, link)
= Clean (clean)
Module = component module name (nucleus, l1, ...)
Example:
To make / build new GPRS project, clean all old objects, libraries, and log files etc., the new action also creates necessary directories and removes all temporary files, and flushes log files automatically.
D:> \ pvcs \ maui \ mcu \ Make custom = Monza GPRS new
To update project dependency, and compile changed modules, link. Notice that, update and remake action won't remove temporary files, and flush log file. Build results will be append after last log file.
D:> \ pvcs \ maui \ mcu \ Make custom = Monza GPRS update
To recompile changed files, and link
D:> \ pvcs \ maui \ mcu \ Make custom = Monza GPRS remake
To clean all objects, temporary files, libraries, and executable binaries. Meanwhile log file will also be flushed.
D:> \ pvcs \ maui \ mcu \ Make custom = Monza GPRS clean
To clean dedicated init modules' objects libraries. Meanwhile log file will also be flushed.
D:> \ pvcs \ maui \ mcu \ Make custom = Monza GPRS clean init
-- "How to customize your build environment
! ! ! To add some modules into or remove some modules from the building procedure.
To complete this kind of configuration, it is necessary to understand the following variables in the make file
Monza_GPRS.mak
COMPLIST: list all source code modules can be built to. Lib. In initial custom release, COMPLIST
Should be the sum of CUS_REL_SRC_COMP and CUS_REL_PAR_SRC_COMP. The following is the initial setting in custom release.
Ifeq ($ (strip $ (CUSTOM_RELEASE)), TRUE)
COMPLIST = $ (strip $ (CUS_REL_SRC_COMP))
COMPLIST + = $ (strip $ (CUS_REL_PAR_SRC_COMP))
Endif
CUS_REL_MTK_COMP: list all modules provided with. Lib only. These. Lib are put in \ mcu \ mtk_libs.
If you want to add a source module
1. Add the module "xyz" (in lower case) into COMPLIST.
Ifeq ($ (strip $ (CUSTOM_RELEASE)), TRUE)
COMPLIST = $ (strip $ (CUS_REL_SRC_COMP))
COMPLIST + = $ (strip $ (CUS_REL_PAR_SRC_COMP))
COMPLIST + = xyz
Endif
2. Add a folder "mcu \ make \ xyz" for xyz.lis, xyz.inc, xyz.pth, xyz.def.
-- "Compiler generated documentation and log
1. Compiled log in the directory C: \ code_100 \ build \ a100 in MT6218B.log. Contents C: \ code_100 \ build \ a100 \ log under the log file for each module compiled generated log.
2. Bin compiler generated for the C: \ code_100 \ build \ a100 under a100_PCB01_gprs_MT6218B_FN.W05_12.bin.
3. The objective of compiling documents generated in the C: \ code_100 \ build \ a100 \ gprs \ MT6218Bo directory.
3. Analytic development directory structure
Reference Document: wcr - MTK_MakeBuild_Design_Customer_040930.pdf
Directory structure:
Directory names Contents Description
Build Generated object, libraries, executable binary and log files directory. The directory will be created
Automatically. For details, see "Generated Objects, Libraries, Executable Binary and Log Files" sections.
Make Main build scripts and option file directory.
Nucleus
Nucleus Plus RTOS source codes directory include C, Assembly, and included header files.
Init
System boot and hardware dependent initialization directory. Meanwhile, exception handling, and interrupt service routine dispatcher are also placed here.
Inc
System boot, initialization, layer1, and driver modules common included header files directory.
L1
Layer 1 source codes directory.
Drv
Driver modules source codes directory.
Custom
Custom's task / modules' sources and header files
Fast_DL
Cmm files for fast download [/quote]
Sprich doch mal mit looka der hat eine FLashbox gekauft 
