MTK架构及系统原理-Glimon.ppt

,MTK平台架构及系统原理,讲解：Glimon 2009年7月,LONGCHEER CONFIDENTIAL,目录,MTK平台介绍MTK系统架构MMI软件框架总体介绍,MTK平台介绍,MTK平台介绍,什么是平台？平台是程序运行所依赖的环境。比如windows就是平台，它提供各种程序运行所以来的环境，不管是超级解霸还是msn还是ie都可以在windows上运行。当然windows是个大平台，很基础的。所以又叫操作系统。,MTK平台介绍,什么是MTK平台？MTK平台是手机开发和运行的一个环境为MTK套片开发了一套软件方案,MTK平台介绍,MTK平台有哪些？MTK芯片：6227、6225、6230.,MTK平台介绍,MTK平台操作系统？NucleusNucleusPLUS嵌入式操作系统是目前最受欢迎的操作系统NucleusPLUS是为实时嵌入式应用而设计的一个抢先式多任务操作系统内核，其95的代码是用ANSIC写成的，因此非常便于移植并能够支持大多数类型的处理器。从实现角度来看，NucleusPLUS是一组C函数库，应用程序代码与核心函数库连接在一起，生成一个目标代码，下载到目标板的RAM中或直接烧录到目标板的ROM中执行。在典型的目标环境中，NucleusPLUS核心代码区一般不超过20K字节大小。NucleusPLUS采用了软件组件的方法。每个组件具有单一而明确的目的，通常由几个C及汇编语言模块构成，提供清晰的外部接口，对组件的引用就是通过这些接口完成的。除了少数一些特殊情况外，不允许从外部对组件内的全局进行访问。由于采用了软件组件的方法，NucleusPLUS各个组件非常易于替换和复用。NucleusPLUS的组件包括任务控制、内存管理、任务间通信、任务的同步与互斥、中断管理、定时器及I/O驱动等。,MTK系统架构,MTK系统架构,设备架构芯片的外部设备及控制口,MMI软件框架总体介绍,MMI软件框架总体介绍,Application Layer,UI Layer,Operating Systen&protocol Stack Layer,Framework,MMI基本架构,MMI基本架构,Application layer(应用层)用户定义的应用.Framework layer(框架层)管理信息和事件处理管理应用流程提供抽象的操作系统UI layer(UI层)管理用户界面相关的功能。,代码结构,CustomerMMI,代码结构和导航,目录树Alarm:-头文件和源文件-闹铃应用程序。AsyncEvents:-包含头文件和源文件-处理异步事件如硬件和协议事件 Audio:-包含头文件和源文件-音频管理Calendar:-包含头文件和源文件-日历应用程序。CallManagement:-包含头文件和源文件-电话通话管理,代码结构和导航,Calls:call管理CommonScreens:包含头文件和源文件共同屏幕使用的所有应用程序。Date Time:包日期和时间的应用函数。Framework:管理应用信息，流程控制和操作系统应用FunandGames:FunandGames应用 GPIO:操纵各种外部设备，如背光，振子，发光二极管模式。GUI:管理用户界面相关功能。,代码结构和导航,Inc：包含头文件对所有应用include 头文件和宏定义MiscFramework:the Pixtel MMI platform 管理字体和支持Unicode Organizer:工具管理应用PhoneBook：电话本应用Profiles:情景模式应用,SAT:SIM卡应用工具包 Settings:设置应用程序 Shortcuts:快捷键的应用ToDoList：代办事项应用,任务结构-浅析,MMI Queue,NETWORKSIMULATOR/L4,NS/L4Queue,OPERATINGSYSTEMLAYER,MMITASK,任务结构-浅析,Tasks-任务MMI Task 管理应用程序。,任务结构-浅析,任务会从相关的消息队列中读取消息MMI Queue:L4向MMI Queue 写消息，MMI 从MMI Queue 读取消息。L4/NS Queue:The MMI task 将MMI 的事件写入L4/NS Queue，L4 task/Network Simulator从L4/NS Queue中读取消息.,任务结构-详解（续）。,MMI Task Waits on the MMI queue.通过协议栈从消息队列中提取消息。Messages in this queue are put by the Protocol Stack.Framework Layer 处理事件.Framework Layer 通过回调回到应用层Application layer 使用UI Layer category functions 和themes 做屏幕显示。,任务之间事件流程-示例1,两个例子：Key press events to applications.,Key Press Event,NETWORKSIMULATOR/L4,MMI Queue,FRAMEWORK,APPLICATION,任务之间事件流程-示例1,The Protocol stack writes an event to the MMI QueueMMI Task reads from MMI queueFramework makes application function callback for latest event registrationApplication receives key press event.,任务之间事件流程-示例2,Second example Request to play sound from applications,NETWORKSIMULATOR/L4,MMI Queue,FRAMEWORK,APPLICATION,任务之间事件流程-示例2,Application makes call to framework layer for passing message to L4 queue.Framework writes message to the L4 Queue.The L4 task reads event from the L4 queue and plays requested sound.,人机界面-简述,EventHandler,History,OSL,NVRAM,FileSystem,FILESYSTEM,CATEGORYSCREENS,UILAYER,UIELEMENTS,图像,字体,主体,GRAPHICSLIBRARYWRAPPERS,GRAPHICSLIBRARYIMPLEMENTATION,EventsFrom/ToL4,人机界面-简述,Framework layer（框架层）接收所有任务的事件帮助应用程序的控制屏幕流.提供封装的系统应用Framework的成员 Event Handlers 注册应用程序要求支持的各种活动Classification of events（事件分类）Protocol Events（协议事件）Highlight Events（高亮事件）Key events（按键事件）,人机界面-简述,History 有助于保持屏幕流应用和存储中间数据OSL 提供所有操作系统应用的封装函数NVRAM 提供数据存储和检索数据的封装函数 File System 提供从文件系统数据存储和检索数据的封装函数,人机界面-简述,History 帮助应用程序记录屏幕流并存储屏幕数据OSL 提供依赖操作系统调用的封装函数，NVRAM 提供来自NVRAM 的数据存储和检索数据的封装函数File System 提供来自文件系统的数据存储和检索数据的封装函数,人机界面-简述,Application Layer（应用层）包含用户定义的执行应用的逻辑代码,人机界面-简述,UI Layer（界面处理）提供了用户界面功能，应用UI 层包含的元素Category Screens封装各种屏幕的显示函数处理资源，如字符串ID和图像显示的保持独立的布局和外观屏幕的应用程序提供history接口,人机界面-简述,UI Elements这一层提供了显示能力和使用各种用户界面元素，如按钮，滚动条，菜单等这些是界面中的控件Themes负责实施一套固定的外观和感觉功能的用户界面元素Themes consist of物体形状和颜色字体使用(Font type,style,text color)其他显示属性,人机界面-简述,Fonts这是数据所使用的是图形库，显示屏幕上的字符Images一套独立的图像设备如：Icons,Splash screens and WallpapersGraphics Library（图形库）提供图形元包含显示字体和图像的功能,下面介绍一下模块的架构及其应用,handler,Framework LayerEvent Handlers Provides API for application to manage event handlers at run time.Keyboard Event handlers API Typically used by applications and category functionsSet key handler for particular keySet Key handler for group of keysExecute current key handler for key press eventClear key handlers for particular keyClear key handlers for all keysSpecial handling for Power and End Key,handler,Protocol Event Handler API Typically used by applicationsSet protocol event handler.Execute Current protocol event handler.Clear handler for specific protocol event.Clear all protocol event handler.Misc.HandlersExit HandlersSet Exit handler for particular screenExecute Exit handler for current screenClear Current exit handler,history,HistoryDatabase containing snapshots of screenImplemented as a non default LIFOStructure of history nodeScreen ID-of screen to be savedEntry Function Pointer to redraw the screenInput Buffer to save running text data for this screenGUI Buffer to save UI related information for this screen,history,History APIAdd Node to HistoryDelete N nodes from historyGo back N nodes in historyRetrieve history for a screenRetrieve input buffer for screenRetrieve UI buffer for screenDump History for debuggingInitialize historySubtle facts about historyIs implemented as stackFirst screen saved after boot up is never removedNew Nodes are added to the head of history,OSL Layer,OSL LayerProvides abstraction over system calls to make MMI portableFollowing Kernel objects are wrappedQueuesTimers,Queue,Queue APICreate QueueoslMsgqid OslIntCreateMsgQ(PS8 queue_name,U32 max_msg_size,U32 max_msgs)Write To QueueOSLSTATUS OslIntWriteMsgQ(oslMsgqid msgqid,void*msgPtr,U32 msgSize,OSLWAITMODE wait_mode)Read From QueueOSLSTATUS OslIntReadMsgQ(oslMsgqid msgqid,void*msgPtr,U32*msgSize,OSLWAITMODE wait_mode),Timer API,Timer APIStart a timerStartTimer(U16 timerid,U32 delay,FuncPtr funcPtr)Stop a timerStopTimer(U16 timerid),OSL,Subtle features of OSLSkin is loaded as bitmap.Button coordinates and Press Event(Up or Down)are calculated and passed to KBD task.Keyboard interface to test the functionality,UI Layer,UI LayerCategory Functions The category layer consists of a set of functions that an application can use to define its User Interface.Each Category screen contains the following functions:-Function to enter(display)-Function to exit-Function to get the size of History-Function to get the History,DEBUG,调试,Debugging Support,Debug LevelsDebug window is associated with simulator on PC versionAPI provided for writing debug messages to fileVarious debug levels are presentDEBUG_FATALDEBUG_ERRORDEBUG_INFORMATIONDEBUG_DUMPDEBUG_TEMPORARYDebug MacrosPRINT_FATAL(args)PRINT_ERROR(args)PRINT_INFORMATION(args)PRINT_DUMP(args)PRINT_TEMPORARY(args),Debugging Support,ExamplesPRINT_TEMPORARY(File:%s Line:%d n,_FILE_,_LINE_);PRINT_INFORMATION(n*In processIncomingEventsn);,剖析一个应用,Initialization RoutineRoutines to setup data for use in applicationsProtocol Event and Highlight HandlersStrings,Images and Menu resourcesHighlight HandlersRoutines that execute user defined code on high lighting the menu item.Entry and Exit FunctionsFunctions to manage flow of screen for an applicationForward flow of screen is managed by the applicationBackward flow of screen is managed by history,Customizing An Application,The menu items are initialized by the application in thePopulate functions using theADD_APPLICATION_MENUITEM macro.Example to Add Menu ItemsADD_APPLICATION_MENUITEM(MITEM_OPT_PSEUDO,0,2,MITEM_INC_OPT_ANSWER,MITEM_INC_OPT_DEFLN,0,0,2,STR_OPT_PSEUDO,OPT_PSEUDO_ICN);ADD_APPLICATION_MENUITEM(MITEM_INC_OPT_ANSWER,MITEM_OPT_PSEUDO,0,0,0,1,MITEM_INC_OPT_ANSWER,ICN_OPT_ANSWER);ADD_APPLICATION_MENUITEM(MITEM_INC_OPT_DEFLN,MITEM_OPT_PSEUDO,0,0,0,2,MITEM_INC_OPT_DEFLN,ICN_OPT_CDEFN);ADD_APPLICATION_STRING2(MITEM_INC_OPT_ANSWER,Answer“,”answer string”);ADD_APPLICATION_STRING2(MITEM_INC_OPT_DEFLN,Deflect“,”call deflection string”);ADD_APPLICATION_IMAGE2(OPT_PSEUDO_ICN,.IMAGES16x12NoImage.bmp“,”nomage”);ADD_APPLICATION_IMAGE2(ICN_OPT_ANSWER,.IMAGES16x12NoImage.bmp);ADD_APPLICATION_IMAGE2(ICN_OPT_CDEFN,.IMAGES16x12NoImage.bmp);This code will provides a screen as follows,谢 谢,