Abstract:
A method of operating a computer system to design an application specific processor (ASP) comprises defining a set of peripherals for the ASP which are responsive to stimuli and which communicate with a processor, generating for each peripheral an input file which defines the functional attributes of that peripheral in a high level language with an input data structure, entering the input file into the computer system and operating a modelling tool loaded on the computer system to generate from the input file a register definition file by allocating specific elements of the input data structure to predefined sectors of a register definition table, and using the register definition file to create in silicon the registers of the ASP.

Description:
A computer program listing appendix is included herewith on the accompanying compact discs (two copies provided). The computer program listing appendix includes Annexes 1-6, which are referred to in the specification. The computer program listing appendix is stored in a single file named Appendix.txt. The file Appendix.txt was created on Dec. 5, 2002 and has a size of 27,109 bytes. The contents of the computer program listing appendix are hereby incorporated by reference in their entirety. 
   FIELD OF THE INVENTION 
   The present invention relates to the design of an application specific processor (ASP) and in particular to the use of a modelling tool in the design process to aid the development of architectural modelling. 
   BACKGROUND TO THE INVENTION 
   a design process of an ASP, a model is constructed based on a CPU and a set of peripherals. Three basic types of data are required to be generated before any “real modelling” can start. These can be summarised as follows:
         A set of low level functions and constants to aid the integration of a functional model of a peripheral in a modelling language such as C.   A set of low level functions and constants to aid the testing of the functional model. This code would execute on a simulation of the CPU and would also be useful for functional verification.   A register or data structure mapping, indicating the size of various fields within the register, the reset state and its function.       

   Typically this set of data is generated by hand and must be completed before any real modelling can start. The generation by hand is a laborious task and is prone to all the usual human errors. 
   It is an object of the present invention to make this task less labour intensive, particularly as concerns the register or data structure mapping. 
   SUMMARY OF THE INVENTION 
   According to one aspect of the present invention there is provided a method of operating a computer system to design an application specific processor (ASP) comprising:
         defining a set of peripherals for the ASP which are responsive to stimuli and which communicate with a processor;   generating for each peripheral an input file which defines the functional attributes of that peripheral in a high level language with an input data structure;   entering the input file into the computer system and operating a modelling tool loaded on the computer system to generate from the input file a register definition file by allocating specific elements of the input data structure to predefined sectors of a register definition table; and   using the register definition file to create in silicon the registers of the ASP.       

   According to another aspect of the present invention there is provided a computer system which comprises a processor and a memory, the memory holding a program representing a modelling tool for use in designing an application specific processor (ASP), wherein the computer system comprises an input means for receiving a plurality of input files, each input file defining the functional attributes of a peripheral for the ASP in a high level language within an input data structure;
         the processor being operable to execute the program representing the modelling tool to generate from the input file a register definition file by allocating specific elements of the input data structure to predefined sectors of a register definition table; and   wherein the computer system further comprises an output means for outputting the register definition file in a manner which is usable to create in silicon the registers of the ASP.       

   The input file can be loaded onto the computer from a physical recording device such as a disk. Likewise, the register definition file can be recorded onto a physical recording device such as a disk. 
   The modelling tool described herein ensures that the generation of the above sets of data are completely in sync. It also greatly reduces the time to develop the models of various peripherals by allowing the designer to concentrate on the task at hand—that of the peripheral itself. The tool also makes it possible for novice designers to get started using the peripheral modelling much quicker by not having to learn about the finer details of a particular simulator, for example by removing the need to learn details of how to send and receive data from the simulator to the peripheral. 
   The modelling tool is designed for use in an environment in which a simulator simulates a CPU and a memory system to which peripherals can be added. 
   Peripheral and subsystem support is provided by allowing the user to define a set of functions for each device that will simulate its behaviour. These functions are compiled into a device library by the user, and loaded by the simulator during execution. All the device libraries for the devices being simulated are listed in a device definition file. When the simulator is executed, these functions are dynamically linked with the simulator code. 
   Each device has an address range associated with it in the device definition file. Any load from or store to an address in that range will cause the simulator to execute the appropriate peripheral read or write function instead of a memory access. 
   The following functions are provided in each device library:
         An initialization function which is run when the simulation starts before any application code is executed. This function must set up a structure with the names of the other functions.   A loop function which executes regularly. The loop function is used to define asynchronous or delayed behaviour by the device, such as sending an interrupt. Each device has a loop cycle step variable which defines the frequency of execution, i.e. how many instructions are executed between two executions of the loop function. By default, the loop function is executed after every instruction.   A function for each type of signal expected from the CPU. For peripherals this would usually be one function for Load (called the peripheral read) and one for Store (called the peripheral write). These functions are called by the simulator where an appropriate instruction is executed for an address related to the device. They define any immediate device response to the signal, such as sending back a value when a shared register location is loaded.       

   As an example, suppose that the application running on the CPU executes a load from a peripheral address. At this point the simulator calls the peripheral read function in the peripheral model dynamic library. The peripheral read function returns the data stored at the address and the simulator then places this value onto the stack. 
   A typical peripheral model and its integration within a functional simulator is shown in FIG.  2 . The peripheral is written in a high level language such as C and the code for this model operates upon data structures written in a manner which aids the architecture development. In order for the CPU, and hence code executing on the CPU, to access various bits of state or data, such as a control register, it must read or write to various words in memory. The read peripherals being modelled are memory mapped in the CPU memory space. The states or data structures that are maintained within the model which are visible to the CPU, and hence to the code, must be copied to or from the registers or memory. The simulator has special calls to handle accesses to special areas such as memory. 
   The peripheral model writer declares an area of memory that is to be treated as special, in this case seen, as the registers memory or a data structure memory. When the CPU accesses this area of memory the peripheral model must copy or update its internal representation of the externally visible state. This is usually done by the Read and write functions in the simulator. These functions allow the modelling to proceed in a free and easy manner, without any constraints on how it should be written or how data should be manipulated and only when it is necessary to transfer the data to the outside world is it done so via these functions. The description of the registers and data structure visible to the CPU within the peripheral will be described within the functional specification document for that peripheral. 
   The modelling tool described herein automates the generation of the low level functions, constants and the basis of the documentation by using the data structures specified by the peripheral model. There is sufficient information within the specification of these data structures to generate these low level functions and the documentation, using some basic conventions developed by the inventor. 
   These can be summarised as:
         All accesses to the data structures used within the peripheral model are done via functions. These are Query, and Set functions for each attribute (element) for each data structure.   All accesses to the registers are done via functions with a common interface.   The names of all the functions are derived from the attributes and structure definition of the data structures.   All constant names used to access bits within registers are derived from the attributes and structure definition of the data structures.       

   For a better understanding of the present invention and to show how the same may be carried into effect reference will now be made by way of example to the accompanying drawings. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
       FIG. 1  is a block diagram illustrating the modelling of an ASP; 
       FIG. 2  is a diagram illustrating the CPU to peripheral interfaces; 
       FIG. 3  is a diagram illustrating the function of the modelling tool; 
       FIG. 4  is a diagram illustrating how the files are derived from the data structure of the input file using the modelling tool; 
       FIG. 5  is a flow chart illustrating the high level operation of the modelling tool; 
       FIG. 6  is a sketch illustrating the use of the files in a simulation; and 
       FIG. 7  is a sketch illustrating how a functional model can interact with a real simulation. 
   

   DESCRIPTION OF THE PREFERRED EMBODIMENTS 
   An application specific processor is modelled as a central processor (CPU)  2  and a set of peripherals  4 . The CPU  2  is modelled with the basic elements of an interrupt handler  6  and memory  8 . A set of applications running on the CPU are denoted by the process circle  10  labelled APPLS. Each peripheral  4  is modelled with an internal interface  12  between the peripherals and the CPU  2  and an external interface  14  between the peripheral and the “outside world”, that is external of the ASP. At the time of modelling the ASP, it is not known whether or not the peripherals will in fact be implemented in software, hardware or some combination of both. However, whether finally implemented in software or hardware or some combination of both, the peripherals  4  represent how the central processor  2  cooperates with the external environment. The external interfaces  14  receive stimuli S from the external environment and generate responses R in response to the stimuli. These are carried by the external interface  14 . The internal interfaces  12  carry state information and data between the peripherals and the applications  10  running on the CPU  2 . This is described in more detail with reference to FIG.  2 . 
     FIG. 2  illustrates a single peripheral  4  which is to be modelled as a plurality of peripheral processes P 1 ,P 2 ,P 3  etc. The CPU  2  is shown only with its applications  10  and a register bank  16 . The register bank  16  represents a particular area of memory which may be modelled as registers or a conventional RAM which is dedicated to activities of that peripheral. A number of different applications may be running on the CPU  2 , denoted APP 1 ,APP 2 , etc. The applications  10 , running on the CPU are able to write data to the register bank  16  along the write path  18  and can read data from the register bank  16  along the read path  20 . These register read and writes are simulated as CPU Read/Write functions. In addition the peripheral  4  needs to be able to receive data and state from the register bank  16  and to write data and state to the register bank  16 . This is accomplished by the interface  12 . The modelling tool described herein is valuable for implementing the interface  12  in the modelling phase, the simulation phase and the implementation (silicon) phase of the design process. It is not a trivial matter to model, simulate or implement the interface  12 . In designing an ASP, the peripherals  4  are modelled in a high level language such as C. One of the facets of that language is that the data structure which is utilised is written in a manner which aids architecture development in particular in terms of its portability between environments. In particular, it allows the definition, modification and access of individual elements very easily, regardless of the length of the element. This is a particularly useful feature when designing or modelling because it means that the length of elements can be altered without requiring a complete revision of the modelling code. C also allows very simple access to an element, regardless of its length. However, this facet of C and other high level languages creates a practical difficulty when the code developed in that language has to be simulated with applications running or a conventional CPU and using fixed length registers. The tool described herein provides a mechanism for greatly simplifying this task. 
     FIG. 3  shows in general terms how this is achieved. 
   An input file is created for each peripheral  4  in a high level language such as C using an input data structure compatible with that language. That input file defines the interface behaviour of the peripheral  4  with respect to the CPU. The architect determines the responses R of the peripheral with respect to external stimuli S. A modelling tool  24  generates automatically from the data structure defined in the input file  22  a documentation file  26 , an interface functions file  28 , and a test functions file  30 . 
   The interface functions file  28  contains a set of “glue” functions which are derived from the individual elements of the data structure in the input file  22  but which are defined in a manner which is independent of any particular data structure. The “glue” functions define the attributes of the interface  12  and include:
         constant definitions   read functions   write functions   query functions   set functions.       

   The constant definitions define the context for the peripheral. 
   In Particular, they define the address range in memory associated with the device being modelled by that peripheral and bit locations within the registers of particular elements of the data structure. Any load from or store to an address in that defined range will cause a simulator to execute the appropriate peripheral read or write function instead of a memory access. 
   The read and write functions allow the peripheral to read and write data and state from and to the specified register of the CPU. 
   Query functions allow the peripheral to request a value from a specified register in the CPU. 
   Set functions allow the peripheral to write a value to a specified register of the CPU. 
   The documentation file defines the registers and their contents for use in setting up a simulator on the CPU. 
   The test functions define the attributes of the CPU read/write paths  18 ,  20  and include:
         constant definitions   read functions   write functions.       

   The constant definitions match those already defined as part of the interface function file  28 . Likewise, the read and write functions allow the CPU to read and write from the specified registers. Once again the functions are defined such that they have a common name but are implemented in a manner which is dependent on the environment. 
   The modelling tool  24  generates the documentation file  26 , interface functions file  28  and test functions file  30  by using the data structure specified for the peripheral model. The inventor has realised that there is sufficient information within the specification of these data structures to generate the contents of these files automatically. An example is illustrated in FIG.  4 . In  FIG. 4 , the input file  22  is shown defining the data structure for the registers named:
         SarControlRegister, and   SarSegmentationContextRegister.       

   The register named SarControlRegister has a data structure comprising three elements each having a length of one bit and which defines one of the following:
         StartSegmentation   EnablePacingEngine   EnablePacingClock.       

   The SarSegmentationContextRegister has a data structure comprising one element having a length of 32 bits defining a ContextStartAddress. 
     FIG. 4  illustrates how the functions for the various files can be derived directly from the data structure of the input file using a naming convention. The NAME N of the register is used to directly define the read and write functions for the interface function file  28  in the form of:
         Read NAME   Write NAME
 
