Hallo..
Vielleicht hilft das hier..??
http://blog.csdn.net/flyfish30/archive/2007/10/28/1852182.aspx
Vielleicht hilft das hier..??
http://blog.csdn.net/flyfish30/archive/2007/10/28/1852182.aspx
MTK Developement tool... Maybe??
- Starter*in Taddy
- Datum Start
- Status
den google translator nutzen.
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] <project> <platform> <action> [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
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] <project> <platform> <action> [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
2. Teil
Tools
Miscellaneous tools used in build / make and customer release procedures
Mtk_libs
Component libraries provided my MediaTek.
Tst
Database for trace
Verno
Source code for keeping version information
4. Understanding of development tools
Reference Table of Contents "tools" in the document.
Tools:
-- "Catcher
Catcher is a PC-side tool for MTK GSM / GPRS Products. The main purpose of Catcher is for logging primitives and debug information. Engineers can use Catcher to analyze the behavior of mobile phones.
-- "META
META (Mobile Engineering Testing Architecture) is designed to provide the functionality of RF testing, NVRAM access testing, speech related testing of advanced feature - melody and voice memo.
-- "MCT
UI production tools, including menu production, production photos, etc. produced fonts.
5. Import procedures, procedures Guide
-- "MMI task entrance:
C: \ code_100 \ plutommi \ mmi \ Framework \ Tasks \ TasksSrc
MMI_task MMITask.c function in the paper.
-- "The establishment of MMI tasks:
C: \ code_100 \ plutommi \ mmi \ Framework \ Osl \ OslSrc
The document called InitApplication pixtelMMI.c function WinMain function, the function of the establishment of MMI set up a task interface function: osl_create_task.
-- "MMI tasks:
( "MMI TASK" (task name), "MMI Q" (queue name), 127 (priority), 4096 (stack size), MAX_PRT_NODES (queue node number), MMI_task (task entrance)),
-- "MMI module entrance:
Contents C: \ code_100 \ plutommi \ mmi for MMI various modules of code. For example, alarm clock module, the source code in the C: \ code_100 \ plutommi \ mmi \ Alarm \ AlarmSrc, header files in the C: \ code_100 \ plutommi \ mmi \ Alarm \ AlarmInc in. First find the initialization function AlmInit alarm clock, the alarm clock function defined in the choice of menu items at the function call HighlightAlmMenu entered alarm clock function.
6. MMI production
Reference Document:
Name Description content
API For Writing Applications Using Pixtel MMI Platform.pdf
List all types of window
Writing Applications Using Pixtel MMI Platform.pdf how to write applications
MMI 2.0 Design DOC and MMI Design Doc directory on the MMI in a description of the various modules, a module in the study of these two documents can be found in the folder module, these documents can be accelerated through the module coding understanding.
MMI modules in the path C: \ code_100 \ plutommi in.
-- "Design an application process is as follows: --
1. Write an Initialization function to register the various event handlers.
2. Write a populate function to register various string and image elements for the
Application.
3. Write highlight handlers for function registered. Menu items and functions, when users choose menu items after the implementation of the function.
4. Write the Entry functions. Import function
5. Write the Exit function. Export Function
6. Write the business logic to call between various entry functions.
Tools
Miscellaneous tools used in build / make and customer release procedures
Mtk_libs
Component libraries provided my MediaTek.
Tst
Database for trace
Verno
Source code for keeping version information
4. Understanding of development tools
Reference Table of Contents "tools" in the document.
Tools:
-- "Catcher
Catcher is a PC-side tool for MTK GSM / GPRS Products. The main purpose of Catcher is for logging primitives and debug information. Engineers can use Catcher to analyze the behavior of mobile phones.
-- "META
META (Mobile Engineering Testing Architecture) is designed to provide the functionality of RF testing, NVRAM access testing, speech related testing of advanced feature - melody and voice memo.
-- "MCT
UI production tools, including menu production, production photos, etc. produced fonts.
5. Import procedures, procedures Guide
-- "MMI task entrance:
C: \ code_100 \ plutommi \ mmi \ Framework \ Tasks \ TasksSrc
MMI_task MMITask.c function in the paper.
-- "The establishment of MMI tasks:
C: \ code_100 \ plutommi \ mmi \ Framework \ Osl \ OslSrc
The document called InitApplication pixtelMMI.c function WinMain function, the function of the establishment of MMI set up a task interface function: osl_create_task.
-- "MMI tasks:
( "MMI TASK" (task name), "MMI Q" (queue name), 127 (priority), 4096 (stack size), MAX_PRT_NODES (queue node number), MMI_task (task entrance)),
-- "MMI module entrance:
Contents C: \ code_100 \ plutommi \ mmi for MMI various modules of code. For example, alarm clock module, the source code in the C: \ code_100 \ plutommi \ mmi \ Alarm \ AlarmSrc, header files in the C: \ code_100 \ plutommi \ mmi \ Alarm \ AlarmInc in. First find the initialization function AlmInit alarm clock, the alarm clock function defined in the choice of menu items at the function call HighlightAlmMenu entered alarm clock function.
6. MMI production
Reference Document:
Name Description content
API For Writing Applications Using Pixtel MMI Platform.pdf
List all types of window
Writing Applications Using Pixtel MMI Platform.pdf how to write applications
MMI 2.0 Design DOC and MMI Design Doc directory on the MMI in a description of the various modules, a module in the study of these two documents can be found in the folder module, these documents can be accelerated through the module coding understanding.
MMI modules in the path C: \ code_100 \ plutommi in.
-- "Design an application process is as follows: --
1. Write an Initialization function to register the various event handlers.
2. Write a populate function to register various string and image elements for the
Application.
3. Write highlight handlers for function registered. Menu items and functions, when users choose menu items after the implementation of the function.
4. Write the Entry functions. Import function
5. Write the Exit function. Export Function
6. Write the business logic to call between various entry functions.
Ich denke, das ist die richtige Spur.
Gerade gefunden:
Quelle:
http://www.gsmhosting.com/vbb/showthread.php?t=469588
Hi All the expert, does any one know how to embeded Java image file to make it possible our all chinese phone model work for all java application program?
I think, this is good forum to sharing each other how to embeded or added java application into our Chinese phone.
With this facility, our chinese phone model will easy to get applications software, java program software.
So, who the first know about this, please sharing it with us.
-------------------------------------------------------------------------------------------------------------------
Almost Chinese Phone with based on MT6227/MT6228 or others type of mediatek are using MTK software based on nucleus operating system.
Here the link of nucleus operating system:
http://www.mentor.com/products/embedded_software/nucleus_rtos/index.cfm
Nucleus OS is open source, and really posible to make embedded java into the phone.
Hi All the programmer expert, would u challenge this issue?
-----------------------------------------------------------------------------------------------------------------------
Here the link for Java source code download:
https://mobileandembedded.dev.java.net/downloads.html
------------------------------------------------------------------------------------------------------------------------
Ich bezweifle aber, das Nucleus open source ist.
Gerade gefunden:
Quelle:
http://www.gsmhosting.com/vbb/showthread.php?t=469588
Hi All the expert, does any one know how to embeded Java image file to make it possible our all chinese phone model work for all java application program?
I think, this is good forum to sharing each other how to embeded or added java application into our Chinese phone.
With this facility, our chinese phone model will easy to get applications software, java program software.
So, who the first know about this, please sharing it with us.
-------------------------------------------------------------------------------------------------------------------
Almost Chinese Phone with based on MT6227/MT6228 or others type of mediatek are using MTK software based on nucleus operating system.
Here the link of nucleus operating system:
http://www.mentor.com/products/embedded_software/nucleus_rtos/index.cfm
Nucleus OS is open source, and really posible to make embedded java into the phone.
Hi All the programmer expert, would u challenge this issue?
-----------------------------------------------------------------------------------------------------------------------
Here the link for Java source code download:
https://mobileandembedded.dev.java.net/downloads.html
------------------------------------------------------------------------------------------------------------------------
Ich bezweifle aber, das Nucleus open source ist.
kleenercectfan2
Entsperrt
http://de.wikipedia.org/wiki/Nucleus_(Betriebssystem)
hier falls es weiterhilft...darfin steht z.b. dass nucleus von mentor bernommen wurde. auf der Mentor.com seite oben steht auch das es Nucleus OS ist!
Der Nucleus OS USB bietet eine komplette Softwarelsung.
Hab mald ein vorteil von Nucleos USB bersetzt:
Der Nucleus OS Sicherheit Komponente ist mit Quellcode und ohne Lizenzgebhren erhoben. Der Quellcode ist ANSI C konform.
hier falls es weiterhilft...darfin steht z.b. dass nucleus von mentor bernommen wurde. auf der Mentor.com seite oben steht auch das es Nucleus OS ist!
Der Nucleus OS USB bietet eine komplette Softwarelsung.
Hab mald ein vorteil von Nucleos USB bersetzt:
Der Nucleus OS Sicherheit Komponente ist mit Quellcode und ohne Lizenzgebhren erhoben. Der Quellcode ist ANSI C konform.
Quellcode solte es dafr geben..
..aber wir mten es von bzw. fr mtk bekommen. Habe gestern noch ein bisschen in einer mtk-Werbebroschre geblttert, dort konnte man dann auch ber Nucleus lesen.
Mtk - Treiber usw. als unterbau. Nucleus als Betriebssystem.
Wir brauchen auf jedenfall beides.
Flash lesen / schreiben geht brigens ber serielle Schnittstelle.
..aber wir mten es von bzw. fr mtk bekommen. Habe gestern noch ein bisschen in einer mtk-Werbebroschre geblttert, dort konnte man dann auch ber Nucleus lesen.
Mtk - Treiber usw. als unterbau. Nucleus als Betriebssystem.
Wir brauchen auf jedenfall beides.
Flash lesen / schreiben geht brigens ber serielle Schnittstelle.
kleenercectfan2
Entsperrt
und wie bekommen wir das nun hin?
Gratis Download Nucleus Plus.....
http://www.acceleratedtechnology.com.tw/embedded/plus.php
bringt uns das weiter?
http://www.acceleratedtechnology.com.tw/embedded/plus.php
bringt uns das weiter?
Irgendwie finde ich keine Kompatibilität zu den MT CPUs der Chinahandys 
http://www.acceleratedtechnology.com.tw/embedded/cpu_nucleus.php
http://www.acceleratedtechnology.com.tw/embedded/cpu_nucleus.php
chinashenzhen
Gesperrt
The development platform
I have this development platform. If any body interested please contact me.
I have this development platform. If any body interested please contact me.
hello
I bought a chinese phone called Tiger G3 It runs MTK OS. I want to know more about this OS. I want to know more about it. What software do I need to connect to the phone? Can I do it with cable that comes with the phone? Do I need the MTK Development Platform?
What I know about the phone is when I enter *#8375# it says:
E706_GXT3V18.01.0
SERIAL#:E70601114000713
Don't know what it to be honest. Thank you for your help.
I bought a chinese phone called Tiger G3 It runs MTK OS. I want to know more about this OS. I want to know more about it. What software do I need to connect to the phone? Can I do it with cable that comes with the phone? Do I need the MTK Development Platform?
What I know about the phone is when I enter *#8375# it says:
E706_GXT3V18.01.0
SERIAL#:E70601114000713
Don't know what it to be honest. Thank you for your help.
Hello. Thank you for your reply. What makes you think that this phone runs Android? It's a replica of HTC Hero but it is just the looks which does not imply the OS is Android. How can I verify the OS?
Loonix
Spokenkieker
from your first link:
If you can install Android applications it runs Android.
I myself associate MTK with MTK's Nucleus OS Plus which is a very basic operating system that can (according to my knowledge) not be enhanced by external applications but by JAVA programms (and even that is very limited). It is a very popular OS in chineese clone phones because you can make it look like anything without its actual functionality.
//edit: OK, following another link in your first post i found some pictures that convince me that the phone is one of those knockoffs that run Nucleus OS:
Those are typical Nucleus OS submenu images.
Zuletzt bearbeitet:
thanks
Thank you for your reply, brother. Yes, this is the UI of my phone.
I am currently reading about MTK and Nucleus OS. Can I connect to the phone with a software program and try to play with the operating system? What program do I need? Do I have to download the MTK develpment platform or the Development Suite for Nucleus? In respect to JAVA what JAVA applications can I run and install on MTK/Nucleus? Any specific version or any specific applications?
Thank you for your replies.
Thank you for your reply, brother. Yes, this is the UI of my phone.
I am currently reading about MTK and Nucleus OS. Can I connect to the phone with a software program and try to play with the operating system? What program do I need? Do I have to download the MTK develpment platform or the Development Suite for Nucleus? In respect to JAVA what JAVA applications can I run and install on MTK/Nucleus? Any specific version or any specific applications?
Thank you for your replies.
Zuletzt bearbeitet:
Loonix
Spokenkieker
uh, yes... that is Nucleus OS, allright...
Nucleus OS is more or less 'Solid state' and it is hard to change anything in it.
You can try (if you can dump the Firmware) to use OXA's MTK Firmware editor (with that you can edit pictures (the skin) and build in tones (ring tones)
and maybe soon his Language editor too. at the moment i reccomend to try i9rosetta.
Those tools are originaly for i9/i68 iPhone clones and its Firmware but since they use the same OS you might be able to use them too.
To dump the firmware you will need a serial flash cable, but i have no idea if the flash pins are connectable from the outside on your phone.
For better help i would like to refere you to the GSMHosting forum because the forum is in english.
Nucleus OS is more or less 'Solid state' and it is hard to change anything in it.
You can try (if you can dump the Firmware) to use OXA's MTK Firmware editor (with that you can edit pictures (the skin) and build in tones (ring tones)
and maybe soon his Language editor too. at the moment i reccomend to try i9rosetta.
Those tools are originaly for i9/i68 iPhone clones and its Firmware but since they use the same OS you might be able to use them too.
To dump the firmware you will need a serial flash cable, but i have no idea if the flash pins are connectable from the outside on your phone.
For better help i would like to refere you to the GSMHosting forum because the forum is in english.
oliversum
Erfahrener Benutzer
We've got a special english forum, friends 
- Status
