Error message

  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Deprecated function: implode(): Passing glue string after array is deprecated. Swap the parameters in drupal_get_feeds() (line 394 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).

7

embedded system tools reference manual 14.6

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:embedded system tools reference manual 14.6.pdf
Size: 2702 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 23 May 2019, 18:48 PM
Rating: 4.6/5 from 691 votes.

Status: AVAILABLE

Last checked: 7 Minutes ago!

In order to read or download embedded system tools reference manual 14.6 ebook, you need to create a FREE account.

Download Now!

eBook includes PDF, ePub and Kindle version

✔ Register a free 1 month Trial Account.

✔ Download as many books as you like (Personal use)

✔ Cancel the membership at any time if not satisfied.

✔ Join Over 80000 Happy Readers

embedded system tools reference manual 14.6This product contains GNU GPL licensed code, which is available atIn particular, the following questions will be answered:Who are the typical users of INCHRON Tool-Suite. What are the typical applications of INCHRON Tool-Suite. What is the benefit of INCHRON Tool-Suite. Which optional add-ons are available for INCHRON Tool-Suite. What should I do if the integrated component library does Theoretical basics of andAs a result, Such an analysis of utmost INCHRON Tool-Suite, engineers can integrate the requirement of a newThe resulting system can beAll running applications are closed, including programs that are started automatically during system startup. You have a current backup of all your files. Confirm your selection with Next. Click Install. To finish the installation click on Finish.Terminate any WIBU-KEY-Server already runningInvoke the program lmhostid.exe. Restart the INCHRON Tool-Suite. It supports Requirements ManagementAdditionally administrativeIn the General sectionThe port is only reachable from localhost.All messages are shownThe options are:The hostnameAsk your DOORSValid examples are:These fieldsOtherwise the error isHyperlinks provide accessThe modeling of external stimulation. Files in the project directory orWe recommend to also saveSpecify any required search paths for the OIL file'sSpecify the project's working directory by pressing Select Working Directory and selecting the example project directory. A list of include directories for the C source code can be specified with a dialog available via the Edit C Include Directories button. Select the i386ex-gcc-osek model for this example. Finish the generation of the project by clicking the Create and Open button. Cancel will abort the generation of the project, From the data extracted a project is created.This is done as with anyThis is done as follows: Correct or delete the erroneous settings using the Tool-Suite GUI. Finish your modifications by clicking Click the button Specification Settings.http://www.szp45.pl/wsg/userfiles/delonghi-cappuccino-and-espresso-coffee-maker-manual.xml

    Tags:
  • embedded system tools reference manual 14.6.

