tailieunhanh - Model-Based Design for Embedded Systems- P35

Model-Based Design for Embedded Systems- P35: 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. | 306 Model-Based Design for Embedded Systems are different ways in which the cost may be calculated. Steps 6-7 in Figure illustrate two different types of processing elements that may be used and the interface to inform them which processing routine they should compute a cost for. The type of the processing element may be changed easily to provide the necessary balance between the speed of simulation and the required pre-simulation effort. Mapped System Table describes the 48 mappings investigated. These vary from 11 PEs to 1 PE. Partitions are broken down by the Rx the Tx the RLC and the MAC functionalities. Each is categorized into one of nine separate classes based on the number of processing elements and the mix of pre-profiled and runtime processing elements. Mappings are further categorized as purely runtime processing RTP elements purely profiled processing PP elements or a mix MIX . Results Results relating to the design effort the processing time the framework simulation time and the event processing are analyzed. Five different models were used a timed SystemC UMTS model 55 a timed Metro II UMTS model an untimed Metro II UMTS model a SystemC runtime processing model and a Metro II architectural model. In specific configurations Metro II constraints were used as opposed to explicit synchronization. The selection of constraints functional model configuration architectural model parameters and mapping assignment is all achieved through small changes to the top-level netlist. All results are gathered on a GHz Pentium M laptop running Windows XP with 1GB of RAM. Figure shows the UMTS estimated execution times cycles along with the average processing-element utilization. Utilization is calculated as the percentage of simulation rounds that an architectural processing element has enabled outstanding functional model event requests for its services. Low utilization indicates that a processing element is idle despite available