and the test function file  30  in the form:
   Read From NAME   Write To NAME       
   In the example of  FIG. 4 , this is done for both the SarControlRecister and the SarSegmentationContextRegister. The query and set functions are defined by reference to each ELEMENT E of the data structure in the form:
         ELEMENT In NAME   Set ELEMENT In NAME       

   The documentation file  26  is set up or each register by deriving information directly from the data structure as indicated in FIG.  4 . Thus, each register definition comprises the following parameters:
         word offset—defining an offset location of the register in memory   bit offset—defining the bit location of each element in the register and derivable from the bit length BL in the data structure   bit field—naming the element of that bit location   function—defining the function F of the element   reset state—value of entity on reset   read/write—whether entity is readable or writable from CPU       

   The contents for each field to define these parameters can be derived directly from the data structure of the input file  22 . To avoid over-complicating the figure, the arrows are shown only for the read and write functions in respect of the SarControlRegister and, as far as the documentation file is concerned, only for the first bit location of that register. Tables 1 and 2 show the complete documentation files for the SarControlRegister and SarSegmentationContextRegister. 
   For each of the typedefs in the input file a table will be generated which will describe the allocation of the attributes to the words that make up the data structure in the CPU memory space. Each table will also describe the allocation of the bits within the word(s) as well as the meaning associated to these bits. The reset state will be given, and whether the attribute (bits are read, writable or both. The allocation of the bits within a word and indeed the words themselves will be driven by command line arguments to the modelling tool. The documentation file can be output in various formats, for example ascii and mif. The files are intended to be included or pasted into the main functional (or other) specification of the peripheral. 
     FIG. 5  is a flow chart illustrating high level operation of the modelling tool  24 . At step S 1 , input parameters given to the modelling tool  24 . At step S 1 , input parameters give to the modelling tool are checked. At step S 2 , the input file corresponding to one of the specified parameters is opened. Its contents are checked and any errors are reported in a meaningful manner (step S 3 ) by an error routine. If the contents of the input file are valid, the files are opened and named at step S 4 . At step S 5 , the files are created as described earlier with reference to  FIGS. 3 and 4 . Finally, at step S 6 , the files are closed. 
   Some specific examples are given in the following annexes. 
   Annexe 1 is an exemplary BNF sequence (Backus Naur Form of notation) for an input file  22 . Annexe 2 is an example of a simple data structure within the input file, and Annexe 3 is an example of a data structure of medium complexity within the input file. 
   Annexe 4 is an exemplary BNF sequence for the read function of the interface functions file for a data structure of medium complexity and Annexe 5 is an example of an output fragment. 
   Annexe 6 is an exemplary BNF sequence for a write function for the interface functions file for a data structure of medium complexity and Annexe 7 is an example of an output fragment. 
   Annexe 8 is an exemplary BNF sequence for a query function for a data structure of a simple type and Annexe 9 is an example output fragment. Annexe 10 is an exemplary BNF sequence for a set function of a simple data structure type and Annexe 11 is an example of an output fragment. 
   For the test functions file  30 , Annexe 12 is an exemplary BNF sequence for a read function for a data structure of medium complexity, and Annexe 13 is an exemplary output fragment. Annexe 14 is an exemplary ENF sequence for a data structure of medium complexity for the write function of the test functions file  30  and Annexe 15 is an exemplary output fragment. 
   Annexe 16 is one example in BNF format of a documentation file. 
     FIG. 6  shows how the modelling tool used herein is used in the simulation phase of a design process. Each peripheral device has a set of functions which simulate its behaviour. These are created as the input file  22  for each peripheral device. As already explained, each peripheral device may have a number of different simulated processes, P 1 ,P 2 ,P 3 , etc (see FIG.  2 ). The input file  22  defines each peripheral device and therefore may include information about each of the individual simulation processes. As described above, the input file is entered into a processor which is loaded with the modelling tool  24  and which thus generates the various files illustrated in FIG.  3 . As already mentioned, these include an interface functions file  28  and a test functions file  30 . The interface functions file for each peripheral device is held in a device library  40 . In  FIG. 6 , the denotation IFP 1  denotes the interface functions for the simulated process P 1  of the peripheral device. The test functions for each simulated process form part of the simulation code for the applications to be run on the CPU. The denotation TFP 1  denotes the test function for the simulated process P 1 . In  FIG. 6  it is illustrated as running in the simulated version of application  1 , APP 1 . A device definition file  42  holds a list of the device libraries. Each device has an address range associated with it in the device definition file. Any load from or store to an address in that range will cause the simulator to execute the appropriate peripheral read or write function instead of a memory access. For example, if the simulator processor attempts to access an address in range A 0  to A 3 , this maps onto the device library  40  holding the simulating processes for the peripheral of FIG.  2 . Instead of allowing the access to go ahead, that causes the simulator processor to perform the function defined by the relevant interface function file. This causes data to be written to, accessed from or modified in the representation of the register bank  16  associated with that peripheral. This type of access may have been caused by the simulator processor running code from the test functions incorporated within the process being simulated, APP 1  or by code within the device libraries if the peripherals are at that time being simulated. Either way, the representation of the register bank  16  associated with that peripheral device is kept correctly updated. 
   The modelling tool described herein gives rise to another advantage.  FIG. 7  illustrates a functional model for the application specific processor (ASP) running in a high level language such as C, and a real simulation which will run in a simulation language such as WHDL. The real simulation simulates the actual implemented chip down at the transistor level, and is used before the circuit which has been designed is actually implemented in silicon. The real simulation itself is necessary prior to implementing a circuit in silicon to try and establish as far as possible how an actual device will operate. However, real simulations are very slow. Conversely, the functional model itself can run quite quickly, although of course that is only modelling the architecture and not the actual silicon implementation as designed. However, because the modelling tool described herein generates matching test function and interface function files for each peripheral device, it is possible to speed up the real simulation by running the functional model for an initialisation or set up phase (or any other phase) and, at the end of that phase, extracting the state of the application programs, APP 1 ,APP 2  at a particular point in time and the state of the peripheral devices at the same point of time. The state of the application programs and the environmental stimuli can be derived from the test function files  30  and the state of the peripheral devices can be derived from the interface function files  28 . The contents of these files are loaded into a modelling file which is translated into a simulation file which can be loaded into the real simulation process. The modelling file can be in memory or on disk, as can the simulation file. Thus, it is possible for the functional model and the real simulation to run on the same CPU, with a transfer of the modelling file to the simulation file in the CPU memory. Alternatively, the functional model can be run on one CPU, with the modelling file being on a transferable disk which can be translated onto a simulation file and loaded into another CPU running the real simulation. The extraction of state from the functional model at a particular point in time in order to “kick start” the real simulation significantly reduces the overall simulation time. The environmental stimuli from and to the peripheral devices at that point of time can also be derived from the functional model and loaded into the real simulation. 
   Another advantage of the modelling tool described herein is its generation of the documentation file  26 . This defines the actual registers and can be used therefore to implement these registers in a final silicon implementation. This significantly reduces the amount of manual design work that needs to be carried out. 
   
     
       
             
           
             
             
             
             
             
             
           
         
             
               TABLE 1 
             
           
           
             
                 
             
             
               SarControlRegister 
             
           
        
         
             
               Word 
               Bit 
                 
                 
               Reset 
                 
             
             
               Offset 
               Offset 
               Bit Field 
               Function 
               State 
               R/W 
             
             
                 
             
             
               0 
               0 
               StartSeg- 
               Enables seg- 
               0 
               R/W 
             
             
                 
                 
               mentation 
               mentation 
             
             
                 
                 
                 
               engine 
             
             
                 
               1 
               EnablePac- 
               Enables pac- 
               0 
               R/W 
             
             
                 
                 
               ingEngine 
               ing engine 
             
             
                 
               2 
               EnablePac- 
               Enables pac- 
               0 
               R/W 
             
             
                 
                 
               ingClock 
               ing clock 
             
             
                 
             
           
        
       
     
   
   
     
       
             
           
             
             
             
             
             
             
           
         
             
               TABLE 2 
             
           
           
             
                 
             
             
               SarSegmentationContextRegister 
             
           
        
         
             
               Word 
               Bit 
                 
                 
               Reset 
                 
             
             
               Offset 
               Offset 
               Bit Field 
               Function 
               State 
               R/W 
             
             
                 
             
             
               0 
               0:31 
               Value 
               Context start 
               0 
               R/W 
             
             
                 
                 
                 
               address