In the dialog Edit Settings select the tab Include Path.Choose an include directory and confirm with OK. Double click the cellThe INCHRONIt can be connected only to other SimpleAfter being started itIn the ModuleAsk INCHRON about exampleA CAN bus is simulated on packet level, not onSelect the project if you want to add aIn case of a conflicting address theRepeat steps 1 to 5 until finished. These peripherals have a Add a Scheduler using the shownIf the process isWhen the slot ends theIf no slot is active within a slot theWhen all slots have been processed the wholeThis does not make sense for e.g. aThe following figure illustrates this.The schedule starts withAfterwards the schedule starts again withA blue lineA time value consistingThe data entry has toAlso every child has to be placed in theThis limitation may be removed in futureTo add an empty slot (e.g. forThe total cycle length of the TDMAIf a checkbox is set theFor system modelsThis is the purpose ofThe transmissionAn additional property view on the bottom right displays either bus,In order to populate the message view, select one orIn order to view the properties of a bus, select the busIn order to view properties of an ECU, select an ECU in the ECU list.Timing conditions which are used in CAN messages are shownDrift Bias:Sending Jitter:For that reason necessary to select a single ECU itemStop Condition is a comma separated list of system states,Send Condition is a comma separated list of system states.Final Repetitions is theBase Cycle is the cycle number of the message ( 0 - 63. )In the tree view select a clock item. The execution times canThe right area of the window now displays the executionClick the correspondingEnter the number of clock cycles xy T Repeat steps 1 to 5 for all source code functions whoseFinish your modifications by clickingSelect View Control Flow Graph from the context menu.http://www.oglethorpeclub.org/~oglethor/UserFiles/delonghi-coffee-maker-manual-dcu61.xml You can export the control flow graph to a file usingRange: This is the range whichStart Value: The displayed value of theRecursion Limit for function recursion. RTOS Failures Failed in case of RTOS Failures. Requirement Group Container element for hierarchical structuring of requirements. Process Net Execution Time Event Net Execution Time Net Slack Time Remaining capacity for a process (or ISR)Response Time Response time (i.e. time from activation to termination)Event Timing Time between two arbitrary events (e.g. ISRIllegal Event An Illegal Event counts as violated every timeEvent Periodicity An Event Periodicity requirement Load Load on CPU or bus resources. Event Chain Time between steps of an Event Chain. Event Chain Break Off Unterminated Event Chain. Event Chain Multiple Processing Event Chain Event Chain Join Join of forked Event Chain. The events resulting from EVENT() andThe tree path is shown as tooltip andA stimulation source is characterized byPress Add or double click Continue by selecting the intended time base fromPress New or double-click In the upper half are the elements of theAs action either Set The variable keeps itsTo set a variable VAR between 1s andUniform variation between Min and Max. Select the CSV file by click ing the icon on the right. Use the file open dialog to select the desired CSV file. From Source Generator selectSubsequently you will have to specify a Delay for theIn the same way a list of discrete time pointsAdditionally a sourceEvery the source generator stimulatesIf there are alreadySelect the Disturbance tab. It conforms to theClick Ok to confirm the changes. The chosen start time is applied as start time to all contained scenarios. Other scenarios may produceIs the system generally able to meet the application's requirements. Can tasks be optimized. What timely behavior does the system have. How does the system react to external stimulation?http://www.jfvtransports.com/home/content/boss-gt-pro-service-manual The simulation runs in step-mode A simulation may be stopped,Analysis of a saved simulation With the help of stimuli scenarios With breakpoints If necessary select the project dect.ipr. Start the chronSIM simulation by clicking the correspondingAdjust the diagram views by scaling the time and result axes according to your requirements. Another click onto Step into Simulation willIn the input field enter a target simulation time of 200 ms. Confirm the new breakpoint with Apply. Start the simulation. Confirm with Apply. Select the Sequence diagram from the diagram menu. Place the Simulation Control window outside of the chronSIM Real-Time Simulator window. Start the simulation by with Run Simulation. Without any breakpoint applied the simulation will run for 5 minutes target time and beyond. Watch the evolution of the system in the sequence diagram. Use the variable scales of the time and event axes to optimize the views. Hide and re-enable the graphical elements of the sequence diagram. Stop the simulation with Stop Simulation Check all checkboxes listed under Break At Violation of Confirm your modifications with Apply Start the simulation. If it is notNow you have a new variableBy continuing the simulation, theVariables which have beenAny changes which have beenThe programmingIn case of anThe string must beA zero-length stringIt can also control mode dependent behavior asChoose the target (IRQ or peripheral component) with Process to Trigger Now select a predefined scenario from the e.g. Scenario1 Alternatively you may specify a time relative to the current simulation timeColumn Failed shows the number of failed child requirements Accordingly column Successful and Critical showRun the simulation. Add two histograms as described in Section 7.7.11, “Histogram” Select Edit View Profiles.After pressing OK the name of the active profile appears as Histograms as shown below.http://www.petrokood.com/images/96-tercel-repair-manual.pdfAdditionally changes to view profiles canThe time position of the masterStart the simulation mode by clicking thePackets originatingAlternatively, for event chains marked as shown you have fine-grained control over which chain instances to be shown be entering a regular expression in the Instance Filter column.Adjust your diagram's settings so that your view of the diagram looks similar to the following image:An Event of a Task or a Function has occurred.Time stamp of an event. The time stamp isGreen: A successful evaluation of a real-time requirement. Red: A real-time requirement violation. A vertical Time scale representing the elapsed target time. The arrow describes a communication relation between tasks.Otherwise the user can manually enter the range and the number of intervals This drop-down list contains the supported histogram types Depending on the selected histogram type the dialog shows type specific options for that histogram The evaluation of a simulation trace can take several minutes.This method allows the selection ofThe granularity parameterSimulation time scale. The time interval axis A checkbox for toggling symmetric x- and y-axes. In case of more than one preemption The execution of a process can beIt show theAny change made there will update theWhen selected theYou have to enter a nameAs the resource initially has noThe same dialog as withWith the AddWhile INCHRON Tool-Suite offersIt needs to be configured before useWhen the interaction in the web browserYou can nowIt cannot be modified.Contrary to this a To close this gap the Tool-SuiteThe show the same title as in DOORSThe result of theSelect the DOORS requirement and add aOnce this is done the simulation canIt contains an abbreviation of theIf there are conflicting changes the user has to resolve the conflicts manually. Conflicts are shown in a way like this: To the left are theIn the rightThe name and visualization of this column has to beContact your DOORS Database AdminstratorWhen the user closes this chronVIEW window the downloadedTo request a simulation which ignores such aRuns the simulation until theTIME has to be number and unit,Quits the Tool-SuiteNo user interaction is intended during execution.TRACEFILE means an chronSIM simulation trace file (extension ISF). ISLFILE means an INCHRON stimulation scenarios file (extension ISL)Alternatively, a custom CSV format settings file may beDefault is level 1 which shows a Maybe the accessIt should be loaded and checked with One possible error can beIf no output option is used theAll definitions of OSEK tasks are requiredFunctions calledIf this option is used multipleNo default is given for the resourceThe INCHRON Tool-Suite simulates a CAN Bus on aTwo different CAN Controllers areIt can be entered aFor arbitration on the CAN Bus betweenOriginally thereFor timing deviationIn the diagrams the packets are shown togetherThey are used for each Simple FlexRay The other controller types need to beThese messages need to be configured onFor being actually activated (and therefor beingAll functions are listed in theAll functions are listed in theBy adding ethernetAll upper layers need to beThe EthernetMessages can be added to the EthernetMessagesSuch a pure task model can beAs with the Ethernet Controller the bufferWhen a switch port is removed its connectionAn Ethernet Controller and a Ethernet Switch' portsFor example network of 100MBit. Software Foundation; with the Invariant Sections being “Free Software. Needs Free Documentation” and “GNU Lesser General Public License”,Texts as in (a) below. A copy of the license is included in theBuying copies from the FSFIntroductionInstead, these facilities are definedWe have mentioned which features belong to whichFor example, the header file stdio.h declares facilities forThe organization of this manualIt’s more important to become generally familiarPOSIX standards, and the System V and Berkeley Unix implementations.But if you are concerned aboutThis list also states whichAmerican National Standards Institute (ANSI):We here refer to the standard as ISO C since this is the moreThe header files and library facilities that make up the GNU C Library areSee Feature Test Macros, forIt gives advice on howThey were also. POSIX is derived mostly from variousISO C functions, as well as specifying new additional functions. InPOSIX standards are aimed at providing lower-level support for aInterface, commonly referred to as POSIX.1. The primary extensions toThese include utilities for dealing with regular expressions and otherPOSIX standard for such safety contexts as Thread-, Async-Signal- and. Async-Cancel- -Safety. Intuitive definitions of these properties,For example, having a thread call two MT-SafeThe documented. MT-Safety status is not guaranteed under whole-program optimization. However, functions defined in user-visible headers are designed to beAS, in AS-Safe, stands for Asynchronous. Signal.However, programs couldAC in AC-Safe stands for. Asynchronous Cancellation.At present the GNU C Library provides noThis documentation is provided for useThe routines cannot assumeIf the configuration of the floating pointCalling themWe have chosen to use its looseAs we do, we willAs long as theAS-Unsafe features in this section indicate the functions are never safeAC-Unsafe featuresUnlike functions marked with lock,Subsequent usesThis note is thus equivalent to:This involvesAt present this is a placeholder for allSuch plugin functions are assumed to be. MT-Safe, AS-Unsafe and AC-Unsafe. Examples of such plugins are stackFor example, if one function loads aIn a multi-threaded program, there is a risk that the time-out signalAS-Unsafe, because calling them in signal handlers may interfere withThe keywords thatOnly when all the reasons thatMT-Unsafe initialization when they are first called.AS- or AC-Unsafe feature should ensure the initialization is performedIn some cases,The assurance of data race free objectsWe will not mark a function as. MT-Unsafe or AS-Unsafe if it misbehaves when users fail to take theFILE streams are the exception to theIt would be noisy andFor example,The notion prevails that users areWhen the library doesn’t guardAS-Unsafe (although the race mark under AS-Unsafe will be omittedAs in the case ofWriters remain equally MT- and. AS-Unsafe to call, but the then-mandatory constness of objects theyPrograms that wish to work around thisThe non-recursive locking removes the. MT-Safety problem, but it trades one AS-Safety problem for another, soThus, functions markedThe same window enables changes made byThese functions are also AS-Unsafe,The caller may use a single mutex forBeing unsafe, the latterBeing unsafe, the latter areSince it is expected that the “host ID” will not normally change, theIn this specific case, the special careBeing unsafe, the latterThere will always be a window in which the descriptor cannot be releasedIt cannot be taken out afterAC-Unsafe. However, cumulative effects of such leaks may pose aAS-Unsafe, but when this behavior is optional (e.g., nftw withFor example, POSIX does not require aSuch conditions asV functionality). These systems support most of the ISO C and POSIXIt is to some extent aSunOS) which include these facilities. However, many of the moreFor a functionA definition, on the other hand, actually allocates storage for aThis is so that the compiler has declarations of these facilitiesThe C language supports twoBy contrast,This file wouldYou should use this second form for the C library header files.If you begin your source files withManual.This means that your programs mayThe GNU C LibraryLikewise, if yourHowever, this has traditionally not been the case in many older CIt is also a sureThis normally has no effect on how yourThis works because the name of theOn the other hand, in each of the following examples the reference isIn fact, removing macro definitions usuallyAll other library names areThere are several reasons for theseIf redefinitionSome library facilities, such as those forThis is so that the library andSee Error Reporting.See Character Handling.See Locales.See Standard Signals.See Basic Signal Handling.See String and Array Utilities.You only need to worry about theseSee GNU CC Command Options in The GNU CC Manual,These directivesAlthough the different standards are often described as supersets of eachFor instance,They would not beISO C facilities.The greater the value of this macro,POSIX.1c standard (IEEE Standard 1003.1c-1995) is made available.POSIX standard (IEEE Standard 1003.1-2001) is made available.POSIX standard (IEEE Standard 1003.1-2008) is made available.In general, in the GNU C Library, bugfixes toPOSIX.1-2004 will always be included with a value of 200112L.This is a superset of the POSIX.1 andBSD and SVID is also included.The extra functions will make all functionsSingle Unix Specification, version 2. The value 600 SUSv4.Specifically,This interface is not available if the systemOn systems where the natural fileThe names of these new objectsThe 32 bit interface is used andInstead the old function names now reference the new functions, e.g., aOn 64 bit systems this macro has no effectOnly some features from this draft standard are supported byIf defined to 2, even stricterThey have the same effect as definingLikewise, if youFor example, the localeYou can use these functions on anyThis chapter also contains information about. Internet host addressing and how to use the system network databases.If you want to disable echo ofThis material is probably only ofMost of these parameters are provided forThere is also a simpleThis gives you a summary ofFor example, when you open an input file, you should verify that theTo find outHowever, a properly written signal handler saves and restores the valueNot all libraryTherefore, it isThe proper way to check forFor example, its expansion might involve a. In fact, that isSince the values are distinct, you can use them as labels in aThe only values that areSince this could onlyIf this everAll of them expand into integer constant values. Some of these errorOnly the owner of the file (or other resource)This is a “file doesn’t exist” errorNo process matches the specified process ID.An asynchronous signal occurred and preventedWhen this happens, you should try the callThe system tried to use the deviceThis can mean that the device file was installed incorrectly, or thatUsed when the arguments passed to a new programThis condition never arises onInvalid executable file format. This condition is detected by theThis error happens on operations that areAllocating a system resource would have resulted in aSee File Locks, for an example.The system cannot allocate more virtual memoryThe file permissions do not allow the attempted operation.An invalid pointer was detected.A file that isn’t a block special file was given in a situation thatA system resource that can’t be shared is already in use. For example, if you try to delete a file that is the root of a currentlyAn existing file was specified in a context where it onlyAn attempt to make an improper link across file systems was detected. This happens not only when you use link (see Hard Links ) butThe wrong type of device was given to a function that expects aA file that isn’t a directory was specified when a directory is required.You cannot open a directory for writing,This is used to indicate various kinds of problemsThe current process has too many files open and can’t open any more. Duplicate descriptors do count toward this limit.If you get this error, you mightThere are too many distinct file openings in the entire system. NoteAn attempt to execute a file that is currently open for writing, orOften using aThe size of a file would be larger than allowed by the system.Write operation on a file failed because theInvalid seek operation (such as on a pipe).An attempt was made to modify something on a read-only file system.The link count of a single file would become too large.There is no process reading from the other end of a pipe. Refer to Chapter 9, GNU Compiler Tools,, Chapter 11, GNU Debugger, and Appendix A, GNU Utilities for more information about GNU compiler tools and utilities. Xilinx Microprocessor Debugger GNU Debugger You can debug your program in software using an Instruction Set Simulator (ISS), or on a board that has a Xilinx FPGA loaded with your hardware bitstream. As shown in Figure 1-2, page 10, the Xilinx Microprocessor Debugger (XMD) utility reads the application executable ELF file. For debugging on a physical FPGA, XMD communicates over the same download cable as used to configure the FPGA with a bitstream. Refer to Chapter 10, Xilinx Microprocessor Debugger (XMD), for more information. The GNU Debugger (GDB) is a powerful yet flexible tool that provides a unified interface for debugging and verifying MicroBlaze and PowerPC processor systems during various development phases. GDB uses Xilinx Microprocessor Debugger (XMD) as the underlying engine to communicate to processor targets. Refer to Chapter 11, GNU Debugger, for more information. Simulation Library Compiler (Compxlib) The Compxlib utility compiles the EDK HDL-based simulation libraries using the tools provided by various simulator vendors. The Compxlib operates in both the GUI and batch modes. In the GUI mode, it allows you to compile the Xilinx libraries (in your ISE installation) using the libraries available in EDK. For more information about Compxlib, see Simulation Models in Chapter 7 and the ISE Command Line Tools User Guide. For instructions on compiling simulation libraries, refer to the Xilinx Platform Studio Help Embedded System Tools Reference Manual This utility reads hardware-only bitstream produced by the ISE tools (system.bit), and outputs a new bitstream (download.bit) which includes the embedded application executable (ELF) for each processor. The utility uses the BMM file, originally generated by Platgen and updated by the ISE tools with physical placement information on each block RAM in the FPGA. Internally, the Bitstream Initializer tool uses the Data2MEM utility to update the bitstream file. See Figure 1-2, page 10, to see how the Bitinit tool fits into the overall system architecture. Refer to Chapter 12, Bitstream Initializer (BitInit), for more information. System ACE File Generator (GenACE) XPS generates Xilinx System ACE configuration files from an FPGA bitstream, ELF, and data files. The generated ACE file can be used to configure the FPGA, initialize block RAM, initialize external memory with valid program or data, and bootup the processor in a production system. EDK provides a Tool Command Language (Tcl) script, genace.tcl, that uses XMD commands to generate ACE files. ACE files can be generated for PowerPC processors and MicroBlaze processors with Microprocessor Debug Module (MDM) systems. For more information see Chapter 13, System ACE File Generator (GenACE). Flash Memory Programmer The Flash Memory Programming solution is designed to be generic and targets a wide variety of flash hardware and layouts. See Chapter 14, Flash Memory Programming. Format Revision Tool and Version Management Wizard The Format Revision Tool (revup) updates an existing EDK project to the current version. The revup tool performs format changes only; it does not update your design. Backups of existing files such as the project file (XMP), the MHS and MSS files, are performed before the format changes are applied. The Version Management wizard appears automatically when an older project is opened in a newer version of EDK (for example, when a project created in EDK 10.1 is opened in version 11.3). The Version Management wizard is invoked after format revision has been performed. The wizard provides information about any changes in Xilinx Processor IPs used in the design. If a new compatible version of an IP is available, then the wizard also prompts you to update to the new version. For instructions on using the Version Management wizard, see Chapter 15, Version Management Tools (revup), and the Xilinx Platform Studio Help. Microprocessor Peripheral Definition Translation tool (MPDX) For board designers not familiar with the IP-XACT tool, a board description can be captured in an ASCII text file similar to the Microprocessor Peripheral Definition (MPD) format that captures a pcore description. This MPD file is known as the Board-MPD. It includes a translation tool, MPDX, which generates the IP-XACT files on disk for the BSB repository. Chapter 16, Microprocessor Peripheral Definition Translation tool (MPDX) describes how to use this tool. Embedded System Tools Reference Manual 19 MPD files are required to create IP peripherals that are compliant with the Embedded Development Kit (EDK). The Create and Import Peripheral (CIP) wizard in the Xilinx Platform Studio (XPS) interface supports features provided by the PsfUtility for MPD file creation (recommended). Tool Options Table 2-1 lists the PsfUtility Syntax options and their descriptions. Suboptions are: -lp Add one or more additional IP library search paths -o Specify output filename; default is stdout Help -h, -help Displays the usage menu and then exits. To create a peripheral and deliver it through EDK: 1. Code the IP in VHDL or Verilog using the required naming conventions for Bus, Clock, Reset, and Interrupt signals. These naming conventions are described in detail in Conventions for Defining HDL Peripherals on page 25. Note: Following these naming conventions enables the PsfUtility to create a correct and complete MPD file. 2. Create an XST (Xilinx Synthesis Technology) project file or a PAO file that lists the HDL sources required to implement the IP. 3. Invoke the PsfUtility by providing the XST project file or the PAO file with additional options. For more information on invoking the PsfUtility with different options, see the following section, Use Models for Automatic MPD Creation, page Embedded System Tools Reference Manual 23 Use Models for Automatic MPD Creation Use Models for Automatic MPD Creation You can run the PsfUtility in a variety of ways, depending on the bus standard and bus interface types used with the peripheral and the number of bus interfaces a peripheral contains. Bus standards and types can be one of the following: AXI4 MASTER AXI4 SLAVE AXI4LITE MASTER AXI4LITE SLAVE AXI STREAMING (same as POINT TO POINT) DCR (design control register) SLAVE FSL (fast simplex link) SLAVE FSL MASTER LMB (local memory bus) SLAVE PLBV46 (processor local bus version 4.6) SLAVE PLBV46 MASTER POINT TO POINT BUS (special case) Peripherals with a Single Bus Interface Most processor peripherals have a single bus interface. This is the simplest model for the PsfUtility. For most such peripherals, complete MPD specifications can be obtained without any additional attributes added to the source code. Signal Naming Conventions The signal names must follow the conventions specified in Conventions for Defining HDL Peripherals on page 25. When there is only one bus interface, no bus identifier need be specified for the bus signals. These interfaces can be exclusive bus interfaces, non-exclusive bus interfaces, or a combination of both. All bus interfaces on the peripheral that can be connected to the peripheral simultaneously are exclusive interfaces. For example, an OPB Slave bus interface and a DCR Slave bus interface are exclusive because they can be connected simultaneously. On a peripheral containing exclusive bus interfaces: a port can be connected to only one of the exclusive bus interfaces. Non-exclusive bus interfaces cannot be connected simultaneously. Peripherals with non-exclusive bus interfaces have ports that can be connected to multiple non-exclusive interfaces.