Đang chuẩn bị liên kết để tải về tài liệu:
Model-Based Design for Embedded Systems- Part 24

Model-Based Design for Embedded Systems- P24: This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to publish reliable data and information, but the author and publisher cannot assume responsibility for the validity of all materials or the consequences of their use. | 196 Model-Based Design for Embedded Systems FIGURE 7.6 MpCompose tool. The application capture The platform description The set of directives optionally generated by the MpAssign tool The MpCompose tool relies on a library of abstract communication services that provide different communication mechanisms that can be inserted in the application graph. Three types of services are currently supported by MpCompose 1. Local bindings consisting mainly of a FIFO implemented with memory buffers and enabling the intra-processor communication e.g. block B1 is connected to block B2 via local buffer LB1 2 . 2. Global binding FIFOs which enable the inter-processor communication e.g. block B1 on PE1 communicates to block B3 on PE2 via external buffers GB1 3 . 3. A scheduler on each PE which is configurable in terms of number and types of blocks and which enables the sharing of a processor between several application blocks. A set of libraries are used to abstract part of the platform and provide communication and synchronization mechanism point-to-point communication semaphores access to shared memory access to I O etc. . The various FIFO components have a default depth but these are configuration values that can be changed during the mapping. Since we support custom data types for I O port tokens each element of a FIFO has a certain size that matches the data type and maximum size specified in the intermediate format. MPSoC Platform Mapping Tools for Data-Dominated Applications 197 There is no global central controller a local scheduler is created on each processor. This component is the main controller and has access to the control interface of all the components it is responsible for scheduling. The proper control interface for each filter task is automatically added based on the type of filter specified in the application IR and connected to the scheduler. The implementations of the schedulers are partly generated for example the list of filter tasks a static list and some .