Home

CoMET 5.14 User Guide

1. T eHalle ECE B AART Anan SS S Ole H S gt BOB H CG workspace 2 RE SimpleYSP1 Simple SP1 c ax E Workspace SimpleVSP a i i H i System F c apr 2 include SimpleVSP1i h Elapsed Time E E Source Files 3 include vast std types h ies fair ee 4 include ampi symlink dll body h ARM926EI51 o e E Simple SP1 c Rann aip a catia Be 5 inc lude les JE imulation Time fo SimpleVSP 1 Frix ee Simple SP1 Simple SP1 fmx Consumed Time 3 SimpleVSP 1 rc Fee Simple SP1 Instructions i ampi_symlink_dll_body c 8 i fe Parameters PoP b ampi_symlink_init c Sy Header Files a Document Windows Target Window E B SimplevSP1 h o BS ClockNet E ampi_symlink_names h 12 pe a ResetNet i t B config h 13 t fez StdLogicONet _ Workspace Window 14 Be Tasks i x Mody Expand Tasks Ctrl E _ pistat lS Generated Files SAP a a Collapse Tasks Ctrl L i ga Configurations 17 eae 2 4 _ BE s Nova2 cDil Debug E Be Add Task B a Nova2ycDlI Release E j i ga SI Edit Tasks F2 Gy C Includes agi 0t Context Menu P faa i faa i be ee es 24 i Cut Tasks Ctrl x _ Bae Tarosts 22 E Copy Tasks Ctrl C EEA virtualPlatform i py pec 23 i J Paste Girl El Folders za P d g a Source Files BER v v xml Tree view VirtualPlatform c a g l iia alg Memory Parameter View E i EN Bus Parameter View a od l i Sno E vpm Parameter Vie
2. E SystemCStandalone cpp basen H SystemCStandalone rc ani ampi_ s stemc_ dil body cpp ies ampi_s rolink_init c SI a Header Files an System Standalone h a ampi_symlink_names h ee E config init h nns gE config_struct h a config symlink h SE config _types h gE resource h m version number h oy gc aniguraticn via SystemC cbDill Debug ai ikr T Includes lt c wwast5_hometSystemCiinclude El J C Libraries i pe systemecd lib fe system lib a a Runtime Options H AP SystemC cDI Release You need to choose SystemC libraries that correspond to the version of C compiler you are using See Choosing the SystemC Libraries for VC 6 VC 7 VC 8 and GCC page 166 Creating a CIF SystemC Project A module instance of a project of this type can be created in a CIF platform To create a CIF SystemC project choose Workspace Add New Project In the Workspace dialog Project VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 165 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 4 and SystemC Compatibility Creating SystemC Projects panel select a project type of Fabric See Adding a New Project page 45 Specify a name for the project and select other options as required In the Project dialog Fabric Module panel Module Class field select Peripheral Model Systemc CoMET creates the project files from templates aj JEA
3. ccccceeceeeeeeeeeeees 5 PIONS E N E E E T 29 CoMET configuration ccceeeeeeees 26 SOURCE TICS pcos tae diouncuoreanedcoeeansemetnasedoys 129 COMET Editor isernia seomtecedenaseceeenes 129 environment variables cccsssscceeeeeeeeeeeees 6 CoMET environment 26 ATI eect cicssee iene psuclga a nonaeceiaeesueusaualns 7 configuration PVA AV OI oo pecisah cictmctincns rash cubrexsieevatchciasentine 6 COMPE orr E EN 26 Exporting editor OptiONS sisien 29 Target Binare S sssini oreen 58 general configuration cceeeeeeeeeeeees 26 ES gee ee een eee ere ee ee 57 Connection View ASK 0 0 lt 01 1 lt a eee 57 XML Table Views cccccccccccccseeeeeeeeees 99 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 197 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Index F CC SCE DU OM de sce dacaiedasossce areo e 14 Fabric O NIAC e E EE E A E pi _ l Fabre ModileDeniniion Opening an existing project eee 50 EE 63 Output Windows ccccccceeeeeeeeeeeeeeeeeeees 13 TRG ORE e E 100 P Fabric Module type isc ccccescaceetedecesstetecnsscetences 47 l ie ey a Parameter Overrides sscasscacosaldatavsabsagnasaecaneesed es 89 omei 129 Viewing in Prototype Repott 105 PEIEE EE E Parameter ce IFAT EE E AOT 14 27 63 97 l Connection View ccccssesessseesssesseeeeees 99 NIN TN ACM a E e Report ccccecssssscssccecsssscceccsss
4. When you have defined the list of project source files you can build the Virtual System Prototype The build process compiles and links the source files and libraries creating a simulator executable file image To build the Virtual System Prototype From the Workspace menu select a Build or Rebuild option or Select the Rebuild tool bar button or Select the Rebuild All tool bar button Clean All Batch Build VaSTI SYSTEMS TECHNOLOGY Confidential and Proprietary 137 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Building the Workspace and Projects Special Editing Keys The following describes the purpose of each Build option Rebuild Builds the active configuration for the active project Clean Removes all built and CoMET generated files associated with the active project Rebuild All Builds the active configuration for all projects in the workspace Clean All Removes all built and CoMET generated files for all projects in the workspace Batch Build Allows you to select which configurations and projects are to be built CoMET begins building the system model While CoMET is building the system model the Build window displays messages generated by the compilers To view a source file where a compile error has occurred double click the compiler message in the Build window To stop the compilation before it terminates From the Wo
5. Open File PobReqisterResets llRegisters IP gt pPpBDemobdeviceRegisters PdbstdBustasterReset IF gt pMasterBuslata FALSE Cue Etr PdbStdLogicMasterReset IP gt pTransferCompleteData FALSE COPY Ctrl C H Paste Gey tWords2 Index for Index O Index lt 16 Index PohstdVectorMasterReset IlP SpVectorDriverOutputData Index FALSE Properties Ctrl F I t PDBResetDeviceEnd PDBDemobevyiceResetUserDPatalIP EnteringReset NOTE Ifyou attempt to use the Go To Definition function without building the module a warning message will be displayed indicating that the identifier could not be found An example of such a warning 1s shown below Ci x Unable to find pTaskInstanceName xe is the project built in ve Debug mode To fix this error simply build the module see Building the Workspace and Projects page 137 134 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Locating Symbols with the Browse Database Using the Source Editor Browse Symbol To see all occurrences of an identifier or symbol in code select an identifier right click and choose Browse Symbol from the context menu Browse Symbol Xx PobGenerated PdbDemoDevice registers h 55 PobGenerated PdbDemolevice_registers h 56 PobGenerated PdbDemoDevice registers h 54 PobGenerated pdb register tyoes h B2 PdbGener
6. Vasl SYSTEMS TECHNOLOGY CoMe i ee eels User guide VaST Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET Version 5 14 User Guide VaSTI SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Document Version No 1 0 Copyright 1997 2006 VaST Systems Technology Corp All rights reserved The copyright owner of CoMET hereby disclaims all warranties relating to this software whether express or implied including without limitation any implied warranties of merchantability or fitness for a particular purpose The copyright owner will not be liable for any special incidental consequential indirect or similar damages due to loss of data or any other reasons even if the possibility of such damages has been advised The person using the software shall bear all the risks as to the consequences of using this software RCA aioe ercccc A E A N R i WEDGE OU CUNO Mocs cask seer atedeccsceatelcteceaceseest secesteceuestecacceessasncustatseeesiessesisseastetsiessesbiechseeieierient About This Nan A a2 5 tncatscteangceanssnn EN FRM CIC e T EET AO OTEN PE E EA T AEA A Wbhbars New COME UE cour ct Sars ecenin ann EE EEEE E TNS OMET a e E E N E R Visual C Version 8 and Version 8 Express Supported ccccsssss
7. ao Witt Wirt 40d Tools ae virt Edit Project F2 an am Delete Project Del is a E am Cut Project Ckrl EJ Genera Copy Project Ctrl C E Paste Ert E Configurati Hga Targets Activate Project Ctrl A Project Properties Ctrl F h or Select the project in the Workspace Window and press Ctrl A VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 53 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Configuring a Project Configuring a Project When you create a new project depending on the project type COMET automatically generates a set of files and build configuration options Generated files contain skeleton code providing a basis for further development This list of files and options is maintained in the Project pjx file You can add and remove components such as source files and other alter options via the Workspace window interface This interface follows the general COMET methodology for managing configuration files Right click on an element and select an action from the context menu x El eel Workspace POBDemoDevice A EM virtualPlatform E O Folders a Source Files Eoo hu E VirtualPlatForm c oo E VirtualPlatForrn fm TA E virtualPlatform re a E ampi_syrmlink_dll_body c ampi_syrnlink_init c ov Header Files H A Generated Files ce ies Configurations Ea SimpleTimer SB SimplevsP1 O Folders H E
8. The tab file contained declarations of PLI functions This is not required for Fabric modules For non Fabric projects that use Behavioral C PLI functions there is an alternative approach to using tab files If you have Behavioral C projects that use tab files you may continue to use them or you can update the projects to operate without tab files To update such projects to use no tab file Remove the vpa_ prefix from all user tasks Change the function type of all user tasks from void to tAmpiUserTask Delete the entry in the tab file field from the HDL tab of the project settings dialogue box Delete the tab file as it is no longer required 112 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Build Configuration Configuring Build and Runtime Options Alternatively to use tab files specify the required tab file in the VBus project dialog Tab File field If you leave the Tab file field blank COMET assumes there is no tab file and operates in the No Tab File mode VBus CIF Build Configuration Properties x Configuration Properties Tes Noviccol Mode Debu o Path MovaDebug a C Options DNOVA2 DMODULE DPRE_SYMLINK_INIT_RE Link Options PO Define File fvBusCIFDemo def Device Type SlaveDny O Device Regions Poo Memon Regions OO Active Cancel Apply H
9. To add a file click Add then browse to locate the desired file Repeat until you have specified all desired files To remove a file from the list select the file and click Delete To directly edit the file path select the file and click Edit When the list is complete click OK Export Files OK notes notes bet Cancel Add Edit Delete You can add an entire folder to be included in the exported Workspace In the Export Workspace dialog click on the Folders button COMET displays the Export Folders dialog To add a folder click Add then browse to locate the desired folder Repeat until you have specified all desired folders To remove a folder from the list select the folder and click Delete To directly edit the folder path select the folder and click Edit When the list is complete click OK Export Folders 7 notes Edit Delete VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 59 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Exporting a Virtual System Prototype Workspace for METeor Location of extra files and folders in Workspace CoMET determines the location of extra files and folders by their path relative to the Workspace folder If extra files or folders are within the Workspace folder they appear in the same relative path within the exported folder If an extra
10. Using the Matlab Generator As in CoMET 4 you can generate Matlab source from a Matlab Interface ml1 file When CoMET 5 converts a COMET 4 VBus project it detects tools settings that specify the mli file and includes the mli file in the converted project To generate the Matlab source choose Tools Matlab Generator This tool is only applicable when you are using a Workspace containing a converted CoMET 4 VBus project that included a Matlab interface After generating the source according to the mli file specifications follow a similar procedure as that followed in CoMET 4 to externally compile the dll Link the dll into the CoMET 5 VBus project and build as for other CoMET 5 projects For more details see Application Note Converting CoMET 4 VBus Projects to CoMET 5 VBus Projects VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 159 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 4 and SystemC Compatibility Running a VBus Peripheral Model on CIF Running a VBus Peripheral Model on CIF You can import a VBus peripheral device model into COMET 5 A VBus peripheral device model can then be instantiated in a CIF platform and simulated as if it were a CIF model Creating a VBus Peripheral Model Project Choose Workspace Add New Project Workspace Simple SP f i x Project Project Name E UsPernpheralD evice Location Ic work cometoroa
11. VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 57 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Exporting a Virtual System Prototype Workspace for METeor Choosing Export Options Export Workspace x Project Configurations fs armd2be_ x1 system Nova cD Debug Export fs _arm zbe_ 1_spstem Nova cDI Release Itt arm be_ 2 system Nova cDI Debug Files fs _arm zbe_s2_ system Nova cDI Release fs ecl2Z00 1 system Nova cD Debug Folders fs ecl2Z00 1 system Hovas cDI Release viterbi ArnCcapp Debug viterbi ArnCc app Release e n o a m Target Binaries Select All Select All Debug Select All Release C Select All Novaz cDil Debug Select All Novaz cDill Release 1 Select All AmCc400 Debug E In this list you can specify one or more configurations to export What files are exported depends on the type of project you select Files Exported for Specified Projects Fabric projects COMET exports the dll files for all modules within the platform It also exports the project pjx file and the Prototype Configuration File pcx associated with the selected Build Configuration You can choose to export the target binaries associated with the project To export associated target binaries check the Export Target Binaries check box Target projects CoMET
12. Build Options Build All Target Time Limita Simulation jo ls Real jo Target Options Simulate z Prototype Options Active Prototype To add a workspace Click the Add button Browse for the workspace To delete a workspace Select the workspace in the Batch Mode dialog Workspace Paths list Click Delete VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 147 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Building and Simulating in Batch Mode To Edit the workspace path as text Select the workspace in the Batch Mode dialog Workspace Paths list Click Edit When the list is complete you can select options to determine how to build and simulate all of the items in the list For each workspace in the list there is a separate set of options Build options None Build nothing Build All Build all projects in the workspace This has the same effect as selecting the Build All option from menu or toolbar Rebuild All Rebuild all projects in the workspace Same as selecting the Rebuild All option from menu or toolbar Prototype Options Active Prototype Simulate only the active prototype All Prototypes Simulate all prototypes in the workspace one by one in the order in which they are listed in the workspace Target options 148 None Simulate nothing Simulate
13. Click the Versions button in the About Box dialog box Versions Path cuerhvastycometh ampbinamp debugger io dll cusrvastycometS 4amphbinvampi_ipe dll 1 6 0 cuervastycometS amphbinvampl memory alloc all 1 6 0 cuervastycometS 4amprhbin amp metris all 1 6 0 cusrvastycometS ampibinvampl model memnary dll 1 6 0 cuervastycometS 4ampibinamp streams dll 1 6 0 cuervastycometh ampbinvampi stream_file ll 1 6 0 cuervastycometS ampibinvamp stream pipe dll 1 6 0 cusrvastycometh amprs binampt debugger ic dll 3 75 0 cusrvastycometh ampis bin amp pc all 32 0 cuervastycometh amprs bin amp menor alloc dll 32 1 cusrvastycomethampis binampimetrix dll 3 4 0 cusrvastycometh amprs binampi streams all 32 1 cAusrvastycometh amprs binamp stream_file dll 32 1 cusrvastycometh amprs binamp stream pipe all 32 0 cusrvastycomethampi binampi stream vcd dll 322 cusrvastycometh amprs bintsys loader exe 3 4 0 cusrvastycometS amprsbinisys loader gcc exe 3 4 0 cusrvastycometS amprs B instil _ cott dll 1 0 1 cuervastycometSamprs bist ctrl dll 3 7 0 reru arh anra At A rani 0 Bek HL alf Al 37 The list of tools and models can be sorted by Path or by Version number Click OK to close the Versions dialog box Note When you close the Versions dialog box using the OK button the list of tools and models and their respective version numbers are automatically saved to the buffer Thus to keep a record of the tools and models simply save the bu
14. Parameter Overrides Hame Type Value Descnpton Number OfMemory Blocks tv ord32 3 Determines the size of the array of GenericMemoaryl module instances Detail entries show a Module Path Submodule list and module instance properties All Parameter Overrides are shown in a table Use links in the Module Path list to navigate to higher levels of the hierarchy Use links in the Submodules list to navigate to submodules The ModuleType entry links to the Fmx file for the Module corresponding to this module instance Viewing All Connections in a Virtual System Prototype The Module Instance Parent Connections entry links to the detail entry for this Module Instance in its parent module Fmx Report which shows all the connections for this Module Instance By navigating to module instances and viewing their parent connections you can use the Pex Report to view every module instance in the Virtual System Prototype and its connections To navigate around the hierarchy click links in the Module Path list the Submodules list or return to the top of the file Ctrl Home in IE Mozilla to use the Structure tree map Click ModuleType links and Parent Connections links to view Fmx Reports By using the first window as a menu you can easily return to base 106 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Viewing Module D
15. The platform NumberOfMemoryBlocks parameter determines platform and VSP structure You can then regenerate the pcx file by rebuilding the VSP project Module Instance Parameter Overrides appear in the pcx for each member of the array E ge Simpler B ko Module Instances E 7 EH Top pa Parameter Overrides H E vastopRkeseti iy Pe epee 3 Ge 2 Parameter Overrides g aP ee Parameter Overrides F VastGpStdLogicOl esi GenericMenory1 0 EAEN GenericMenory1 1 HEE GenericMemory1 2 Eel ARM9Z6EI51 Ee StdBusl The generated pcx file shows a set of Module Instance Parameter Overrides for each member of the GenericMemory array Such a build time parameter should not appear in the Pcx file You can control whether a Parameter Override appears in the Pcx file using the Parameter Pcx Access attribute Set Pcx Access to Private to prevent generation of a Pcx Parameter Override See Parameter page 78 Note that the above pcx file does not contain a Parameter Override for the NumberOfMemoryBlocks parameter as the NumberOfMemoryBlocks Parameter Pcx Access attribute is set to Private VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 123 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Target Executable Setting the Target Executable If the module includes a Virtual Processor Model instance CoMET requires target code
16. Description Bus Protocol selection You can view the attributes of a Module Instance Parameter Override but the only attribute you can change is Value If the original Parameter has Protected access the Value cannot be edited Name This name matches a module Parameter name Type This name is derived from the Type attribute of the corresponding module Parameter Value This contains the value that overrides the corresponding Parameter value Default Corresponding Parameter value Pcx Access Determines access to this parameter via a Parameter Override from a Prototype Configuration pcx file in which an instance of this module appears Allowed values e Public Visible and editable in pcx e Protected Visible not editable in pcx e Private Not visible not editable in pcx See Parameter Fmx Access Pex Access and Parameter Overrides above Parameter Override Values can be modified in Parameter Views See Parameter Views page 98 Description This description is derived from the description attribute of the corresponding module Parameter VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 91 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Parameter Override Changing the Override Value To alter the Override Value of a Parameter Override element Either Double click on the Parameter Override element or otherwise open
17. The fmx file opens in a document window Several views of the fmx file are available 2 Simple SP Simple SP 1 Simple SP 1 fmx 1 2 lt DOCTYPE FabricModule SYSTEM er use vast comets Configi FabricModule v1 1 0 3 4 lt FabricHodule Type SinmplevaPri 5 Version 1 0 0 6 InitFunction SimpleVSFiInitModuleInstance 7 ExitFunetion SimpleVSPLExitMNodulelnestance S Class Sr g SuHClasa mr 10 Desce iption x 1i Amlversion iais O0T gt 12 13 Parameters gt 14 15 lt Ports gt 16 17 lt Nets gt 16 19 lt Net Name ClockMet 20 Type atc lock z1 Mumberor i 22 Deseription This Connects the War Glock to the VirtualPlatciorn 23 24 lt Net Mame ResetNert 25 Type StdLogic 26 Numberof i XML Text View 64 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Opening the Fabric Module Definition file Developing a Fabric Module Definition Right click on the Document Window to select the XML Tree View from the Context Menu 22 Simple SP Simple SP1 Simple SP 1 fmk Simpley SP 1 ie Parameters Ports Bis g Mets HBa ClockMet a ResetMet 2a Tasks i Module Instances EME vastapReseti loo Instance Ports ES VastGoclock1 l Ge Instance Ports nga Parameter Overrides EE VirtualPlatForrd Fle Instance Ports El
18. cccccccccccccccccecesceeesceeeeeeeeeceeeeaeeeeeeeeeeaeeeeeeeeeeeeeas 6 Fovionmnent Variable ic scacustincasaenionundennldannaaedinascacnateansdauceupeinsneiaencasteeesadecasseseoudiuaneceians 6 Changing Environment Variables in Windows XP or Windows 2000 eee 7 Installing COMET on a NetWworKk nnnnnnnnnennrrrerrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrerrrerrrrrren 8 Prepa Oi aea E E E E E EET E 8 COME Tas CaO Wl enrian a eE a a ARAE a Tarna 8 Copying a COMET Installation ccc cccccccccccceccceeeeeeeeeeeeeeeeesesesesaeseeeeeeeeaeeeeaeaaas 8 On each Workstation cccccccccccccccccecesceeeesseeeeesssnnneeeeeeeeeeeeeeeeeseeeeeeeessaaaeeeeeeeeeeseeees 9 S DIDP WO Ca O e e E E EEE A E AE E 9 Set XML R ports LG CATIONS sissrsersissirisir titrs ri nir Tenra n t EAEE ENAN EENET 10 Uninstalling C OME T esnirassssosniieue iti s orii un prei En nEaN E RAA N SEI EE EAE NAN RRI S 10 Ceno SEAL E aaa E E EE 11 Starting COMET in Windows XP 2000 cccccccccccccccccceeeeeeeeeeeeeeeeeeeeseeeeeseeeeseeeeeaeess 11 The CoMET System Engineering Environment cc cccsssssssssssssesssssseseeeeeseeeens 12 DVN STNG BS AD eane a E E E O 12 Tool Da eea E 13 U Da e a E E E susucvsasqetmateayeccossoncoseseeeec 13 Workspace Window eeoeneeeneennnenssssssssessssssssesssessssssssssssssssssssssnssssssssnssnnssssnnnsnnnnno 13 Tapet VV OW serierrnrinriniri rinin iE ESEE EEEE EEE EEEE EEEE 13 Qutput W INdOW Seescrenieerei ri aren
19. Choose Add Tools from the context menu El Workspace Simple SF Eie E E Folders Expand Project Ctri E E j Soure Collapse Project Ckrl L E H 4 Head i Sy Gene Bi ae Configure Edit Project FZ cee Targets Delete Project Del VirbualPlatFort ut Project EEF Workspace Copy Project Ctrl C Paste Etrit Activate Project Ckr 4 Project Properties Ctrl F CoMET adds a Tools node H EA Simple SP1 ch Folders H 4 Source Files H E Header Files ol 4 Generated Files E Configurations n E a Boos a A virtualPlatform Workspace YaST Modules To add a tool to the Tools list Right click on the Tools node Select Add Tool from the context menu CoMET displays the Project dialog Tool tab 152 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Running External Tools during Simulation Simulating and Debugging a Model Project x Tool Properties Mame M y Console Path Jc work projects MyConsole mpconsole exe Parameters kiy Target aiT arget hi Target Test Hol anget AllT argets Project dialog Tool tab Properties panel Name Type the name under which you want the tool listed Path Browse for the path of the tool executable Parameters Specify command line parameters for the tool Target Choose the Targets with which the
20. Module Class Virtual System Prototype Virtual System Prototype Module Type Virtual Platrorrn Penpheral Model iWlesshare Pernpheral Model FCE Peripheral Model Matlab Fernpheral Model SystemC lt Back Cancel Module Class Each fabric module has a module class Different module classes have different properties such as build configuration and runtime options For more details see Setting the Build Configuration page 109 and Setting the Runtime Options page 117 Virtual Virtual System Prototype A module that defines the top of the VSP hierarchy The top level module differs from other modules in the hierarchy in that it does not contain any external connections Platform A module that defines a hierarchy instantiates other modules but does not contain any behavioral functionality Peripheral Model A module that contains behavioral functionality but does not instantiate other modules In this case a project is created that consists of a Peripheral Device Template with generic generated common functions The template provides a reference upon which specific device models can be based VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 47 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Adding a New Project Peripheral Model PDB A module that is built and managed using the Peripheral Device Builder
21. See Viewing Module Definition and Prototype Configuration Reports page 100 Arrays You can declare Port Net and Module Instance elements as arrays This allows a single element definition to take the place of multiple similar elements and simplifies operations on multiple similar elements Members of arrays share attributes Array notation provides for declaring element arrays and referring to members within the array See Port Net and Module Instance below Declaring an Array Element arrays must be declared with the required number of members To declare an element array you can use either the Number Of attribute or an array notation declaration in the element name Array Notation Declaration You can declare an array of elements by using array notation in the element name An array notation declaration follows the element name with square brackets containing the dimension of the array using the same syntax as declaring an array in C For example to create a 16 element array specify the name of a Net as MyNetArray 16 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 67 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Arrays S Fabric Module a x Het Properties Name MyNetiray 1B Type Stdlogio tt sts lt s YS Number OF Description Example of declaring a net array using array notation The Numb
22. The execution continues to the end of the current user function and halts at the line of code following the line of code that called the current function If the current function includes another breakpoint execution halts at the breakpoint To step over a statement From the Debug menu select Step Out Or a Click on the Step Out tool bar button Using the Target Debugger Break Button During a Target debug session a Break button appears for each VPM module instance selected for Target debugging The Break button appears in the Workspace window Target tab The appearance is similar to the button shown below 144 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Validating VPM behavior Simulating and Debugging a Model System Elapsed Time ARMI6E IS 1 Simulation Time Consumed Time Instructions Click the Break button to break execution and launch the external debugger associated with the Target code See the external debugger documentation for further information Validating VPM behavior Validation mode is a special execution mode provided for customers who need to validate the Virtual Processor Model behavior against the microprocessor manufacturer test suite Validation mode runs test target code on the Virtual Processor Model and returns a pass or fail status indicating whether the VPM correctly conforms t
23. 1 in the StdVector32 will be mapped to a 1 Driven High and a bit value of 0 will be mapped to 0 Driven Low e For details on how to select Fabric port types for mapping to VDHL ports see Selecting a Fabric Port Type for a VDHL Port page 176 Running a VHDL Model on CIF Tool Locations Configuration Settings for VHDL Model In CoMET Configuration Tool Locations tab set ModelSim to point to ModelSim home directory See Tool Locations Configuration Settings page 31 CoMET Configuration 4 x General Editor Options Tool Locations User Locations ML Tables Modules Environment Arme C Program FilesW4AM aDSy1 2 ArmeE lace Cdb C Program Files Debugging Tools for Windows FinSim ee cWusrvvast cometh Gec Matlab Mipse face ModelSim C Program Files Modeltech_6 Uc Marc C Program Files Microsott Visual Studio NET 2003er FlatformS dk C Program Files Microsott Visual Studio MET 2003c r Flato Sysheml c uerwastycomets S ysteml WOOUE IGC Cancel Apply VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 171 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support VHDL Co Simulation Support Creating a VHDL Model Project Choose Workspace Add New Project Workspace Simple SP i l xX Froject Project Name TestHDLM odel Location Ic Work cometprojects T estyYHOLM odel E C C
24. 89 PE ARIA UC OV doe N E EE 89 Parameter Fmx Access Pex Access and Parameter Ovetrrides ccceececeeeceee ee 90 The Pex Access Field is Always Editable in a Parameter Override 91 Changing the Override Value cccccseessssssssesessessessssssseesseesesssseeseeeseseeseeeeegs 92 SUb Piram OVENI ES asea A saab RES R 93 IMS ance OM aa E E E E ebedetenenease 94 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary V May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Contents CoMET 5 14 User Guide ITASCA TCS OIG ipo se orreyentes coxenede aoxenaten E E E E N A 94 Porn COMME CLIC Hs cscscecasganetcnsssunbecasdesesenacgupssapsieeseonstantsoniadunaracgensdunsieeseensdanseebiedssyoobeoses 95 ATS ACS seats sc E E E E E A E AA A E S 96 JEE EE a i o EEEE AANE NEE IA EN EREE A AEEA A E E 96 Views and IRCION US so sectcrseseciscesanscicsssascuswesacssceasscconcssicedciasscccucasacsseissseauveasaassciassecisiaacsies 97 MS Stn MUG N ON soseerecsc cere T duc vsacncusesaaaacactar tacsaaasonsianacieeetnssonssare eens 97 Changing Column Order csc se secese cassie ee ones seco se scene ancl E REKEN KENEN TEETE 97 Pad AMG tel VVC W S 5 srcuecaneacinsstnrausdasvoqebedenietonsaamancinssinieGusdaudonebe E ESNA EEEN ESENS 98 OTS OTL VT WS ee eens ats pee cece E E E E EEEE 99 Viewing Module Definition and Prototype Configuration Reports ccccee 100 Viewing a Fabric
25. COMET ONOS LINKS sen re E E EE 42 COMET WeD Paine atc soe vedas snd otcesvacsessossesectovadsesso EEEE ES 42 COMET Support Services pcicccspacctdacsnenonacrnancusmsncadannecennosnawenschmeneusonsicenaagicentensen 42 Managing Workspaces and Projects ccooossssssseseccccccecoocosssssssssesesceeseosooosssssssssesee 43 reann a WorkSpace neaiiorisrorn n horier E O Eiee 43 Adding a New PIO CCU oncdavensiniasiosaissinaconsnisnedaineibavedsindeidedeinessusaordnionatersibaradendsbdedercseeoneress 45 Defining a Fabric Module sccisnseisiccsoaspsconternndotaspdnonaceinsiiennaspaundterasssnndannadensenpecentaniens 47 Modul Clag ees E E E E S 47 Module TPE een a E E E AEE S 48 VEON re e E E E E N 49 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary iii May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Contents CoMET 5 14 User Guide Project Conn gorao yenen EE tastes ENNE 49 Adding an Existing Project ccccccccsssssssseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 50 Removing a Project from the Workspace ccccccceesesseseesessesseeeeeeeeeeeeeeeeeeeeeeees 51 Viewing the Properties Of a Project ccccccccceeeseeeeeeeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 52 Setting the Active Project i vesgcseeiec vexiusinnvesdsaside vancutinnxecstelse vesiweovacsasuilenncasteexessuilnsraasaiexeecads 53 COM RIO Plate cease sectaretna vanes E EEOAE AEN E 5
26. Code debugging session you use the Target Code break button for the VPM you wish to debug See Using the Target Debugger Break Button page 144 140 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Executing in Simulation Mode and Debug Mode Simulating and Debugging a Model Executing in Simulation Mode and Debug Mode To execute the Virtual System Prototype in simulation mode Active the top model in the workspace From the Workspace menu select Simulate or Select the Simulate All from the Simulate tool bar button Simulate All Validate Alt F6 Validate All To execute the Virtual System Prototype in debug mode Active the top model in the workspace From the Debug menu select Start Debug or Select the Debug tool bar button CoMET may display dialogs requiring confirmation of build options CoMET then displays the Debug Options dialog The Debug options dialog allows you to select whether to perform Hardware model debugging or simulation and whether to perform Target Code debugging or simulation on each of your VPMs Debug Options i x Hw Model Debug Simulate ARMI26EJ5S C Debug Simulate Cancel H W Model Select Debug to debug VaST models Select Simulate to simulate the VaST models i e run the simulation without debugging the VaST models in your platform ARM9
27. General Configuration SettingS ccccsssssssssssssssssssssssssssssssssssesssseseseseeseeeeeeees 26 TED CA OS ae E 2l Ie Fatal XML VC WS sie spcscsenenaeansawasarsaaandonnsshotnaanenanacusamergussaancnontinaspnetaaanadanadans 27 Runtime Options Enable runtime dependency checks cccccccccceceeeeeees 28 Runtime Options Auto convert Gcc projects to No Cygwin DIL 28 Editor Options Configuration Settings ccccccccccsessseeeeeeeeeeeeeeeeeeeeeeeceeeeeeeees 29 Tool Locations Configuration Settings cccccccsssssssssssssssssssssssseesssessesseeeeseeeeees 31 User Locations Configuration Settings cccccccccceseeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 32 XML Tables Configuration Settings 0 cccccccceseesseeseeeeeeeeeeeeeeeeeeeeeeeeeeseeees 33 Parameter Table Editing iscsiccasacsanasvarensncnayoannonasoantenaneaaeeneniadeosageansarsienstonssvacsanees 34 Conneccion Tableedi ine a oar cicesasseeisnatcnneniduansacisonaceneceamesnenenschueuesteaniecesaaseeaensenseee 36 Modules Configuration Settings ccccccccccccccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 38 Environment Configuration SettingS cccccccccccseseesseseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 40 Displaying CoMET and Tools Models Versions cccccccecceceeeeeeeeeeeeeeeeeeeeeeeees 41 Getting Assistance while You Work ccccccccccccccccccccsecceeeeeeceeeeeeeeceeeeeeeseeeseeeseeeeaaes 42
28. Interface The Interfaces element is used only when developing either modules that have direct access to the target debugger or modules that require a target image loader Typically these modules are Virtual Processor Models VPMs or memory modules More information on these features will be provided in future Fabric Module a Interface Properties Mame Mew Interface Default Description 96 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Views and Reports You can view information on your Fabric Module in a number of different ways COMET provides a number of different views and reports Using Table Views Table views allow you to view the fmx file as a filtered list in various formats The table views offer ways to view and edit the fmx file as alternatives to using the XML Tree View To choose a table view right click on a line in the fmx document window and select the view from the context menu The table view shows all specified parameters or connections for the project If you press the Ctrl key while right clicking on a module instance node the table is restricted to the specified parameters or connections within the selected module instance You can configure table views to show the information you require See XML Tables Configuration Settings page 33 You can specify the default vie
29. Module The Fabric Module element is the top level element of the Fabric Module Definition Open it by double clicking the top level element in the XML Tree View This element is labeled with its Type attribute in the XML Tree View Fabric Module q x Fabric Module Properties Type FmsD emol Version 1 0 0 Init Function FreD emo lnith odulelnstance I Fait Function Fria emol Exithiodulel stance Ey Class WSP Sub Class Description Type The type of module to be created The module is listed under this type in the Module library and in the Module Instance dialog Type attribute list Default ProjectName Version Specify the version of this module This attribute is used in conjunction with the Module Instance Required Version attribute See Module Instance page 84 Init Function Specify the name of the function to be run by the simulator on initializing the module instance This function is generated by the Add New Project wizard in Source Files ProjectName c Click the button beside the function to view the source definition of the function Exit Function Specify the name of the function to be run by the simulator on exit Default name ProjectNameExitModuleInstance By default a null definition of this function is generated by the Add New Project wizard in Header Files config h Click the button beside the function to view the source definition of the function Class This attribute is reserved f
30. Name 004 70 Using Array Notation in a Port or Net View ccccccccececeeeeeeeeeeeeeeeeeeeeeeeeeeees 70 Options for Referring to Array Membets cccssesesesssesssesssssseeseseseeeeeees 71 Fmx Update Update Fabric ccccccccccccccccccceeccecccccecccccecccccccccccccccccecceeceeeeeeees T2 TANG ENG MCT S P EEE A T AEE A T E A A T 72 Creating Child ECM l xiscocoscsssssenseanesesesansdesesedenssebsnadenseansaesecansbbensteradeedeineansees 12 OU Tes FS AS CLAN Ora acters cece test aces hat deere sh NE E EENE ENNE 73 FMA Shan CA eienen E E 74 Hierarchical Parameter Type Naming ccccccccccccccccsseeeeeeeeeeeeeeeeeeeeceeeeeeeeeeeeeeeeeees 76 Foie MOUE sn E E H Parae E e E E E A E O E 78 Paranie OT e E E AE E EE E E 78 WOP a AEO ee e E E E ET E E E 79 PO e a E E T E E E E ES 80 PON E E T E E E E A 80 NO oe a E A E E E E E 8l WO E E eee 8l TASKS E E A E E 82 TAG EE E E T E A AE E A E AA E T 82 DAS Ka E E E E E E E A A E N 82 PO OENE ON er E ER E E E E EE 83 POr Or IN VOW E E 83 TNO GUNS FS aC Oean E E EE E EE 84 VIO CUS TO IN e E E E E A A NAE 84 Adding a Module Instance using the Context Menu cccccccceceeeceeeeeeeeeeeeees 86 Adding a Module Instance using Drag and Drop from the Modules window 87 Adding a Module Instance using Copy and Paste cccccccccceeeeeeeeeeeeeeeeeeeeees 88 Parametr Overrides axinasronecsaaaasss pona ieron ann aa aE e Ea AEAT a
31. PDB See the PDB User Guide and associated documentation This is available only to customers who have installed the PDB option Peripheral Model Matlab A module that interfaces a Matlab Model with a CIF Virtual Platform This is available only to customers who have installed the Matlab Interface Device Generator Matgen CIF option See the Matlab Interface Device Generator Matgen_CIF v1 0 User Guide Peripheral Model SystemC A module that interfaces a SystemC module or modules with a Fabric platform The project skeleton code for a SystemC adapter module with interfaces to both a Fabric bus and a sample SystemC device module See Creating SystemC Projects page 165 Project TopModule x Fabric Module Module Class Virtual System Prototype i Module Type Toph odule Versions 1 00 lt Back Cancel Module Type A Module Type name The name is system generated and is the type of module that the project will represent Separate instantiations of this Module share this Module Type You can change the predefined value to any desired name Note that you cannot use spaces in the name 48 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Adding a New Project Managing Workspaces and Projects Version A version number for the module You can use the version number for version control of modules For
32. Parameter View shows a list of parameter belonging to the modules or its submodules filtered on the parameter types e BusProtocol e BusWidth e Arbitration e AddressBits e BusMonitor e RequestLatency The Vpm Parameter View shows a list of parameter belonging to the modules or its submodules filtered on the parameter types e Endian e DynamicOil e Metrix e DataCache Size e WorkBufferSize e DataCache Ways e Debugger e InstCache Size e MinimumOil e InstCache Ways VaST modules follow a standard parameter naming scheme see Hierarchical Parameter Type Naming page 76 with parameters named according to the types above so the Memory Parameter View may list a number of modules and show their corresponding parameter values EE Simple 5P1 pcx ModuleT ype StartAddress Tope YirtualPlattorn Genenchtenoavl 0 Genenchernory 0 a M Top irtualPlattorn GenenchMenoyl 1 Genenchemor 0A 0000000 Bel hd Too irtualPlattorn Generichemoand 2 Generichemoary 0E OOO0000 Weed You can change the value of a parameter in a Parameter View by clicking on the cell displaying the parameter value and editing it You can also use parameter views to edit pcx files The picture shows a pcx file being edited in Memory Parameter View 98 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Using Table Views Views a
33. Runtime Options node under the build Configuration node Workspace GEA Simple SP1 2 Folders Agr Configurations Ea MNovazY cDIl Debug H E C Includes e Fi J ntime Optic ne 4 Fl NovazvcDOl Release ae E E Includes Workspace g YaST Modules VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 117 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Runtime Options Viewing and Setting Runtime Options Properties To set the runtime options for the top module Right mouse click on Runtime Options B JEA Simple 5P1 E Folders EI i la Ege hn Novaz cDil Debug H Includes a Runtime Options Sore Nova2veDll Re Expand Runtime Options Ctrl e B ia Z Includes Collapse Runtime Options Ctri L E han E a 2 Genera dd Dlls 2g Targets Edit Runtime Options FZ HIG Target Test Delete Runtime Options Del H A sieve a Cut Runtime Options Chrl e E Ea Timer Test 5 l Copy Runtime Options Chrl Workspace WaST Modules Faste Snr br Runtime Options Properties Ctrl F Select Runtime Options Properties or Double click on Runtime Options 118 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Runtime Options Configuring Build and Runti
34. Source Files ch 4 Header Files fe 2 Generated Files l 4 Pa oleae E a No a2 cDll Debug ol Nova cdl Release Flee Targets fe Target Test To set or change project components Right mouse click on the appropriate component icon and select the appropriate command For an example see Adding a Source File to a Project below 54 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring a Project Managing Workspaces and Projects Adding a Source File to a Project x E Workspace POBDemoDevice JEA virtualPlatForm H Folders Ei ra Source Files E virtualPlatform c oe E virtualFlatForm Frm oe VirtualPlatForm rc ve ampi_symlink_dll_body c a E ampi _symlink init c ye Header Files El Generated Files Hga Configurations Fa Simple Timer E E SimplevsP1 EI Folders Source Files el 4 Header File Expand Folder Ctri E E 4 Generated Collapse Folder Ctrl L r PA A e 3 Bl ben Noval cl ee Movar cEll Edit Folder FZ es Targets Delete Folder Del ag larget Te Cut Folder Ctrl Copy Folder Crrl C Paste try Folder Properties Ctrl F To add a source file Right click on a Folder under the Folders element Choose Add File from the context menu Inthe Browse for Source Files dialog locate the file to add Click Ope
35. Source Files or Header Files folder See Adding a Source File to a Project page 55 130 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Highlighting Keywords Using the Source Editor Highlighting Keywords By default the module editor highlights certain keywords in the body of a source file for example to separate the syntax of the language from module variables etc You can modify the list of keywords or add new keywords for example to add user functions or other control syntax to the keyword list The keywords are contained in four files e SVAST5 HOMES Config verilogkeywords txt for Nova and Verilog source files e SVAST5 HOMES Config vhdlkeywords txt for VHDL source files e SVAST5 HOMES Config ckeywords txt for C source files e SVAST5 HOMES Config vastkeywords txt VaST functions and macros NOTE VAST5 HOMES stands for the directory where CoMET is installed To edit a list of keywords Use the CoMET editor or your favorite editor to open the keyword file Add or remove keywords from the list Save the file Editor features The Document window provides a number of useful features for editing code With a source file open in the Document window choose the Edit menu to see a list of available features View Workspace Debug Tools Undo Ctrl 2 Redo Ctrl Copy Chrl C Select All Chrl 4 4 F
36. Subject to licensing COMET may be installed 1n a single shared network location and used by multiple users The procedure for installation is as follows Preparation Determine an appropriate shared directory in which CoMET can be installed e g serverl shared Determine an appropriate drive letter to which all user workstations can map the shared CoMET installation directory e g W Determine a home directory for COMET under the shared directory e g vasto home CoMET Installation Set up a workstation with the selected drive letter mapped to the selected shared folder E g using the examples above map serverl shared to W From the workstation install COMET in the selected home directory on the mapped drive Using the examples above install COMET inW vast5 home Run CoMET once to ensure automatic path updating takes place Copying a CoMET Installation Alternatively you can copy a CoMET installation from another location In this case the procedure is Copy the CoMET installation to the selected home directory on the shared drive Set up a workstation with the selected drive letter mapped to the selected shared folder E g using the examples above map serverl shared to W Ensure that the VASTS5 HOME environment variable is set to the COMET installation directory via the mapped drive Using the examples above set VAST5S_ HOME to the value W vast5 home See Setting up Environment Variables above Run CoMET once
37. a Fabric Port Type for a Verilog Port cccccccccccccccccccceeeeeeeeeeeeeees 188 Setting the Runtime Options cccccccccccccccceceeeeeeeeeeeeeeeeeecseeeeeeeeeeeeeeeeeeeeeeeas 189 C TOSSI a E 193 TINO E P A E E E 197 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 1x May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Introduction Welcome to CoMET Co Design Methodology and Engineering Toolset an integrated development environment for building VaST Virtual System Prototypes From within CoMET you can model verify and debug complete hardware software systems in systems on chip SOC application specific integrated circuits ASIC and printed circuit board PCB designs A Virtual System Prototype 1s a virtual computer based model of a hardware software system that you can use to develop system architecture With a VSP you can simulate and analyze system performance before you develop and manufacture the actual hardware You can incorporate incremental detailed subsystem design as it becomes available A VSP also provides you with a precise format for communicating specifications to the software and hardware design groups With a CoMET Virtual System Prototype you can develop and debug hardware and software concurrently instead of sequentially A VSP provides complete system verification across all components resource usage data and performance quantificat
38. a small text window next to the mouse pointer displays the purpose of that button A short description also displays in the status bar at the bottom of the window See Toolbar Buttons page 17 for additional details on some of the buttons in the Toolbar Status Bar The status bar displays messages and information while you are building debugging and simulating a Virtual System Prototype The status bar is located at the bottom of the window Workspace Window The workspace window displays the project files header files and other files associated with the workspace You can use this pane to add files and to select files for editing Target Window Displays output information from the target application software when the Virtual System Prototype is executing The target window also displays timing information about the simulation when the Virtual System Prototype is executing Output Windows The output windows display messages during CoMET operation These are color coded e Gray CoMET information e Green CoMET success message e Dark Yellow Warning message from external tool e Red Error message from external tool e Black Output from external tool VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 13 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started The CoMET System Engineering Environment Document Windows The Document windows display a vari
39. and other safeguards to ensure a valid fmx file is generated For each element in the specification there is a node in the XML tree and a corresponding properties dialog The remainder of this chapter provides details for each of the elements and its properties dialog Each dialog corresponds to an element such as a Port or Net For each dialog and corresponding element attributes are listed with a full description Dialogs are listed according to their path from the top of the Fabric Module tree For example the Port element dialog which appears when you add a Port to the Ports node of the Fabric Module has the path Fabric Module Ports Port A double slash in the path indicates there may be intervening elements For example Fabric Module Parameters Parameter This path implies that the Parameter element must have an ancestor Parameters element but may have closer ancestors In the case of the Parameter element closer ancestors may be SubParameters elements Prerequisite Elements The path of an element indicates some prerequisites to creating the element For example before creating a Fabric Module Task Port Or Net Views Port Or Net View element you must first create a Fabric Module Task Port Or Net Views element Some elements may require as prerequisites elements in other branches of the tree For example if you wish to define the value of a Port attribute as a Parameter you
40. by one ActivePrototype Run target for active prototype AllPrototypes Run target for all prototypes one by one SimTime time Unit Limit batch run to the specified number of simulation time units Allowed units fs ps ns us ms s e g SimTime 30ms stop after 30 milliseconds of simulation time RealTime time Limit batch run to the specified realtime seconds e g RealTime 5 stop after 5 seconds Command line batch mode using a CoMET 4 batch file To use a CoMET 4 batch file run CoMET in batch mode from the command line specifying the name of the batch file comet b filename Or comet batchmode filename CoMET runs the batch file as described in Command line batch mode above For more details see Application Note Loading CoMET 4 Batch Files into CoMET 5 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 151 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Running External Tools during Simulation Running External Tools during Simulation For each project COMET allows you to specify tools to be run immediately prior to each simulation Such tools can perform functions such as communicating with the simulation process to provide input and output To specify a tool first create a Tools node under the project node in the Workspace window To add a Tools node Right click on the project icon in the Workspace window
41. directory on the CoMET installation mapped drive See DTD Locations page 27 CoMET Configuration E i x General Editor Options Tool Locations User Locations ML Tables Modules Environment Default Srl Wiews Fms files Kml Tree View Pes tiles Kml Tree View Startup Requires re start M Reload last workspace on startup DTD Locations Requires re start YaST home C Substitute local drive C Network drive VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 9 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Installing CoMET Uninstalling COMET Set XML Reports Locations The XML Reports directory should be distinct for each user to avoid overwriting other user reports The XML Reports location specified in the COMET configuration is set per workstation Copy the YovastS home XMLReports directory to a distinct location for each user On the user workstation specify the XMLReports location with the Tools CoMET Configuration Tool Locations tab CoMET Configuration q x General Editor Options Tool Locations User Locations ML Tables Modules Environment Ame C Program FilesW4AM aDSy1 2 ArmE lace Cdb C Program Files Debugging Tools for Windows FinSim ee cWusrvast cometh Goc Matlab Mipse lface ModelSim Marc C Program Filess Microsott Visual Studio WET 20034 Y c SystemC c usrvastycomets S ysteml WOOUE
42. down menu Refer to Features and requirements page 169 for a list of valid Fabric Port types which can be selected for particular VHDL port types e Click OK to accept the selection Setting the Runtime Options The build configuration of the top module supports a set of runtime options Runtime Option properties vary for different build configuration types See Build Configuration Types page 110 Adding Runtime Option Properties To gain access to view and change Runtime Options you need to create a Runtime Options node in the Workspace window under the Configuration node CoMET creates a Runtime Options node automatically only for top level Fabric projects and VBus projects You can manually add a Runtime Options node To add runtime options e Right click on the appropriate build Configuration node e Choose Add Runtime Options from the context menu Workspace Hea Test HDLModel f g Folders Configurations i C Includes Expand Configuration Ctri E H E Verilog Inch Collapse Configuration Ctrl L H a Modelimi ce C Includes 4dd Objects Add Runtime Options EI Edit Configuration F2 Workspace z YaST Modules Delete Configuration Del Cut Configuration Ctrl e Copy Configuration Chrl c Paste Cobre Configuration Properties Ctrl F CoMET creates a new Runtime Options node under the build Configuration node VasST SYSTEMS TECHNOLOGY Confidential and Proprietary 177
43. exports all source files and supporting files for the project Using these you can rebuild the target binary in METeor and associate it with the METeor project Metrix projects COMET exports all source files and supporting files for the project Ensuring the Fabric project Prototype Configuration pcx file is exported The pcx file associated with the build configuration can be viewed and modified in the Runtime Options for that configuration See Setting the Runtime Options page 117 The pcx file is automatically added to the Runtime properties when it is created When you build a project COMET checks for an existing pcx file and if none exists COMET prompts you to create one If you can successfully simulate your project you have a valid pcx file that will be exported with the Fabric Workspace 58 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Exporting a Virtual System Prototype Workspace for METeor Managing Workspaces and Projects Exporting Additional Files and Folders You may wish to export additional support files such as configuration data or documentation files You can add individual files or entire directories for export with the project You can add individual files to be included in the exported Workspace In the Export Workspace dialog click on the Files button COMET displays the Export Files dialog
44. header Alter the above source files as required You can also add other VHDL or Verilog source files to the project You can now build the VHDL Model 174 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST VHDL Co Simulation Support ModelSim HDL Co Simulation Support e Test YHDLModel Test HDan ye Jed Testy HOLModel A Ge Parameters ArchitectureName default a p Forts Reset ap a6 Tasks HHE Test HDLModelTask E Port Or Nek Views Xml tree view of automatically generated VHDL fmx file When the VHDL Model is successfully complied a module instance of the model can be added to a CIF platform El do SimplevSP 1 fe be Parameters eae Ports gy Mets BL ClockMet Eaa A vive Resethet oe Tasks i Module Instances E El VHOLModuleInstance Eb fe Instance Forts rat Reset E Parameter Overrides Bs ge ArchitectureName default Parameters CoMET automatically creates the following parameters for the VHDL Model These appear in the module instance Parameter Overrides and the Prototype configuration pcx Parameter Overrides e ArchitectureName Specify the architecture to be used in each instance of this entity If the value of default is accepted then the simulator will choose the default architecture to be used For each generics declared in the VHDL model a co
45. model The screen capture below shows how different versions of the Arm926e js VPM are organized in the Modules Vpm directory 14 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST The CoMET System Engineering Environment Getting Started r C usri vasti Comet5 Modules pm Aarm926ejs Fie Edit View Favorites Tools Help Back sd gt E Bi gt Search te Folders ja E x ie Bak Address CAusr vast Comets Modules ypmiArmgz6ejs Folders i E 2 Modules gt O Ausiliary 9 Bus 9 Gp Memory E I vpr 9 Arm7tdmi E O MEEBE O v4 4 5 O v4 4 6 a v4 4 7 O v4 6 1 C drmo46es O Arm1136f The screen capture below shows multiple versions of the Arm926ejs VPM as it appears in the VaST Modules window in CoMET E WaST Modules H E Auxiliary H E Bus H E Gp H E Memory Bey Worn Sy Arm etd i e Feo B vis o ARMIZ6EI5 ORM IZ6EI5 Eley v4 4 7 TE SRMI2Z6EI5 Fy v4 6 1 i ARMOZ6EJS HE Arm es vasT Modules User Modules VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 15 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started The CoMET System Engineering Environment Maintaining Multiple Versions of a Module CoMET VaST s Models and Platforms releases install only the latest version o
46. must first create the Parameter To make a Module Instances Module Instance Port Connections Port Connection you must first create the Port to which it connects Elements are arranged in the XML Tree View in an order indicating which should be created first It is usually more convenient to first create elements which appear earlier in the hierarchy element order However the methodology is flexible and you can create elements in any order 66 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Choosing Names Developing a Fabric Module Definition Choosing Names Most elements have a name attribute which together with the position in the Fabric Module Definition hierarchy uniquely identifies the element Choose names carefully Names appear in generated code views and reports A name should therefore not contain characters disallowed in C code Other useful features of a name include being easy to recognize and carrying some useful meaning such as function or type A strict naming convention appropriate to your project 1s recommended Names may also include an array declaration or a reference to array members See Arrays below Description attributes Many elements contain a Description attribute Use these to provide documentation for your Fabric Module and its elements Descriptions appear in Prototype Reports
47. out the action represented by that button The following sections describe some of the special buttons on the Toolbar New File Button CoMET 5 C astProjects base _ File Edit View Workspace a g Xx Mew Ctrl M You can use the New File button to create a new e Fabric Module e Peripheral Model e Matlab Model e Instruction Prototype requires the VaST VPM Transformer toolset e Instruction Definition requires the VaST VPM Transformer toolset e Instruction Selection requires the VaST VPM Transformer toolset e Platform Configuration e Metrix Configuration To create a new file From the Tool Bar click the down arrow next to New File button CoMET 5 C astProjectsbase File Edit View Workspace Fabric Module Matlab Model A Instruction Prototype Instruction Definition Instruction Selection Platform Config Metrix Config Select the type of file from the drop down menu NOTE Clicking the New File button will automatically create a new text file VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 17 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Toolbar Buttons Workspace Button If the Workspace is not visible on the COMET SEE click the Workspace button on the Tool Bar to display the Workspace YaST Modules User Modules NS You can use the drop down arrow on t
48. parameters according to type For example if you have a number of memory modules each with a parameter specifying the base address of the memory you should give the parameter the same name in each case e g SstartAddress Naming parameters according to type offers a number of advantages When creating a Parameter Table View see Parameter Table Editing page 34 you can define a column using the common parameter type name This allows you to view compare and edit parameter values for all module instances sharing that parameter type Parameters with the same name can be distinguished by placing each in a separate subgroup To name parameter types for example when defining parameter table view columns you can use a dot convention to specify a hierarchical name for parameters within Sub Parameters groups For example a parameter named Size belonging to the Sub Parameters group DataCache can be referred to as DataCache Size This distinguishes it from the parameter InstCache Size the Size parameter located in the InstCache Sub Parameters group When populating the parameter table view for each module instance row CoMET uses the first parameter it finds within that module instance matching the column parameter type 76 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Fabric Module Developing a Fabric Module Definition Fabric
49. test Virtual System Prototypes The System Engineering Environment consists of a workspace an output window a source file editor and tools for building configuring executing or simulating and debugging Virtual System Prototypes A function written using the C language that invokes AMPI functions in order to interact with module elements and interconnections See Virtual Platform VP The building block of a Virtual System Prototype A Virtual Platform may consist of one or more virtual processors that executes software embedded within the product peripheral devices and interconnections such as buses Virtual Platforms can also contain other Virtual Platforms in a hierarchical structure Virtual Platforms may be interconnected VPM A device model that simulates the functionality of a hardware processor CPU VSP The virtual representation or executable specification of a hardware product that incorporates subsystem design together with the environment that drives the execution or simulation of the virtual product A Virtual System Prototype consists of one or more Virtual Platforms and optionally a test bench and performance and analysis tools The design area within the COMET SEE where you create Virtual System Prototypes 195 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Glossary 196 VaST SYSTEMS TECHNOLOGY Confidential and Proprietar
50. to ensure automatic path updating takes place This updates the DTD path in the files Yovast5 home Config Vast6_1 0 0 cfx and Vast7_1 0 0 cfx The DTD paths must agree with the CoMET installation For example if you have mapped the shared folder to V and installed in the subfolder vast5 home the second line of each of the files should read as follows lt DOCTYEE Vase Sistem Ve ves co home Contig Vast V71 1 0 ded gt You may edit the DTD paths manually if you wish VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Installing COMET on a Network Installing CoMET On each Workstation Map the selected drive letter to the selected shared folder on workstations of all users Using the examples above map serverl shared to W On each workstation ensure that the VASTS5 HOME environment variable is set to the CoMET installation directory via the mapped drive Using the examples above set VAST5S_ HOME to the value W vast5 home This can be set up in the COMET Configuration dialog choose Tools COMET Configuration Environment tab Alternatively you can set it using standard Windows administration procedures See Setting up Environment Variables above Set DTD Locations Inthe COMET Configuration dialog choose Tools CoMET Configuration General tab set the DTD Locations to VaST Home This results in a shared Config
51. using Copy and Paste To add module instantiations to a module using copy and paste from the Modules Window 88 Highlight the module icon in the Modules window Copy Ctrl C Edit Copy Highlight module instances in the fmx XML tree view Paste Ctrl V Edit Paste You can also copy a module from the Modules window and paste into the appropriate fmx file table view For example copy VastGpSTdBusBridge into the fmx file Bus Connections view VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Parameter Overrides Developing a Fabric Module Definition Parameter Overrides Module Instances Module Instance Parameter Overrides A Module Instance element may contain a single Parameter Overrides element This element is a container for all Parameter Overrides and Sub Parameter Overrides elements within the Module Instance Child Elements The Parameter Overrides element may contain one or more Parameter Override elements The Parameters element may contain one or more Sub Parameter Overrides elements Parameter Override Module Instances Module Instance Parameter Overrides Parameter Override When you create a parameter it is defined and its default value is set in the Fabric Module Definition fmx file When you add a Module Instance of that Module to another Fabric Module CoMET examines each Parameter element d
52. written agreement with VaST Developing a Fabric Module Definition Parameter Override Parameter Fmx Access Pcx Access and Parameter Overrides The picture below shows examples of how varying the Fmx Access and Pex Access in Module Parameters affects the Parameter Overrides of a corresponding Module Instance FmxDemoPlatform contains an instance of the FmxDemol module FmxVSPDemo contains an instance of FmxDemoPlatform This results in Parameter Overrides in FmxDemol Instance in FmxDemoPlatform fmx and in FmxDemo1Instance in FmxVSPDemo pcx corresponding to the Parameters in FmxDemol1 fmx ae FmxuDemo1 F FrixDermoPlatForm FrixDemol al Ge Parameters Precedence 3 be Parameters a Pl FroxPrivate_PcxPrivate 23 ie Ports P2_FrxProbected_PcxPublic 34 Fe Mets vee PS FroxcPublic_PcxPublic Test string oo Tasks P4_FmzPrivate_PexPublic 45 P5_FmxPublic_PexPrivate 56 P _FroxPrivate_PcxProbected 1 Forts Mets Tasks 2 h Module Instances i EE Fmx SPDemo pcx g Fine SPDema 5 Module Instances Flea eal Top EME FrixDemoPlatformt A ko Module Instances Egi El FrixDemal Instance E ga Instance Ports apa Parameter Overrides Precedence 2 oi Pz _FmxProtected_PexPublic 34 x PS FroxPublic_PcxPublic Test string 2 S P5 _FmePublic_PexPrivate 57 El Ee aoii ales ag L 5 Parameter Overrides Precedence 1 it 2 P2_FrxProtecked PexPublic 35 Gil PS_FmxPublic_PcxPublic Test str
53. 131 IF MAGE Tia ENS EE E E E O E AS 132 Locating Symbols with the Browse Database ccccccccccccccccceeeeeeeeeeeeeeeeeeeseeeeaeas 134 COTO TOG WO erana E E EE E TENTE A EEE EE E 134 Browse oy DDOL areae aE xs atv eee E R 135 Special P Nt KEYS sorrie icreataate amas EA NEE ETE EEI EE 136 Building the Workspace and Projects ssecccocsssssececocosseseeceocossssececcoossesecesossssseee 137 Simulating and Debugging a MOdel cccccccssssssssccccccssssssssssscccsccssssssccccssseseees 139 Choosing a DeDUC ZET oan eee eee iakin a RAE AN RANN RATE eee 139 Hardware Model Debugging cccccccccccscceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 139 GDB Internal Debugger isi0s evasvansesnsvepnevdsvessedabiadessessacsaievaeentsvadenibiaderusueces 140 CDB Internal De OS C0 sicescsenensactinennsedtncsdacidestspdeaunasunauniadianwnssest REENEN ERES 140 Target Code Debugging pisiirririsiireis iirinn anaa ra EEN AEA EEA 140 Executing in Simulation Mode and Debug Mode ccccccccccccccccececeeeeeeeeeeeeeeeeess 141 Interrupting the Execution FlOW cccccccccccccccccccccececeeeeeececeeeeceeeeceeccccccceecceeeeeacs 142 Setting Breakpoints in Hardware Model Debugging eeeeenesesnsensnnnnnnnenssnssssss 142 Managing Breakpoints een en een nh ne en er een ne eee een ee 143 Contnuine FESO Oierri anaE n ENIE DEE NAE N E 143 Continte DEDU SEINE 2 cscscanessnnusnsasesandssossesasnesnassnseaienacsasnandasesseearnee
54. 26EJS or other VPM instance A set of Debug Simulate options appears for each VPM module instance in the platform Select Debug to debug Target code on the associated VPM Select Simulate to run the Target code on the associated VPM without debugging Click OK The model begins executing and continues until it reaches an interruption to the execution such as a breakpoint See nterrupting the Execution Flow below CoMET initiates execution of the Virtual System Prototype in a new process The Software window displays the output from the target executable running on the VPMs VasST SYSTEMS TECHNOLOGY Confidential and Proprietary 141 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Interrupting the Execution Flow To stop debugging or simulation From the Debug menu select Stop Debug Simulate Or Select the Stop Debug tool bar button Interrupting the Execution Flow You can interrupt execution in both Hardware Model debugging and Target Code debugging Setting Breakpoints in Hardware Model Debugging You can interrupt the execution of your hardware models by setting breakpoints To set a breakpoint in the hardware or behavioral source code In the C source file click on the line of code Click on the Toggle breakpoint tool bar button or press the F9 key A red diamond appears in the left window margin to indicate the breakpo
55. 4 Adding a Source File to a P10 CCl iseercdccsonsseacthasdsceientancelarsdedanandendtvertocdeanevdecwenstene 55 Viewing Project Component Properties s siissssrersiissverrsinsviesisvevareiiiris trasna iseasi 56 Properties of Special Components ccccccccccsccsessssssssssssssssssssssssssssssssseaeas 56 Viewing the File Path Property ccccccccccsssssssssssssssssssssessssssssssssssseeseseeeeeeees 56 Disabled PLOPEITIES joer cncscasereanandecesiosedendsdansauesieneheneneninannesiesioduinsdsiosiaberesadedenedeniedendsoeand 56 Savine Workspace Files cha cau aectaccaricancinaancnedaansenacid i enana anaien aen EEA EENE 57 Exporting a Virtual System Prototype Workspace for METeor ccccccccceeeeeees 57 Exporting a Workspace eaueicciasvsscudwaucteesnasaceutrantecetnnvescudaussesaittesDecalenttesaaloaradeeimanteness 57 Choosing Expor Opus ci desexaceieterevsadecaveridgenvecadecevesiorextecadecnvxciorexenateetesaeieanades 58 Files Exported for Specified Projects cccccccccscccccsesseessesssessssssssssssssssssssseeeaes 58 Ensuring the Fabric project Prototype Configuration pcx file is exported 58 Exporting Additional Files and Folders ccccccccccsssesseeecesseseesssssssssssssssseeees 59 Location of extra files and folders in Workspace cccccccccccsssscceeeeeeeeeeeeeees 60 Creating the Exported Workspace cab File ccccccccccccccccccccecceeeeeeeeeeeeeeeeeeeeeeeeaas 60 Moving a workspace from one direct
56. COMET on the Windows XP and Windows 2000 operating systems CoMET Components A CoMET release contains VaST Systems Technology s COMET System Engineering Toolset including The CoMET System Engineering Environment CoMET the graphical interface that provides a user friendly and efficient design and analysis environment VaST s Architectural Modeling Programming Interface functions AMPIs Virtual System Modeling function libraries VaST VPMs one or more virtual processor models Module Library a set of complete hardware and software example projects that you can use as references or as templates for your own projects Installing CoMET on Windows XP or Windows 2000 The minimum system requirements are Processor IBM compatible PC with a Pentium or better processor Operating System Windows XP or Windows 2000 RAM Minimum 64 Mbytes of DRAM Hard Disk 800 Mbytes with all supporting GCC cross compilers Video A S VGA video graphics adaptor A pointing device e g mouse VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 5 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Installing COMET Setting up Environment Variables NOTE Itis recommended that you reserve at least an additional 50 Mbytes of disk storage for swap space You will require more swap area if you wish to simulate large designs To install COMET on Windows XP Windows2000 Insert th
57. CoMET batch file See below H Hide don t show the COMET GUI M Minimized minimize COMET GUI L Logpath specify a directory in which three logs are saved corresponding to the COMET Log Build and Software output windows Non Batch Mode Options Workspace wkx You may specify a Workspace on the command line On launch COMET opens the Workspace File txt You may specify a file other than a workspace on the command line On launch CoMET opens the file in the Document window CoMET Batch File A CoMET batch file is distinct from a DOS Batch file It provides an alternative to specifying workspaces and options in the COMET Tools Batch Mode dialog It consists of lines of the form workspace wkx option option2 e g C VastProjects Fabric base sh2a cif base sh2a wkx BuildAll AllPrototypes SimulateAll SimTime 20ms RealTime 5 150 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Building and Simulating in Batch Mode Simulating and Debugging a Model Options can be specified with the minimum characters required for unique recognition e g Simulate Simulate SimTime SimT Options are Build Build the active project BuildAll Build all projects Rebuild Rebuild the active project RebuildAll Rebuild all projects Simulate Simulate the active project SimulateAll Simulate all projects one
58. Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Runtime Options Configuring Build and Runtime Options Setting the Runtime Options The build configuration of the top module supports a set of runtime options Runtime Option properties vary for different build configuration types See Build Configuration Types page 110 Adding Runtime Option Properties To gain access to view and change Runtime Options you need to create a Runtime Options node in the Workspace window under the Configuration node COMET creates a Runtime Options node automatically only for top level Fabric projects and VBus projects You can manually add a Runtime Options node To add runtime options Right click on the appropriate build Configuration node Choose Add Runtime Options from the context menu G VirtualPlatForm aie Simple Timer a Simple SP1 o E Folders ag Configurations le Nova cDll Debug Fa os C Includes Expand Configuration Ctri E oo Collapse Configuration Ctri L EA Novaz cDil Re Add C Objects i C Includes dd Libraries ay Add Runtime Options E Genere Edit Configuration F2 See Targets Delete Configuration Del nga Target Test Ene ee Cuk Configuration Cr Workspace YaST Modules COPY Configuration Ctrl c Paste trl Configuration Properties Ctrl F CoMET creates a new
59. DMODULE DPRE_SYMLINK_INIT_RE Link Options Doo E Define File VBusClFDemo2 def Device Type SlaveOrny O Decoding Type Ae Memon Regions Poo Active Tue VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 161 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 4 and SystemC Compatibility Running a VBus Peripheral Model on CIF CoMET creates a VBus Peripheral Model project from templates workspace E JEA vBusPeripheralDevice E E Folders a Source Files E BusPeripheralbevice c E vBusPeripheralDevice rc BusPeripheralbevice w config_vda c ampi_syrolink_dll_ body c ampi_s rolink_inik c a Header Files E BusPeripheralbevice h E BusPeripheralbevice vrh ampi_symlink_names h config h canfig_types h resource h a Generated Files I vBusPeripheralDevice fmx conFig_init c config_symlink c config_init h config_struct h config_sy rolink A version_number h E config_vda h a Ta ee ee si a MovaGccDll Debug nA Ai a NovaGeccEl Release aST Modules You can now replace the newly created files with the corresponding files from the existing VBus project e Source Files ProjectName e Source Files ProjectName e Header Files ProjectName e Header Files ProjectName c behavioral C for VBus device v HDL wrapper for VBus device h behavioral C header vrh HDL wrapper header Provided you
60. Folders Configurations a een Nova cDll Debug ae Hoya cDll Release Flee Targets Expand Configuration Ckrl E oga Target Test Collapse Configuration Ckrl L Hee sieve demo HAE TimerTest Add 2 Objects Add Libraries Edit Configuration Fz Delete Configuration Del Cut Configuration Ctrl e Copy Configuration Chrl Paste trl Activate Configuration Ctri 4 Configuration Properties Ctrl F k Select Activate Configuration or Double click on the configuration icon VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 115 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Active Build Configuration Project x Configuration Properties Type NovaVeDN OO Mode Releases o YS Path vcRelease a C Options DNOWA2 DMODULE DPRE_SYMLINK_INIT_RE Lisle Diptions PO Define File SimpleTimen def a Achye Fase s s lt SsC True Cancel Apply Help we i Set the Active field to True and click the OK button NOTE When CoMET builds a project in debug mode debug information that allows you to debug the behavioral code is stored in the executable Debug information adds a significant overhead which may degrade performance To run the model at maximum performance you should configure and build a model in release mode 116 VaST SYSTEMS TECHNOLOGY
61. Gerit aml Tree View sml Text View Memory Parameter view Bus Parameter view Vor Parameter View Bus Connection view Clock Connection view Logic Connection view Ctrl P AML Table Properties 37 Getting Started Configuring the CoMET System Engineering Environment Modules Configuration Settings CoMET comes with a preconfigured module library arranged as a tree structure You can view this library in the VaST Modules tab of the Modules window You can add your own module libraries using the COMET Configuration Modules Tab CoMET Configuration x General Editor Options Tool Locations User Locations ML Tables Modules Environment Module Path CAwokscometprojects PdbDemol 2000 To add a library Click Add Browse to the top level directory containing your library of module dll files Click Apply or OK CoMET recursively searches the specified directory and its subdirectories adding each module dll it finds to the library The library tree structure mirrors the directory structure CoMET encounters during its search To determine the library tree structure of your library arrange your module dll files in the required directory structure You can specify a workspace or project directory as the library directory CoMET finds any built dlls and adds them to the library This may result in redundant levels in the library tree Structure On completion CoMET adds a tab to the Modules windo
62. Hew Porto rN etier Type Number Of f Description Name Select a Port or Net from the list Before creating a Port Or Net View you must first create the corresponding Port or Net You can refer to members of a Port or Net array using array notation See Arrays page 67 Type Select a Port Or Net View type Allowable Values e Slave The Task provides a response to a stimulus on the Net or Port A slave connection typically limits a task to reading values of the Net or Port e Master The Task provides a stimulus to the Net or Port The task can drive values onto the Net or Port e MasterSlave The Task both provides a stimulus to and responds to a stimulus on the Net or Port e NetController This is currently used only by VaST built Net Control Protocol Engines e NetSlave Equivalent to Slave Provided for compatibility Use Slave instead e NetMaster Equivalent to Master Provided for compatibility Use Master instead Number Of This attribute may refer to members of a Port or Net array Use array notation omitting brackets e g 0 15 or0 1 2 Array notation in the Name attribute takes precedence over this field See Arrays page 67 Default 1 a single element not an array Description You may add a description for documentation purposes VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 83 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developin
63. Hot Keys Simulating and Debugging ee ceeeeeeeseseeeseesesssessssssessseeeeeeeeeeees 157 COMET 4 and SystemC Compatibility ccsrrcccccscscccccssscccccccccsssesesesseeeeeees 159 Convettins COMET 4 i jG Ots srein ine EENT 159 Using the Matlab Generator ccccccccccccceseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 159 Running a VBus Peripheral Model on CIP 20 00 00 cece cccecceeeeeeeeeeeeeeeeeeeeeeeeeeeees 160 Creating a VBus Peripheral Model Project ccccccccccccccccccccceeeeeeeeeeeeeeeeeeeeeeeees 160 PAT AIC ECTS e e E E E E E T E A 163 Speci yine he V BUS devicetype eea a Eik 163 viii VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 5 14 User Guide Contents Simulating the VBus Peripheral Model ccccccccccccccccccceeeeeeeeeeeeeeeeeeeeeeeeeeeees 163 Simulating a VBus Peripheral Model with FinSim cccccccseeeessessseeeeeeeeeeeens 163 Creatine Sy Stemi PLO CCS ean N AO ecawnecnesteorss 165 Creating a Standalone SystemC Project cc ceeeeeseessesssssssesssssssssssseesessesseeeeens 165 Creating a CIF SystemC PLO CC cssaascsoracnmuudusasadsnssansedsaaastesnsacesaudeaaandsondanneanaasnes 165 Choosing the SystemC Libraries for VC 6 VC 7 VC 8 and GCC 166 ModelSim HDL Co Simulation Support ccccccssssss
64. LLUSERSPAROFILESC Documents and Settings all Users APPOAT ASC Documents and Settings rana4oplication Data SAMCONFEC Program Files AA MADS ABIM AAMOLLEC Program FilesW4AM A0Sy1_ ABIN AAMAOME C Program Files 4AMAADS yw 2 ARMINC C Program Files 4AM ADSy1_ 2sINCLUDE SAMLIB C Program Files W4AM a0 Sy1_ ALIB CommonProgramFiles C Progranm FilesCormmon Files COMPUTERNAME PLATYRPUS ComS pec l WINDOWS systenisevomd exe devrigr show nonpresent devices 1 FP_NO_ HOST CHECK NO HOMEDRIWE H HOMEPRATH HOMFSHARF 5karnanirana Add Edit Delete mea vont Environment Configuration Tab 40 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Displaying CoMET and Tools Models Versions Getting Started Displaying CoMET and Tools Models Versions You can find out the version of the COMET GUI or the versions of the tools and models via the About CoMET option from the Help menu To display version information about the COMET GUI From the Help menu select About CoMET To close the About Box dialog box click OK x CoMET Version 5 14 0 Yc Copyright 2006 YaST Systems Technology Corporation This product includes software developed by the 4pache Software Foundation https avi apache org Versions vas To display version information about the tools and models within CoMET
65. May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Options for Referring to Array Members The table below shows the various array notation options for specifying elements In the Example column the notation indicates a connection between the Instance Port array members on the left and the Port or Net array members on the right Port or Net connection s Resetin Signal to signal SignalA SignalB ResetModule Irqin 3 Bit to bit SignalA x SignalB y IrqModule 1 Bit range to bit l l Irqaln 4 7 SignalA 0 x SignalB 2 y range IrqModule 0 3 Bit range to bit l l Iraln 4 7 l SignalA 0 x SignalB x 0 range twisted IrqModule 3 0 Irqin 1 3 5 6 IrqModule 0 2 3 4 Connection Type Instance Port s Bit list to bit list SignalA x1 x2 x3 SignalB y1 y2 y3 Bit list and or range Irqln 0 2 4 7 to bit list and or SignalA x1 x2 x3 x4 SignalB y1 y2 y3 range IrqModule 0 2 6 Single bit l Daa l l i Irqaln 15 31 connection to bit list SignalA 0 x SignalB x or SignalB SsomeSignal and or range Bit list or range l l l SomeSignal connection to SignalA or SignalA x SignalB y1 y2 y3 Irqin 15 31 single bit aa l VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 71 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabri
66. May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support x H A Test YHDLModel H E Folders o Configurations 2 ModelSim cDll Debug H J Z Includes ni 9 Verilog Includes Runtime Options jy hn Modelsim eDl Release H E E Includes H E Verilog Includes Workspace a YaST Modules User Modules Viewing and Setting Runtime Options Properties To set the runtime options for the top module e Right mouse click on Runtime Options e Select Runtime Options Properties H E Test HDLModel I Folders Sa Source Files fy Header Files Generated Files So Configurations El ModelSim cDIl Debug H J Includes n Verilog Includes Runtime Options cues je Modelimi col Expand Runtime Options H E Includes Collapse Runtime Options H E Verilog Inc WaST Module E dd lls Edit Runtime Options Delete Runtime Options Cut Runtime Options Copy Runtime Options Paste Ctrl E Ctrl re Del Ctrl Ctrl c cobra Runtime Options Properties Ctri k Or e Double click on Runtime Options VHDL Co Simulation Support 178 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST VHDL Co Simulation Support ModelSim HDL Co Simulation Support VHDL Project Runtime Options x
67. Module Definition Report Fmx Report eeeeeeeeeeeeees 100 Fmx Report Errors and Warnings ssscsssssssssssssssssssssssssssssssssssssssssssees 104 Viewing a Prototype Configuration Report Pex Report eeeseeeeeeeeeeeees 105 Viewing All Connections in a Virtual System Prototype 0000000000000000000000 106 Configuring Build and Runtime Options ccccccccsscccccccccccccccccccesssssssscscees 109 Setting the Build Config rati N sscyoatscxccossssnsdentesncxoasesaseewensseqounseasdeneacnseaaeesesearsanens 109 Build Configuration Types xcs cccavexcaceaccsaceanancusaavenincndeanoaceaveetavsasaneasaaventaentsaendesaaets 110 Common Build Configuration Properties ccccccccccccccccceceeeeeseeeeeeeeeeeeeeeeeeeeeeeas 110 CIF Project Build Configuration Properties ccccccccccccccccecceeeeeeeeeeeeeeeeeeeeeeeeees 111 VBus Standalone Build Configuration Parameters cccccsssssssssseesseeeeeseeeees 112 Tab Tiles are no 1ONSEr TE GUI 6 Os eserine 112 VBus CIF Build Configuration Properties cccccccccccscsscceeeeeeeeeeeeeeeeeeeeeeeeeeeees 113 Target Project Build Configuration Properties cccccccccccceeeseeeeeeeeeeeeeeeeeeeeeeees 114 Setting the Active Build Configuration cccccccccccccccccccecceeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeess 114 Setting the Runtime OP UON Ss 5 cccsccacededanenanedonnsuaseeenansnaensiideheasantcaseunnesenceantdebesenanedosees 117 Adding Runtim
68. Module Instance telti sml Text view Memory Parameter view Bus Parameter view Vom Parameter view Bus Connection view Clack Connection view Chrl P Corresponding Bus Parameter View See also Parameter Views page 98 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 35 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Configuring the CoMET System Engineering Environment Connection Table editing To create a new connection table click Add Connection in the XML Tables Configuration tab To edit an existing connection table select the table and click Edit or double click the table CoMET Configuration Memon Parameter Bus Parameter Worn Parameter Bus Connection Clock Connection Logic Connection x StdBus Neither ad Cancel StdClack Nether StdLogic Bath Neither std vectorst p ets Ports Both a OE Cancel Apply XML Tables Configuration Connection Table Editor The Connection Table dialog allows you to specify the types of connection to be listed in the table Available types are shown For example you can choose to display neither Nets nor Ports of type StdBus but both Nets and Ports of type StdLogic The view shows rows with module instance name module instance type and additional columns each of which corresponds to a connection of one of the specified types The corresponding view of
69. MowhereMet 104 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Viewing Module Definition and Prototype Configuration Reports Views and Reports Viewing a Prototype Configuration Report Pcx Report Open the Prototype Configuration pcx file in the Document Window mH e a Click the Open Config File button down arrow and select the Prototype Configuration file from the list Select Tools Prototype Report or click the Prototype Report button ej CoMET opens the report in the default XML browser GenericMemory1 0 Module Path Top VirtualPlatform1 GenericMemory1 0 Submodules No Submodules Prototype Configuration SimpleVSP1 Type Required ersion Class SubClass Description Parent s Properties 8 Structure 58 Module Instance Parameter Overrides Detail Connections GenericMemory None This is an array of module VirtualPlatform fmx f s instances with the size of This window acts as a menu of module instances to which you can return at any time The ra acrauicatannicner Gy h structure map shows the hierarchy of module instances Use module instance links in the the map to navigate to the details of that module instance including properties and parameter NumberOfMemoryBlocks overrides Links open in a second content window Module instance details also include l
70. Runtime Options Properties Simulator Options PO Contig File Demo ctg O a Metrix Config Fie Demo mes 0 a Executable File Jc wast8_home Ampi2 Bin sys_loader exe I Task Stack Size Jak Max Tasks f O00 Cancel Apply Help we Simulator Options These options are passed to the hardware simulator For the ModelSim Co Simulation Support there are some additional options you can specify l script lt commandfile gt used to specify the name of the file containing the ModelSim simulation commands to be executed 2 vcddump lt vcdfilename gt used to activate the VCD dump of all the signals in the HDL hierarchy to the specified file 3 deltamode any HDL port signal change will only be propagated to the CIF at the next delta If this option is not specified all the signal changes will only be propagated to CIF at the end of the delta cycles 4 sharemem lt size gt Amount of share memory in bytes to be allocated for sharing information for example Port states between the Nova 2 scheduler and the ModelSim simulator A default value of 512 K of share memory is allocated Config File The Architecture Configuration File for this project Metrix Config File The path of the associated Metrix Configuration mcx file See the Metrix Configuration File User Guide Executable File This specifies the file that calls the Fabric dll Task Stack Size Default 32K May be increased for large projects Max Tas
71. Simulate the active target in the prototype This has the same effect as selecting the Simulate option from menu or toolbar Simulate All Simulate all targets in the workspace This has the same effect as selecting the Simulate All option from menu or toolbar Validate Validate the active target in the prototype This has the same effect as selecting the Validate option from menu or toolbar Validate All Validate all targets in the workspace This has the same effect as selecting the Validate All option from menu or toolbar Debug Debug the active target in the prototype This has the same effect as selecting the Debug option from menu or toolbar Debug All Debug all targets in the workspace This has the same effect as selecting the Debug All option from menu or toolbar VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Building and Simulating in Batch Mode Simulating and Debugging a Model Target Time Limits You can set the maximum time for which the simulation runs e Simulation Limit batch run to the specified number of simulation time units Allowed units fs ps ns us ms s e g SimTime 30ms stop after 30 milliseconds of simulation time e RealTime time Limit batch run to the specified realtime seconds e g RealTime 5 stop after 5 seconds Saving the batch When the batch mode options a
72. System IF I Folders aj a Source Files ow Ey SystemCCIF cpp E Z SystemCCIF fm a oo Z SystemCclF rc jpa E ampi_syrolink_dll_body c ee vo EY ampi_ symlink init c aj a Header Files i SystemCCIF h beeen gE ampi_symlink_names h a config h bese E config_types h m vo resource h a Generated Files conFig_init c oa SE config_symlink c gE config_init h config_struct h gt SE config_symlink h a E version_number h oe Ta guranians Ses Sa Mova2 cDll Debug o E C Includes C Libraries ho systemcd lib oie Novaz cDil Release The template includes skeleton code for a SystemC adapter module with interfaces to both a Fabric bus and a sample SystemC device module To develop a module of this type you need to be familiar with development in both Fabric and SystemC For more details see Modeling Guide using the Communication and Infrastructure Fabric and the application note Interfacing a SystemC Device Model to a Fabric Platform You need to choose SystemC libraries that correspond to the version of C compiler you are using See Choosing the SystemC Libraries for VC 6 VC 7 VC 8 and GCC below Choosing the SystemC Libraries for VC 6 VC 7 VC 8 and GCC You need to choose SystemC libraries that correspond to the version of C compiler you are using If you have chosen the Microsoft Visual C compiler the template sets up the libraries for VC 6 166 VaST SYSTEMS TECHNOLOGY Confidential a
73. Tool is to be associated You can choose a specific Target no target or all Targets Project dialog Click OK x Es Simple SP1 Et ra Folders E Source Files gi 4 Header Files H E Generated Files H Configurations a Targets da My Console Workspace VaST Modules CoMET displays the new Tool node under the project Tools node in the Workspace window When you run a simulation COMET runs the tools in the Tools list first and then runs the simulation VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 153 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Target Debugging Considerations Target Debugging Considerations CoMET is designed to provide highly accurate timing during model simulation Care must be taken in performing certain target debugging operations which may affect either simulation time or model state The modeler has a choice of whether to advance simulation time when the target debugger writes to or reads from a register VaST recommends that the modeler does not advance simulation time when the target debugger reads from a register When the target debugger writes to a register the choices are as follows If simulation time advances on the write then debugging affects the accuracy of the simulation and the model responds as expected to the write If simulation time does not advance on the write the
74. a Module Type TestVerilagModel Version 1 00 Back am Cancel Module Class Select Peripheral Model Verilog fora Verilog project Module Type Specify the name of the Verilog entity in the Module Type field or accept the default Version Specify the version or accept the default Click Finish NOTE The Module Type has to match the name of the Verilog model The top module can will be a Verilog module may instantiate other VHDL entities and Verilog modules in the project Double click the Build Configuration to open the Configuration window S Project x Configuration Properties Type Mode Debus O Path ModelSimDebug O O aier DNOVA2 DMODULE DPRE_SYMLINK_INIT_RE Verilog Options PO hdl Options PF ile Daere PO Detine File TestVHDLModel def Achye lt lt Specify the Verilog complier options for Vlog in the Verilog Options field Specify the VDHL complier options for Vcom in the VHDL Options field if there are VHDL entities in the project VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 185 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support Verilog Co Simulation Support CoMET creates a Verilog Model project from templates xi mep Test erilogModel E E Folders a Source Files os E Test erilogModel c E TestverilogModel rc TestverilogMoadel conFig_hda c ampi_sy rolink_
75. a module All modules including Virtual Platforms VPMs peripheral devices and Virtual Buses communicate using ports VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST project register Software Development Environment StdBus System Engineering Environment task function Virtual Hardware Platform Virtual Platform Virtual Processor Model Virtual System Prototype workspace VaST SYSTEMS TECHNOLOGY Confidential and Proprietary Glossary A set of files from which you build a Virtual System Prototype A project may include source files header files pre built modules DLL s include files libraries and target software files One of a small set of data holding places that are part of a system and that provide a place for storing variable data Registers can have arbitrary names SDE A graphical user interface in which you can build interactive real time embedded software for target system architectures The VaST Standard Bus StdBus Protocol Engine is the main component of a generic Bus Model that can be used for Device and Module Interconnect The StdBus does not represent a specific proprietary Bus Protocol It provides a generic StdBus protocol and emulation of proprietary protocols including AHB AHB Lite and PCI SEE The graphical user interface in which you design build and
76. acecnestnedatens 14 Target WIndOW cccccccccceeeeeeeeeeeeeeeeeeeeees 13 OUt ienien i 13 POO DAK EPATIT 13 WAU EE AA T E A E T 13 Tools Work p te sccasescacdnacssssesioeecbcorgenceseesueadenens 13 Matlab Generator cccccccecceeeeeeees 159 Windows XP ATIS CALI ING ccosesseaccnaiie dearenoescanoecedcanteeeecentdertes 6 4 Workspace Update C ae E 43 anD PEE E E E AE 12 Exporting 0 0 cccccccccccccccccccccccccccccccceeeeeees 57 Update F abi ic cccscahisesiseceeccntecesesiancuecenaticeds 72 AAT 6 0 13 Update PE esee 122 Window keys sssseoeesessssssssssssssrrreeeesess 156 Update Platform cccccccccccccccccseeeeeeeeeeees 122 y XML Table Views Validate Connection View sssssssssseeesesesssssssseeee 99 Validating VPM behavior 068 145 Parameter VICW wcaccvetneresnsascosecesaeaenaaincescncs 98 Value Change Dump ccececcccceeeeeeeees 146 A 6 Deemer E A B A ee een een 146 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 199 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST
77. al models of a hardware system that have superior performance and accuracy A Model that can generate transactions to the StdBus but cannot receive transactions via the StdBus A Virtual Processor Model VPM is an example of a Bus Master A Model that can receive transactions via the StdBus but cannot generate transactions to the StdBus A Model that is capable both of receiving from and generating transactions to the StdBus Protocol Engine VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 193 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Glossary device device model Fabric Module hardware constant hardware value hardware variable instantiation latency model module peripheral device ports 194 A hardware unit that is capable of providing input to a system or of receiving output from the system or both A virtual representation of a hardware unit that is capable of providing input to a system or of receiving output from the system or both Device models for example VPMs timers controllers and memory are connected to the bus Any device model that is driven by target code must be connected to the bus A device model that does not connect to the bus such as a console or a test bench is called an auxiliary device A VaST Communications and Infrastructure Fabric Module See module A fundamental entity of a module The
78. an Instance Port Port Connection Port Or Net Name you can use array notation to indicate a selection of array members COMET connects the members of the expanded Instance Port array members list to the respective members of the expanded Port Or Net Name list The number of members in each list must match For example to connect the first group in the above Instance Port example add a Port Connection to the Instance Port IrqIn 0 7 You can now specify a connection to 8 members of a Net array Fabric Module Port Connection Properties Port Or Net Name MoN etarran 0 15 MMO ther et rray 0 15 To connect member Irq 0 to member MyNetArray 0 Irq 1 to MyNetArray 1 and Irq 7 to MyNetArray 7 specify the Port or Net Name as MyNetArray 0 7 To connect member Irq 0 to member MyNetArray 7 Irq 1 to MyNetArray 6 and Irq 7 to MyNetArray 0 specify the Port or Net Name as MyNetArray 7 0 Using Array Notation in a Port or Net View CoMET distinguishes a Net or Port array by listing it with an element range in the drop down list for the Port Or Net View Name field You can edit the range to specify the required members or specify the members in the Number Of attribute omitting brackets Fabric Module j x Port Or Wet view Properties Mame Her Port rH etier MiNet rrap 0 15 Type Number Of f Description 70 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary
79. ance Developing a Fabric Module Definition Adding a Module Instance using Drag and Drop from the Modules window To add module instantiations to a module using the Modules Window using drag and drop Open the required fmx file in XML Tree View Inthe Modules Window navigate to the icon for the module of which you want to add an instance Click on the module icon drag it to the Module Instances node in the fmx file and drop YaST Modules E Eg vasT Modules E Auxiliary S vast_uart_console j TEE os Parameters Ports EI pe a Mets Tasks E Module Instances A a StdBus StdBus_6 be us Bri Bal vactcpRecct a oy az sE Vastopllockl Clock H a ae eel virtualPlathorn FS Inte_Arm Sa Invert g YaST Modules The new module instance appears in the fmx file view with a default name WaT Modules E Eg vasT Modules B Auxiliary H E vast_uart_console fe Bus N o E StdBus oe D i Module Instances Ele eal StdBus 1 3 E e Instance Ports uga G2 Parameter Overrides Ea VastGpReset FES vastaptlocki HEE virtualPlatform1 Simplex SF 1 l H E StdBus_Bridge A a Gp Sa Clock fq Bac fl E Inte_Arm z j Invert FE YaST Modules VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 87 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Module Instance Adding a Module Instance
80. array determined by the NumberOftMemoryBlacks parameter Instance Ports Port Descnpton Connectons BusClock Module port BusClock E m StdBusiclackNet Reset Module port Reset E T PlatformReset Bus Module port Bus E AF StdBusinet Enable Module port Enable MemoryPageSelect Module port MemoryPageSelect Parameter Overrides Name Type Value Description BurstReadBeatLimit twWord32 a Maximum beats in a read burst Each beat MemorywWwidth of bytes If O then no burst limit Burst WriteBeatLimit twWord32 E Maximum beats in a write burst Each beat MemorywWwidth of bytes If 0 then no burst limit Enable PowerOnDecode tEoolean i Setting this Parameter to TRUE will allow this Memory Model to have its Decode available at Power On to facilitate Loading by VPM Memory Size twWord32 p Ml Total Size in Bytes of the memory being attached to the Bus via this memory controller Memory Width twWord32 4 width of the memory being attached to the Bus via this memory controller Profiling tAltList Disabled Startaddress tWorde4 la Base Address of the memory being attached to the bus via this memory controller pereen pa eat this Parameter to TRUE will allow the Enable Pin to be Used to Enable Disable this Memory Memory Paging NoOfMemory Pages twWord32 p Specifies the number of Memory Pages within the GP Memory Model Pagesize tWord32 p Fh Specifies the Page Size in Bytes if NoOtMemoryPages gt 1 Otherw
81. ated pdb register tyoes h r0 PobGenerated pdb register types h 7 PobGeneratedsbus standard slave h 1 76 C work cometoroajectssPdbD emoD evicesPdbDemoDevice PdbGen LC work cometorojectssPdbD emol evicesPdbDemoDevice Pdbo eni C teark SS cometonoiecte s PARC enolase Pdh ema evine PORG ern Cloze E CoMET displays a list of occurrences of the symbol in code showing file and line number Click on an occurrence in the list to move to that file and line NOTE Ifyou attempt to use the Browse Symbol function without building the module an empty Browse Symbol dialog box will result as shown below Browse Symbol S x To fix this error simply build the module see Building the Workspace and Projects page 137 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 135 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Using the Source Editor Special Editing Keys Special Editing Keys In the source code editor you can perform standard editing functions with commonly used hot keys You can also toggle bookmarks and breakpoints go to a specific line and perform search and replace operations Many of these options are available from the Edit menu as well as by hot key Navigation P 136 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST
82. aving a r RF ampi_symlink_names 48 49 config_types h 50 ft resource h 51 o ES Generated Files 52 Hga Configurations 53 SEH SimpleTimer 54 Ey Folders 55 BE Source Files 56 H E Header Files SF i H Generated Files 58 age Configurations 59 60 YaST Modules Find In Files Searching for Returns ae Nothing t7 e tInstanceData IP tBoolean Ente PDBResetDeviceStart DO NOT ADD CODE TO THIS SECTION PdbRegqisterResetiallRegisters IP gt pPDBDemoDeviceRegisters PdbStdBusMasterReset IP gt pMasterBusData FALSE PdbStdLogicMasterReset IP gt pTransferCompleteData FALSE tWord32 Index ea Tadas Me Twas A 7 Thanas tt th Na b in C VastProjects PDBDemoDevice PDBDemoDevice c cpp cxx cc h hpp v vila tInstanceData C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 38 void PDBDemoDeviceReset Device tInstance C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 52 void PDBDemoDeviceResetDevice tInstanceData IP tBoc C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 93 tInstanceData IP C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 101 IP tInstanceData AmpiMemory calloc 1 sizec C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 170 tInstanceData IP C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 173 IP tInsta
83. c Module Definition Fmx Update Update Fabric Fmx Update Update Fabric An Fmx file may contain a module instance of a module still under development When the module changes the derived module instance must change to reflect those changes In particular the Instance Ports of the module instance must correspond to the Ports in the changed module and the Parameter Overrides of the module instance must correspond to the Parameters in the changed module The Fmx Update process accomplishes this Fmx Update occurs as part of the Build process and may also be initiated by choosing a menu option To update the active project fmx file choose Workspace Update Fabric CoMET determines all modules that contribute to module instances within the active fmx file and working from the lowest level of the hierarchy updates module instances up to the active fmx file Instance Port Port Connections and Parameter Override values in a module instance are preserved by the Fmx Update process where the Port or Parameter in the module is unchanged New module Ports and Parameters result in new Instance Ports and Parameter Overrides in the module instance Where a Port or Parameter is deleted in the module the corresponding Instance Port or Parameter Override 1s deleted from the module instance and connections and values are lost See Port Parameter Module Instance Parameter Override and Instance Port below Prototype Configuration Files use the same mechan
84. ce menu select Add Existing Project BrowseforProjectfiles TB Look in oS SimpleySP1 Oe e i My Recent Ej Simplex 5P 1 pjx Documenta Dezkto m My Documents er hy Computer Bi File name Simplevs Fi pis wii ETM Files of type Project Files pis Lancel Open as read only E Navigate to the location of the project select the pjx file and click the Open button 50 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Removing a Project from the Workspace Managing Workspaces and Projects x Ea workspace POBDemoDevice a VirtualPlatForrn 2g Folders Sy Source Files 3 VirtualPlatForm c VirtualPlatFormm fmz VirtualPlatForm rc ampi_s rolink_dll_body c armipi_s rolink_inik c H E Header Files Generated Files ce ies Configurations Ee Simple Timer Eel Simple SP1 Removing a Project from the Workspace To remove an existing project from the workspace From the Workspace menu select Remove Project or Right mouse click on the project icon and select Delete Project Workspace POBDemoDeyvice Fa VirtualPlatForm Fa Sirnple Timer SRE Simple 5SI Expand Project ctrl E G J Folders Collapse Project Ckrl L H E mi gJ dd Targets Add Tools Edit Project e Project Gut Project atts Copy Project Ctrl C Paste Cobre Act
85. ceeeeeeeeeeeeeees 159 cep P TIC TUL DAI sccecun ernannnnedeads N 12 E METeor sae EAE EE cater EE E 54 Exporting VSP to METEOt ccccccccsssssssssee 57 in ea Modeine Phat sae te E ET EAE NE a Fabric module 25 sc0ssc0ssn0dsesasnnssnacsaveonsesensss 47 ea uae andon ee 14 Modules Window SSS software WINdOW sssssssssssssssssssssssssessssssenns adding a new module library 38 ca aes aneia 142 creating module instances by drag and drop Pepe este pee 97 i 0 DSL 21 10 eee en 139 Sical E E E and editing Keys ssss s PAP A AT 136 i 88 managing breakpoints cccccceeees 143 PAS be oeo Seine E E cae casciaracsee 142 198 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST source files Index virtual system prototype ICID oceans ues EE A AET 55 TIVOG Gis aece pence ceraendoeseeneee nest oe eee eens l creating new source files 130 VSP SAIN a E E 129 55 4016 101 ate ee EE 5 PEUS OAL roe E 13 W SUPPOFL SCIVICES 2 dsccacaseareasvacsdacdavivseaneaviedtiaess 42 By NG r te en mia canna E 165 WoO 0 21 eee en ee ee eee eee eee ere 42 Peripheral Module SystemC 48 Window T Build output cc eeeeeeeeeeeeeeeees 138 DOCUMENT wisaccacnacsssessninaeseoandeaecadetnetaraceagaes 14 Target Binaries Expotrt ccccccceeeeeeees 58 MOGUIES cccscenctctses seedeccncetoenccorge
86. ces Module Instance Sub Parameter Overrides A Sub Parameter Overrides element corresponds to a Sub Parameters element in the module from which the module instance derives It maintains the hierarchy of the Sub Parameters and Parameter elements in the module allowing correct placement of Parameter Override elements When you add a Module Instance to a Fabric Module COMET automatically creates Sub Parameter Override elements corresponding to the Parameter Override elements in the module Sub Parameter Overrides also appear in the VSP Prototype Configuration pcx file Fabric Module x Sub Parameter Overrides Properties Name Description Name This matches the name of the Sub Parameters element in the module Its path of parent Sub Parameters elements must also match the path of Sub Parameters elements in the module A Sub Parameters element has no purpose if its name does not match a module Sub Parameters element Child Elements The Sub Parameter Overrides element may contain one or more Parameter Override elements The Sub Parameter Overrides element may contain one or more Sub Parameter Overrides elements Description You may add a description for documentation purposes VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 93 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Instance Ports Ins
87. choose a project name to match the name of the existing VBus module it is not necessary to alter the source files You can edit them if you wish You can now build the VBus Peripheral Model When the VBus Peripheral Model is successfully compiled a module instance of the model can be added to a CIF platform 162 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating a VBus Peripheral Model with FinSim CoMET 4 and SystemC Compatibility E kn Testplatform 4 Parameters A Ports A Mets 7 fil Tacks Ei Module Instances eel vBusPeripheralModelInstance Hga Instance Ports Aas Parameter Overrides fe device_base_address 0 a device base length 0 device _pre_time 0 device _post_tine 0 MoyaLibPath Novatmdargs You can have only one VBus Peripheral Model in each VBus Peripheral Model project Parameters CoMET automatically creates the following parameters for the VBus Peripheral Model These appear in the module instance Parameter Overrides and the Prototype Configuration pcx Parameter Overrides e device base address e device base length e device pre time e device post time e NovaCmdArgs Specifying the VBus device type The VBus device type is specified in the Project Configuration Double click the VBus Device Project node in the workspace to open the Project Configuration dialog Simula
88. choosing the Substitute Local Drive option and selecting the agreed drive letter Network Drive Alternatively the DTDs may be placed on an agreed network drive and all users can refer to it by the same UNC Choose Network Drive browse and select the agreed UNC Default XML Views Choose the view you prefer as a default on first opening a pcx or an fmx file For more on table views see XML Tables Configuration Settings page 33 and Using Table Views page 97 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 27 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Configuring the CoMET System Engineering Environment Runtime Options Enable runtime dependency checks Check this box to enable runtime dependency checks This is the default behavior At the beginning of simulation COMET checks dependencies in all projects in the workspaces CoMETs prompts to rebuild projects with out of date builds Uncheck this box to disable runtime dependency checks COMET performs no dependency checking A warning appears at the start of simulation Warning Runtime dependency checking will not be made Runtime Options Auto convert Gcc projects to No Cygwin DII Check this box to automatically convert any Gcc project to use the no cygwin DII option With this option enabled e Loading an existing Gcc project into COMET will automatically use the no cygwin op
89. cription for documentation purposes 80 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Nets Developing a Fabric Module Definition Nets A Fabric Module element may contain a single Nets element This element is a container for all Net elements Child Elements The Nets element may contain one or more Net elements Net Nets Net A Net allows a connection between Ports of two Module Instances within a platform Fabric Module q Xx Net Properties Hame Type Number Ut f Description Name Type a name for the Net See Choosing Names page 67 You can create a Net array See Arrays page 67 Type Select a net type The Net and any Port to which it connects must be the same net type Allowable Values StdBus StdClock StdLogic CanBus StdVector32 The Connect Net Type is reserved for VaST internal use Number Of You can create a Net array by specifying a dimension in this attribute Each member of the array shares properties but may be independently connected See Arrays page 67 Allowable values Positive integer Default 1 A single Port not an array Description You may add a description for documentation purposes Child Elements None VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 1 May not be used disclosed or reproduced except as expressly authorized in a writte
90. d 8 Express Gcc Choose a version of the Gcc compiler appropriate to the tools and features you are using such as VBus project support and FinSim support COMET supports Gec 3 2 set Gee Location to Yvast5 home gcc and Gece 2 91 57 Set Gcc location to vastS home gcc eges 2 91 57 See COMET 4 and SystemC Compatibility page 159 NOTE Ifyou have Cygwin installed on the same computer as COMET you must ensure that you use the version of Cygwin supplied with CoMET Later versions of the cygwinl dll do not work correctly with the version supplied with CoMET VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 31 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Configuring the CoMET System Engineering Environment User Locations Configuration Settings The User Locations tab allows a user to configure variables to represent directory paths on the user s machine CoMET substitutes the variable for the corresponding path on closing a project file or workspace file On opening the project file or workspace file COMET substitutes the path for the corresponding variable This is useful if you have libraries or other file resources outside the COMET workspace and you share the workspace between users who keep the file resources in a different directory configuration If each user sets the user location variable to the correct directory path on that user s machine then th
91. d Stop Simulation menu or toolbar items to stop execution Within each workspace targets are built and simulated in the order in which they appear in the workspace projects tree VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 149 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Building and Simulating in Batch Mode Command line batch mode CoMET can be started from a DOS command batch file with a B parameter specifying that CoMET is to execute with specified batch mode options After a batch run invoked from the command line COMET closes You can specify batch mode options in the COMET Tools Batch Mode dialog Alternatively you can specify them in a CoMET batch file When you run CoMET from the command line you have the following options CoMET B atchMode lt BatchFile txt gt H ide M inimized L ogPath lt LogPath gt lt Workspace wkx gt lt File txt gt e g c vast5 home Bin Comet exe b h 1 c logs The above command line results in a COMET run in batch mode with Batch Mode options specified in Tools Batch Mode dialog and saved in the registry The COMET GUI does not appear Log files of the Software Log and Build output are saved in the c logs directory Batch Mode Options B batchmode Run in batch mode Use COMET batch options specified in COMET Tools BatchMode dialog or optionally specify a
92. d Version Number UF f Class IN one Sub Class Description 84 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Module Instance Developing a Fabric Module Definition Instance Name Type the desired Instance Name Each Instance Name must be unique You can create a Module Instance array See Arrays page 67 Module Type Select one of the listed module types Listed modules are either projects within the Workspace or compiled modules in the Modules library See Modules Configuration Settings page 38 Required Version This attribute is used in module versioning in conjunction with the Fabric Module Version attribute If a Required Version is specified on simulation COMET attempts to locate and load a module of the specified version If a module with the specified Required Version cannot be found CoMET displays an error If no Required Version is specified COMET locates and loads the latest version of the module To locate a module version CoMET first searches the current workspace then the svast5 home Modules directory and then any additional user defined module library directories Number Of You can create a Module Instance array by specifying a dimension in this attribute Each member of the array shares properties but may be independently connected See Arrays page 67 Description You may add a descrip
93. d except as expressly authorized in a written agreement with VaST Arranging Windows Getting Started CoMET 5 C YastProjects Simple YSP Simple SP wkx File Edit View Workspace Debug Tools Window Help HE XMRIE B BlRae s a Y PP Workspace l E El Workspace Simple SP Hi config_types h en Module Instances E resource h gal ARM926EJ51 Ee 2 include SimpleVSP1 h By en 3 include vast _std_types h 7 SimpleVSP1 c 4 include amp i_symlink_dll body h i include SimpleVSP1 Fmx z eal Simple SP1 rc Peete ee ampi_symlink_dll_body c k CR i E ampi_symlink_init c 9 Eby Header Files a En E Simple SP1 h E y ResetNet a ampi_symlink_names h Mss Intel By StdLogicONet config h Ag Tasks j Generated Files iil ge Instance F Configurations sety cee Parameter H Nova2 cDil Debug y EEE StdBusInstanc a Nova2vcDl Release ig a C Includes a be E G Runtime Options a a g Targets s PoE Gg GEA VirtualPlatform B Folders Source Files VirtualPlatForm c virtualPlatform fmx VirtualPlatform rc ampi_symlink_dll_body c E aroni esrolin z vaST Modules Instance F G8 Parameter VastGpDiagno Instance F HP Master Q Slavet Q Master wp SlaveE i OO manned For Help pr
94. d for a VHDL logic input port VCST generates a clock signal for the VHDL logic port having the same clock period as the input StdClock e Ifa StdClock is selected for a VHDL logic output port VCST will evaluate and output the clock period of the VHDL logic signal to the output StdClock port 170 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST VHDL Co Simulation Support ModelSim HDL Co Simulation Support e If StdClock is selected for a VHDL integer input port the VHDL integer port will be provided with the clock period value of the StdClock e If StdClock is selected fora VHDL integer output port the clock period value of the StdClock will be assigned with the value of the integer port outputted e If StdVector32 is selected fora VHDL output port of std logic std _ulogic or array of these types then a value of H Weak High or Driven High will be mapped to a value of 1 in the StdVector32 All other values will be mapped to 0 This also applies to arrays of std logic and std_ulogic In this case the corresponding bit value will be set accordingly as shown n the following example A std logic vector value of HOLZX1 will be mapped to the StdVector32 value of 0000 0000 D000 0000 0000 OOJO COTO GOOT e If StdVector32 is selected for a VHDL input port of std logic std_ulogic or array of these types then a bit value of
95. d reading the Modeling Guide before reading this document e Metrix User Guide e Metrix Configuration File User Guide e CoMET Modeling Guide v1 0 if working with VBus projects e CoMET and METeor Third Party Tool Support integration with debuggers and other third party tools 2 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Whats New in CoMET Introduction What s New in CoMET New in CoMET 5 14 Visual C Version 8 and Version 8 Express Supported CoMET now supports Visual C Version 8 and Version 8 Express See Tool Locations Configuration Settings page 31 Implemented Support for mno cygwin Option with Gcc Projects Implemented support for the mno cygwin option with Gcc projects See General Configuration Settings page 26 New Buttons Added to Toolbar The following buttons have been added to the Toolbar New File Workspace Log and Target See Toolbar Buttons page 17 New in CoMET 5 13 Verilog Support The ModelSim HDL Co Simulation now supports Verilog models See Verilog Co Simulation Support page 180 Multiple Versions of Models Support CoMET supports multiple versions of a model to be located in the modules VASTS HOME Modules directory See Multiple Versions of Models within CoMET page 14 New Parameters Added to the Default Parameter Views e Added MemoryWidth Tunneling NoOfM
96. der Files H E Generated Files H AP Configurations de Targets rF TargetTesk E E VirtualPlatforrn Expand Target Ctrl E H sieve _demo Collapse Target Ckrl L EREL SimpleTimer a HEA TimerTest Add Symbol File Workspace a YaST Mo Edit Target F2 Delete Target Del Cut Target Ctrl Copy Target Chrl 0 Paste Etrit Activate Target Cbri 4 Target Properties Ctrl F Select Add Target Image CoMET displays the Project dialog Target Image Properties tab Target Image Properties Project i x Target Image Properties Module nztance fT op B asesheax 1 MSH 24 Reader SRec Fath target appsshealgp ibus demo device a Map Defaut Comparator File Ea In the Target Image dialog Module Instance Specify the module into which the the target is to be loaded CoMET provides a list of all available module instances with target image loader interfaces VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 125 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Target Executable Reader Specify the binary format of the target image Path m Elf Coff SRec AbsToSrec Hex Default Browse and locate the image file Map Select the map to be used with this image Comparator File Click OK Default maps byte addressing to byte addr
97. dll_ body c armpi_sy rolink_inik c a Header Files oo E Test erilogModel h i TestverilogModel wrh ampi_symlink_names h config h canfig_types h resource h a Generated Files E TestYerilogModel fmx config_init c config_symlink c config init h config_struct h config symlink h version_number h config_hda h oe ga Configurations Ses ae ModelSim cDIl Debug f g C Includes 2 Verilog Includes Soren Modelsim cDill Release Fy c Includes H E Verilog Includes Workspace ss YaST Modules User Modules You can now replace the newly created files with the corresponding files from the existing Verilog project e Source Files ProjectName c behavioral C for Verilog device e Source Files ProjectName v Verilog source file e Header Files ProjectName h behavioral C header e Header Files ProjectName vrh Verilog header file Alter the above source files as required You can also add other VHDL or Verilog source files to the project You can now build the Verilog Model 186 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Verilog Co Simulation Support ModelSim HDL Co Simulation Support BE Test erilogModel Test Few oj x TestVeriloghodel Parameters a g Ports Pa Reset aa Tasks 4 el TestverilogModelTask H E E Port Or Net views Xml tree v
98. dule for each specific build configuration You can also add your own build configurations El Workspace Simplev SF ogi VirtualPlatForm rec Simple Timer a Simple SP1 o H Folders ag Configurations H S Nowa2 cDll Debug oy NovaeYeDill Release Foe Targets HGS Target Test Eel sieve_demo ele Timer Test Workspace va5T Modules Setting the Build Configuration You can set different parameters for each build configuration The build configuration parameters vary for different project types Fabric VBus Metrix Target or General and module classes VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 109 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Build Configuration To set parameters for the build configuration Right mouse click on the build configuration icon or name in the workspace tree El Workspace Simplex 5F Hea virtualPlatForm Hea SimpleTimer HEA Simple SP1 2g Folders So ae Configurations E a Nova cDil Debug eee Novazvc Expand Configuration x Ctrl E Fle Targets Collapse Configuration Cbri b on Target ci Pal sieve demo Add C Objects mea Timer lest 4dd Libraries works Te Edit Configuration F2 eee S Delete Configuration Del uk Configuration Chrl Copy Configuration Chrl Paste Cory Configuration Properties Ctrl F Select Configuratio
99. e COMET CD ROM or unzip the supplied zip file Ifthe installation program does not run automatically start the installation program by selecting setup exe and follow the procedure displayed by the setup program There is no need to reboot your computer after the setup procedure has completed Copy the VaST license file license dat from email or floppy disk as provided to the VASTS HOME license directory YVASTS HOME is the default installation directory where this release is installed Install the FLEXIm license manager software See Globetrotter Software Inc s documentation for more information NOTE CoMET requires MsXml4 SP2 When CoMET launches it determines whether MsXml4 is installed If not COMET launches the MsXml4 installer You need to complete this installation before proceeding with CoMET NOTE Ifyou do not have the license files or if licenses have expired please contact VaST at support vastsystems com Setting up Environment Variables CoMET uses environment variables to define the location of COMET components When you install CoMET these variables are set to default locations Usually you will not have to change the settings of the environment variables from their default values however if you change the location directories of the CoMET files you must update the environment variables so that CoMET can locate the associated files Environment Variables CoMET uses the following mandat
100. e Option Properties 00 0 0 ccccccceeeeesessesccseesssssssesessessessesseseeeeeeees 117 Viewing and Setting Runtime Options Properties cccccccssesessseesseseeeeseeeeeens 118 Fabric Project Runtime OPON saseces te ceccseccte royce terwscnctiavas E 119 VBus Module Runtime Options Properties ccsecesesssssessssessssessseeseeees 120 Supported simulation engines serseri sir iin nni TEATE 120 Modifying Parameter Values in the Prototype Configuration File ce 121 Pex Update Update Platter ti vxicaek lt venacedovansicaseienensndvasiiiehawesnieieseswnenesausnedehesenenehosess 122 Excluding Build Time Parameters from Prototype Configuration Files 122 vi VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 5 14 User Guide Contents Setting the Target Executable ou ccsc nreschennswandasedeccisanlase davedesehstnswantasebeseisenerereetuasnddes 124 Tarzet iia 6 Proper iGS tccncsosnecaassesesssndeosonossonspusbsonsnusssenenss esos sbesesueccsanseuensoateeas 125 Restrictions on the Target Image Comparator SREC format cccccceeeees 127 SM the Source Editor sisascisstiaconcesacctesssanrastececasaascevcasadiatstasesessetsisessistgissnusteensaesiess 129 Mebhehiad KeyWords isi cescxecantacersdecorecaarsmetassadeveticeavate eve aeetensaderetaceerensaniee 131 EAO TC ADEECS R E EEE E AAEE
101. e workspace can be shared without the users requiring identical directory configurations It is not necessary to create User Locations for paths within the workspace CoMET stores these as relative paths CoMET Configuration gq x General Editor Options Tool Locations User Locations etiL Tables Modules Environment Add Edit Delete cad a To create a new User Location click the Add button To edit the User Location path select the User Location entry and click the Edit button or double click the User Location entry To alter the User Location name select the User Location entry and press F2 or with the User Location entry selected click the name 32 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring the CoMET System Engineering Environment Getting Started XML Tables Configuration Settings The XML Tables Configuration determines the layout of XML Table views within Document windows These views are available from the right click context menu for Fabric Module Definition files They provide a tabular listing of selected elements within the module There are two types of table Parameter lists module instances with their module type and columns corresponding to specified parameter types Connection lists module instances with their module type and all con
102. eInstance B s Instance Ports oe ral Reset Ep Y Interfaces a sa TargetDebugger A e a nader 74 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST FMX Hierarchy Developing a Fabric Module Definition The table shows elements with their immediate child elements Jo Fabric Module G Parameters 0 Ports Jo Nets 28 Tasks Module Instances hy Interfaces S parmeters Aa Parameter E l Sub Parameters pal Sub Parameters Ao Parameter EA Sub Parameters So 2 w Net 28 Tasks Task Port Or Net Views do Port Or Net View of specified Port or Net o Module Instances ie Module Instance Port Or Net Views Ge z r Module Instance Instance Ports Parameter Overrides Ge Instance Ports ral Instance Port ral Instance Port a Port Connection to specified Port or Net a 23 f Parameter Overrides Parameter Override Sub Parameter Overrides as T ae Sub Parameter Overrides Parameter Override Sub Parameter Overrides x My Interfaces Interface ry None i VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 75 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Hierarchical Parameter Type Naming Hierarchical Parameter Type Naming Parameter names should be chosen to distinguish
103. ects BusPernpherall evic eB C Compiler Cygwin Goo E Simulator or Execution Engine Application Library DLL No Cygwin Dil lt Back Cancel Project Select the Fabric project type Project Name Specify name matching the name of the existing VBus peripheral device module Location Specify desired location for project files C Compiler Select Cygwin Gcc Simulator or Execution Engine Select VaST Nova No Cygwin DLL Check this box to enable the project to use the No Cygwin DII option Click Next 160 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Running a VBus Peripheral Model on CIF CoMET 4 and SystemC Compatibility Project BusPeripheralModel x Fabric Module Module Class Peripheral Model Module Type v BusPeripherallodel Version 1 00 When the Simulator or Execution Engine is VaST Nova the Fabric Module Class is restricted to Peripheral Model Specify the Module type and version or accept the defaults Click Finish Device Type Decoding Type and number of Memory Regions are specified in the Build Configuration The build type is NovaGccDIl See Setting the Build Configuration page 109 and VBus CIF Build Configuration Properties page 113 Project F xj Configuration Properties Type NovaGiccDN 0 Mode Debu o Path NovaDebug O C Options DNOVA2
104. ects Adding a New Project type Peripheral Module SystemC See Defining a Fabric Module page 47 and Creating SystemC Projects page 165 Metrix A project for tracing profiling and dynamic debugging of your Virtual System Prototype For information about Metrix refer to the Metrix User Guide An alternative to developing a Metrix project is to use a Metrix Configuration file and the generic Metrix dll See the Metrix Configuration File User Guide Target A project that builds a target application executable The target code runs on one or more VPMs defined within the Virtual System Prototype CoMET currently supports the ADS ARM Tools and a number of GCC cross compilers Select the required compiler in the C Compiler field For more details see Application Note Third Party Tool Support General A general purpose project that you can use to build modules specific for your application for example a test bench analysis modules or other performance analysis tools Project Name A name for the new project Location The path of the folder in which the project files are stored The default location of a new project and the project files 1s the workspace directory When the project name is specified the name specified is appended to the location of the workspace so the default project location becomes a sub directory of the workspace You can modify this path so that it points to another location by adding sub directories browsing to a d
105. ecution e Continue Debugging e Step Into e Step Over e Step Out Continue Debugging The execution continues until the next breakpoint or the end of the code is reached To continue execution From the Debug menu select Continue Or Click on the Continue tool bar button VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 143 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Interrupting the Execution Flow Step Into The execution continues with the next statement in the code If the statement includes a call to another user function in the project the execution continues at or steps into the first line of the new function In this mode you can examine your entire code one statement at a time To step into a function From the Debug menu select Step Into Or Click on the Step Into tool bar button Step Over The execution continues with the next statement in the code If the statement includes a call to another user function in the project all of the code in the function is executed and the debugger continues execution at the following statement unless the statement includes a VaST API function call or a breakpoint has been set elsewhere In this case execution halts at the breakpoint To step over a statement From the Debug menu select Step Over Or Click on the Step Over tool bar button Step Out
106. ed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Arranging Windows CoMET 5 C astProjects Simple SP Simple SP wkx File Edit View Workspace Debug Tools Window Help O SGHG XOBIF BG lABOl AAA mn R SOB H HB G gt BOB H BG simple SP1 Simple SP1 c 5 x include SimpleVSP1 h inc lude vast std_types h include amp i_symlink dll body h ieeeeiteeed Simple SP1 Simple SP1 fmx timpisym G Parameters Ports jr Juge Nets KEEKKEEE ber 2 ClockNet wt Ay ResetNet Intel P Ay StdLogicONet Be Tasks E Module Instances tampiStat EEA ARM926E351 RET Instance P retu Ege Parameter a ga StdBusInstanc YaST Modules Loaded Modules For Help press F1 ln 1 Colt Inum a Docking as a tab window into exiting docked windows on left hand side of SEE You can also double click in the window s title bar to toggle between the docked and undocked position To undock a tools window from multiple windows docked together in tabs double click the tab of the window you wish to undock Double clicking the window s title bar of a multiple tabbed docked window will result in all windows being undocked 24 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Arranging Windows Getting Started Auto Hide Button When a tool windo
107. ed parameter types corresponds to a column in the Parameter Table Click Add to add a new parameter Use the hierarchical parameter naming scheme to distinguish parameter types See Hierarchical Parameter Type Naming page 76 Select an existing parameter and click Edit to change its name or Delete to remove it Click OK to return to the XML Tables tab and OK again to save changes The corresponding view of the fabric module definition xml file is shown below 34 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring the CoMET System Engineering Environment Getting Started workspae x ModuleT ype Bustwidth AddressBits gy T StdBusT StdB us Firstlorme Disabled 4 32 23 Generated Goto Module Instance Gtr El Runtime Options a Le ae ip Dlls dd Module Instance EGS Target Test Edit Module Instance ae ual Top SimplePlatform Delete Module Instance Del JEA SimplePlatform4 A papa we aut Module Instance Ctrl Hy Source Riles Copy Module Instance Etr E eee SimplePlatForm1 c SimpleFlatform 1 Fri ell Tee wiew pee SimplePlatform1 rc ampi_syrolink_dll_box T ampi_symlink inik c H E Header Files o H Generated Files dga Configurations E o Nova cDll Debug i i n A Nova2 cDill Release Logic Connection view Elza arm 26e_sieve AML Table Properties 1 Folders Paste
108. ee the Microsoft Visual C Express website http msdn microsoft com vstudio express visualC default aspx To choose an internal debugger for Hardware Models choose Tools and ensure that the External Debugger menu item is unchecked VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 139 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Choosing a Debugger The internal debugger used for Hardware Models depends on the active Configuration in the Project Workspace Configurations GDB Internal Debugger If the selected Configuration requires the gcc compiler e g Nova2GccDIl the internal debugger is GDB The debugger output and command line interface appears in the software window with a gdb prompt CDB Internal Debugger If the selected Configuration requires the Vc compiler e g Nova2VcDII the internal debugger is Cdb The debugger output and command line interface appears in the software window Target Code Debugging The external debugger used for Target code depends on the type of the VPM module instance on which the Target code runs It also depends on your selection from among the supported cross compilers for your Target code At the start of a debug session for each VPM in your VSP you can independently select Debug or Simulation mode See Executing in Simulation Mode and Debug Mode below To interrupt execution during a Target
109. efined in the Module of which you are adding an instance For a Parameter element whose Fmx Access attribute has a value of Public or Protected CoMET creates a corresponding Parameter Override element It maintains the Parameter hierarchy by creating Sub Parameter Override elements corresponding to each Sub Parameters element in the module You can override a Module Instance Parameter value by altering the values in the corresponding Parameter Override elements You cannot delete Parameter Override elements or add them The Edit feature in the Parameter Override context menu allows you directly to change the Parameter Override value without opening the element dialog Parameter Override elements also appear in the Virtual System Prototype VSP Configuration pcx file defined for the VSP The Prototype Configuration file contains Module Instances and their Parameter Override elements for every Module Instance within the VSP hierarchy A Prototype Configuration Parameter Override value takes precedence over the matching platform fmx file Module Instance Parameter Override value which in turn takes precedence over the matching module fmx file Parameter Value defined when creating the module Alterations to a module must result in changes to module instances of that type See Fmx Update page 72 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 89 May not be used disclosed or reproduced except as expressly authorized in a
110. efinition and Prototype Configuration Reports Views and Reports GenericMemory1 0 Module Path Top VirtualPlatormnd Generichemory 0 Submodules Wo Submodules Type Required Version Class SubClass Description Parent Connections GenericMermory Hone This is an array of VWirtualPlatform fm module instances with the size of the array determined by the NumberOthMernaryBlacks parameter Parameter Overrides Hame Type Value Descnpton BurstReadBeatLimit twords2 0 Maximum beats in a read burst Each beat Memory Width of bytes If O then no burst limit Burst Write BeatLimit tWords2 0 Maximum beats in a write burst Each beat Memory Width of bytes If 0 then no burst limit Enable PowerOnDecode tBoolean 1 Setting this Parameter ta TRUE will allow this Memory Model to have its Decode available at Power On to facilitate Loading by VPM Memory Size tWords2 8 M Total Size in Bytes of the memory being attached to the Bus via this memory controller Memory Width tWoard32 4 Width of the memory being attached to the Bus via this memory controller Profiling taltList Disabled StartAddress tWord 4 O Base Address of the memory being attached to the bus via this memory controller Use Enable Input tBoolean O Setting this Parameter ta TRUE will allow the Enable 7 to be Used to Enable Disable this Memory MemoryPaging NoOfMemory Pages r 1 __ the number of Memory Pages within the GP Memory Model Pa
111. ei ri mee eee 13 Document Windows et seacsaeceretatsaceentesaccemersenscacusraecetasasuecuevacesmar sanucacwaeceensesaseecnesacnat 14 COICO XG M Oe O E O E E E 14 Modules WNION sani EE EE T E E TEE TE EAE 14 Multiple Versions of Models within COMET ccccccccccccccscecceeeeeeeeeeeeeeeeeeeees 14 Maintaining Multiple Versions of a Module COMET eeeceeeeeeeeeseeteees 16 PPO eae ONS ash soa E e E E E E E E 17 Mow TG BUO e E E E EE AE E EEEE 17 W OU SAG MD oee E E E E 18 Loe TSO e n E A A E E ionaadnetiaacontassasecatonpsesaned 18 Toe TO arena E ces E EE E I EE E E sus E E 19 li VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 5 14 User Guide Contents POT tho Tutorials ocr cerca reketeracek ncetevesnterauickveesaviebesetacekaidetavesehetauekseetaceheseracebatoleveseseapecs 19 Windows XP Theme Display ISSue ccccccccccccccccseeeeeeeeeeeeeeeceseeeeeaeeeeeeeeeeeeeeeeeeeaees 20 Aranno VV OW S sin co cgercececa been E E 22 Document WINCO WS sicsseouenesicaceduneaxsasdvansessevcboustandebtebanssiunsdinensusionebosstandebiolanssnumnnres 22 TOW ON ea EE T E ES E E T E EAA EEE ETO 22 Docking Tool Windows cccccccccesssseeseeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 22 Awo Tide BUON aerer EE EEE 25 Configuring the COMET System Engineering Environment cccccccccccceeeeeeeeeees 26
112. elp E2 See Common Build Configuration Properties page 110 Device Type Allowable Values SlaveOn1ly Default MasterSlave NonBus Device Regions The number of device decoding regions Default 1 Memory Regions The number of memory decoding regions Default O VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 113 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Active Build Configuration Target Project Build Configuration Properties x Configuration Properties Type ArmCcApp oy m ae Mode Debus tC Asm Options PO C Options Po Link Options Po Define File PO l Archive Fass O o Cancel Apply Help we See Common Build Configuration Properties page 110 Asm Options Assembler command line options Setting the Active Build Configuration A project module may contain several build configurations When you build the project it is the active build configuration that is built To set the active configuration Right mouse click on the configuration icon 114 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Active Build Configuration Configuring Build and Runtime Options Workspace Workspace Simple SP Hea virtualPlatForm Hea SimpleTimer e Simple 5P1 o E
113. emoryPages and PageSize to the default Memory Parameter view See Parameter Views page 98 e Added BusProtocol amp RequestLatency to the default Bus Parameter view See Parameter Views page 98 e Added WorkBufferSize to the default VPM Parameter view See Parameter Views page 98 Enabled Sorting in Versions Dialog Box The list of tools and models displayed in the Versions dialog box can be sorted by Path or by Version number See Displaying CoMET and Tools Models Versions page 41 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 3 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Introduction What s New in CoMET New in CoMET 5 12 VaST VPM Transformer Toolset Users of COMET 5 12 have the ability to transform a VPM using the VaST VPM Transformer toolset The VaST VPM Transformer is a toolset and methodology which allows users to modify the instruction set of a VaST Seed VPM The VaST VPM Transformer Toolset needs to be purchased and installed before a VPM Transformer project can be started New in CoMET 5 11 Visual C Version 8 Supported CoMET 5 11 supports Visual C Version 8 See Tool Locations Configuration Settings page 31 4 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Installing CoMET This chapter describes how to install
114. er Select Cygwin Gcc In CoMET Configuration Tool Locations tab set Gcc to point to Gcc compiler version gcc egcs 2 91 57 See Tool Locations Configuration Settings page 31 Simulator or Execution Engine Select Fintronic FinSim Click Next The Build Configuration for the VBus FinSim project shows a Build type of FinSimGccApp x Configuration Properties Type FinSimGccApp Mode Debug Path FinSimDebuc ie 164 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Creating SystemC Projects CoMET 4 and SystemC Compatibility Creating SystemC Projects CoMET supports two kinds of SystemC Project You can build a standalone SystemC project using the SystemC project type Alternatively you can build a project of type Fabric type with a Module Class of Peripheral Model SystemC You need to choose SystemC libraries that correspond to the version of C compiler you are using See Choosing the SystemC Libraries for VC 6 VC 7 VC 8 and GCC page 166 Creating a Standalone SystemC Project Choose Workspace Add New Project In the Workspace dialog Project panel select a project type of SystemC See Adding a New Project page 45 Specify a name for the project and select other options as required CoMET creates a set of default files from templates Be System Standalone ome Folders a Source Files
115. er Of Attribute An element that may be defined as an array has a Number Of attribute that defines the dimension of the array The default value for Number Of is 1 Fabric Module X Het Properties Mame M Other etArray Type StdLogic Number OF f B Description Example of declaring net element array using Number OF 68 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Arrays Developing a Fabric Module Definition Referring to Members of an Element Array You need to specify array members when referring to arrays of nets ports or module instance ports You may specify array members for the following elements within an fmx lt file e A Module Instance Port name e A Port Connection Port or Net name e A Port Or Net View name Array notation provides a compact and efficient way to referring to groups of array members When creating a connection between members of an Instance Port array and members of a Port or Net array array notation allows you to name the element to specify e individual array members by index ElementName i e alist of array members comma separated indexes ElementName 1 j k e arange of members start index end index ElementName 1 k e acombination of list and range ElementName 1 k j Port or Net View elements may also refer to members of Port or Net arrays using a
116. ering Environment SEE contains two basic window types tool windows and document windows These two window types behave in slightly different ways You can increase the viewing and editing space for code depending on how you arrange the windows in the SEE Document windows Document windows are dynamically created when you open or create files or other items The list of open document windows appears in the Window menu in the current z order with the top most window listed first You can arrange windows into cascading or tiled stacks Tool windows Tool windows which include the Workspace Output and Modules windows are listed on the View menu Docking Tool Windows You can arrange the Workspace Output and Modules windows to dock against the edges of the SEE or float over the SEE To un dock a tool window click in the title bar of the window and drag it to a new location within the SEE CoMET 5 C YastProjects Simple YSP Simple SP wkx gt File Edit view Workspace Debug Tools Window Help O SHGIXOBIF B SBlQAAQtl se aK 2H BZ OBlH H GA OOSl H0 amp aX Poo oe ee E Workspace Simple SP x H E Simple SP1 E G Folders Sy Source Files E Simple SP1 c os Simple SP 1 Frnx os EY Simple SP1 re Poi f b B ampi_symlink_dll_body c Ports o E ampi_symiiink_init c ft T Nets Oi B Header Files Suaa oo BS ClockNet BY Simple SP1 h ow BS ResetNet E ampi_symlink_names h ba o StdLogicONet Pi B config h 23 Tas
117. ess F1 ini Coli mmf 2 File Edit View Workspace Debug Tools Window Help H oeuse B MNARA AAA RM R MB H a AE Work Space E Workspace Simple SP al el par easily 2 include SimpleVSP1i h EG Source Files 3 include vast_std_types h i BY SimplevsP1 c 4 include ampi_ symlink_dll body h SimpleVSP 1 Frox 2 ABE SMa SimpleVSP1 re fl p Hgo Parameters ampi_symilink_dll_body c 4 Pampisym bas Ports B ampi_symilink_init c ol Be Nets oe B sn a ji iO ttteeaae EX ClockNet ee imple a ResetNet i Ti t oe ampi_symlink_names h 12 ze Intel fan o StdLogicONet 2 ae Tasks oo ae config_types h 14 EE os Module Instances E resource h i H E Generated Files oe rista T a F Bg Configurations ih i 2 anai H Nova2 cDil Debug He is Sem SE z StdBusInstanc Nova2 cDil Release r Instance F H C Includes A fe o EGA Runtime Options sa Hgg Targets B EEA VirtualPlatform HGA Parameter a 23 a i a ga Folders l YastGpDiagno lt q Source Files Instance F VirtualPlatform c virtualPlatform fmx virtualPlatform rc ampi_symlink_dll_body c Workspace E vast Modes a6 For Help press F1 ln 1Col1 Nm 2 Docking on the right hand side of the SEE VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 23 May not be used disclos
118. essing no translation TeakLiteCode maps word addressing to byte addressing multiplies by 2 TeakLiteData maps word addressing to byte addressing multiplies by 2 and sets MSB to 1 WinCE select this option when loading a binary image built by Microsoft Platform Builder for WinCE Specify the Target Image Comparator SREC file if any used for verification There are restrictions on the Comparator File Format See Restrictions on the Target Image Comparator SREC format page 127 This field is optional To alter Target Image properties at a later stage Right click on the target image icon and select Target Image Properties from the context menu Or Double click on the target image icon 126 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Target Executable Fl Folders am Targets H e sieve demo Hr ea ate mines FJ Workspace Restrictions on the Target Image Comparator SREC format The SREC file format used in CoMET is a restricted version of the standard format Workspace El Workspace Simpley SP Ef Simple sP1 Sa Source Files i 4 Header Files H E Generated Files 8 P Configurations ags GA TargetTest aes Top 4rrnredmit wpm trl r WaST Modules z E e VirtualPlatForm Expand Target Image ctrl E Collapse Target Image Cri b Edi
119. et bookmarks at all points where a match is found This allows you to move from match to match by pressing the F2 key Click OK to perform the search CoMET displays the results in the Find Output window Double click a result line in the Find Output window to display the match in the file Note that matches in backup directories may be displayed depending on the Find dialog Location and Search in sub directories property settings 132 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Find in Files Using the Source Editor CoMET 5 C astProjects PDBDemoDevice PDBDemoDevice wkx PDBDemoDevice PDBDemoDevice c File Edit view Workspace Debug Tools Window Help fa X ae EIE Ste Workspace j q x 3 6 d Target E 8 Workspace PDBDemoDevice SEI t Function Sea VirtualPlatform 38 m void PDBDemoDeviceResetDevice tInstanceData IP tBool A we Folders 39 B Source Files 40 P YirtualPlatform c 41 virtualPlatForm Fmx 42 virtualPlatform rc 43 Description ka This function is called to process a device reset tk Parameters ampi_symlink_dll_bod 44 LP ampi_symlink_init c 45 A pointer to the module instance data H E Header Files 46 EnteringReset i virtualPlatform h 47 A flag to indicate whether entering or le
120. eters to enable or disable VCD output The size of the vcd file is unlimited You can indirectly control the size by enabling or disabling sources of VCD output 146 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Building and Simulating in Batch Mode Simulating and Debugging a Model Building and Simulating in Batch Mode CoMET allows you to build and simulate models in batch mode After specifying workspaces and what actions are to be performed upon them in the Batch Mode dialog you can run the batch from the Batch Mode dialog or from the command line You can also run from the command line using a CoMET Batch file to specify options See CoMET Batch File page 150 You can create only one set of batch mode options using the Batch Mode dialog You can save a number of options sets as separate CoMET batch files Specifying Batch Mode Options using the Batch Mode Dialog To specify Batch Mode options Choose Tools Batch Mode The Batch Mode dialog appears It allows you to create a list of Workspaces by browsing for workspace wkx files Batch Mode x Workspace Add Workspace Paths CA Work cometprojects S imple S PS implev S P wks C VastProjects POBDemoDevice POBDemoDevice wks Edit Delete set All Hel Import Esport Aun Save Aun Cancel
121. ety of files in a variety of views For example an XML document such as a fabric module definition file can be displayed in XML Text view XML Tree view and various Table views You can choose the view from the Context menu Open documents are listed in the Window menu Document windows can edit source files fabric module definition fmx files and display dll files and other project files Context Menu Right click to display a context menu with options appropriate to the context in which you clicked For example right click on a document window to view document properties and actions or choose view format from the document context menu Modules Window The Modules Windows lists available modules You can add modules to projects by drag and drop or copy and paste from the Modules Window to a fabric module definition fmx file in a Document Window To refresh the contents of the module window choose Tools Rescan Modules Multiple Versions of Models within CoMET CoMET supports multiple versions of a model to be located in the modules VASTS HOME Modules directory To enable multiple versions of a Model to co exist in the modules directory the CoMET directory structure includes a set of sub directories under each Model type The sub directory under each Model type identifies the Model The sub directories under the Model type directory each contain a different version of the Model with the directory name reflecting the version of the
122. example you can build several versions of the same module for use in different VSPs or use the latest version of the module in all VSPs Project Configuration When you add a new project to the workspace a set of source files arranged in folders configurations and targets are included in the project Workspace PM El Workspace Simple SF HEA Simple sP1 o Folders Ay Source Files 3 Simple SP 1 c Simpley SP1 Fro SimplevSP 1c armpi_symilink_dll_body c l ampi_symlink init c E E Header Files H E Generated Files ce Configurations la Targets ERE virtualPlatform o Folders Sy Source Files _ VirtualPlatFormn c VirtualPlatFormn Priv VirtualPlatForm rc ampi_ symlink dll body c amipi_s rolink_init c H E Header Files H E Generated Files mgr Configurations VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 49 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Adding an Existing Project Adding an Existing Project You can add existing projects to the workspace To add an existing project to the workspace Right mouse click on the workspace icon and select Add Project Workspace iit or E 5 Expand Workspace Ctkrl E Collapse Workspace Ckrl L Edit Workspace X Fz Delete Workspace pel aut workspace EFA Copy Workspace Chrl C Paste Corley Workspace Properties Gtr R or From the Workspa
123. f all Models distributed as part of VaST s library of Models VPM Standard Bus GP Memory etc The Models are placed in a version sub directory under the VASTS HOME Modules Module_Type Module Name Version Number When installing the latest Models and Platform release if you wish to maintain earlier versions of your Models follow the steps described below 1 Backup the VASTS5 HOME Modules directory 2 Follow the installation instructions documented in the Models and Platforms release notes for installing the release 3 Within your Backup location for each Model version you wish to retain create a sub directory which includes the Model name and Model version number For example for v4 5 7 of an ARM926E VPM the path of the newly created sub directory would be as follows VASTS HOME Modules VPM ARM926E v4 5 7 4 Copy the model sub directory as detailed in step 3 above from the backup location to the VASTS HOME Modules Module_Type Module_Name directory For further information on multiple versions of models with in CoMET see Maintaining Multiple Versions of same Model in CoMET 16 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Toolbar Buttons Getting Started Toolbar Buttons The tool bar provides quick access to commonly used commands You click on a button in the tool bar to carry
124. fa oc erlA eporta cAusrvastycomets imlA eports Uninstalling CoMET To uninstall COMET From the Taskbar click the Start button Select Settings Control Panel Select the Add Remove Programs icon Select VaST Release xx xx COMET Click the Remove button 10 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET runs on the Windows XP and Windows 2000 operating systems Note that if CoMET has not been installed correctly the necessary environment variables may not be set to the correct values and you may experience difficulties running CoMET Starting CoMET in Windows XP 2000 To start CoMET in Windows XP 2000 From the Taskbar click on the Start button Select Programs VaST CoMETS SEE or Double click on the desktop icon COMETS SEE VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 11 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started The CoMET System Engineering Environment The CoMET System Engineering Environment CoMET provides a graphical System Engineering Environment SEE in which you can build Virtual System Prototypes for analysis and testing Menu Bar CoMET 5 C astProjects Simple SP Simple SP wkx File Edit view Workspace Debug Tools windo Help
125. ffer to a text file VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 41 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Getting Assistance while You Work Getting Assistance while You Work The Online Help contains extensive information on the COMET System Engineering Environment You can access Help by selecting any of the options from the Help menu or the Help button on the tool bar For information on Help topics From the Help menu select Help Topics or Press Fl CoMET Online Links With Internet access you can get more information about the COMET System Engineering Environment on the World Wide Web CoMET Web Page The VaST home page is located at http www vastsystems com CoMET Support Services For all problems with installing or using CoMET contact VaST by email at support vastsystems com 42 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Each Virtual System Prototype you create consists of one or more modules Modules are defined as projects representing the physical device models within the COMET System Engineering Environment A top level module contains the structure of the Virtual System Prototype Creating a Workspace The workspace contains the projects that define the modules in a Virtual System Pr
126. file is outside the workspace it appears in the exported workspace under the directory Extra under a directory with the same name as the file s original parent directory For example the file c work notes notes txt appears in the exported workspace as extra notes notes txt If an extra folder is outside the workspace it appears in the exported workspace directly under the directory Extra For example the directory c work notes appears in the exported workspace as extra notes Creating the Exported Workspace cab File When the export options are complete click the Export button to export the Workspace CoMET creates a file with the specified path and name and a cab extension To import into METeor choose File Import Workspace and browse for the cab file containing your exported workspace 60 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Moving a workspace from one directory to another Managing Workspaces and Projects Moving a workspace from one directory to another When you move a workspace from one directory to another you may need to reestablish the paths of files within the project depending on the original location of the files The CoMET workspace wkx file records paths of the project pjx files belonging to the workspace The Project pjx file records the path of component files and director
127. g a Fabric Module Definition Module Instances Module Instances A Fabric Module of the Virtual System Prototype or Virtual Platform class may contain a single Module Instances element This element is a container for all Module Instance elements Child Elements The Module Instances element may contain one or more Module Instance elements Parameter Override elements also appear in the Virtual System Prototype VSP Configuration pcx file defined for the VSP The Prototype Configuration file contains Module Instances and their Parameter Override elements for every Module Instance within the VSP hierarchy Module Instance Module Instances Module Instance You can instantiate a module any number of times either by creating multiple instances each with separate Module Instance Names or by creating a Module Instance specified as an array There are several ways to add Module Instances You can use the Module Instances context menu option or use the Modules Window to add modules using drag and drop or cut and paste Module Instance elements also appear in the Virtual System Prototype VSP Configuration pcx file defined for the VSP The Prototype Configuration file contains Module Instances and their Parameter Override elements for every Module Instance within the VSP hierarchy See Parameter Override page 89 Fabric Module q x Module Instance Properties Instance Mame New Modulelnstance Type Require
128. ge Size tWord32 1 M Specities the Page Size in Bytes if an ane gt 1 Otherwise Ignored Timing FirstRead BusClock tick delay on Data Phase inserted for first read of Memory Width data of a burst First Write twords2 1 BusClack tick delay on Data Phase inserted for first write of Mernory Width data of a burst InittalRead tWords2 0 BusClack tick delay on Data Phase inserted on initiating first read burst to memory Initial Write tWord32 0 BusClock tick delay on Data Phase inserted an initiating first write burst to memory NextRead twWords2 1 BusClack tick delay on Data Phase inserted for each read of Memory Width data of a burst Next Write tWord32 1 BusClock tick delay on Data Phase inserted for each write of Mernory Width data of a Burst Where applicable Module Instance detail entries show a table of parameter overrides VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 107 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options A project build configuration specifies details of how the project is to be built such as include paths assembler compiler and linker options and runtime options For each new project COMET automatically assigns two types of build configuration a debug configuration and a release configuration You can modify each build configuration using different characteristics and build and test the mo
129. haracteristics of the module and how the module interconnects with other modules within the Virtual System Prototype Module structure and properties are defined in the Fabric Module definition fmx file for the module By editing the fmx file you can add ports nets module instances tasks parameters and other properties to the module Opening the Fabric Module Definition file To open the Fabric Module Definition file Select the module from the Fabric File button VirtualPlatFornn fmz Open Fabric File Simple inner Fro of Simple ySP 1 Ffm x or Expand the module node in the workspace window and navigate to the fabric module definition file lt module name gt fmx VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 63 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Opening the Fabric Module Definition file xi Workspace SimpleySP rele VirtualPlatForm i El SimpleTimer A EM Simple SP1 E Folders 5 rna Source Files Simplex SP 1c Simplex SF 1 fmx Simplex SP1 rc ampi_syrolink_dll_ body c armipi_s rolink_inik c H 1 Header Files Generated Files A gr Configurations E Sa Nova cDll Debug E AD MovazvcOl Release ee he Targets H Target Test H E sieve een akg Timer Test Workspace g YaST Modules Double click on the Fabric Module Definition file fmx
130. he right of the Workspace button to display the VaST Modules and User Modules windows Log Button The Log button allows you to view open and switch between the output windows To open or switch between the output windows Click on the Log button to open the Log output window To open the other output windows click the down arrow next to Log button Build Software K Loaded Modules Targets Select the output window you wish to open or switch to from the drop down menu The following screen shot shows all the output windows arranged as separate tabs Build O FrocessFabricModules processed Std Bus in c usrivast i comets a FrocessFabricModules processed VastGpStdLogicO in C VastPr FrocessFabricModules processed VastGpStdLogicl in C VastPr ProcessFabricModules processed VastGpReset in C VastProjec Build completed successfully 4 18 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Doing the Tutorials Getting Started Target Button If the Target window is not visible on the COMET SEE click the Target button on the Tool Bar to display the Target window The following screen shot shows the Target window Target System Elapsed Time St 1200 Simulation Time Consumed Time Instructions Doing the Tutorials The tutorials provide a step by step introduction to developing
131. ic Port The list of valid Fabric port types that may be mapped to the various Verilog port types is shown in the table below Verilog Port Type Fabric Port Type Default Other Valid User Selectable Types Logic scaler StdLogic StdVector32 StdClock Logic vector StdLogic array StdVector32 StdClock e Selecting StdClock for inout port is not allowed e Ifa StdClock is selected for a Verilog input port a clock signal for the Verilog port having the same clock period as the input StdClock will be generated e Ifa StdClock is selected for a Verilog output port the clock period of the Verilog signal will be evaluated continuously and outputted to the StdClock output port e If StdVector32 is selected for a Verilog output port then the corresponding bits of the Verilog signal are mapped as follows 180 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Verilog Co Simulation Support ModelSim HDL Co Simulation Support Std Vector32 Bit e If StdLogic is selected for a Verilog output port then the Verilog states are mapped to the StdLogic states as follows riz Slog Smid StaLogiek Smi StdLogieht sax Satogew StdLogicL VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 181 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Sim
132. ies such as includes or libraries Workspaces are represented on disk as directory trees The wkx and pjx files record all paths as relative except for paths residing in the COMET home directory determined by the environment variable SVAST5 HOMES These are recorded as absolute with oVASTS HOME as root If you move the workspace directory the project file paths remain valid for project files residing under the workspace directory Similarly the project component paths remain valid for components residing under the workspace root directory Paths to files or directories residing in the 3VAST5 HOME are automatically reestablished after moving a workspace to another directory However if a wkx file or pjx file refers to a file or directory outside both the workspace directory and the sVAST5 HOMES directory the file path becomes invalid if you move the workspace directory In this case you must reestablish the file path manually To reestablish project and component file paths open the project in the COMET Workspace Window for each project component browse to find the correct path Alternatively Edit the workspace wkx and project pjx files directly in a text or xml editor VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 61 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition The module structure defines the c
133. ies from the context menu VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 167 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 4 and SystemC Compatibility Creating SystemC Projects 168 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support Introduction to ModelSim HDL Co Simulation Support There are many RTL device models written in Verilog and VHDL and run on HDL simulators such as the Mentor Graphics ModelSim The ModelSim HDL Co Simulation support provides an easy way for existing RTL models written in Verilog or VHDL to run with CIF without the laborious task of rewriting and converting the models completely as CIF devices This allows you to co simulate your existing HDL device models with CIF with no or only minor modifications to the models VHDL Co Simulation Support Features and requirements ModelSim SE 6 0 or higher is required Pure VHDL models as well as VHDL with Verilog instances are supported ModelSim Foreign Language Interface FLI with C models is supported A signal level interface to the CIF AHB bus protocol 1s provided to interface VHDL AHB device models to the VaST AHB StdBus Debugging VHDL source is supported through the ModelSim graphic interface For VHDL array port types the element with the smallest
134. iew of automatically generated Verilog fmx file When the Verilog Model is successfully complied a module instance of the model can be added to a CIF platform E By SimplevsPi Es Parameters ive Ports ve n boson a ClockNet l at a ResetMet i a Tasks Ei Module Instances See eal YerilogModuleInstance sj The Instance Ports Sa as Parameter Overrides VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 187 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support Verilog Co Simulation Support Selecting a Fabric Port Type for a Verilog Port Note This can only be done after the Verilog source files have been successfully complied and the fmx file has been successfully updated with the list of ports in the Verilog entity To select a particular Fabric Port Type for a Verilog Port e Double click on the Generated Files ProjectName fmx file This will open the generated fmx file document window 2 Test erilogModel Test erilogModel fm ol x Test erilogModel Ge Parameters A H Ports Baan Reset Sige Tasks Flea TestVerilagModelT ask e Double click on the port for which you want to set the Fabric Port Type Fabric Module i Xx Fort Properties Name Reset Type StdLogic GtdLa gic Number OF StdClock Std us Direction CanBus Std ectordz Elaes Connect Sub Class Descr
135. ifferent location etc Note that if you subsequently change the name of the project then this will change the text after the last directory separator to that of the specified project name C Compiler The C Compiler used to build the source code files Simulator or Execution Engine This selects the mode of simulation to be used for the module Vast Nova 2 Default Select this for a CIF model It 1s simulated with the Nova 2 Scheduler Mentor Graphics ModelSim Select this to co simulate your HDL device model with CIF using the ModelSim HDL simulator See ModelSim HDL Co Simulation Support page 169 Vast Nova Select this for a COMET 4 VBus model The model is built with a CIF wrapper allowing it to be instantiated in a CIF platform It is co simulated with the Nova Execution Engine and the Nova 2 Scheduler No Cygwin DII Check Box The No Cygwin DII check box is selectable for Gcc projects Check this box to automatically convert any Gcc project to use the no cygwin DII option See Runtime Options Auto convert Gcc projects to No Cygwin DII page 28 46 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Adding a New Project Managing Workspaces and Projects Defining a Fabric Module If you select a Fabric project you must define the module class and the type of module Project TopModule x Fabric Module
136. ind In Files Ctrl Shift F Ctrl F W Find Next F3 Replace Ckrl H A Toggle Bookmark Ctrl F2 Syntax Colouring 0 To Line Chrl i VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 131 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Using the Source Editor Find in Files Find in Files This feature assists in finding function names or other specified strings in source code Choose Edit Find in Files to locate specified text in files under a specified directory xl search String tInstanceD ata File Types oo cpp crr cc h bpp w vbdl Location C WWastProjects PDEDemoDevice MW Search in sub directories iY Open files OF W Case sensitive I Set bookmarks Cancel W Match whole word Find In Files dialog Search String Type the string for which you wish to search File Types Specify patterns for file types you wish to search for the string Location Specify the top level directory from which you wish to start searching Search in sub directories Check to search recursively through subdirectories of the Location directory Case sensitive Uncheck to ignore case in matching the search string to text in files Match whole word Check to match only instances of the string with word delimiters on either side Open files Check to open in the Document window all files in which a match is found Set bookmarks Check to s
137. index of the VHDL array port maps to index 0 of the corresponding CIF port and the highest index of the VHDL array port maps to the highest index of the corresponding CIF port Only VHDL port types of std logic std ulogic bit std logic vector array of std logics std ulogic vector array of std _ulogics bit vector array of bits integer signed unsigned and array of integers can be used to interface with CIF VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 169 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support VHDL Co Simulation Support Mappings between VHDL and Fabric Port The list of valid Fabric port types that may be mapped to the various VHDL port types is shown in the table below VDHL Port Type Fabric Port Type Default Other Valid User Selectable Types StdLogic StdVector32 StdClock StdLogic StdVector32 StdClock std ulogic StdLogic StdVector32 StdClock StdVector32 StdClock StdVector32 StdClock StdVector32 StdClock meray SuVszamy Notes e The mapping between VHDL std logic type and Fabric StdLogic type is shown below OO U Sog O x sio S O wY StdLogicZ StdLogicW lt a a z aE T E StdLogicH S StdLogicUnkown e Overriding the default StdVector32 type and selecting StdLogic for integer VHDL ports or selecting StdClock for inout port is not allowed e Ifa StdClock is selecte
138. ing 3 fl p4 FrxPrivate_PexPublic 46 a P _FroxPrivate_PcxProtected 1 FmxDemoPlatform fmx displays only parameters with Fmx Access set to Public or Protected FmxVSPDemo pcx file displays only parameters with Pcx Access set to Public or Protected The final values for the FmxDemol Instance Parameters are e Pl FmxPrivate PcxPrivate 23 e P2 FmxProtected PcxPublic 35 e P3 FmxPublic PcxPublic Test string 3 e P4 FmxPrivate PcxPublic 46 e P5 FmxPublic PcxPrivate 57 e P6 FmxPrivate PcxProtected 1 For more on the Prototype Configuration pcx file see Modifying Parameter Values in the Prototype Configuration File page 121 90 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Parameter Override Developing a Fabric Module Definition The Pcx Access Field is Always Editable in a Parameter Override A module designer may set Fmx Access to Protected for a module Parameter A platform designer may create a module instance of the module To permit the platform designer to control access to the corresponding module instance Parameter Override the Pcx Access field of the corresponding Parameter Override is editable even though the Parameter has Fmx Access set to Protected Fabric Module Parameter Override Properties Hame EusProtoco Type Altice Value StdB us T Pox Access Public z
139. inks parameter to Fmx Reports The Parent Connections entry links to the Fx Report of the parent module instance which contains the connections for its child module instances The Module type Parameter Overrides entry links to the Fmx Report for the module instance s corresponding module type B Name Type Value Description Pr operties BurstReadBeatLimit tWord32 0 Maximum beats in a read burst Each beat Memory Width of bytes If 0 then no burst limit xml Version Description BurstWriteBeatLimit tword32 0 Maximum beats in a write burst Each beat 1 ai Memory Width of bytes If O then no burst limit Enable PowerOnDecode tBoolean 1 Setting this Parameter to TRUE will allow this Memory Model to have its Decode available at Power On to Structure facilitate Loading by VPM Memory Size tWord32 8 M Total Size in Bytes of the memory being attached to L inet N ModuleT t the Bus via this memory controller eegend instanceName Mogule lype Vescription g Memory Width tWord32 4 Width of the memory being attached to the Bus via this memory controller e Top SimpleVSP1 Profiling tAltList Disabled VastGpClock1 VastGpClock VastGpReset VastGpReset StartAddress tword 4 0 Base Address of the memory being attached to the bus via this memory controller VirtualPlatform1 V
140. int During debugging the execution halts at the statement containing the breakpoint before it is executed To clear a breakpoint In the C source file click on the line of code that has the breakpoint you wish to clear From the Debug menu select Stop At Or Click on the Toggle breakpoint tool bar button or Press the F9 key To clear all the breakpoints From the Debug menu select Remove All Breakpoints Or Click on the Remove All Breakpoints tool bar button or Press the CTRL SHFT F9 keys 142 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Interrupting the Execution Flow Simulating and Debugging a Model Managing Breakpoints You can add breakpoints at any statement within the source code of a module To see a concise list of breakpoints in the Breakpoints dialog box From the Debug menu select Breakpoints Breakpoints xX TopModule c de TopModule c 3 Breakpoints Dialog To jump to the location of a breakpoint From the Breakpoints list box select the breakpoint Click on the OK button You can also instruct the debugger to ignore all breakpoints without removing them from the breakpoint list you can enable or disable all breakpoints as required Continuing Execution Once execution has halted at a breakpoint you can select one of three step modes to continue ex
141. ion at every level of design CoMET supports the specification and timing accurate modeling of electronic hardware buses and networks Using a VSP you can develop and run software applications operating systems middleware and drivers and test telecommunications protocols and DSP algorithms prior to hardware availability CoMET allows you to quantitatively experiment early in the engineering process with hardware software partitioning choice of processors and co processors and configuration and operating system options You can use COMET to evaluate trade offs in design such as cache sizing clock speed and processor type throughout the design process without sacrificing timing or accuracy You can test more of the software before realization and experiment with various processor combinations performing what if analyses to determine optimal designs With CoMET you can move the boundary between hardware and software and view and control the interaction between hardware and software interactively even in highly VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 1 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Introduction About This Manual concurrent designs having several different processors and considerable application specific hardware CoMET is ideally suited for complex system on chip SOC designs including multi processor systems It simula
142. iption Module port Reset Cancel Apply Help Es 188 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Verilog Co Simulation Support ModelSim HDL Co Simulation Support e Select the Fabric Port Type from the Type pull down menu Refer to Features and requirements page 180 for a list of valid Fabric Port types which can be selected for particular Verilog port types e Click OK to accept the selection Setting the Runtime Options The build configuration of the top module supports a set of runtime options Runtime Option properties vary for different build configuration types See Build Configuration Types page 110 Adding Runtime Option Properties To gain access to view and change Runtime Options you need to create a Runtime Options node in the Workspace window under the Configuration node CoMET creates a Runtime Options node automatically only for top level Fabric projects and VBus projects You can manually add a Runtime Options node To add runtime options e Right click on the appropriate build Configuration node e Choose Add Runtime Options from the context menu Workspace K Elem TestYerilogModel E E Folders agr Configurations H C Includes Expand Configuration ctrl E l E Verilog Includes Collapse Configuration Ctri b See ModelSinvcDll Relea E E C Includes E E Verilog Includes ial YaST M
143. ironment starts without a workspace If you select this option your last workspace is automatically loaded when the COMET System Engineering Environment starts XML documents open in tree view by default Determines whether XML configuration files are displayed as a tree view or in XML source Be MyProject fmx Ioj x O x lt uml version 1 0 7 gt E lt I DOCTYPE FabricModule 5 i MyProject Ge Parameters i Ports Mets Le Tasks ih Module Instances FabricHodule ModuleType Version 1 0 0 InitFunction Hy Pr FxitFunction MyProa Description MyProj Timestamp Af Interfaces Su Vere oe 91 as lt Parameters gt Ports gt XML in Tree View XML in Source View DTD Locations These options are required for users collaborating on development using a source file repository The Document Type Definitions that appear in the various XML files e g fmx pcx must refer to an absolute file location If these file locations differ from user to user there will be an XML source file conflict in the repository These options provide a mechanism by which all users can refer to the same absolute file location avoiding conflict Vast Home If all users agree to install COMET in the same local directory then the file locations agree and the default Vast Home setting choice is appropriate Substitute Local Drive Otherwise users can agree to map the DTD location to the same virtual drive by
144. irtualPlatform The VSP contains a single instance ofthe i F a UseEnable Input i i i VirtualPlatform which in turn contains all other Module Instances inate tor tBoolsanio Enae Poe ce e ee a ARM926EJS1 ARM926EJS EAE a GenericMemory1 0 GenericMemory This is an array of module ot it instances with the size ofthe array determined by the NoOfMemory Pages twWord32 i Specifies the number of Memory Pages within the GP NumberOffiemoryBlocks parameter r akete GenericMemory1 1 GenericMemory This is an array of module PageSize twWord32 i M Specifies the Page Size in Bytes if NoOfMemoryPages instances with the size of the array determined by the gt t Otherwise Ignored NumberOfMemoryBlocks parameter Timing a GenericMemory1 2 GenericMemory This is an array of module FirstRead twWord32 1 BusClock tick delay on Data Phase inserted for first instances with the size ofthe array determined by the read of MemoryWidth data of a burst NumberOfMemoryBlocks parameter First Write twWord32 1 BusClock tick delay on Data Phase inserted for first a StdBus1 StdBus write of Memory Width data of a burst a YastGpStdLogicO1 VastGpStdLogicO InitialRead twWord32 0 BusClock tick delay on Data Phase inserted on initiating first read burst to memory Initial Write tWord32 0 BusClock tick delay on Data Phase inserted on Module Instance Parameter Overrides Detail a is auiio His eta E AnaM 2 NextRead tword32 1 BusClock tick delay on Data Phase inserted f
145. ise Ignored Timing FirstRead tWord32 p BusClock tick delay on Data Phase inserted for first read of Memory Width data of a burst First Write tword32 p BusClock tick delay on Data Phase inserted for first write of Mernory Width data of a burst InitialRead twWord32 a BusClock tick delay on Data Phase inserted on initiating first read burst to memory Initial Write tWord32 E BusClock tick delay on Data Phase inserted on initiating first write burst to memory NextRead tw ordaz p BusClock tick delay on Data Phase inserted for each read of Memory Width data of a burst Next Write tWord32 p BusClock tick delay on Data Phase inserted for each write of Mermory Width data of a burst The module Ports and module Nets summaries show ports properties the number of connections and the port or net view types If the connection count is zero it is highlighted In some cases a zero connection count may indicate an error i Ports Name Type NumberGf Descnpton Connections Port or Net View Types Bus E StdBus Module port Bus E NetSlave BusClock jam Std Clack Module port Bus clock E NetSlave Reset r StdLogic Module port Reset E NetSlave Click on the connections column entry to move to the connections list in the related Port or Net detail entry Click on a link in the Port or Net View Types column to move to the related Task detail VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 103 May not be used disclosed or reproduced e
146. ism to accommodate changes to module definitions See Pcx Update 122 Child Elements Some elements may contain child elements For example a SubParameters element may contain one or more Parameters and one or more SubParameters elements In the element descriptions below where an element may have child elements the child elements are listed The top Fabric Module element is created with some automatically generated child elements Depending on the project class these may include Parameters Ports Nets Tasks Module Instances Interfaces Creating a Child Element To create a child element Open the Fabric Module Definition fmx in the Document window XML Tree View Right click on the node corresponding to the parent element From the context menu choose the Add action for the child element you wish to create For example to create a Port right click on the Ports element and choose Add Port from the context menu The dialog for the Fabric Module Ports Port element appears 72 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Child Elements Developing a Fabric Module Definition An Add action is available on the context menu only if the element prerequisites exist 2 Simple SP Simple SP 1 Simple SPas E simpleySP1 Hoe Parameters a nB pP Expand Ports Ctrl E te Mets C
147. ivate Project Ctri 4 Project Properties Ctrl R VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 51 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Viewing the Properties of a Project Viewing the Properties of a Project To view the properties of a project Double click on the project icon Or Right mouse click on the project icon and select Project Properties 52 VaSTI SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Active Project Managing Workspaces and Projects Setting the Active Project A CoMET workspace may contain several projects When you build the workspace and execute the Virtual System Prototype the active project is built and executed To set the active project Double click on the project icon S Project S x Froject Properties Path C vastProjects Simplevs Pav irtualPlathorm ie Type Fabric Active False X True Cancel Apply Help Es Set the Active field to True and click the OK button or Right click the project in the Workspace Window and choose Active Project from the context menu x E Workspace Simplex SP Eel Simple sP1 Se virtualPlatform A Folders Expand Project Ctr E EMS Source Collapse Project Ctri L
148. ks Default 1000 May be increased for large projects VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 179 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support Verilog Co Simulation Support Verilog Co Simulation Support Features and requirements e ModelSim SE 6 0 or higher is required e Pure Verilog models as well as Verilog with VHDL instances are supported e ModelSim Procedural Language Interface PLI with C models is supported e A signal level interface to the CIF AHB bus protocol is provided to interface Verilog AHB device models to the VaST AHB StdBus e Debugging Verilog source is supported through the ModelSim graphic interface e Due to the limitation of the PLI implemented in the current version of ModelSim Verilog bidirectional inout port types are not currently supported e For Verilog vector port types the element with the smallest index maps to index 0 of the corresponding Fabric port and the highest index of a Verilog vector port maps to the highest index of the corresponding Fabric port e Array index that is a negative number or an expression evaluating to a negative number in a vector port declaration of a top Verilog module port is currently not supported Only the and mod arithmetic operators are supported in expression used as array index of a vector port declaration Mappings between Verilog and Fabr
149. ks oO Interfaces 0 H Errors and Instances 4 Warnings Summary Properties ersion InitFuncton ExitFunction Descnpton Timestamp 1 0 0 VWirtualPlatformiInitModuleInstance VirtualPlathormExitModuleInstance VirtualPlatfarm Fabric Module KERR Ge Parameters Name Type value Allowable Values Description NumberOfMemory Blocks tWord32 3 Determines the size of the array af GenericMemoryl module instances B Ports Hame Type NumberOf Description Connectons Port or Net View Types Loose Port T a StdLogic Platform Clock This connects all module instances within 2 Std Clack WirtualPlatform to the WSP clock PlattormReset This connects all module instances within 1 StdLoagic WirtualPlatform to the VSP reset Module Instances Instance Name ModuleType Required Yersion NumberOf Description YastGpStdLogicO i VastGpStdLogicO GenencMemory 1 GenericMemory NurmberOfMernoaryBlacks This is an array of module instances with the size of the array determined by the NuormberofMemoryBlacks parameter ARMS26E751 ARM S26EI5 stdBus 1 StdBus The Fabric Module Definition report displays a menu allowing you to browse to Properties Parameters Ports Module Instances Nets Tasks and Interfaces The Summary section contains concise tables of the various items You can use links in the tables to drill down to a detailed view of each item ModuleInstance ModuleType column entries link
150. lSim C Program Files Modeltech 6 0c Mavic C Program Files Microsott Visual Studio NET 20034 Y c PlathorrS dk C Program Files Microsoft Visual Studio NET 20034Y c Plattorm SyshemL cusrvastycomets S ystemnl WOOQE fac Edit Clear Cancel Apply VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 183 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support Verilog Co Simulation Support Creating a Verilog Model Project Choose Workspace Add New Project Workspace Simple SP i l xX Froject Project Name Testv erilogM odel Location Ic Work cometprojects T est entoghodel E C Compiler ms Visual C F Simulator or Execution Engine Application f Library DLL F No Cygwin Dil Back Cancel Project Select the Fabric project type Project Name Specify name of the Verilog Project Location Specify desired location for project files C Compiler Select MS Visual C Simulator or Execution Engine Select Mentor Graphics ModelSim Click Next 184 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Verilog Co Simulation Support ModelSim HDL Co Simulation Support Project Test erilogModel x Fabric Module Module Class Fenpheral Model Verilog
151. line cancel Apo _ Editor Options Configuration Tab Item You can set the colors used by the text editor for various fields such as comments and numbers Click on the item and select the color s from the Foreground Background color drop lists Insert spaces for tabs When you press the lt tab gt key four lt space gt characters will be inserted not a lt tab gt character Auto indent When you press the lt enter gt key the indent of the new line will match the indent of the current line Print line numbers Line numbers will be printed when you print a file VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 29 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Configuring the CoMET System Engineering Environment Display line numbers Edit windows will display line numbers on the left of the frame Track end of line Prevents the cursor from continuing past the end of a line For example when you move a cursor that is at the end of a long line to the following shorter line by using the down arrow button the cursor will go the end of the line instead of staying in the same column Margin Selecting Fixed margin displays a gray margin on the left hand edge of code windows The margin displays symbols indicating bookmarks and breakpoints If you select No margin then highlighting of the line of code indicates bookmarks and breakpoin
152. me Options Fabric Project Runtime Options x Runtime Options Properties Config File Demo pes im Metrix Config File Demo mcs eI Executable File Jc vast8_home Ampi2 Bin sys_loader exe Bi Task Stack Size ak Max Tasks f og Cancel Apply Help we Config File The Prototype Configuration file for the project See Modifying Parameter Values in the Prototype Configuration File page 121 Metrix Config File The path of the associated Metrix Configuration mcx file See the Metrix Configuration File User Guide Executable File This specifies the file that calls the Fabric dll Task Stack Size Default 32K May be increased for large projects Max Tasks Default 1000 May be increased for large projects VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 119 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Runtime Options VBus Module Runtime Options Properties Project x Runtime Options Properties Design Name test Simulator Options is pil fiado s S Config File mconiactg a ti lt t i s dC d k Cancel Apply Help Design Name Verilog design name Simulator Options These options are passed to the hardware simulator See Supported simulation engines page 120 Oil Optimum Interrupt Latency This setting controls the maximum time difference allowed during the sim
153. me for the Task For more on Tasks see the CoMET Modeling Guide CIF Init Function Type a name or leave blank to allow CoMET to assign default TaskNameInitTaskInstance Click the button beside the function to view the source definition of the function Exit Function Type a name or leave blank to allow CoMET to assign default TaskNameExitTaskInstance Click the button beside the function to view the source definition of the function Task Function Type a name or leave blank to allow CoMET to assign default TaskNameTaskFunction Click the button beside the function view the source definition of the function Description You may add a description for documentation purposes Child Elements A Task can contain a single Port Or Net Views element 82 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Port Or Net Views Developing a Fabric Module Definition Port Or Net Views Task Port Or Net Views A Task may contain a single Port Or Net Views element This element is a container for all Port Or Net View elements belonging to the Task Child Elements The Port Or Net Views element may contain one or more Port Or Net View elements Port Or Net View Task Port Or Net Views Port Or Net View A Port Or Net View specifies the task access to the Port or Net Fabric Module x Port Or Met wiew Properties Mame
154. n Properties or Double click on the configuration icon CoMET displays the Project dialog Build Configuration tab with attributes appropriate to the Build Configuration type Build Configuration Types The build configuration type depends on e Simulator Nova2 Nova CIF or Nova or other e Compiler Vc Visual C or Gcc e Type of output executable App application or DIl Dynamic Linking Library The build configuration type name is created by concatenating these specifiers e g Nova2VcD11 Common Build Configuration Properties All projects have the following fields in common Type Build Configuration Type See Build Configuration Types page 110 Mode Debug or Release Path The destination folder for the output files 110 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Build Configuration Configuring Build and Runtime Options NOTE Ifyou create a Build Configuration using the same Path as used for a previous Build Configuration you must choose the Rebuild All option on the next build to ensure that all output files are replaced with newly built files C Options C compiler command line options Link Options Linker command line options Define File Certain project definitions Active Active status True or False the Build command builds the project using the Build Configuration with Active a
155. n agreement with VaST Developing a Fabric Module Definition Tasks Tasks A Fabric Module element may contain a single Tasks element This element is a container for all Task elements Child Elements The Tasks element may contain one or more Task elements Task Tasks Task You can model behavior with tasks or callback functions Callbacks run in response to events Tasks are initialized and run after module initialization Details of callbacks and tasks are discussed in The CoMET Modeling Guide CIF When you create a top level VSP module typically you do not have to add tasks When you create a module of type Peripheral Module some default tasks are created in the fmx file and the skeleton module code projectName c file If you want to add an additional task to a peripheral module you need both to declare it in the module fmx and to create the task code Declaring the task in the fmx file notifies the simulator of the existence of the task You do not need to specify a name for the Init Function Exit Function or Task Function attributes COMET assigns a default name for these default functions as indicated below The name must match the name in the source code for the module If the named task functions do not appear in the module source code CoMET displays errors on Build Fabric Module a x Task Properties Hame Init Function Exit Function ey Taek Function el Description Name Type a na
156. n debugging does not affect the accuracy of the simulation However if a change to the register value normally results in a model behavior response this does not take place until simulation advances The choice depends on the modeler s requirements 154 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Hot Keys Many hot keys are documented in the COMET menus next to the associated function and in the tool tips that pop up when you hover over a tool bar button This section gathers the information on hot keys and special mouse clicks under functional headings Many keys operate according to the Windows conventions Hot Keys All Windows Shift F7 i View CoMET Configuration dialog o O Hot Keys All Windows Files Ctrl O Open file Ctrl F4 Close top file in Document Window VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 155 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Hot Keys Hot Keys Workspace Window Hot Keys All Windows Editing e o o w o e S C S CAA S L Hot Keys Viewing CoMET Windows wm O O eme OOOO o o cny C A Ca Fae er Window ty ems PPTs Win oy Hot Keys Workspace Window Item selected in workspace tree Opens the selected item Double Click Double click on item in workspace tree Opens the selec
157. n to add the file to the project VasST SYSTEMS TECHNOLOGY Confidential and Proprietary 55 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Configuring a Project Viewing Project Component Properties To view project component properties Right mouse click on the project component and from the context menu select the corresponding Properties choice e g Folder Properties Properties of Special Components Projects Configurations RunTime Options and other components have a number of properties These are displayed for viewing and editing in a Properties dialog Viewing the File Path Property File components have a single property the path of the file COMET displays the path property for viewing and editing in a browser window rather than a properties dialog Disabled Properties Some components such as the Folders Folder do not permit viewing and editing of properties so the Properties context menu item is disabled Project x Froject Properties Path C Awork cometprojects Pdbb emolevice Pdb ie Type Fabric Active False bd Cancel Apply Help ws Workspace element properties dialog example Project properties 56 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Saving Workspace Files Managi
158. nanccoernscesenuesansuapedersannancdostusidannseunideiurusrertecess 150 Batch Mode Options cccccccccccccececeeeeceeeeeeeeeeeeeeeeceeceeseeeeeceeseessseeeaeeeeeaaasaaas 150 Non Batch Mode OptionS enenenssssssssesessssssesssesrerereeerrerrrrrrrrrrrrrrrrrrrrrerren 150 COMET DICT Io a E E TEE 150 Command line batch mode using a CoMET 4 batch file ceeeeeeees 151 Running External Tools during Simulation ccccsceeeeesesesssssssssssssseseeseseeeees 152 Target Debugging Considerations cc scsseessessseseessssssssssssssssssssssssssseeeeeeeeeees 154 Hol Eoy Saa E E A RE 155 Hot Keys All W 1nd OWS siscsoosciscsocnsdedessivavecsnantdnenecendecnsastbasndesatecndantaeansnsadeansentaarasads 155 Hot Keys All Windows Files iaiesssccessnssadaiuiesnceanaesncaswensxananeneneseoussneasastesssearsenars 155 Hot Keys All Windows Editing ccccccccccccccccccceceeeeseeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeaes 156 Hot Keys Viewing COMET Window ccccccccssseccceeeeeeceeeeeeeeececeeeeeeeeeeeeeees 156 Hot Keys Workspace Window cccccceessesesseeseeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 156 Hot Keys Document WindoW nneeeeenrerrrrrrrerrrrrsrrrrrrrrrrrrrrrrrrrrrrrrrrerrrrrrrrrrrn 156 Hot Keys Document Window Source Code Navigation and Bookmarks 157 Hot Keys Building Projects cccccccccessesseeeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 157
159. nceData AmpiTaskGetModuleInstance C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 213 tInstanceData IP C VastProjects PDBDemoDevice PDBDemoDevice PDBDemoDevice c 217 IP tInstanceData Se eee ee eae 4 b For Help press F1 3 Find In Files in 52 Col 1 jin eet ieee VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 133 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Using the Source Editor Locating Symbols with the Browse Database Locating Symbols with the Browse Database CoMET provides browse features to assist in navigating code The browse feature requires the browser database which is built during a successful build of your model in Debug configuration In the course of building the model the output message appears COMET is building the browser database Goto Definition After the build completes you can select an identifier in the code right click and select Goto Definition from the context menu COMET opens the file containing the definition of the identifier EF PDBDemoDevice PDBDemoDevice c Parameters IF A pointer to the modale instance data EnteringRkeset A flag to indicate whether entering or leaving a reset state Returns tt Nothing F Miwoid PPBPemobeviceResetDevice tinstanceData IP tBoolean Enteringkesethl i f PDRBResetDeyvicesStart 7 Browse Symbal be f DO NOT ADD CODE TO THIS SECTION
160. nd Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Creating SystemC Projects CoMET 4 and SystemC Compatibility If you are using VC 7 VC 8 or GCC net you need to choose a different set of libraries Libraries are found in the svast5 home SystemC directory The libraries are as follows the d in the library name denotes a Debug version Visual C v6 systemcd lib Visual C v7 systeme vc7 lib Visual C v7 systemcd_ve7 lib Visual C v8 systemc_vc8 lib Visual C v8 systemcd_ vc8 lib The libraries are specified within the Active Configuration This is the highlighted configuration under the Configurations node in the Workspace Project tree For example in the screen picture below the active configuration is SystemC VcDIl Debug To change a library double click the library file in the SystemC project Active Configuration C Libraries list Browse and select the required library ag Configurations E ga SystemCYcDll Debug A C Includes Sq CiastS_homelSystemChinclude EMS C Libraries BaS stencd lib Baen system lib oe a Runtime Options To add a library right click the SystemC project Active Configuration C Libraries node and choose Add Library from the context menu Browse and select the required library If there is no C Libraries node you need to add it Right click the Active Configuration node and choose Add Librar
161. nd Reports Connection Views A connection view shows module instance port or net connections filtered on the type of port or net For each Module Instance there is a row in the table identified by the InstanceName in the first column on the left The second column shows the ModuleType The remaining table columns represent the module ports and nets Ports are followed bya port type suffix Nets are followed by a net type suffix An entry in a cell shows a connection between a port belonging to the row module instance and the column net or port NOTE a connection view can show only one connection where multiple ports from the same device connect to the same net or port a single instance port is connected to multiple nets or ports The possible net and port types are e StdBus e StdClock e StdLogic e StVector32 The default connection views show both nets and ports filtered on each of the types e Bus Connection View StdBus e Clock Connection View StdClock e Logic Connection View StdLogic You can configure connection views according to your requirements See XML Tables Configuration Settings page33 To edit connections in connection view click in the cell at the intersection of the required module instance row and the required net or port column CoMET displays a list of available ports Select the port to connect the selected module instance port to the selected net or port Be virtualPlatform irtualPlatf
162. ndow Windows and buttons Windows F style WF Color scheme Default Blue ade Font size Norma rarang 20 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Windows XP Theme Display Issue Getting Started On the Advanced Appearance dialog box select 3D Objects from the Item drop down list From the Color 1 drop down list select a darker color than one that is already selected Advanced Appearance Inactive Window l Active Window Mormal Disabled Selecked Window Text Message Box Message Text OK TF you select a windows and buttons setting other than Windows Classic it will override the Following settings except in some older programs Item Size Color 1 olor 2 3D Objects kod Font Ce E The following diagram shows a selected tab Workspace tab and an unselected tab VaST Modules with a darker color selected for the unselected tab Workspace E Workspace Simplev SF SE Simple sSP1 a gt Folders Sy Source Files H E Header Files ff Generated Files Configurations gp Workspace a YaST Modules ie VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 21 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Arranging Windows Arranging Windows The CoMET System Engine
163. nections of specified types CoMET Configuration Gg xX General Editor Options Tool Locations User Locations ML Tables Modules Environment Me Parameter Bus Paramete Vom Parameter Bus Connection Clock Connection Logic Connection Add Parameter Add Connection Edit Delete cad a XML Tables Configuration Tab Several parameter and connection views are provided with CoMET You can edit the existing views or add new tables VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 33 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Configuring the CoMET System Engineering Environment Parameter Table Editing To create a new parameter table click Add Parameter in the XML Tables Configuration tab To edit an existing parameter table select the table and click Edit or double click the table CoMET Configuration x General Editor Options Tool Locations User Locations ML Tables Modules Environment blemo Farameter Bus Parameter Vom Parameter Bus Connection Clock Connection Logic Connection Add Parameter Add Connection Edit Delete x Le BusProtocol Arbitration Cancel Bush onitor Busw idth JK Cancel Apply AddressB its Add AequestLatency Edit Delete XML Tables Configuration Parameter Table Editor In the Parameter Table dialogue each of the list
164. nenenserseuens 143 OP TO gaat car EEE EE EE E ENS 144 DPI VCE e E E E A E E E 144 DLS gt E E E PT E TAE A AOTT E A 144 Using the Target Debugger Break Button ccccccccceccceeeeeeeeeeeeeeeeeeeeeeees 144 Validating VPM Gh VOL aie ssccsataceconecstaecaiteorenanicisaae sane mesmneadaanaiaromeneneeuaensaadanecwnradact 145 YU AS secs E E a reset ean Sa ara E tana aos 145 NAC o l E E A E E A A E A 145 Obtaining a Value Change Dump VCD ccccccccccccccceceeeeeeeeeeeeeeceeeeceseeeeeeeeeaees 146 Building and Simulating in Batch Mode ccc ccccccceseseeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeees 147 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary Vii May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Contents CoMET 5 14 User Guide Specifying Batch Mode Options using the Batch Mode Dialog 0008 147 Buld O 11 O11 S o 1ccnsncesenndeeeanssoeseganonoencesnbnesoaucnaedtgeaesqnadesaeaseesmsonmeunneostyeneceeaeesbaeds 148 i 2 0 809 bs OPON aa Renner Neen ee eee Oe nee nee eee 148 Tae OPON S ee ee ne E 148 Target Time CIMI S es ccc vesceutttns ess ri annenin TENNER vececeienecneteeneecnieeceeetereeen 149 Sav E Da E pa EE E EAEE E TEE EAE 149 Exporting a COMET Batch Tile vccavsscconsenssscndvandecetensiecnnimnedenditieuDesctantascedosraiacimenadee 149 Importing aC OME T batch Tle sisena E ak 149 R nno DE DA a TTAN AANT 149 Command line batch MOCS ssssseststedscu
165. nfidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Port Connection Developing a Fabric Module Definition Port Connection Module Instances Instance Ports Instance Ports Port Connection A Port Connection element specifies a connection between a Module Instance Instance Port and a Ports Port or Nets Net element of the containing platform Alterations to a module must result in changes to module instances of that type See Fmx Update page 72 Fabric Module Xx Port Connection Properties Fort Or Wet Name Hew Portlonnection Clock et Port Or Net Name Select from the list the Port or Net to which you wish to connect the Instance Port CoMET lists all Port and Net elements belonging to the Fabric Module You can refer to members of a Port or Net array See Arrays page 67 Port Connection Port Or Net Name values can be modified in a Connection View See Connection Views page 99 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 95 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Interfaces Interfaces A Fabric Module may contain a single Interfaces element This element is a container for all Interface elements Child Elements The Module Instances element may contain one or more Interface elements Interface Interfaces
166. ng Workspaces and Projects Saving Workspace Files To save the Workspace and all files open in the Document Window Choose File Save Workspace To save all files open in the Document Window Choose File Save All Files Exporting a Virtual System Prototype Workspace for METeor Virtual System Prototypes developed in COMET can be exported as a Workspace to a file for import by METeor METeor users can develop target software and Metrix projects and perform simulations on the VSP VBus standalone projects are exported as a Workspace containing a single VSP Project CIF Workspaces can be exported with multiple projects including CIF projects Target projects General projects and Metrix projects NOTE To successfully export a CIF workspace all CIF projects in the workspace must be of the same build type and configuration All projects must be in either Debug or Release configuration but not a mixture of both All projects must use the same compiler either Vc or Gcc but not a mixture of both To export a VSP you export the Workspace containing the VSP Exporting a Workspace To export a Workspace Choose File Export Workspace xi Fath C Temp Export z Hame PFOBDemoDevice Cancel Export Workspace dialog Path Enter the required path for the exported file Name Specify the required name for the exported file Click OK CoMET displays the Export Workspace dialog Project Configurations list
167. o the actual microprocessor behavior Target code is a subset of the microprocessor manufacturer test suite NOTE This option requires a specialized VSP and test suite code For more details contact VaST Systems Technology Corporation Validate To execute in Validation mode Inthe Workspace menu choose Validate CoMET runs the target code and returns a Pass Fail status in the output window Validate All Validate All runs a set of microprocessor test routines The set is specified by a list file To execute a set of Validation tests Inthe Workspace menu choose Validate All CoMET runs each of the specified target tests and returns a Pass Fail status in the output window VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 145 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model Obtaining a Value Change Dump VCD Obtaining a Value Change Dump VCD To obtain a VCD Choose Tools VCD Configuration value Change Dump i x W Enabled Location VaST ved E Cancel Check Enabled and specify the Location of the vcd file to be saved You can browse to the location If you provide only the file name the file is saved in the current project directory The VCD is created during simulation After simulation the VCD can be analyzed with standard VCD analysis tools Some modules such as StdBus provide param
168. ob TE E config_types h Sm oy Module cx E resource h i pe tampiStat ah E Generated Files i pee IA aga Configurations ae er Chemriicdae include SimpleVSP1 h include vas t std _types h include amp i_symlink_dll body h inc lude E include E simple SP1 Simple SP1 fmx tampiSym e Parameters retul i Hs Nova2 cDil Debug i BER stdBiithstance is i BS Nova2 cDil Release aga Instance Ports ig 29 c Includes f BusClockin HG Runtime Options oll Busclock Ese 4 Targets lif Bus EEM VirtualPlatform GS Parameter Overrides EG Folders E8 YastGpDiagnosticStdBus G Source Fles E G Instance Ports fl f MasterBusClock BY irtualPlatform fx ff SlaveBusClock EB VirtualPlatform re Pb R MasterBus i it ampi_symlink_dll_body c R SlaveBus 7 l ini i i s n d F H i rolink init c E i i i A nake laale z YaST Modules m g Loaded Modules For Help press F1 Ln 1Col1 NUM h To re dock the tool window click in the title bar and drag the cursor to any of the available docking positions displayed When the cursor is placed over a docking position the resulting location of the window if docked at that docking position is shown by a shaded area The following diagrams show the same tool window the Target window being docked at different positions within the SEE 22 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduce
169. odules Ea Add Objects Add Libraries dd Runtime Options Workspace Edit Configuration Delete Configuration Del Cut Configuration Ckrl s Copy Configuration Ctrl C Paste Cobre Build Configuration Rebuild Configuration Configuration Properties Ctrl F CoMET creates a new Runtime Options node under the build Configuration node VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST 189 ModelSim HDL Co Simulation Support Verilog Co Simulation Support Elem Test erilogModel H Folders ee 7 rd beara Eig hn ModelSim cDil Debug Fl Includes ni 9 Verilog Includes Runtime Options T p ModelsimVcDI Release H E E Includes E E Verilog Includes g WaST Modules User Modules Viewing and Setting Runtime Options Properties To set the runtime options for the top module e Right mouse click on Runtime Options e Select Runtime Options Properties Flea Test erilogModel f g Folders o Configurations Eure ModelSim cDil Debug i J Includes n 9 Verilog Includes a Sg Runtime Options cE Sa ModelsimVcDI IRE Expand Runtime Options Ctrl E H E Includes Collapse Runtime Options Ctrl L H Verilog Indui a E Add ills Edit Runtime Options Ez Delete Runtime Options Del Cut Runtime Options Ctrl e Copy Runtime Options Ctrl C Pas
170. ollapse Ports Ctrl L ee Modu M Interi Edit Ports FZ Meloke Darke Mel CoMET opens the dialog corresponding to the element The Element Dialog On choosing an Add or Edit action the element dialog appears Element dialogs have a standard format with Properties listed a control for editing each property and the standard OK Cancel Apply and Help buttons at the foot of the dialog Fabric Module x Fort Properties Hame Type Stoic s t s Number OF f Direction Inpa o Class None o Sub Class fF Description Cancel Apply Help ws In the element descriptions below dialog pictures are truncated to avoid repetition of standard elements VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 73 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition FMX Hierarchy FMX Hierarchy Below is the XML Tree view of a fmx file showing all types of element El Se FrixDemo a5 Module Instances rf Parameters Es Ea fenericMenory 1 3 Et be Instance Ports os B B a Pork oy Sp Nets a Nett E 1 28 1 Tasks EHE Taski H E Ea Port Or Net Views be ath Porti Memory Size i f Memory width 4 Burst wiriteBeatLlimit 0 BurstReadBeatLimit 0 UseEnableInput 0 EnablePowerQnDecode 1 Profiling Disabled VastProtiling Disabled Se liming Se MemorvyPaging Fea al ResetModul
171. ompiler ms Visual C F Simulator or Execution Engine Application f Library DLL F No Cygwin Dil Back Cancel Project Select the Fabric project type Project Name Specify name of the VHDL Project Location Specify desired location for project files C Compiler Select MS Visual C Simulator or Execution Engine Select Mentor Graphics ModelSim Click Next 172 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST VHDL Co Simulation Support ModelSim HDL Co Simulation Support Project Test HDLModel E x Fabric Module Module Class Peripheral Model hdi bs Module Type Test HOLModel Version 1 00 Back Ey Cancel i Module Class Select Peripheral Model Vhdl fora VHDL project Module Type Specify the name of the VHDL entity in the Module Type field or accept the default Version Specify the version or accept the default Click Finish NOTE The Module Type has to match the entity name of the VHDL entity The top VHDL entity may instantiate other VHDL entities and or Verilog modules in the project Double click the Build Configuration to open the Configuration window Project x Configuration Properties Type Mode Debus O Path ModelSimDebug O O aier DNOVA2 DMODULE DPRE_SYMLINK_INIT_RE Verilog Options PO hdl Options PF ile Daere PO De
172. onnections Reset T PlatformReset Port or Net connection to PlatformReset tlockIn B Mm PlathormClock Port or Net connection to PlatformClock DataBusClock E M StdBusiClockMet Port or Net connection to StdBusiClockNet InstBus Clock i al Port or Net connection to StdBusilClockMNet DataBus de 8 StdBusiNet Po Met connection ta StdBusiNet InstBus i A3 StdBusiNet Port or Net connection to StdBusiNet Irq S T StdlogicONet Port or Net connection to StdLogic Net Fiq BE T StdlogicONet Port or Net connection to StdLogicONet The Module Instance Detail lists Instance Ports and their connections Icons indicate whether the connection 1s a net or a port and port or net type Click on a link in the Connections column to move to the detail entry for the connected port or net Entries in the Module Type column link to the Fmx Report for the module from which the Module Instance 1s derived 102 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Viewing Module Definition and Prototype Configuration Reports Views and Reports As well as properties Instance Ports and connections Module Instance Detail entries show a table of Parameter Overrides GenericMemoryl Type Required Yersion NumberOf tlass sub Class Description GenericMemoary NumberOtMemoaryBlocks Mone This is an array of module instances with the size of the
173. or each x The report shows the prototype properties and a tree view of the prototype structure Use the module instance links in the Structure map to navigate to module instance detail entries The Pex Report effectively has two windows This helps in navigating complex hierarchies The first window opens when you first open the report When you click on a link in the first window a second window opens Position the two windows side by side Now you can use the first window Structure list as a menu to select module instances and other items in the second window If you prefer to use a single window close the first window after opening the second window VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 105 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Views and Reports Viewing Module Definition and Prototype Configuration Reports To return to the Structure map move to the top of the file The hot key Ctrl Home performs this function in Microsoft Internet Explorer and Mozilla VirtualPlatformi Module Path Top VirtualPlattorn Submodules ARM926EJ51 GenericMemor 0 GenericMemornt 1 gt GenericMemor 2 Sidbust YastGpstdLogicot Type Required Version Class SubClass Description Parent Connectons VirtualPlatftorm WSP The WSP contains a single Simplex SP fm instance of the YWirtualPlattorm which in turn contains all other Module Instances
174. or future use Sub Class This attribute is reserved for future use Description Provide a brief description of the Fabric Module This description appears in Fabric Module Definition Specification reports Child Elements Parameters Ports Nets Tasks Module Instances Interfaces VasST SYSTEMS TECHNOLOGY Confidential and Proprietary 77 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Parameters Parameters A Fabric Module element may contain a single Parameters element This element is a container for all Parameters and Sub Parameters elements Sub Parameters elements allow you to set up nested groups of Parameters Child Elements The Parameters element may contain one or more Parameter elements The Parameters element may contain one or more Sub Parameters elements Parameter Parameters Sub Parameter Parameters allow you to create more general configurable modules When you create an instance of the module corresponding Parameter Override elements are created in the Module Instance Further Parameter Override elements are generated in the pcx file for the containing VSP The Parameter Override elements values can override the specified Parameter value See Parameter Override page 89 Fabric Module q x Parameter Properties Hame Type ftBooean O Allowable Values Value Fms Access P
175. or or Execution Engine vast Novas Application f Library DLO F Ho Cygwin Ell lt Back Cancel Project A Virtual System Prototype can contain several types of project Fabric A project built with the VaST Communication and Infrastructure Fabric methodology Fabric projects create modules that represent the physical device models within the Virtual System Prototype For information about the VaST Communication and Infrastructure Fabric methodology refer to the CoMET Modeling Guide using the Communication and Infrastructure Fabric VpmT A VPM Transformer project The VaST VPM Transformer is a toolset and methodology which allows users to modify the instruction set of a VaST Seed VPM The VaST VPM Transformer Toolset needs to be purchased and installed before a VPM Transformer project can be created Vbus VBus project For information on CoMET 5 support for VBus projects see Application Note Converting CoMET 4 VBus Projects to CoMET 5 VBus Projects Systemc Standalone System C project You can develop a pure SystemC project within the CoMET environment A System C standalone model cannot be exported for use in METeor A System C standalone model can later be interfaced with CIF models by migrating it to a Fabric module of module VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 45 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Proj
176. orm fmx Ioj x Module Type StdLogic M et Met PlathormA eset Fort Vast pStdLogicl VastapStdlogicl Signallut Genenchlemory Genenchlemory ARM IZ6ESS 1 ARMS26ES Fig StdEus1 StdB us The picture shows an fmx file being edited in Logic Connection View The Reset Port of the ARM926EJS1 module instance is being connected to the PlatformReset module port Note that the columns are identified as Net or Port by a suffix VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 99 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Views and Reports Viewing Module Definition and Prototype Configuration Reports Viewing Module Definition and Prototype Configuration Reports CoMET provides a number of different views of module structure and prototype configuration The XML Tree view and XML Table views allow you to browse and edit Fabric Module Definition fmx files and Prototype Configuration pcx files within the Document window You can also view a comprehensive report on the contents of an fmx or a pcx file using the Prototype Report feature To view Prototype Reports you need an XML viewer capable of performing XSL transformations Recent versions of Microsoft Internet Explorer http www microsoft com windows ie and Mozilla http www mozilla org have this capability and may be freely downloaded and used NOTE Prototype reports open in the application specified for perf
177. orming the Open action on xml files This must be a browser capable of viewing HTML and of performing XSL transformation for prototype reports to appear in the correct format To determine the application registered to open xml files open Windows Explorer choose Tools Folder Options File Types and browse to the XML entry To view a Prototype Report Open a pcx or fmx file in the Document windows and choose Tools Prototype Report Or click the Prototype Report button on the tool bar Viewing a Fabric Module Definition Report Fmx Report Open the Fabric Module Definition fmx file in the Document Window To open an fmx file in the Document Window Double click the fmx file icon or name in the Workspace window or To open the f mx of a module in the module library double click on the module icon or Open a Fabric Module dll by choosing File Open File and browsing for the dll file To view the prototype report for the fmx file Select Tools Prototype Report Or click the Prototype Report button CoMET opens the report in the default XML browser 100 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Viewing Module Definition and Prototype Configuration Reports Views and Reports Fabric Module Definition VirtualPlatform ie Properties cn Parameters 1 i Ports 3 Module l k Nets 4 2g Tas
178. ory environment variables e VASTS HOME The home directory of the COMET System Engineering Environment SEE and associated system tools CoMET automatically sets the local path to tools based on tool locations e LM LICENSE FILE The location of the FLEXIm license manager license file NOTE Ifyou are using any third party tools with COMET compilers debuggers etc you may also require other environment variables depending on the application Refer to the documentation provided with the third party tools for setup requirements 6 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting up Environment Variables Installing COMET Changing Environment Variables in Windows XP or Windows 2000 To change or add an environment variable in Windows XP or Windows 2000 From the Taskbar click the Start button Select Settings Control Panel Select the System icon In System Properties select the Advanced tab Click the Environment Variables button Select the user environment variable to change Click the Edit button Type a new value for the variable typically a path Click OK VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 7 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Installing COMET Installing CoMET on a Network Installing CoMET on a Network
179. ory is allocated Config File The Architecture Configuration File for this project Metrix Config File The path of the associated Metrix Configuration mcx file See the Metrix Configuration File User Guide Executable File This specifies the file that calls the Fabric dll Task Stack Size Default 32K May be increased for large projects Max Tasks Default 1000 May be increased for large projects VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 191 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST AMPI architecture CIF Bus Master Bus Slave Bus Master Slave Glossary Architecture Modeling Programming Interface A term applied to both the process and outcome of designing and creating a specific technological product including its overall structure behavior logical components and logical interrelationships An architecture may contain instances of other architectures By comparison the term design has less scope than architecture An architecture is a design but most designs are not architectures A single sub system or a new function has a design that has to fit within the overall architecture A similar term framework can be thought of as the structural part of an architecture VaST Communications and Infrastructure Fabric an innovative methodology that allows you to design and specify fully executable Virtual System Prototypes virtu
180. ory to another cccccccceeeeeeeeeeeeeeeeeeeeeees 61 Developing a Fabric Module Defimition ccccccccsssssssssscccccccssssssssccccssseeessssecs 63 Opening the Fabric Module Definition file cee ceeeeeeeseseeeeeseeeessessssseeeseeeseeeens 63 Editing the Fabric Module Definition file cccccececceeceeeeeeeeeeeeeeeeeeeeeeeeees 66 PLETE GIDISILS ElemeNiS ccsconsanncecnedenconnsannnosenaanconasannooseednoonnbanoesenaeseonsbeducesossaasassnees 66 TAO St TN AN Sergei aspen tase esisee ane dessa cane esse aug EESE RESER EAEEREN SA 67 Description ALT DUUCS osoianccessienessrocsnanvensonsedunseiennseheeadestsiannaeenbentedediienndenmnesaaitaoratoredaness 67 TTA o E I EE E PE E E A A E aca 67 Declaring an ATE AY scscesciecenetsnsneansanediesiedendvasinasiesienehonenanindanoseniodehdssanaanesenebendaannsanenenioets 67 Array Notation DeClarationi lt 10cscsdscncseseannescsvsenrsdeagncadcdensaaeedeacadaccnnaeaetlansddee 67 The Number OL AG NOUS csecsen ea e EEEa 68 Referring to Members of an Element Array cccccccccccccccceeeeeeeeeeeeeeeeeeeeeees 69 Using Array Notation in an Instance Port Name cccccssssesesseeseeeeeeeeeeeeens 69 iV VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 5 14 User Guide Contents Using Array Notation in a Port Connection Port Or Net
181. ototype A workspace may consist of a single project or multiple projects To create a new workspace From the File menu select New Workspace VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 43 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Managing Workspaces and Projects Creating a Workspace Workspace SYSTEM ENGINEERING ENVIRONMENT hn Workspace Mame simpleySP Location LC AMork cometprojects Simpley S P lt Back Cancel NOTE When you create a new workspace COMET automatically adds a new project to the workspace To build a Virtual System Prototype you must also add new modules projects or add existing modules projects to the workspace 44 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Adding a New Project Managing Workspaces and Projects Adding a New Project A project contains the configuration of a module for example the module files and their locations settings for the compiler and simulator etc To add a new project to the workspace From the Workspace menu select Add New Project my x Project Project Name els SimplevSP Location 4 Sy sternL C workcometprojects Simple S PSimplev s E C Compiler Zi 4 eal Metrix eal Target EE General MS Visual C Simulat
182. p Platforrmlock fll ClockNet El p PlatformReset a Resethet Ags Parameter Overrides GE NumberoFMemoryBlocks 3 XML Tree View There are also various table views Memory Parameter Bus Connection and so on See XML Tables Configuration Settings page33 Defining the Fabric Module involves editing the fmx file to add and specify the details of elements such as Parameters Ports Nets Tasks Module Instances and Interfaces Each change modifies the fmx file Depending on the changes you make COMET may make further modifications to the fmx file and may generate changes in other files VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 65 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Editing the Fabric Module Definition file Editing the Fabric Module Definition file The CoMET Methodology involves first creating the Fabric Module Definition then creating any behavioral code required Use the Project wizard to create a CIF project Choose Workspace Add New Project and choose a Fabric project type This ensures that the appropriate templates are used for source and fmx files Creating the Fabric Module Definition involves editing the Fabric Module Definition fmx file This can be done by directly editing the XML file in XML Text View but it is recommended to use the XML Tree View interface XML Tree View provides validation
183. pdate Platform After changes to an fmx file the project dll and the pcx file must be updated The pcx file is created or updated on build You can also create or update the Pcx file at any time without building the dll To update the configuration file From the Workspace menu select Update Platform CoMET updates the pcx to contain Override Parameters corresponding to all module instance Parameters in the VSP Update Platform determines the fmx hierarchy by examining the fmx files from the top down It creates a corresponding Module Instance in the pcx tree It then determines the Parameter elements for each Module Instance and populates the corresponding pcx Module Instance with corresponding Parameter Overrides See Fmx Update page 72 When the pcx is open in the Document window you can edit it in XML Tree view shown above or XML Table parameter view See Parameter Views page 98 You can view a comprehensive report on the pcx file See Viewing a Prototype Configuration Report page 105 Excluding Build Time Parameters from Prototype Configuration Files Pcx files are generated from fmx files It is not possible to make a change to a pcx file which results in a change in an fmx file that is a change in the structure of the VSP Pcx files are intended for runtime Parameter Overrides Pcx file Parameter Overrides are not evaluated until simulation time Fmx files may contain parameters which are not runtime pa
184. r reproduced except as expressly authorized in a written agreement with VaST Using the Source Editor Setting the Target Executable The module editor uses standard file and editing functions File and Edit menus for creating new files opening existing files searching copying and pasting text and so on You can also use tools from the tool bar for commonly used commands and standard keyboard shortcuts To create a new file From the Tool Bar click the down arrow next to New File button CoMET 5 C astProjects base _ CoMET 5 C astProjectsbase File Edit view Workspace File Edit wiew Workspace a K Fabric Module Matlab Model X Instruction Prototype oo Instruction Definition Instruction Selection Platform Contig Metrix Config Select the type of file you wish to create from the drop down menu NOTE Clicking the New File button will automatically create a new text file To open an existing file From the File menu select Open File Navigate to the directory in which the source file is stored Select the file name Click on the Open button or Double click on a source file in the Workspace Source Files or Header Files folders NOTE Creating a new file or opening an existing file does not automatically add the file into the project You must also add a reference to the file in the Project pjx file using the Workspace window interface so that it appears in the
185. rameters but which affect VSP structure These are build time parameters and should not appear in the pex file For example it is common to use a platform level Parameter to specify the size of a Generic Memory Module Instance array In the example below the Parameter is called NumberOfMemoryBlocks This makes it easy to vary the number of memory blocks in a platform You should vary this parameter by changing the value of the NumberOfMemoryBlocks Parameter Override in the platform module instance in the VSP 122 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Modifying Parameter Values in the Prototype Configuration File Configuring Build and Runtime Options E Se VirtualPlatForm ai rae Parameters bese kn MumberofMemoryBlocks 3 a Ports kun PlatFormdclock ba PlatFormReset at Mets oe BY StdBuslNet Be StdBus1ClockNet eB StdLogicONet E Tasks A h Module Instances HEE vastapStdLogic l EEEn Ea Generichemory 1 E be Instance Ports gi TRA BusClack Fabric Module Module Instance Properties Genenchemorrl Instance Mame Type GenericM emay Required Version LS Number OF Numberl emorBlocks Class None Sub Class Ga StdBusiClockNet a T Reset Description This ig an array of module instances with the size of ae PlatformR eset the aray determined by the Ba Bus Humbe thMemonblocks parameter
186. re specified you can save the batch mode specifications by clicking the Save button The options are saved in the Windows Registry CoMET can then be invoked from the command line See Command line batch mode below Exporting a CoMET Batch File You can export the Batch Mode dialog batch specifications as a COMET 5 batch file Click the Export button browse to the required location and specify the file name to save You can then reload the batch file using the Import feature or specify the CoMET batch mode as an option when running CoMET in command line batch mode See Command line batch mode page 150 Importing a CoMET batch file If you have created a batch file in the COMET 4 batch file or COMET 5 batch file format you can load it in the COMET 5 batch dialog Click the Import button and browse for the CoMET batch file COMET imports the options and displays it in the Batch dialog Workspace Paths list You can then edit it using the editing features described above You can also run a CoMET 4 batch file from the command line See Command line batch mode using a COMET 4 batch file page 151 Running the batch When the batch mode options are created you can run the batch mode by clicking the Run button Alternatively you can run the batch from the command line See Command line batch mode below If anything causes a halt such as errors in building or simulating or manual intervention batch mode ends You can use the Stop Build an
187. rkspace menu select Stop Building Or Select the Stop tool bar button 138 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Simulating and Debugging a Model With CoMET you can analyze the performance of your system model The COMET debugging tools are also useful for locating the source of bugs analyzing how execution flows from one part of the system model to another and observing how variables change as statements are executed CoMET allows you to execute the Virtual System Prototype in two modes simulation and debug A third execution mode validation 1s useful to certain customers for validating VPM behavior Choosing a Debugger You can debug either Hardware Models that is VaST models or Target code running on each VPM module instance in your platform You determine what kind of debugging is performed at the start of each debug session See Executing in Simulation Mode and Debug Mode page 141 Hardware Model Debugging To debug your hardware model you can use the CoMET internal debugger or an external debugger To choose an external debugger for Hardware Models choose Tools and check the External Debugger menu item The external debugger can be only VC6 VC7 or VC8 NOTE You cannot use VC8 Express as an external debugger because VC8 Express does not support extensibility For further information s
188. rray notation See Port Or Net View Instance Port and Port Connection below Using Array Notation in an Instance Port Name When you add a Module Instance to a platform CoMET creates a single Instance Port for each Module Port You can create subgroups of Instance Port array members by adding additional Ports and naming them using array notation For example the Instance Port name IrqIn 0 15 refers to members 0 to 15 of the IrqIn element array You can rename this Instance Port name to IrqIn 0 7 and add another Instance Port named Irg 8 15 to permit you to connect the two groups of array members independently l y Module Instances E iy Module Instances JEA InterruptController1 el eet InterruptController 1 m as Instance Ports zis Instance Ports Default module instance with a single Modified module instance with an additional Instance Port for each Module Port Instance Port allowing two groups of IrqIn array members to be connected independently VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 69 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Arrays Using Array Notation in a Port Connection Port Or Net Name CoMET distinguishes a Net or Port array by listing it with an element range in the drop down list for the Port Or Net Name field You can edit the range to specify the required elements When you specify
189. rresponding parameter of the same name will be created automatically VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 175 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support VHDL Co Simulation Support Selecting a Fabric Port Type for a VDHL Port Note This can only be done after the VHDL source files have been successfully complied and the fmx file has been successfully updated with the list of ports in the VHDL entity To select a particular Fabric Port Type for a VHDL Port e Double click on the Generated Files ProjectName fmx file This will open the generated fmx file document window EF TestYHOLModel Test HDLModel fma Test HOLModel Ege Parameters 4rchitectureWamne default a Forts ee Reset Flo Tasks 28 TestYHDLModelTask CHER Port Or Net views 3 nm Reset e Double click on the port for which you want to set the Fabric Port Type Fabric Module x Fort Properties Name reset Type StdLogic bi Number Of Direction Std ecto Class Sub Class Description Module port reset Cancel Apply Help ee 176 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST VHDL Co Simulation Support ModelSim HDL Co Simulation Support e Select the Fabric Port Type from the Type pull
190. sseeeeeeeees Implemented Support for mno cygwin Option with Gec Projects 00 New Buttons Added to Toolbar 5 ieiassapvdeicwnacsionusiennenoenssaseatdoleneeecsduenahenmemmaaasoniiee ING TC GIVE 3 3 creseronscinssinied wsdasoneve deniataia dentaintasdagauset EEE EEEE E NST OS FA OU aieri EAEE NEETER Multiple Versions of Models Support cccccccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees New Parameters Added to the Default Parameter ViewS cccccceeeeeeeeeees Enabled Sorting in Versions Dialog BOX ecceesssccccceeeeeeeeeeneeeeeeeeeeeessnaaees ING Vy 1G OVE Dil ee E E ie inntodsonete sta atedaiteucaboyeietnnnsanes 4 Vasil VPM Transtorme r LOOMS s ccsusteiamossensecnscrnuvsneossacnsranshnevasannenctecsaneusterenees 4 N w n COMET Dial clic creseronaainssinied osaaudonene deetaia nEn ES A EEEE EN EEA 4 Visual C Version 8 Supported nse ccassacanease dannetencudidenspadeanscssduendinnct dectgeceneaneens 4 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Contents CoMET 5 14 User Guide ie bne Cy od eeeererrerreerrarrercerrr errr errr rrr rrr ererrrrrrrrr E vere errr creer rrr erry rrr er 5 COMET COmponeniS saengan neoion ine aara n a E a R Ne r aan nn e EE 5 Installing COMET on Windows XP or Windows 2000 ccccccccccccccceceeeeeeeeeeeeeeeeees 5 Setting up Environment Variables
191. ssssscccccssssssssssccccscseesssscees 169 Introduction to ModelSim HDL Co Simulation Support cccccccccccccceseeeeeeeeees 169 VHDL Co Simulation Support cccccccccccccccccccccccccccecccecccccccccccccccscccccsececceceees 169 Features and reguiremen S 5s siecinssicnaedsaseentersesaisdansesrensniediedaxniacsdvateddeacnexderivadeesta 169 Mappings between VHDL and Fabric Port nnneeesennnsnrrresersrrrererererrren 170 Running a VHDL Model on CIF saspacnrarinn R 171 Tool Locations Configuration Settings for VHDL Model ee eeees 171 Creating a VHDL Model Proj Cl sssscascaccesacnsesivsaaeeunseaseaaeasansansseaasedesseaaaniestneons 172 Farao O e E E E EN O EE 175 Selecting a Fabric Port Type for a VDHL Port ccc cccccceceeeeeeeeeeeeees 176 Setting the Runtime Options ecic csadasdvaciacianccadandenckeesenecndeesvientsdoadondeasssaccsdvasensts 177 Verilog Co Simulation Support ccccccccccccccccccccecceccceceeecceccceeccceccceceeeeceeeeeeeeers 180 Pe atures and TeguUIremeniS x 2555 iecovascsecevessiauskaceadea ven NT E E 180 Mappings between Verilog and Fabric Port ccccccccccesceseeeeeeeeeeeeeeeeeeees 180 Running a Verilog Model on CIP sessies ccccccceseeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 183 Tool Locations Configuration Settings for Verilog Model cceeeeeee 183 Creating a Verilog Model Projet cccscacnnnesactsnndewdanvasdactinenssodacudactesvessedvaratacsas 184 Selecting
192. sssssssssssssssssssee 100 POX E siseseeencenceneeneeneeneenceneenacen MGA ee E 12 KoA A seein As BDO gsconsusncaiceastnacamnconsuaetestwenaassunitenes 100 H NGL PO E E 122 hardware requirements 5 6 Periph fai Modulo aysigme EE aeaaaee Siriei ei 42 Mod le TY DC senina 48 highlighting keyWords ss sssssssssssesssee 131 a ee 5 Hot IN CVS wc asssacdiersirasstusargnonaadsaeanacdsotons See Keys pares ini a ieee aim FIG GT segre y E 45 I adding source files 55 installing COMET irs EE A EIEE A A 137 Windows XP 6 CONT SUMING piccrosrouasnocnadsetdvmsacrdeaatehednewenns a ees EEEn AN E E ATN gi EE ANE CREEN NONE aiins aei ve debugging sesiunii ernie 141 K opening an existing project 50 k TG 110 VINO oerni 51 ee t acti FS e EE E AEE TTT 53 Building Projects ccceeeeeeeeeeeees 157 7 a ve projec 14 Debugging cccccccesscccesseceeeseeeeeenseees 157 seu cea ae Document Window 156 viewing properties eeeeeeessseeeeeeeeeeteees 52 A Prototype E i E EE PEE E E N Viewing structure in Prototype Report 105 ae LAA Sean pape E E AEE T Prototype Configuration R eee re er errr ae i H T Wo 00 0 eorssiisiorseieiiserarsrisirinseirsint l ic Workspace Window 0 seeeeeeeeeees 156 R keywords ino Report Se a a IMIS e E E 100 M PROUOLY DO aenor 100 mandatory environment variables 6 S Matlab Generator ccccce
193. stance element see Module Instance page 84 Fl ge simple sP1 I a Module Instances Elf Tee 8 Parameter Overrides VastopResetl VastapClack1 te Parameter Overrides been ClockPeriod pS 10000 oz VirtualPlatforrn Ges Parameter Overrides fee YastGpStdLagictt Ee 2 GenericMenory1 0 fl Eel ea GenericMemary1 1 E Eel ea GenericMemory 1 2 Blea ARM926EJ51 See ee StdBusl fa enamels Overrides if BusProtocol StdBus S Arbitration FirshCome BusMonitor Disabled BusWwidth 4 Addressbits 32 Bus4rbitrationReport Disabled Warninglevel All Profiling Disabled VastProtiling Disabled Se liming The pcx file above is arranged according to the hierarchy of module instances The SimpleVSP1 module contains a VirtualPlatform1 module instance which in turn contains Module Instances at a lower level with Parameter Overrides for all Parameters of the corresponding modules To create a new configuration file Choose Workspace Update Platform VasST SYSTEMS TECHNOLOGY Confidential and Proprietary 121 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Modifying Parameter Values in the Prototype Configuration File A pcex file is also created on a successful build To open the configuration file From the toolbar click the Open Config button 3 F Simpler 5P 1 pcx Pcx Update U
194. systems in COMET See the CoMET Tutorial This is a good point to work through the tutorials The remainder of this guide is a reference document You can read the sections in any order VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 19 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Windows XP Theme Display Issue Windows XP Theme Display Issue When using Windows XP Theme display options selected tabs may be indistinguishable from unselected tabs For example in the diagram below the Workspace tab is very similar to the VaST Modules tab This is due to Windows XP color scheme where the two color options are very similar Workspace FF Workspace Simplex SP o a Simple SP1 2g Folders AS Source Files oy Header Files SS Generated Files Gn Configurations on Workspace z MaST Modules To address this issue you can alter the shade of the unselected tab The following procedure outlines how you can change the shade of unselected tabs From the Taskbar click on the Start button and select Control Panel On the Control Panel window double click Display On the Display Properties dialog box select the Appearance tab Click the Advanced button to select advanced options Display Properties Themes Desktop Screen Saver Appearance Settings Inactive Window Active Wi
195. t Target Image Fz Delete Target Image Del Cut Target Image Ckrl Hs Copy Target Image Ckrel Z Paste Etrit Target Image Properties Ctrl F Restrictions are as follows e S records must be sorted in ascending order by Address field Configuring Build and Runtime Options e Records must not overlap i e No record may contain an Address that falls within the address range start Address end Address Length 1 of another record e Any memory that does not fall within the address range of a record is assumed to contain zero VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST 127 With the text editor provided by CoMET you can edit the module source files module description files and C source code files Be Simple SP irtualPlatform irtualPlatform c Hinclude VirtualPlattform h Hinclude vast std types h inc lude ampi symlink dll body h inc lude version number h ta mpisyolinkFindEntry a ampisSymlinkFindEntry i ee tt t Interface functions and table the common symlink Dll body wy ta ampistatus VirtualFlatformInitModuleInstance t ArmpiModulerId AmpiModul i return AmpigUccESS Ie jt Have just been loaded by the On ud woid InitDll void CoMET Code Editor Window VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 129 May not be used disclosed o
196. t to suit your preferences with the CoMET configuration settings To display the CoMET Configuration dialog From the Tools menu select COMET Configuration or Click the COMET Configuration tool bar button The Configuration Settings are defined on several tabs described in the following sections When you have made all your selections Click OK General Configuration Settings These options allow you to customize the general behavior of the COMET System Engineering Environment Check the option to enable the feature The following list explains the behavior of each option when selected CoMET Configuration f q x General Editor Options Tool Locations User Locations ML Tables Modules Environment Default rl Wiews Fri tiles xm Tree view ha Pex tiles xm Tree view ha Startup Requires re start M Reload last workspace on startup DTD Locations Requires re start YaST home C Substitute local drive C Network drive Runtime Options MW Enable runtime dependency checks Auto convert Gee projects to Mo Cygwin Dil General Configuration Tab 26 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring the CoMET System Engineering Environment Getting Started Reload last workspace at startup By default the COMET System Engineering Env
197. tance Ports Module Instances Instance Ports A Module Instance element may contain a single Instance Ports element This element is a container for all Instance Port elements within the Module Instance When you add a Module Instance to a Fabric Module CoMET automatically creates an Instance Ports element and Instance Port elements within it corresponding to all the Port elements in the module Child Elements The Instance Ports element may contain one more Instance Port elements Instance Port Module Instances Instance Ports Instance Ports An Instance Port in a Module Instance corresponds to a Port in the module The Instance Port can contain a Port Connections element which in turn contains Port Connection elements allowing multiple connections between the Instance Port and Port elements or Net elements within the parent Platform Alterations to a module must result in changes to module instances of that type See Fmx Update page 72 Fabric Module J x Instance Port Properties Hame Description Name This must match a Port in the module You can refer to members of an Instance Port array See Arrays page 67 Description You may add a description for documentation purposes Descriptions appear in Prototype Reports See Viewing Module Definition and Prototype Configuration Reports page 100 Child Elements An Instance Port may contain one or more Port Connection elements 94 VaST SYSTEMS TECHNOLOGY Co
198. te Cobre Runtime Options Properties Ctrl F Or e Double click on Runtime Options 190 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Verilog Co Simulation Support ModelSim HDL Co Simulation Support Verilog Project Runtime Options x Runtime Options Properties Simulator Options PO Contig File Demo ctg O a Metrix Config Fie Demo mes 0 a Executable File Jc wast8_home Ampi2 Bin sys_loader exe I Task Stack Size Jak Max Tasks f O00 Cancel Apply Help we Simulator Options These options are passed to the hardware simulator For the ModelSim Co Simulation Support there are some additional options you can specify l script lt commandfile gt used to specify the name of the file containing the ModelSim simulation commands to be executed 2 vcddump lt vcdfilename gt used to activate the VCD dump of all the signals in the HDL hierarchy to the specified file 3 deltamode any HDL port signal change will only be propagated to the CIF at the next delta If this option is not specified all the signal changes will only be propagated to CIF at the end of the delta cycles 4 sharemem lt size gt Amount of share memory in bytes to be allocated for sharing information for example Port states between the Nova 2 scheduler and the ModelSim simulator A default value of 512 K of share mem
199. ted item Ctrl P Item selected in workspace tree Displays the properties of the selected item Hot Keys Document Window Ctrl Right Viewing fmx or pcx file XML Table On selecting table view from Click View Ctrl Right Click on module context menu restricts view instance to module instance 156 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Hot Keys Building Projects Hot Keys Ctrl Shift F9 Remove all breakpoints Hot Keys Document Window Source Code Navigation and Bookmarks ee o Hot Keys Building Projects Shift F8 Build current project Hot Keys Simulating and Debugging Alt F5 Simulate Debugging stepping through code Step into code block Debugging stepping through code Step over code block Shift F 1 1 Debugging stepping through code Step out of code block VasST SYSTEMS TECHNOLOGY Confidential and Proprietary 157 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 4 and SystemC Compatibility Converting CoMET 4 projects You can convert and edit VBus projects created in COMET 4 A CoMET 5 VBus project can be built and simulated using similar procedures to those used in CoMET 4 For information on CoMET 5 support for VBus projects see Application Note Converting CoMET 4 VBus Projects to COMET 5 VBus Projects
200. ter via a Parameter Override from a Fabric Module Definition fmx file in which an instance of this module appears Allowed values e Public Visible and editable in fmx e Protected Visible not editable in fmx e Private Not visible not editable in fmx See Parameter Override page 89 Pcx Access Determines access to this parameter via a Parameter Override from a Prototype Configuration pcx file in which an instance of this module appears Allowed values e Public Visible and editable in pcx e Protected Visible not editable in pcx e Private Not visible not editable in pcx See Parameter Override page 89 Description Provide a brief description of this Parameter Sub Parameters Parameters Sub Parameters Sub Parameters provide a way hierarchically to distinguish parameters See Hierarchical Parameter Type Naming page 76 Fabric Module x Sub Farameters Properties Hame Hew SubParameters Description Name Type the desired name for the Sub Parameters element This name acts as a category heading for parameter child elements Description Provide a brief description of this Sub Parameters element Child Elements A Sub Parameters element may contain one or more Parameter elements A Sub Parameters element may contain one or more Sub Parameters elements VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 79 May not be used disclosed or reproduced except as expressly authorized in a
201. tes complete system level behavior function and timing CoMET is also ideal for larger system designs such as ECUs in automotive or even full distributed systems of ECUs CoMET supports incremental integration of components as they are completed and tested throughout the engineering process CoMET executes application software on retarget able Virtual Processor Models VPM at speeds in excess of 50 000 000 instructions second while preserving timing accuracy across the hardware software interface About This Manual This document discusses how to install and use VaST Systems Technology s CoMET System Engineering Environment tool and how to build simulate and debug a Virtual System Prototype There are several topics on system design beyond the scope of this document The definition of system architecture and how to make a fast efficient model is not included in this document Also beyond the scope of this document is a description of VaST s Communication and Infrastructure Fabric Virtual Processor Models Virtual Architecture Platforms and the following add on modules or features e The specific virtual processor models VPMs available from VaST Systems Technology e Metrix tracing profiling and dynamic debugging methodology e Integrating Physical models such as Matlab References You should use this manual in conjunction with the following e CoMET v5 14 Tutorial e CoMET Modeling Guide CIF We recommen
202. the Parameter Override dialog Alter the Override Value attribute Alternatively In the fmx or pcx XML Tree View expand the Module Instance and the Parameter Overrides nodes Right click on the parameter you wish to edit Select Edit Parameter Override from the Context menu Edit the value of the parameter override and press Enter to complete Alternatively Select the parameter in the XML Tree View and press F2 Edit the value of the parameter override and press Enter to complete Be Simple SP Simple SP1 Simple SP1 fmx Simplex SF 1 m e Parameters Ports Mets ot Wl Tasks Module Instances eal StdBus1 ap te Instance Ports a Ki BusClockIn bese a BusClock Oi Bus sProkocol StdBus Arbitration FirstCor Expand Parameter Override Crrl E BusMonitor Disablec Collapse Parameter Override Ctri L Bus width 4 Tea eer ae AddressRits 32 Edit Parameter Overrit z 2 k Bus rbitrationReport Delete Parameter Gyerride pel WarningLevel All Gut Parameter Override Chri g amima Copy Parameter Override Ctrl H A vastGpReset Paste Corr Hy fee YastGpClacki Ee virtualPlatformt y nml Tree view ee eee 92 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Sub Parameter Overrides Developing a Fabric Module Definition Sub Parameter Overrides Module Instan
203. the fabric module definition xml file is shown below 36 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring the CoMET System Engineering Environment Instance ame ModuleT ype StdLogicO_1Net E w astGoStdLogicl VastGo5S tdLagicO Signal ut a o a i ARMIZBEJS ARMI26EJS Fig Reset y ae Genelec StdBust StdBus Eg Runtime Options VastGpClack VastGpClack ABA Dlls GenerichMernory Generichemory Reset Ge Targets Flees Target Test Seve al Top SimplePlatform EES SimplePlatform1 A Folders o Source Files P SimpleFlatform1 c Ba SimplePlatFormn1 Friis Bosse SimplePlatForrn1 rc Bee ampi_syrolink_dll_ bor a ampi _symlink init c H E Header Files 23 Generated Files El Configurations E Pa Nova YcDIl Debug H a Novaz cDill Release EEG arm926e_sieve Bay Folders E23 Asm Source Files Corresponding Logic Connection View See also Connection Views page 99 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ResetFort Getting Started Goto Module Instance Ckrl 6 dd Module Instance Add Met Add Fort Edit Column F2 Edit Module Instance Delete Module Instance Del Cut Module Instance Ctrl Copy Module Instance Chrl C Paste Module Instance
204. tine File TestVHDLModel def Achye lt lt Specify the Verilog complier options for Vlog in the Verilog Options field if there are Verilog modules in the project Specify the VHDL complier options for Vcom in the VHDL Options field VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 173 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST ModelSim HDL Co Simulation Support VHDL Co Simulation Support CoMET creates a VHDL Model project from templates xi a TestyHDLMadel E E Folders a Source Files Ey Test HDLModel c E TestYHDLModel rc Test HDLModel vhd conFig_hda c ampi_ symlink dll body ampi_ symlink init c a Header Files B TestvHDLModel h ampi_symlink_names h E config h B config _types h resource h sS Generated Files E Test HDLModel fmx i config_init c config _symlink c config init h config_struct h config symlink h yersion_number A config _hda h oF ga eases ve ModelSim cDil Debug o E E Includes o E Verilog Includes G a ModelSimycEl Release H E C Includes Fly Verilog Includes Workspace g YaST Modules User Modules VHDL Model You can now replace the newly created files with the corresponding files from the existing VHDL project e Source Files ProjectName c behavioral C for HDL device e Source Files ProjectName vhd VHDL source file e Header Files ProjectName h behavioral C
205. ting the VBus Peripheral Model When you simulate a CIF VSP containing a VBus Peripheral Model the VBus Peripheral Model is run by the Nova Execution Engine and is co simulating with other CIF Models in the VSP You can specify the Nova Execution Engine command line parameters with the NovaCmdArgs module instance parameter overrides Simulating a VBus Peripheral Model with FinSim The FinSim verilog simulator requires a specific version of the GCC compiler version 2 9 lia VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 163 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST CoMET 4 and SystemC Compatibility Simulating a VBus Peripheral Model with FinSim You cannot create a VBus module that 1s compatible with both CIF and FinSim because to create a VBus CIF model you must use GCC version 3 2 packaged with CoMET This is incompatible with FinSim There is no Verilog debugger support To create a VBus model using FinSim choose Workspace Add New Project Workspace Simple SP l x Project Project Name E usFinSimD emo Location Ic ork cometorajects 4 BusFinSimL emo Ey C Compiler Cygwin Goo E Simulator or Execution Engine f Application Library DLL Ho Cygwin Dil lt Back Cancel Project Select the VBus project type Project Name Specify the required name Location Specify desired location for project files C Compil
206. tion mno cygwin e Starting a new Gcc project in CoMET will automatically use the no cygwin option mno cygwin Fabric VDag Metrix and general Gcc project configurations are supported by this feature NOTE Itis also possible to enable disable the No Cygwin DII option when creating a new Cygwin Gcc project Enabling the No Cygwin DII option in the COMET Configuration dialog box will override the No Cygwin DII option in the New Project wizard See Adding a New Project page 45 28 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring the CoMET System Engineering Environment Getting Started Editor Options Configuration Settings These options allow you to customize the appearance and behavior of the text editor Check the option to enable the feature The following list explains the behavior of each option when selected CoMET Configuration x General Editor Options Tool Locations User Locations ML Tables Modules Environment bern Waa i i d Cal b aC E groun d F Ge a lawn d GO mij Default text Number Floating point number Background color String System Window Color Comment Preprocessor block Character Language reserved word VWaST AFI Margin No margin M Auto indent Fixed margin MW Print line numbers M Display line numbers W Track end of
207. tion for documentation purposes VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 85 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Developing a Fabric Module Definition Module Instance Adding a Module Instance using the Context Menu To add module instances to a module using the context menu Inthe fmx XML Tree View right click on Module Instances Select Add Module Instance BE Simple SP Simple SP 1 Simple SP1 tm Simple SF 1 Hoe Parameters Ports ce Mets see Tasks m Module Instances Expand Module Instances Ctrl E Collapse Module Instances Ctrl L lol x Add Module Instance Edit Module Instances F2 k In the Fabric Module Module Instance dialog select the Type from the Type combo box list This list shows the available modules in the current Workspace in the VaST module library and in any user module libraries Fabric Module x Module Instance Properties Instance Mame New Modulelnstance Type Required version VirtualPlathorm Simple T imer Number Of VastU artConsole Class VastapStdBusb ridge Vastipllock VastapD mac Sub Class Vastaplntaarm ee Vastaplrvert Description VastGpReset en a Oe ee 86 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Module Inst
208. to run the simulation When you create a module COMET automatically adds a target setting to contain target properties such as the type of executable and the location of the executable image You can load a target image into any module that has been built with a target image loader interface These include VPMs and some other modules such as memory devices Note that you can target debug only target images loaded into VPM instances x El Workspace Simpley SP a Simple SP1 Folders Sy Source Files H E Header Files H E Generated Files i fn Configurations ao Tarots a TargetTest Bl om VirtualPlatForm Ea sieve_demo Ea SimpleTimer ee Timer Test Workspace a YaST Modules To add a target Right click on Targets and choose Add Target from the context menu To delete a target Right click on the target icon or name and choose Delete Target from the context menu To change the name of the target or its Active status Right click on the target icon or name and choose Target Properties from the context menu To add target information Right mouse click on the target icon or name 124 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Setting the Target Executable Configuring Build and Runtime Options x El Workspace Simple SF EEA Simple SP1 fa Folders o B Source Files H 4 Hea
209. to the FmxReport for that module Name column entries link to the detail entry for that name d Nets Name Type NumberOf Descnpton Connections Port or Net View Types an StdClock Module net StdBus1ClockNet 4 Std Bus iNet E StdBus Module net StdBusinet 4 Std Logic ONet r StdLogic Module net StdlogicONet 3 For example click a link in the Name column of the Nets summary to see the detailed entry for that Net VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 101 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Views and Reports Viewing Module Definition and Prototype Configuration Reports d StdBus1ClockNet NZP Type NumberOf Description Port or Net View Types Net an Std Clack Module net StdBusiclackNet Port Connections GenericMemory1 BusClock Port or Net connection ta StdBusi1 is ee ARMSZ6EJS1 DataBusClock Porto r Net c nection to StB JUS Clo kP e et lockt IL InsthusGlock Porto t Netconn ection to a H cke otddus1 Bu ock Fort or Net connection to StdgBus1 locket In the Net detail you can view a list of all ports to which the net is connected You can view a similar display in Port detail Click on a module instance link in the Connections list to move to the detail for that Module Instance ARM926EJ 1 ModuleType Required ersion NumberOf Description ARMS26E 5 Instance Ports Port Description C
210. ts 30 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring the CoMET System Engineering Environment Getting Started Tool Locations Configuration Settings You can specify the location of the ancillary tools that you use in conjunction with COMET for building debugging and executing the Virtual System Prototype CoMET Configuration gy x General Editor Options Tool Locations User Locations ML Tables Modules Environment C Program FilesW4AM AaDSy1_ 2 AmE Gee Cdb C Program Files Debugging Tools for Windows FinSim ee cWusrvast cometh Goc Matlab Mipse face ModelSim C Program Files Modeltech_6 Uc Marc C Program Filess Microsott Visual Studio WET 2003er FlatformS dk C Program Files Microsott Visual Studio NET 20034 M c Plattorm SyshemL c uerwastycomets S ysteml WOOUE lface Edit Clear Tool Locations Configuration Tab MsVe Microsoft Visual C On CoMET installation COMET detects the most recent version of MS Visual C If version 8 net is installed this is automatically detected and becomes the default value for MsVc If you install COMET over an earlier COMET installation it takes the existing setting for the MsVc parameter You can change the version manually by altering the value of this parameter COMET supports MS Visual C versions 6 7 8 an
211. ttribute set to True When the value is False a drop down list allows it to be changed to True CIF Project Build Configuration Properties S Project i x Configuration Properties Type Mode Debu o Path feDebug O pine DNOVA2 DMODULE DPRE_SYMLINK_INIT_RE Link Options PO listing File SimpleTimendef a Achye Tue Cancel Apply Help Ei A CIF Project Build Configuration has the common set of properties See Common Build Configuration Properties page 110 VasST SYSTEMS TECHNOLOGY Confidential and Proprietary 111 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring Build and Runtime Options Setting the Build Configuration VBus Standalone Build Configuration Parameters S Project x Configuration Properties be Oe ar ae ee Mode Debus o Path MovaDebug a C Options pooo OS Verilog Options PO Link Options PO Tab File fF Define File Active Tue Cancel Apply Help E See Common Build Configuration Properties page 110 Verilog Options Command line options for the Verilog simulator or compiler Tab File Specifies the PLI Program Language Interface Table tab required for this build See Tab files are no longer required page 112 Tab files are no longer required The PLI Program Language Interface Table tab file was used in conjunction with Verilog or NOVA modules using Behavioral C PLI functions
212. ubic ss lt Ss Pox Access Public Y Description Name Type the desired name for the Parameter Type Select the type of the parameter Allowed values tBoolean tInt32 tInt64 tWord32 tWord64 tString tAltList tMultiList Types are defined in vast5 home ampi include vast_std_types h To create a drop down menu create a parameter of type tAltList Allowable Values Specify allowable values for the parameter Used only for tAltList and tMultiList types Type a comma separated list of allowable values for the parameter Validation by the Allowable Values list is implemented for parameters of type tAltList only Value Type the default value for the parameter This may be overridden by parameter overrides Type the desired default value of the parameter Values can be specified using macros and arithmetic e g 2 M 24K 12 If you leave Value blank the corresponding Parameter Override generated in the pcx file has the value No Valid Value You must 78 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Sub Parameters Developing a Fabric Module Definition provide a valid Parameter Override value for successful simulation Parameter Values are not validated until simulation time Parameter Values can be modified in Parameter Views See Parameter Views page 98 Fmx Access Determines access to this parame
213. ulation Support Verilog Co Simulation Support Tax StdLogicw Pao SeaLogiek Pat StdLogicH S L P StdLogicH P su StdLogic SX StdLogiex StdLogic0 gt Sul StdLogiel SidLogicX e If StdLogic is selected for a Verilog input port then the StdLogic states are mapped to the Verilog states as follows StdLogicU StdLogicX StX StX StdLogic0 St St i u u u StX PuO StdLogic0 Stl StX al ax ul StdLogicW ul uX StdLogicZ StdLogicW StdLogicL StdLogicH StdLogicUnkown O StX e For details on how to select Fabric port types for mapping with Verilog ports see Selecting a Fabric Port Type for a Verilog Port page 188 0 l Z X 0 l H P P P 182 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Verilog Co Simulation Support ModelSim HDL Co Simulation Support Running a Verilog Model on CIF Tool Locations Configuration Settings for Verilog Model In CoMET Configuration Tool Locations tab set ModelSim to point to ModelSim home directory See Tool Locations Configuration Settings page 31 CoMET Configuration g x General Editor Options Tool Locations User Locations MIL Tables Modules Environment Arle C Program Files4AM ADSy1_ 2 Arme lace Cdb C Program Files Debugging Tools for Windows Fingin lee cAusrvastycometh acc Matlab Mipse lace Mode
214. ulation between the software and hardware components Higher OIL means better simulation performance but possibly late response to interrupts Units are nanoseconds ns Config File The Architecture Configuration File for this project Supported simulation engines This version of COMET supports only Noval for VBus and Fabric projects Nova2 Nova CIF for Fabric CIF projects and Mentor Graphics ModelSim for Fabric VHDL projects Other hardware simulators such as FinSim and NCSIM maybe supported in a later version 120 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Modifying Parameter Values in the Prototype Configuration File Configuring Build and Runtime Options Modifying Parameter Values in the Prototype Configuration File A VSP Virtual System Platform consists of a hierarchy of module instances each of which may have Parameter Override elements For each module instance the corresponding module may itself contain module instances This module instance hierarchy can be represented as a tree structure The Prototype Configuration pcx file provides access to Parameter Override elements corresponding to Parameter elements for each module instance in the tree The pcx file is evaluated at simulation time For details on the Parameter Override element see Parameter Override page 89 For details on the Module In
215. value of a hardware constant can not change The value of a hardware variable or hardware constant A fundamental entity of a module such as a register wire or integer The value of a hardware variable can change Its value is the value last assigned to it The creation of an instance of an object module In a network a synonym for delay 1 e an expression of how much time it takes for a packet of data to get from one designated point to another In a computer system latency is often used to mean any delay or waiting that increases real or perceived response time beyond the response time desired Specific contributors to computer latency include mismatches in data speed between the microprocessor and input output devices and inadequate data buffers A self contained module such as a platform or peripheral device See module The definition of a hardware element within a Virtual System Prototype such as a Virtual Platform a VPM a Virtual Bus or a peripheral device A module describes hardware behavior functionality interconnection and hierarchical structure Modules represent hardware elements and interconnections and can be instantiated within other modules Each module generally but not necessarily describes a single hardware subsystem See device Any device that is not part of the essential system the processor memory and data paths but is situated relatively close by The connection points of
216. w T Workspace z YaST Mod 4 Bus Connection View 4 gt SPE Modules Windows Clock Connection View TE ara Logic Connection View ProcessFabricModules processed VastGpClock in c usr vast come gp clock dll a Tasks Properties Girl R 2 module instance s has been added to Top Type SimpleVSP1 Build completed successfully Output Windows buat Status Bar iog Bald a Find in Fies 3 Software E Loaded Modes For Help press F1 ln 1 Coli NUM h CoMET SEE System Engineering Environment The CoMET System Engineering Environment contains the following elements Menu Bar The menu bar displays the commands you use to build debug and simulate a Virtual System Prototype Besides the standard File Edit View Window and Help menus additional menus such as Workspace and Debug provide access to utilities specific to COMET 12 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST The CoMET System Engineering Environment Getting Started Tool Bar The tool bar provides quick access to commonly used commands You click on a button in the tool bar to carry out the action represented by that button Some tool bar buttons have a drop down arrow to the right of the actual button Click on the drop arrow to display options associated with the button If you move your mouse pointer over a button a tool tip
217. w allowing navigation of the new module library To refresh the contents of the module window choose Tools Rescan Modules 38 VaST SYSTEMS TECHNOLOGY Confidential and Proprietary May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Configuring the CoMET System Engineering Environment Getting Started aST Modules RE El kg vasT Modules B Auxiliary AS vast_uart_console 4S Bus Sy StdBus H E StdBus_Bridge 5 ba Gp H j Clock H E Dmac H E Intec Arm HE Invert H E Reset Sy StdLogic Sy StdLogici fl Timer fy Uart S Memory neneric Memory a T vpm H E Armii HE Armztdmi HE Arma26ejs H E Armo4bes H E Armo4 es4 3 1 HE 5c1200 a YaST Modules User Modules NOTE _CoMET must run each dll to extract the information required to build the library If there is some issue preventing a dll running successfully the library build process may not complete successfully VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 39 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Configuring the CoMET System Engineering Environment Environment Configuration Settings You can view the Windows system environment and add to or edit the environment variables CoMET Configuration Gg x General Editor Options Tool Locations User Locations ML Tables Modules Environment A
218. w is docked you have the option of selecting to automatically hide the window To do this click the Auto Hide button on the right corner of the tool window CoMET 5 C astProjects Simple SP Simple SP wkx File Edit View Workspace Debug Tools Window Help O GHG B E B l04 Workspace El Workspace Simple SP Ef Simple SP1 l l i H Folders i an Ae Source Files at I a SimplevSP 1 vc j inclui Simpley SP 1 Frovx Auto Hide button on a Tool window To display an auto hidden tool window simply scroll the pointer over the hidden tool window tab CoMET 5 C astProjects Simple YSP COMET 5 Ch YastProjects Simple YSP s Fie Edit View Workspace Debug 1 File Edit view Workspace Debug TER S E IE A Eiin TES S E IE S Etim E Workspace Simnpley SP Ea Simple SP1 j Folders B Source Files Simple SP 1 c a Simple SF 1 Fix sanpo Sea Ef aoedsysoyyy l Sa MpOy SBA EI aagdayona l To turn off the Auto Hide option on an auto hidden window click the Auto Hide button again VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 25 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Getting Started Configuring the CoMET System Engineering Environment Configuring the CoMET System Engineering Environment You can modify the configuration of the COMET System Engineering Environmen
219. w you prefer on opening an fmx or pcex file See General Configuration Settings page 26 COMET remembers the current view of each open document when you close a workspace so when you open the workspace again the document appears in the last view chosen Table views are of two main types e Parameter views e Connection views These types are discussed in detail below Changing Column Order You can drag and drop a column label to change the order of columns This is useful for example if you wish to position the InstanceName column next to a column on the far right Changes to column order are not preserved when CoMET is closed VaST SYSTEMS TECHNOLOGY Confidential and Proprietary 97 May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Views and Reports Using Table Views Parameter Views A parameter view shows a list of parameters filtered on parameter type For each module instance there is a row in the table identified by the InstanceName in the left column The second column shows ModuleType The remaining table columns are the parameter types specified in the XML table configuration See XML Tables Configuration Settings page 33 The Memory Parameter View shows a list of all parameters belonging to the module or its submodules filtered on the parameter types e Read e MemoryWidth e Write e Tunneling e StartAddress e NoOfMemoryPages e MemorySize e PageSize The Bus
220. written agreement with VaST Developing a Fabric Module Definition Ports Ports A Fabric Module element may contain a single Ports element This element is a container for all Port elements Child Elements The Ports element may contain one or more Port elements Port Ports Port A Port is a connection point for connecting an instance of the current Fabric Module to a Port element of the parent platform to Port elements of child Module Instances or to Net elements within the same platform A Port has no child elements Fabric Module q x Fort Properties Hame Type Number OF f Direction Input Class IN One Sub Class Description Fabric Module dialog Port tab Properties panel Name Type a name for the port See Choosing Names page 67 You can create a Port array See Arrays page 67 Type Select a net type The Port and any Net or Port to which it connects must be the same net type Allowable Values StdBus StdClock StdLogic CanBus StdVector32 Number Of You can create a Port array by specifying a dimension in this attribute Each member of the array shares properties but may be independently connected See Arrays page 67 Allowable values Positive integer Default 1 A single Port not an array Direction To be used for assisted connection in future The value is currently ignored Class Reserved for future use Sub Class Reserved for future use Description You may add a des
221. xcept as expressly authorized in a written agreement with VaST Views and Reports Viewing Module Definition and Prototype Configuration Reports Task Detail a8 Memory Descnpton InitFuncton ExitFuncton Task Function Task name Memory MermoryInitTask Instance MemoryExitTask Instance MemaryTaskFunction Task Port or Net Views Name NumberOf Type Description B 2 Bus NetSlave B m BusClock NetSlave E T Reset NetSlave Fmx Report Errors and Warnings Click the Errors and Warnings link to see a list of errors and warnings Not all issues reported are errors depending on whether the module is a Platform VSP or Peripheral Device Warnings link to the detail for the related element ft Errors and Warnings Unconnected Ports The list below shows any unconnected Ports In Platform or YSF modules unconnected Ports may be unintentional e LooseFort Unconnected Nets The list below shows any unconnected or singly connected Mets In Platform or YSF modules unconnected Mets may be Unintentional A Wet should connect two or more Ports or Instance Ports Onlyone connection LonelyMet Unconnected Instance Ports The list below shows any Instance Ports not connected or with invalid connections Unconnected Instance Ports may result in a build error e g ERROR EXIT Could not find Fort or Wet in Module YirtualPlatform ARMGYBEIS1 port Reset not connected VastipstdLogicOl port SignalQut invalid connection to
222. y May not be used disclosed or reproduced except as expressly authorized in a written agreement with VaST Index a Context Menu ccccccssseeseceeeeeeesseeseeeeeees 14 creating new source files 00000000000000 130 adding source files cccceceeeeeeeeeeeeeeees 55 D g debugging Batch Mode sesinin an 147 clearing breakpoints in source code 142 CoMET 4 batch files 00000 149 151 continuing EXECUTION cccececceeeeeeeees 143 breakpoints debugging source COdE cceeceeeeeeeees 139 elearning cnd 142 interrupting execution flow 142 continuing execution eee ceeeeeeeeeeee 143 KC YS EI E E E 157 managing oe c cece eee ccccccccceceeeeeeeeeeeeeseeeeeeeees 143 managing breakpoints 00000000000000000 143 SEINE aeniei senk EARANN ERARE 142 setting breakpoints in source code 142 build output Window cccccccccsseeeseeeeeees 138 software WINdOW cccsssssseeeeeeeeeeeeeees 141 building the project ccccccccceeeeeeeeeeeees 137 Disclaimer aries enstcdocexetronecuansosaciesvenemussedonnseatones ii Document Window sssseeeeeseeeeeeeeees 14 C IG YS NEE E EE E 156 CoMET E SUpport SETVICES ssssseoeesssseeeeessssseeeerees 42 system engineering environment 12 Editing System Engineering Toolset 5 CA ne ne ee nn eee eee 136 156 wep page orreri eee eee 42 editor CoMET Componentts

CoMET 5.14 User Guide

Contents

Download Pdf Manuals

Related Search

Related Contents