WO2002008886A2 - System, method and article of manufacture for controlling the use of resources - Google Patents

Abstract

A system, method and article of manufacture are provided for managing the resources of a system. A communications driver is utilized to allow at least two field programmable gate arrays to send messages to each other. Each message between the field programmable gate arrays (FPGAs) includes an identification code, where a first portion of the identification code identifies a request for a resource. The identification code is processed. A macro procedure is called based on the type of message and the identification of the request for the resource. The macro procedure receives and processes the message.

Description

SYSTEM, METHOD AND ARTICLE OF MANUFACTURE FOR CONTROLLING THE USE OF RESOURCES

FIELD OF THE INVENTION

The present invention relates to resource sharing and more particularly to a resource management device and process for allowing multiple field programmable gate arrays to concurrently access resources.

BACKGROUND OF THE INVENTION

It is well known that software-controlled machines provide great flexibility in that they can be adapted to many different desired purposes by the use of suitable software. As well as being used in the familiar general purpose computers, software-controlled processors are now used in many products such as cars, telephones and other domestic products, where they are known as embedded systems.

However, for a given a function, a software-controlled processor is usually slower than hardware dedicated to that function. A way of overcoming this problem is to use a special software-controlled processor such as a RISC processor which can be made to function more quickly for limited purposes by having, its parameters (for instance size, instruction set etc.) tailored to the desired functionality.

Where hardware is used, though, although it increases the speed of operation, it lacks flexibility and, for instance, although it may be suitable for the task for which it was designed it may not be suitable for a modified version of that task which is desired later. It is now possible to form the hardware on reconfigurable logic circuits, such as Field Programmable Gate Arrays (FPGA's) which are logic circuits which can be repeatedly reconfigured in different ways. Thus they provide the speed advantages of dedicated hardware, with some degree of flexibility for later updating or multiple functionality.

A typical board has two FPGAs. The board can be designed in such a way that both FPGAs are connected to each physical device on the board. Thus each is individually able to drive all of the devices on the board. However two main problems arise when trying to access a resource from both FPGAs:

The first is related to external memory and arises because the prior art programming languages, such as HandelC, that are designed to enable the compilation of programs into synchronous hardware are not able to tristate the control and address lines to external RAMs. Thus each RAM bank (and the FLASH memory - which shares address pins with one of the RAM banks) can only be accessed from one FPGA.

The second problem arises when trying to transfer control of a device from one FPGA to the other, both because most existing device drivers are not designed to exit cleanly and because even if they did, most devices would require resetting and reinitializing every time^' control was transferred (an unnecessarily time-consuming procedure). It would be advantageous if a system could be designed such that two or more FPGAs can access all available hardware concurrently.

SUMMARY OF THE INVENTION

In accordance with the invention, a system, method and article of manufacture are provided for managing the resources of a system. The resources comprise any resource that is shared between multiple logic devices such as shared memory banks and shared Input/Output or other peripherals such as audio hardware.

A communications driver is utilized to allow at least two field programmable gate arrays to send messages to each other. Each message between the field programmable gate arrays (FPGAs) includes an identification code, where a first portion of the identification code identifies a type of the message, and where a second portion of the identification code identifies a request for a resource. The identification code is processed. A macro procedure is called based on the type of message and the identification of the request for the resource. The macro procedure receives and processes the message.

Preferably, the field programmable gate arrays are allowed to access external memory. Also preferably, arbitration is provided for preventing conflicts between the field programmable gate arrays when the field programmable gate arrays access the same resource. As an option, shared resources can be locked from other processes while communications are in progress. This can include communications between the FPGAs and/or communication between an FPGA and the resource.

In one embodiment of the present invention, an application on one of the field programmable gate arrays is allowed to send a command to another of the filed programmable gate arrays. In another embodiment of the present invention, one or more of the field programmable gate arrays is reconfigured so that it can access the resource. The invention extends to a computer program comprising program code means for executing the method.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood when consideration is given to the following detailed description of embodiments thereof. Such description makes reference to the annexed drawings wherein:

Figure 1 is a schematic diagram of a hardware implementation of one embodiment of the present invention;

Figure 2 is a flow chart of a process for managing the resources of a system according to one embodiment of the present invention;

Figure 3 is a diagrammatic overview of a board of the resource management device according to an illustrative embodiment of the present invention;

Figure 4 depicts a JTAG chain for the board of Figure 3;

Figure 5 shows a structure of a Parallel Port Data Transmission System according to an embodiment of the present invention;

Figure 6 is a flowchart that shows the typical series of procedure calls when receiving data;

Figure 7 is a flow diagram depicting the typical series of procedure calls when transmitting data;

Figure 8 is a flow diagram illustrating several processes running in parallel; and

Figure 9 is a block diagram of an FPGA device according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A preferred embodiment of a system in accordance with the present invention is preferably practiced in the context of a personal computer such as an IBM compatible personal computer, Apple Macintosh computer or UNIX based workstation. A representative hardware environment is depicted in Figure 1, which illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment having a central processing unit 110, such as a microprocessor, and a number of other units interconnected via a -system bus 112. The workstation shown in Figure.1 includes a Random Access Memory (RAM) 114, Read Only Memory (ROM) 116, an I/O adapter 118 for connecting peripheral devices such as disk storage units 120 to the bus 112, a user interface adapter 122 for connecting a keyboard 124, a mouse 126, a speaker 128, a microphone 132, and/or other user interface devices such as a touch screen (not shown) to the bus 112, communication adapter 134 for connecting the workstation to a commumcation network (e.g., a data processing network) and a display adapter 136 for connecting the bus 112 to a display device 138. The workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/95 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system. Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.

A preferred embodiment is written using JAVA, C, and the C++ language and utilizes object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications. As OOP moves toward the mainstream of software design and development, various software solutions require adaptation to make use of the benefits of OOP. A need exists for these principles of OOP to be applied to a messaging interface of an electronic messaging system such that a set of OOP classes and objects for the messaging interface can be provided. OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program. An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task. OOP, therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation.

In general, OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture. A component integration architecture is a set of architecture mechanisms which allow software modules in different process spaces to utilize each others capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture. It is worthwhile to differentiate between an object and a class of objects at this point. An object is a single instance of the class of objects, which is often just called a class. A class of objects can be viewed as a blueprint, from which many objects can be formed.

OOP allows the programmer to create an object that is a part of another object. For example, the object representing a piston engine is said to have a composition- relationship with the object representing a piston. In reality, a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects. OOP also allows creation of an object that "depends from" another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition. A ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic. In this case, the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it. The object representing the ceramic piston engine "depends from" the object representing the piston engine. The relationship between these objects is called inheritance.

When the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class. However, the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines have different characteristics, but may have the same underlying functions associated with it (e.g., how many pistons in the engine, ignition sequences, lubrication, etc.). To access each of these functions in any piston engine object, a programmer would call the same functions with the same names, but each type of piston engine may have different/overriding implementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects.

With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, one's logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows:

• Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit-design program, countries in an economics model, or aircraft in an air-traffic-control system.

• Objects can represent elements of the computer-user environment such as windows, menus or graphics objects.

• An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities. • An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane.

With this enormous capability of an object to represent just about any logically separable matters, OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an object which can be used as a component in a larger software project in the future.

If 90% of a new OOP software program consists of proven, existing components made from preexisting reusable objects, then only the remaining 10% of the new software project has to be written and tested from scratch. Since 90% already came from an inventory of extensively tested reusable objects, the potential domain from which an error could originate is 10% of the program. As a result, OOP enables software developers to build objects out of other, previously built objects.

This process closely resembles complex machinery being built out of assemblies and sub-assemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increased speed of its development. Programming languages are beginning to fully support the OOP principles, such as encapsulation, inheritance, polymorphism, and composition-relationship. With the advent of the C++ language, many commercial software developers have embraced OOP. C++ is an OOP language that offers a fast, machine-executable code. Furthermore, C++ is suitable for both commercial-application and systems- programming projects. For now, C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal.

The benefits of object classes can be summarized, as follows:

• Objects and their corresponding classes break down complex programming problems into many smaller, simpler problems.

• Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures.

• Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch. • Polymorphism and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways.

• Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them. • Libraries of reusable classes are useful in many situations, but they also have some limitations. For example:

• Complexity. In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes.

• Flow of control. A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library). The programmer has to decide which functions to call at what times for which kinds of objects. • Duplication of effort. Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way. Two different programmers can use the same set of class libraries to write two programs that do exactly the same thing but whose internal structure (i.e., design) may be quite different, depending on hundreds of small decisions each programmer makes along the way.

^■ Inevitably, similar pieces of code end up doing similar things in slightly different ways and do not work as well together as they should.

Class libraries are very flexible. As programs grow more complex, more programmers are forced to reinvent basic solutions to basic problems over and over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers.

Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others. In the early days of procedural programming, the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way.

The development of graphical user interfaces began to turn this procedural , programming arrangement inside out. These interfaces allow the user, rather than program logic, to drive the program and decide when certain actions should be performed. Today, most personal computer software accomplishes this by means of an event loop which monitors the mouse, keyboard, and other sources of external events and calls the appropriate parts of the programmer's code according to actions that the user performs. The programmer no longer determines the order in which events occur. Instead, a program is divided into separate pieces that are called at unpredictable times and in an unpredictable order. By relinquishing control in this way to users, the developer creates a program that is much easier to use. Nevertheless, individual pieces of the program written by the developer still call libraries provided by the operating system to accomplish certain tasks, and the programmer must still determine the flow of control within each piece after it's called by the event loop. Application code still "sits on top of the system.

Even event loop programs require programmers to write a lot of code that should not need to be written separately for every application. The concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making these things all work together, programmers using application frameworks start with working application code and basic user interface elements in place. Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application. Application frameworks reduce the total amount of code that a programmer has to write from scratch. However, because the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit. The framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a proprietary data structure).

A programmer writing a framework program not only relinquishes control to the user, (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs, having custom code, being created over and over again for similar problems.

Thus, as is explained above, a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain. It typically includes objects that provide default behavior (e.g., for menus.and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times.

There are three main differences between frameworks and class libraries: • Behavior versus protocol. Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program. A framework, on the other hand, provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides. • Call versus override. With a class library, the code the programmer instantiates objects and calls their member functions. It's possible to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework. The framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together. • Implementation versus design. With class libraries, programmers reuse only implementations, whereas with frameworks, they- reuse design. A framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems .

Thus, through the development of frameworks for solutions to various problems and programming tasks, significant reductions in the design and development effort for software can be achieved. A preferred embodiment of the invention utilizes HyperText Markup Language (HTML) to implement documents on the Internet together with a general-purpose secure communication protocol for a transport medium between the client and the Newco. HTTP or other protocols could be readily substituted for HTML without undue experimentation. Information on these products is available in T. Berners-Lee, D. Connoly, "RFC 1866: Hypertext Markup Language - 2.0" (Nov. 1995); and R. Fielding, H, Frystyk, T. Bemers-Lee, J. Gettys and J.C. Mogul, "Hypertext Transfer Protocol ~ HTTP/1.1 : HTTP Working Group Internet Draft" (May 2, 1996). HTML is a simple data format used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of domains. HTML has been in use by the World-Wide Web global information initiative since 1990. HTML is an application of ISO Standard 8879; 1986 Information Processing Text and Office Systems; Standard Generalized Markup Language (SGML).

To date, Web development tools have been limited in their ability to create dynamic Web applications which span from client to server and interoperate with existing computing resources. Until recently, HTML has been the dominant technology used in development of Web-based splutions. However, HTML has proven to be inadequate in the following areas:

• Poor performance; • Restricted user interface capabilities; .

• Can only produce static Web pages;

• Lack of interoperability with existing applications and data; and

• Inability to scale.

Sun Microsystem's Java language solves many of the client-side problems by:

• Improving performance on the client side;

• Enabling the creation of dynamic, real-time Web applications; and

• Providing the ability to create a wide variety of user interface components.

With Java, developers >can create robust User Interface (UI) components. Custom "widgets" (e.g., real-time stock tickers, animated icons, etc.) can be created; and client-side performance is improved. Unlike HTML, Java supports the notion of client-side validation, offloading appropriate processing onto the client for improved performance. Dynamic, real-time Web pages can be created. Using the above- mentioned custom UI components, dynamic Web pages can also be created.

Sun's Java language has emerged as an industry-recognized language for "programming the Internet." Sun defines Java as: "a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high- performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language. Java supports programming for the Internet in the form of platform-independent Java applets." Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add "interactive content" to Web documents (e.g., simple animations, page adornments, basic games, etc.). Applets execute within a Java-compatible browser (e.g., Netscape Navigator) by copying code from the server to client. From a language standpoint, Java's core feature set is based on C++. Sun's Java literature states that Java is basically, "C++ with extensions from Objective C for more dynamic method resolution."

Another technology that provides similar function to JAVA is provided by Microsoft and ActiveX Technologies, to give developers and Web designers wherewithal to build dynamic content for the Internet and personal computers. ActiveX includes tools for developing animation, 3-D virtual reality, video and other multimedia content. The tools use Internet standards, work on multiple platforms, and are being supported by over 100 companies. The group's building blocks are called ActiveX Controls, small, fast components that enable developers to embed parts of software in hypertext markup language (HTML) pages. ActiveX Controls work with a variety of programming languages including Microsoft Visual C++, Borland Delphi, Microsoft Visual Basic programming system and, in the future, Microsoft's development tool for Java, code named "Jakarta." ActiveX

Technologies also includes ActiveX Server Framework, allowing developers to create server applications. One of ordinary skill in the art readily recognizes that ActiveX could be substituted for JAVA without undue experimentation to practice the invention.

Handel-C is a programming language. It enables a software or hardware engineer to target directly FPGAs (Field Programmable Gate Array) in a similar fashion to classical microprocessor cross-compiler development tools, without recourse to a Hardware Description Language. Thereby allowing the designer to directly realise the raw real-time computing capability of the FPGA. Handel-C is a programming language designed to enable the compilation of programs into synchronous hardware; it is aimed at compiling high level algorithms directly into gate level hardware.

The Handel-C syntax is based on that of conventional C so programmers familiar with conventional C will recognize almost all the constructs in the Handel-C language.

Sequential programs can be written in Handel-C just as in conventional C but to gain the most benefit in performance from the target hardware its inherent parallelism must be exploited.

Handel-C includes parallel constructs that provide the means for the programmer to exploit this benefit in his applications. The compiler compiles and optimizes Handel-C source code into a file suitable for simulation or a netlist which can be placed and routed on a real FPGA.

The simulator allows you to test your program without using real hardware. It can display the state of every variable (register) in your program at every clock cycle if required, the simulation steps and the number of cycles simulated being under program control. Optionally the source code that was executed at each clock cycle as well as the program state may be displayed in order to assist in the debugging of the source code.

Further debugging options are provided in the toolset, notably the Logic Estimator'. This tool displays the source code in a color highlighted form which relates to the logic depth and usage. So providing feedback to the designer for further optimizations.

Resource Management Process and Device An embodiment of the present invention provides a resource-sharing server for allowing multiple Field Programmable Gate Arrays (FPGAs) on a computer board to access all the available hardware concurrently.

As one of the key features of the board according to an embodiment of the present invention is its ability to reconfigure itself both from Flash and over the Ethernet, it becomes apparent that there is a natural division of the roles of two FPGAs. One (the server, or FPO) should have access- to the Flash and the Network and include the reconfiguration device driver. The other (the client application or FP1) then has control over the LCD, touchscreen and the audio chip.

Figure 2 is a flow chart of a process 200 for managing the resources of a system according to one embodiment of the present invention. The resources comprise any resource that is shared between multiple logic devices such as shared memory banks and shared Input/Output or other peripherals such as audio hardware. In operation 202, a communications driver is utilized to allow at least two FPGAs to send messages to each other. In operation 204, an identification code is included with each message between the FPGAs, where a first portion of the identification code identifies a type of the message and a second portion of the identification code identifies a request for a resource. The identification code is processed in operation 206. A macro procedure is called in operation 208 and is based on the type of message and the identification of the request for the resource. The macro procedure receives and processes the message.

A server according to a preferred embodiment of the present invention includes a bidirectional 16 bit communications driver for allowing the two FPGAs to talk to each other. Every message from one FPGA to the other is preceded by a 16 bit ID, the high eight bits of which identify the type of message (AUDIO, FLASH, ^• • RECONFIGURATION etc...) and the low identify the particular request for that hardware (FLASH_READ etc...). The id codes are processed in the header file fpOserver.h, and then an appropriate macro procedure is called for each type of message (e.g. for AUDIO AudioRequest is called) which then receives and processes the main body of the. communication.

Preferably, the FPGAs are allowed to access external memory. Also preferably, arbitration is provided for preventing conflicts between the FPGAs when the FPGAs access the same resource. Further, the need to stop and reinitialize drivers and hardware when passing from one FPGA to the other is removed.

As an option, shared resources can be locked from other processes while communications are in progress. This can include communications between the FPGAs and or communication between an FPGA and the resource.

In one embodiment of the present invention, an application on one of the FPGAs is allowed to send a command to another of the FPGAs. In another embodiment of the present invention, one or more of the FPGAs is reconfigured so that it can access the resource.

In use, the server process requires a number of parameters to be passed to it. These are:

• PID: Used for locking shared resources (such as the FLASH) from other processes while communications are in progress.

• usendCommand, uSendLock: A channel allowing applications on FPO to send commands to applications on FP1 and a one-bit locking variable to ensure the data is not interleaved with server-sent data.

• uSoundOut, uSoundln: Two channels mirroring the function of the audio driver. Data sent to uSoundOut will be played (assuming the correct code in FP1) out of the MMT2000 speakers, and data read from uSoundln is the input to the MMT2000 microphone. The channels are implemented in such a way that when the sound driver blocks, the communication channel between FPGAs is not held^' up.

• MP3Run: A one bit variable controlling the MP3 GUI. The server will activate or deactivate the MP3 GUI on receipt of commands from FPl.

• ConfϊgAddr: A 23 bit channel controlling the reconfiguration process. When the flash address of a valid FPGA bitfϊle is sent to this channel, the server reconfigures FPl with the bitmap specified.

The data transfer rate between the two FPGAs in either direction is preferably about 16 bits per 5 clock cycles (in the clock domain of the slowest FPGA), for communicating between FPGAs that may be running at different clock rates.

Several Handel-C macros which may be used in various implementations of the present invention are set forth in Table 1. It should be noted that other programming and hardware description languages can be utilized as well, such as VHDL.

Table 1

Filename Type Macro Name Purpose

FpOserver.h Resource server FpO^'serverO Resource server for FPO for the MMT2000 IPPhone/MP3 project

Audiorequesth Audio Server AudioRequestQ Audio server for allowing sharing of sound hardware

Flashrequesth Data server FlashRequestO Server for allowing FPl access to the FLASH memory

'Mp3request.h MP3 server MP3Request0 Server to control the MP3 application and feed it MP3 bitstream data when requested.

Reconfigurerequesth Reconfiguration Reconfigurereq Allows FPl to request to be hardware uestO reconfigured, at an application exit.

Fpgacomms.h Communications FpgacommsQ Implements two unidirectional hardware 16 bit channels for communicating between the two FPGAs

Illustrative Device Development Platform

Figure 3 is a diagrammatic overview of a board 300 of the resource management device according to an illustrative embodiment of the present invention. It should be noted that the following description is set forth as an illustrative embodiment of the ' present invention and, therefore, the various embodiments of the present invention should not be limited by this description. As shown, the board can include two Xilinx Virtex™ 2000e FPGAs 302, 304, an Intel StrongARM SAl 110 processor 306, a large amount of memory 308, 310 and a number of I/O ports 312. Its main features are listed below:

Two XCV 2000e FPGAs each with sole access to the following devices: Two banks (1 MB each) of SRAM (256Kx32 bits wide) Parallel port Serial port ATA port

The FPGAs share the following devices: VGA monitor port Eight LEDs

2 banks of shared SRAM (also shared with the CPU) USB interface (also shared with the CPU) The FPGAs are connected to each other through a General Purpose I/O (GPIO) bus, a 32 bit SelectLink bus and a 32 bit Expansion bus with connectors that allow external devices to be connected to the FPGAs. The FPGAs are mapped to the memory of the StrongARM processor, as variable latency I/O devices.

The Intel StrongARM SAl 110 processor has access to the following: 64Mbytes of SDRAM 16Mbytes of FLASH memory LCD port IRDA port

Serial port It shares the USB port and the shared SRAM with the FPGAs.

In addition to these the board also has a Xilinx XC95288XL CPLD to implement a number of glue logic functions and to act as a shared RAM arbiter, variable rate clock generators and JTAG and MultiLinx SelectMAP support for FPGA configuration.

A number of commumcations mechanisms are possible between the ARM processor and the FPGAs. The FPGAs are mapped into the ARM's memory allowing them to be accessed from the ARM as through they were RAM devices. The FPGAs also share two 1 MB banks of SRAM with the processor, allowing DMA transfers to be performed. There are also a number of direct connections between the FPGAs and the ARM through the ARM's general purpose I/O (GPIO) registers.

The board is fitted with 4 clocks, 2 fixed frequency and 2 PLLs. The PLLs are programmable by the ARM processor.

The ARM is configured to boot into Angel, the ARM onboard debugging monitor, on power up and this can be connected to the ARM debugger on the host PC via a - serial link. This allows applications to be easily developed on the host and run on the board.

There are a variety of ways by which the FPGAs can be configured. These are:

• By an external host using JTAG or MultiLinx SelectMAP

• By the ARM processor, using data stored in either of the Flash RAMs or data acquired through one to the serial ports (USB, IRDA or RS232).

• By the CPLD from power-up with data stored at specific locations in the FPGA FlashRAM.

• By one of the other FPGAs.

StrongARM

The board is fitted with an Intel SAl 110 Strong ARM processor. This has 64Mbytes of SDRAM connected to it locally and 16Mbytes of Intel StrataFL ASH™ from which the processor may boot. The processor has direct connections to the FPGAs, which are mapped to its memory map as SRAM like variable latency I/O devices, and access to various I/O devices including USB, IRDA, and LCD screen connector and serial port. It also has access to 2MB of SRAM shared between the processor and the FPGAs.

Memory Map

The various devices have been mapped to the StrongARM memory locations as shown in Table 2:

Table 2

Address Location

The suggested settings for the StrongARM' s internal memory configuration registers are shown in Table 3:

Table 3

Register EG31

Where the acronyms are defined as: . MDCNFG - DRAM configuration register

MSC0,1,2 - Static memory control registers for banks 0,1,2

MDREF -DRAM refresh control register

MDCAS - CAS rotate control register for DRAM banks

The CPU clock should be set to 191.7MHz (CCF = 9). Please refer to. the

StrongARM Developers Manual, available from Intel Corporation, for further information on how to access these registers. FLASH memory

The Flash RAM is very slow compared to the SRAM or SDRAM. It should only be used for booting from; it is recommended that code be copied from Flash RAM to SDRAM for execution. If the StrongARM is used to update the Flash RAM contents then the code must not be. nning from the Flash or the programming instructions in the Flash will get corrupted.

SDRAM

A standard 64MB SDRAM SODIMM is fitted to the board and this provides the bulk of the memory for the StrongARM. Depending upon the module fitted the SDRAM may not appear contiguous in memory.

Shared RAM banks

These RAM banks are shared with both FPGAs. This resource is arbitrated by the CPLD and may only be accessed once the CPLD has granted the ARM permission to do so. Requesting and receiving permission to access the RAMs is carried out through CPLD register 0x10. Refer to the CPLD section of this document for more information about accessing the CPLD and its internal registers from the ARM processor. See Appendix D.

FPGA access

The FPGAs are mapped to the ARM's memory and the StrongARM can access the FPGAs directly using the specified locations. These locations support variable length accesses so the FPGA is able to prevent the ARM from completing the access until the FPGA is ready to receive or transmit the data. To the StrongARM these will appear as static memory devices, with the FPGAs having access to the Data, Address and Chip Control signals of the RAMs. The FPGAs are also connected to the GPIO block of the processor via the SAIO bus. The GPIO pins map to the SAIO bus is shown in Table 4.

Table 4

GPIO pins SAIO lines

Of these SAIO[0:10] connect to the FPGAs and SAIO[0:14] connect to connector CN25 on the board. The FPGAs and ARM are also able to access 2MB of shared memory, allowing DMA transfers between the devices to be performed.

I/O Devices

The following connectors are provided:

• LCD Interface connector with backlight connector

• IRDA connector (not 5V tolerant)

• . GPIO pins (not 5 V tolerant)

• Serial port

• Reset button to reboot the StrongARM

The connections between these and the ARM processor are defined below in Tables 5-8: .

Table 5: ARM - LCD connections (CN27)

Table 6: ARM IRDA connections (CN8A)

Table 7: ARM GPIO - CN20AP connections

Table 8: ARM - Serial Port connections (CN23)

The serial port is wired in such away that two ports are available with a special lead if handshaking isn't required.

Angel

Angel is the onboard debug monitor for the ARM processor. It communicates with the host PC over the serial port (a null modem serial cable will be required). The ARM is setup to automatically boot into Angel on startup - the startup code in the ARM's Flash RAM will need to be changed if this is not required.

When Angel is in use 32MBs of SDRAM are mapped to 0x00000000 in memory and are marked as cacheable and bufferable (except the top 1MB). The Flash memory is remapped to 0x40000000 and is read only and cacheable. The rest of memory is mapped one to one and is not cacheable or bufferable.

Under Angel it is possible to run the FPGA programmer software which takes a bitfile from the host machine and programs the FPGAs with it. As the .bit files are over 1MB in size and a serial link is used for the data transfer this is however a very slow way of configuring the FPGAs.

Virtex FPGA's

Two Virtex 2000e FPGAs are fitted to the board. They may be programmed from a variety of sources, including at power up from the FLASH memory. Although both devices feature the same components they have different pin definitions; Handel-C header files for the two FPGAs are provided.

One of the devices has been assigned 'Master', the other 'Slave'. This is basically a means of identifying the FPGAs, with the Master having priority over the Slave when requests for the shared memory are processed by the CPLD. The FPGA below the serial number is the Master.

One pin on each of the FPGAs is defined as the Master/Slave define pin. This pin is pulled to GND on the Master FPGA and held high on the Slave. The pins are:

Master FPGA : C9 Slave FPGA: D33

The following part and family parameters should be used when compiling a Handel- C program for these chips:

set family = Xilinx4000E; set part = " XV2000e-β-fgβ80" ;

Clocks

Two socketed clock oscillator modules may be fitted to the board. CLKA is fitted with a 50 MHz oscillator on dispatch and the CLKB socket is left to be fitted by the user should other or multiple frequencies to required. A +5V oscillator module should be used for CLKB.

Two on board PLLs, VCLK and MCLK, provide clock sources between 8MHz and 1 OOMHz (125MHz may well be possible). These are programmable by the ARM processor. VCLK may also be single stepped by the ARM.

This multitude of clock sources allows the FPGAs to be clocked at different rates, or to let one FPGA have multiple clock domains.

The clocks are connected to the FPGAs, as described in Table 9 and Appendices A and B:

Table 9 reππil Master FPGA Slave FPGA

Programming the FPGAs

The FPGAs may be programmed from a variety of sources: • Parallel III cable JTAG

_.• MultiLinx JTAG

• MultiLinx SelectMAP

• ARM processor

• From the other FPGA • Power up from FLASH memory ( FPGA FLASH memory section). When using any of the JTAG methods of programming the FPGAs you must ensure that the Bitgen command is passed the option "-g startupclk:jtagclk ". You will also need a .jed file for the CPLD or a .bsd file, which may be found in "Xilinx\xc9500xl\data\xc95288XL_tql44.bsd". The StrongARM also requires a .bsd file, which may be found on the Intel website http ://developer .intel.com/design/ strong/bsdl/sal 110 b 1.bsd. When downloaded this file will contain HTML headers and footers which will need to be removed first. Alternatively, copies of the required .bsd files are included on the supplied disks.

The JTAG chain 400 for the board is shown in Figure 4.

The connections when using the Xilinx Parallel III cable and the 'JTAG Programmer' are set forth in Table 10:

Table 10: Parallel III Cable JTAG

CN24 oin number JTAG Connector

With the Xilinx cables it may be easier to fit the flying ends into the Xilinx pod so that a number of cables may be connected to the board in one go.

MultiLinx JTAG The board has support for programming using MultiLinx. CN3 is the only connector required for JTAG programming_, with MultiLinx and is wired up as described in Table 11. (Note that not used signals may be connected up to the MultiLinx if required.)

Table 11

CN3 pin number MultiLinx CN3 pin number MultiLinx

MultiLinx SelectMAP

JP3 must be fitted when using MulitLinx SelectMap to configure the FPGAs. This link prevents the CPLD from accessing the FPGA databus to prevent bus contention. This also prevents the ARM accessing the FPGA Flash memory and from attempting FPGA programming from power up. Connectors CN3 and CN4 should be used for Master FPGA programming and CN10 and CNl 1 for programming the Slave FPGA.. See Tables 12-13.

Table 12

CN3/CN10 pin MultiLinx CN3/CN10 pin MultiLinx

■wBBuwl number

Table 13

CN4/CNll pin MultiLinx number

In practice MultiLinx SelectMap was found to be a very tiresome method of programming the FPGAs due to the large number of flying leads involved and the fact that the lack of support for multi FPGA systems means that the leads have to connected to a different connector for configuring each of the FPGA.

ARM processor

The ARM is able to program each FPGA via the CPLD. The FPGAs are set up to be configured in SelectMap mode. Please refer to the CPLD section of this document and Xilinx Datasheets on Virtex configuration for more details of how to access the programming pins of the FPGAs and the actual configuration process respectively. An ARM program for configuring the FPGAs with a .bit file from the host PC under

Angel is supplied. This is a very slow process however as the file is transferred over a serial link. Data could also be acquired from a variety of other sources including

USB and IRDA or the onboard Flash RAMs and this should allow an FPGA to be configured in under 0.5 seconds.

Configuring one FPGA from the other FPGA

One FPGA is able to configure the other through the CPLD in a manner similar to when the ARM is configuring the FPGAs. Again, please refer to the CPLD section of this document and the Xilinx data sheets for more information.

Configuring on power up from Flash Memory

The board can be set to boot the FPGAs using configuration data stored in this memory on power up. The following jumpers should be set if the board is required to boot from the Flash RAM:

• JP1 should be fitted if the Master FPGA is to be programmed from power up

• JP2 should be fitted if the Slave FPGA is to be programmed from power up. If these jumpers are used the Flash RAM needs to be organized as shown in Table 14:

Table 14

The configuration data must be the configuration bit stream only, not the entire .bit file. The .bit file contains header information which must first be stripped out and the bytes of the configuration stream as stored in the .bit file need to be mirrored - i.e. a configuration byte stored as 00110001 in the bit file needs to be applied to the FPGA configuration data pins are 10001100.

For more information on configuration of Xilinx FPGAs and the .bit format refer to the appropriate Xilinx datasheets.

FPGA FLASH Memory

16 MB of Intel StrataFLASH ™ Flash memory is available to the FPGAs. This is shared between the two FPGAs and the CLPD and is connected directly to them. The Flash RAM is much slower than the SRAMs on the board, having a read cycle time of 120ns and a write cycle of around 80ns. The FPGAs are able to read and write to the memory directly, while the ARM processor has access to it via the CPLD. Macros for reading and writing simple commands to the Flash RAM's internal state machine are provided in the klib.h macro library (such as retrieving identification and status information for the RAM), but it is left up to the developer to enhance these to implement the more complex procedures such as block programming and locking. The macros provided are intended to illustrate the basic mechanism for accessing the Flash RAM.

When an FPGA requires access to the Flash RAM it is required to notify the CLPD by setting the Flash Bus Master signal low. This causes the CPLD to tri-state its Flash-RAM pins to avoid bus contention. Similarly, as both FPGAs have access to the Flash RAM over a shared bus, care has to be taken that they do not try and access the memory at the same time (one or both of the two FPGAs may be damaged if they are driven against each other). It is left up to the developer to implement as suitable arbitration system if the sharing of this RAM across both FPGAs is required.

The connections between this RAM and the FPGAs are set forth in Table 15:

Table 15

Flash RAM pin Master FPGA Slave FPGA pin

Local SRAM

Each FPGA has two banks of local SRAM, arranged as 256K words x 32bits. They have an access time of 15ns.

In order to allow single cycle accesses to these RAMs it is recommended that the external clock rate is divided by 2 or 3 for the Handel-C clock rate. I.e. include the following line in your code:

set clock = external_divide "A20" 2; // or higher For an external divide 2 clock rate the RAM should be defined as:

macro expr sram_local_bankO_spec = { offchip = 1, wegate = 1, data = DATA_pins, addr = ADDRESS_pins, cs = { "E2", "FI", "J4", "F2",

Η3"} we = { "H4" }, oe = { "El" }

};

If the clock is divided by more than 2 replace the we gat e parameter with

westart=2, welength=l,

The connections to these RAMs are as follows:

Table 16

Shared SRAM

Each FPGA has access two banks of shared SRAM, again arranged as 256K words x 32bits. These have a 16ns access time. A series of quick switches are used to switch these RAMs between the FPGAs and these are controlled by the CPLD which acts as an arbiter. To request access to a particular SRAM bank the REQUEST pin should be pulled low. The code should then wait until the GRANT signal is pulled low by the CPLD in response.

The Handel-C code to implement this is given below:

// define the Request and Grant interfaces for the Shared SRAM unsigned 1 shared_bankO_request=l; unsigned 1 shared bankl request=l;

interface bus_out ( ) sharedbkOreg (shared_bankO_request) with sram_shared_bankO_request_pin; interface bus_out ( ) sharedbklreg (shared_bankl_request) with sram_shared_bankl_request_pin; interface bus_clock_i (unsigned 1) shared_bankO_grant ( ) with sram_shared_bankO_grant_pin; interface bus_clock_in (unsigned 1) shared_bankl_grant ( ) with sram_shared_bankl_grant_pin;

// Access to a shared RAM bank

{ shared_bankO_request=0 ; while (shared_bankO_grant . in) delay;

}

// perform accesses ....

// release bank shared bankO request=l;

The RAMs should be defined in the same manner as the local RAMs. (See above.)

The connections to the shared RAMs are given in Table 17:

Table 17

Connections to the StrongARM processor

The FPGAs are mapped to the StrongARMs memory as variable latency I/O devices, and are treated as by the ARM as though they were 1024 entry by 32bit RAM devices. The address, data and control signals associated with these RAMs are attached directly to the FPGAs. The manner in which the FPGAs interact with the ARM using these signals is left to the developer.

The connections are as shown in Table 18:

Table 18

Some of the ARM's general purpose I/O pins are also connected to the FPGAs. These go through connector CN25 on the board, allowing external devices to be connected to them (see also ARM section). See Table 19.

Table 19

SAIO bus ARM GPI/O Master FPGASlave FPG,

(ARMGPIO) pins

CPLD Interfacing

Listed in Table 20 are the pins used for setting the Flash Bus Master signal and FP_COMs. Refer to the CPLD section for greater detail on this.

Table 20

Local I/O devices available to each FPGA

ATA port

33 FPGA I/O pins directly connect to the ATA port. These pins have 100Ω series termination resistors which make the port- 5V IO tolerant. These pins may also be used as I/O if the ATA port isn't required. See Table 21.

Table 21

ATA line no. ATA port Master FPGA Slave FPGA

Parallel port

A conventional 25pin D-type connector and a 26way box header are provided to access this port. The I/O pins have 100Ω series termination resistors which also make the port 5 V I/O tolerant. These pins may also be used as I/O if the parallel port isn't required. See Table 22. See also Appendix C.

Table 22

PP line no. Parallel port pm Master FPGA pin Slave FPGA pm

PPO0 1 A8 A35

PPO1 14 B8 C34

Serial port

A standard 9pin D-type connector with a RS232 level shifter is provided. This port may be directly connected to a PC with a Null Modem cable. A box header with 5 V tolerant I/O is also provided. These signals must NOT be connected to a standard RS232 interface without an external level shifter as the FPGAs may be damaged. See Table 23.

Table 23

Serial line no. Serial port pin no. Master FPGA pin Slave FPGA pin

Serial Header Each FPGA also connects to a 10 pin header (CN9/CN16). The connections are shown in Table 24:

Table 24

(CN9/CN16) Master Slave

Header pin no. FPGA pin FPGA pin

Shared I/O Devices

These devices are shared directly between the two FPGAs and great care should be taken as to which FPGA accesses which device at any given time.

VGA Monitor

A standard 15pin High Density connector with an on-board 4bit DAC for each colour (Red, Green, Blue) is provided. This is connected to the FPGAs as set forth in Table 25:

Table 25

VGA line Master FPGA pin Slave FPGA pin

-w-

LEDs

Eight ofthe twelve LEDs on the board are connected directly to the FPGAs. See Table 26.

Table 26

■warn Master FPGA pin Slave FPGA pin

GPIO connector

A 50way Box header with 5V tolerant I/O is provided. 32 data bits (Ε' bus) are available and two clock signals. The connector may be used to implement a SelectLink to another FPGA. +3 V3 and +5V power supplies are provided via fuses. See Table 27. Table 27

Expansion GPI/O Master Slave F bus line header pin FPGA pin pin

SelectLink Interface

There is another 32bit general purpose bus connecting the two FPGAs which may be used to implement a SelectLink interface to provide greater bandwidth between the two devices. The connections are set forth in Table 28:

Table 28

USB

The FPGAs have shared access to the USB chip on the board. As in the case ofthe Flash RAM, the FPGA needs to notify the CPLD that it has taken control ofthe USB chip by setting the USBMaster pin low before accessing the chip. For more information on the USB chip refer to the USB section of this document.

Table 29

CPLD

The board is fitted with a Xilinx XC95288XL CPLD which provides a number of Glue Logic functions for shared RAM arbitration, interfacing between the ARM and FPGA and configuration ofthe FPGAs. The later can be used to either configure the FPGAs from power up or when one FPGA re-configures the other (Refer to section 'Programming the FPGAs'). A full listing of ABEL code contained in the CPLD can be found in Appendix D.

Shared SRAM bank controller The CPLD implements a controller to manage the shared RAM banks. A Request - Grant system has been implemented to allow each SRAM bank to be accessed by one ofthe three devices. A priority system is employed if more than one device requests the SRAM bank at the same time.

Highest priority ARM

Master FPGA Lowest priority : Slave FPGA

The FPGAs request access to the shared SRAM by pulling the corresponding REQUEST signals low and waiting for the CPLD to pull the GRANT signals low in response. Control is relinquished by setting the REQUEST signal high again. The ARM processor is able to request access to the shared SRAM banks via some registers within the CPLD - refer to the next section.

CPLD Registers for the ARM

The ARM can access a number of registers in the CPLD, as shown in Table 30:

Table 30

0x00 This is an address indirection register for register 1 which used for the data access.

0 Write only FLASH Address A0-A7

1 Write only FLASH Address A8-A15

2 Write only FLASH Address Al 6-A24

3 Read / Write FLASH data (Access time must be at least

CPLD Registers for the FPGA 's

The FPGAs can access the CPLD by setting a command on the FPCOM pins. Data is transferred on the FPGA (Flash RAM) databus. See Table 31.

Table 31

These commands will mainly be used when one FPGA reconfigures the other. Refer to the FPGA configuration section and the appropriate Xilinx datasheets for more information.

CPLD LEDs

Four LED's are directly connected to the CPLD. These are used. to indicate the following:

DO DONE LED for the Master FPGA Flashes during programming

Dl DONE LED for the Slave FPGA Flashes during programming

D2 Not used

D3 Flashes until an FPGA becomes programmed

Other Devices

USB

The board has a SCAN Logic SL11H USB interface chip, capable of full speed 12Mbits/s transmission. The chip is directly connected to the FPGAs and can be accessed by the ARM processor via the CLPD (refer to the CPLD section of this document for further information).

The datasheet for this chip is available at http://www.scanlogic.com pdf/sll lh /si l lhspec.pdf

PSU

This board maybe powered from an external 12V DC power supply through the

2.1mm DC JACK. The supply should be capable of providing at least 2.4A. Handel-C Library Reference

Introduction

This section describes the Handel-C libraries written for the board. The klib.h library provides a number of macro procedures to allow easier access to the various devices on the board, including the shared memory, the Flash RAM, the CPLD and the LEDs. Two other libraries are also presented, parallel_port.h and serial_port.h, which are generic Handel-C libraries for accessing the parallel and serial ports and communicating over these with external devices such as a host PC.

Also described is an example program which utilizes these various libraries to implement an echo server for the parallel and serial ports.

Also described here is a host side implementation of ESL's parallel port data transfer protocol, to be used with the data transfer macros in parallel_port.h.

The klib.h Library

Shared RAM arbitration

A request - grant mechanism is implemented to arbitrate the shared RAM between the two FPGAs and the ARM processor. Four macros are provided to make the process of requesting and releasing the individual RAM banks easier.

KRequestMemoryBankOO ;

KRequestMemoryBankl () ; KReleaseMemoryBankOQ; KReleaseMemoryBanklQ;

Arguments

None. Return Values

None.

5 Execution Time

KRequestMemoryBank#() requires at least one clock cycle. KReleaseMemoryBank#() takes one clock cycle.

Description

10 These macro procedures will request and relinquish ownership of their respective memory banks. When a request for a memory bank is made the procedure will block the thread until access to the requested bank has been granted.

Note: The request and release functions for different banks may be called in 15 parallel with each other to gain access to or release both banks in the same cycle.

Flash RAM Macros

20 These macros are provided as a basis through which interfacing to the Flash RAM can be carried out. The macros retrieve model and status information from the RAM to illustrate how the read/write cycle should work. Writing actual data to the Flash RAM is more complex and the implementation of this is left to the developer.

25 KSetFPGAFBMQ

KReleaseFPGAFBMQ

Arguments

None. o 0

Return Values None.

Execution Time

Both macros require one clock cycle.

Description

Before any communication with the Flash RAM is carried out the FPGA needs to let the CPLD know that it is taking control ofthe Flash RAM. This causes the CLPD to tri-state the Flash bus pins, avoiding resource contention. KSetFPGAFBM() sets the Flash Bus Master (FBM) signal and KReleaseFPGAFBM() releases it. This macro is generally called by higher level macros such as KReadFlash() or KWriteFlash().

Note: These two procedures access the same signals and should NOT be called in parallel to each other.

KEnableFlashQ KDisableFlashQ

Arguments None.

Return Values

None.

Execution Time

Both macros require one clock cycle.

Description

These macros raise and lower the chip-select signal ofthe Flash RAM and tri-state the FPGA Flash RAM lines (data bus, address bus and control signals). This is necessary if the Flash RAM is to be shared between the two FPGAs as only one chip can control the Flash at any give time. Both FPGAs trying to access the Flash RAM simultaneously can cause the FPGAs to 'latch up' or seriously damage the FPGAs or Flash RAM chip. This macro is generally called by higher level macros such as KReadFlash() or KWriteFlash().

Note: These macros access the same signals and should NOT be called in parallel with each other.

KWriteFlash(address, data) KReadFlash(address, data)

Arguments

24 bit address to be written or read. 8 bit data byte.

Return Values

KReadFlashO returns the value ofthe location specified by address in the data parameter.

Execution Time

Both procedures take 4 cycles.

The procedures are limited by the timing characteristics ofthe Flash RAM device. A read cycle takes at least 120ns, a write cycle 100ns. The procedures have been set up for a Handel-C clock of 25MHz.

Description

The macros read data from and write data to the address location specified in the address parameter. -01-

Note: These macros access the same signals and should NOT be called in parallel with each other.

KSetFlashAddr ess (address)

Arguments

24 bit address value.

Return Values None.

Execution Time

This macro requires one clock cycle.

Description

The macro sets the Flash address bus to the value passed in the address parameter. This macro is used when a return value ofthe data at the specified location is not required, as may be the case when one FPGA is configuring the other with data from the Flash RAM since the configuration pins ofthe FPGAs are connected directly to the lower 8 data lines ofthe Flash RAM.

KReadFlashID(flash_component_ID, manufacturer _ID) KReadFlashStatus (status)

Arguments

8 bit parameters to hold manufacturer, component and status information.

Return Values

The macros return the requested values in the parameters passed to it.

Execution Time KReadFlashStatusQ requires 10 cycles, KReadFlashID() requires 14 cycles.

Description The macros retrieve component and status information from the Flash RAM. This is done by performing a series of writes and reads to the internal Flash RAM state machine.

Again, these macros are limited by the access time ofthe Flash RAM and the number of cycles required depends on rate the design is clocked at. These macros are designed to be used with a Handel-C clock rate of 25MHz or less.

Although a system is in place for indicating to the CPLD that the Flash RAM is in use (by using the KSetFPGAFBM() and KReleaseFPGAFBMO macros) it is left up to the developers to devise a method of arbitration between the two FPGAs. As all the Flash RAM lines are shared between the FPGAs and there is no switching mechanism as in the shared RAM problems will arise if both FPGAs attempt to access the Flash RAM simultaneously.

Note: These macros access the same signals and should NOT be called in parallel with each other. Also note that these macros provide a basic interface for communication with the Flash RAM. For more in-depth please refer to the Flash RAM datasheet.

CPLD Interfacing

The following are macros for reading and writing to the CPLD status and control registers:

KReadCPLDStatus (status)

KWriteCPLDControl(contι-ol) Arguments

8 bit word

Return Values

KReadStatusQ returns an 8 bit word containing the bits ofthe CPLD's status register. (Refer to the CPLD section for more information)

Execution Time Both macros require six clock cycles, at a Handel-C clock rate of 25MHz or less.

Description

These macros read the status register and write to the control register ofthe CPLD.

KSetFPCOM(fp_command)

Arguments

3 bit word.

Return Values

None.

Execution Time

This macro requires three clock cycles, at a Handel-C clock rate of 25MHz or less.

Description

This macro is provided to make the sending of FP_COMMANDs to the CPLD easier.. FP_COMMANDs are used when the reconfiguration of one FPGA from the other is desired (refer to the CPLD section for more information).

The different possible fp_command (s) are set forth in Table 32: Table 32

FP_SET_IDLE Sets CPLD to idle FP_READ_STATUS Read the status register ofthe CPLD FP_WRITE_CONTROL Write to the control register ofthe CPLD FP_CCLK_LOW Set the configuration clock low FP CCLK HIGH Set the configuration clock high

e.g.

KSetFPCOM(FP_READ_STATUS); KSetFPCOM(FP_SET_IDLE);

Note: These macros access the same signals and should NOT be called in parallel with each other.

LEDs

KSetLEDs(maskByte)

Arguments

8 bit word.

Return Values None.

Execution Time

One clock cycle.

Description This macro procedure has been provided for controlling the LEDs on the board. The maskByte parameter is applied to the LEDs on the board, with a 1 indicating to turn a light on and a 0 to turn it off. The MSB of maskByte corresponds to D12 and the LSB to D5 on the board.

Note: Only one of the FPGAs may access this function. If both attempt to do so the FPGAs will drive against each other and may 'latch-up', possibly damaging them.

Using the Parallel Port

Introduction

The library parallel_port.h contains routines for accessing the parallel port. This implements a parallel port controller as an independent process, modeled closely on the parallel port interface found on an IBM PC. The controller allows simultaneous access to the control, status and data ports (as defined on an IBM PC) ofthe parallel interface. These ports are accessed by reading and writing to channels into the controller process. The reads and writes to these channels are encapsulated in other macro procedures to provide an intuitive API.

Figure 5 shows a^" structure of a Parallel Port Data Transmission System 500 according to an embodiment ofthe present invention. An implementation of ESL's parallel data transfer protocol has also been provided, allowing data transfer over the parallel port, to and from a host computer 502. This is implemented as a separate process which utilizes the parallel port controller layer to implement the protocol. Data can be transferred to and from the host by writing and reading from channels into this process. Again macro procedure abstractions are provided to make the API more intuitive. A host side application for data transfer under Windows95/98 and NT is provided. Data transfer speeds of around 100 Kbytes/s can be achieved over this interface, limited by the speed ofthe parallel port.

Accessing the parallel port directly.

The 17 used pins ofthe port have been split into data, control and status ports as defined in the IBM PC parallel port specification. See Table 33.

Table 33

The parallel port controller process needs to be run in parallel with those part ofthe program wishing to access the parallel port. It is recommended that this is done using a par{} statement in the main() procedure.

The controller procedure is:

parallel _port( pp_data_send_channel, pp_data_ read_channel, pp_control_port_read, pp_status_port_read, pp_status_port_write) ;

where the parameters are all channels through which the various ports can be accessed.

Parallel Port Macros

It is recommended that the following macros be used to access the parallel port rather than writing to the channels directly.

PpWriteData yte) PpReadDataφyte)

Arguments

Unsigned 8 bit word.

Return Values

PpReadDataQ returns the value ofthe data pins in the argument byte. Execution Time

Both macros require one clock cycle.

Description

These write the argument byte to the register controlling the data pins ofthe port, or return the value ofthe data port within the argument byte respectively, with the MSB ofthe argument corresponding to data[7]. Whether or not the value is actually placed on the data pins depends on the direction settings ofthe data pins, controlled by bit 6 ofthe status register.

PpReadControl( control port)

Arguments Unsigned 4 bit word.

Return Values

PpReadControlQ returns the value ofthe control port pins in the argument byte.

Execution Time

This macro requires one clock cycle.

Description

This procedure returns the value ofthe control port. The 4 bit nibble is made up of [nSelect_in @ Init @ nAutofeed @ nStrobe], where nSelect_in is the MSB.

PpReadStatus (status jort) PpSetStatus (status jport)

Arguments

Unsigned 6 bit word. Return Values

PpReadStatusQ returns the value ofthe status port register in the argument byte.

Execution Time

This macro requires one clock cycle.

Description

These read and write to the status port. The 6 bit word passed to the macros is made up of [pp_direction @ busy @ nAck @ PE @ Select @ nError], where pp_direction indicates the direction ofthe data pins (i.e. whether they are in send [1] or receive [0] mode). It is important that this bit is set correctly before trying to write or read data from the port using PpWriteData() or PpReadData().

Note: All of the ports may be accessed simultaneously, but only one operation may be performed on each at any given time. Calls dealing with a particular port should not be made in parallel with each other.

Transferring data to and from the host PC

The library parallel jport.h also contains routines for transferring data to and from a host PC using ESL's data transfer protocol. The data transfer process, pp_coms(), which implements the transfer protocol should to be run in parallel to the parallel port controller process, again preferably in the main par{} statement. A host side implementation ofthe protocol, ksendexe, is provided also.

pp_coms(pp_send_chan, channel to write data to when sending pp_recv_chan, - channel to read data from when receiving pp_command, - channel to write commands to pp_error) - channel to receive error messaged from. The following macros provide interfaces to the data transfer process:

OpenPP (error) - open the parallel port for data transfer

ClosePP (error) - close the port

Note: Make sure that the host side application, ksend.exe, is running. The macros will try and handshake with the host and will block (or timeout) until a response is received. Also note that the following macros all access the same process and should NOT be called in parallel with each other.

Arguments

Unsigned 2 bit word.

Return Values The argument will return an error code indicating the success or failure ofthe command.

Execution Time

This macro requires one clock cycle.

Description

These two macros open and close the port for receiving or sending data. They initiate a handshaking procedure to start communications with the host computer.

SetSendMode (error) - set the port to send mode

SetRecvMode(error) - set the port to receive mode

Arguments

Unsigned 2 bit word.

Return Values The argument will return an error code indicating the success or failure ofthe command.

Execution Time This macro requires one clock cycle.

Description

These set the direction of data transfer and the appropriate mode should be set before attempting to send or receive data over the port.

SendPP yte, error) - send a byte over the port ReadPP yte, error) - read a byte from the port

Arguments Unsigned 8 bit and unsigned 2 bit words.

Return Values

ReadPPQ returns the 8 bit data value read from the host in the byte parameter. Both macros will return an error code indicating the success or failure ofthe command.

Execution Time

How quickly these macros execute depend on the Host. The whole sequence of handshaking actions for each byte need to be completed before the next byte can be read or written.

Description

These two macros will send and receive a byte over the parallel port once this has been initialized and placed in the correct mode. The procedures return a two bit error code indicating the result ofthe operation. These codes are defined as:

#defme PP_NO_ERROR 0 #defme PP_HOST_BUFFER_NOT_FιNISHED 1

#defme PP_OPEN_TIMEOUT 2

Note: SendPP and ReadPP will block the thread until a byte is transmitted or the timeout value is reached. If you need to do some processing while waiting for a communication use a 'prialt' statement to read from the global pp_recv_chan channel or write to the pp_send_chan channel.

Typical macro procedure calls during Read / Write

Figure 6 is a flowchart that shows the typical series of procedure calls 600 when receiving data. Figure 7 is a flow diagram depicting the typical series of procedure calls 700 when transmitting data.

The Ksend application

The ksend.exe application is designed to transfer data to and from the board FPGAs over the parallel port. It implements the ESL data transfer protocol. It is designed to communicate with the pp_comsQ process running on the FPGA. This application is still in the development stage and may have a number of bugs in it.

Two versions of the program exist, one for Windows95/98 and one for WindowsNT. The NT version requires the GenPort driver to be installed. Refer to the GenPort documentation for details of how to do this.

In its current for the ksend application is mainly intended for sending_, data to the board, as is done in the esl_boardtest program. It is how ever also able to accept output form the board. Again, please refer to the application note or the ksend help (invoked by calling ksend without any parameters) for further details.

Serial Port

5

Introduction

Each FPGA has access to a RS232 port allowing it to be connected to a host PC. A driver for transferring data to and from the FPGAs from over the serial port is 10 contained in the file serial_port.h.

RS232A Interface

There are numerous ways of implementing RS232 interfacing,- depending on the capabilities ofthe host and device and what cables are used. This interface is

15 implemented for a cross wired null modem cable which doesn't require any hardware handshaking - the option of software flow control is provided, though this probably won't be necessary as the FPGA will be able to deal with the data at a much faster rate than the host PC can provide it. When soft flow control is used the host can stop and start the FPGA transmitting data by sending the XON and XOFF

20 tokens. This is only necessary when dealing with buffers that can fill up and either side needs to be notified.

Serial port macros

25 Serial port communications have been implemented as a separate process that runs in parallel to the processes that wish to send/ receive data. Figure 8 is a flow diagram illustrating several processes 802, 804 running in parallel.

The serial port controller process is

J 0 serial jport(sp .nput, sp_output); where sp_input and sp_output are n bit channels through which data can be read or written out form the port. These reads and writes are again encapsulated in separate macro procedures to provide the user with a more intuitive API.

SpReadDataφyte) - read a data byte from the port SpWriteDataφyte) - write a byte to the port

Arguments n bit words, where n is the number of data bits specified.

Return Values

SpReadDataQ returns an n bit value corresponding to the transmitted byte in the argument.

Execution Time

The execution time depends to the protocol and the baud rate being used.

Description

These procedures send and receive data over the serial port using the RS232 protocol. The exact communications protocol must be set up using a series of

#defϊnes before including the serial_port.h library. To use an 8 data bit, 1 start and 1 stop bit protocol at 115200 baud on a null modem cable with no flow control the settings would be:

#define BAUD_RATE 115200

#define START_BIT ((unsigned 1)0) #define STOP_BIT ((unsigned 1)1) #define NUM_DATA_BITS 8

Other options are:

For soft flow control: #define SOFTFLO

#define XON <ASCII CHARACTER

CODE>

#define XOFF <ASCII CHARACTER

CODE>

RTS/CTS flow control: idefine HARDFLOW

The default settings are:

Baud rate ^• 9600

Start bit 0

Stop bit 1

Num. data bits 8

XON 17

XOFF 19

Flow control off

Any ofthe standard baud rate settings will work provided that the Handel-C clock rate is at least 8 times higher than the baud rate. Also ensure that the macro

CLOCK_RATE is defined, this is generally found in the pin definition header for each ofthe FPGAs.

e.g.

#define CLOCK_RATE 25000000 // define the clock rate

Example Program

Shown here is an example Handel-C program that illustrates how to use the parallel and serial port routines found in the serial_port.h and parallel_port.h libraries. The program, implements a simple echo server on the serial and parallel ports. The SetLEDsO function from the klib.h library is used to display the ASCII value received over the serial port on the LEDs in binary.

// Include the necessary header files tdefine MASTER #ifdef MASTER

#include "KorapressorMaster . h" ielse

#include "Ko pressorSlave.h" #endif

tinclude "stdlib.h"

#include "parallel_port .h"

#include "klib.h"

// Define the protocol and include the file tdefine BAUD_RATE 9600

#define NUM_DATA_BITS 8

#define NϋLLMODEM #include "serial_port . h"

////////////////////////////////// // Process to echo any data received by the parallel port // to verify it is working properly

macro proc EchoPPO { unsigned 8 pp_data_in; unsigned 2 error with {warn = 0 } ; unsigned 1 done; OpenPP (error) ; // initiate contact with host while ( !done)

{

// read a byte SetRecvMode (error) ;

ReadPP (pp_data_in, error);

// echo it SetSendMode (error) ; WritePP (pp_data_in, error);

} ClosePP (error) ; // close connection

}

//////////////////////////////////

// Process to echo any data received by the serial port

// to verify it is working properly. We are always

// listening on the serial port so there is no need to open it.

macro proc EchoSPO

{ unsigned 8 serial_in_data;

while ( 1)

{

SpReadData (serial_in_data) ; // read a byte from the serial port

SetLEDs (serial_in_data) ;

SpWriteData (serial_in_data) ; // write it back out } delay; // avoid combinational cycles } void main (void) { while (1) { par { EchoPPO; //Parallel port thread

EchoSPO; // Serial port thread

////// Start the services //////// // Parallel Port stuff pp_coms (pp_send_chan, pp__recv_chan, pp_command, ■ pp_error) ;

parallel_port (pp_data_send_channel, pp_data_read_channel, pp_control_port_read, pp_status_port_read, pp_status_port_write ) ;

// Serial port stuff // serial_port (sp_input, sp_output) ;

The code can be compiled for either FPGA by simple defining or un-defining the MASTER macro - lines 1 to 5 More Information

Useful information pertaining to the subjects of this described herein can be found in the following: The Programmable Logic Data Book, Xilinx 1996; Handel-C Preprocessor Reference Manual, Handel-C Compiler Reference Manual, and Handel-C Language Reference Manual, Embedded Solutions Limited 1998; and Xilinx Datasheets and Application notes, available from the Xilinx website http://www.xilinx.com, and which are herein incorporated by reference.

Illustrative Embodiment

According to an embodiment ofthe present invention, a device encapsulates the Creative MP3 encoder engine in to an FPGA device. Figure 9 is a block diagram of an FPGA device 900 according to an exemplary embodiment ofthe present invention. The purpose ofthe device is to stream audio data directly from a CD 902 or CDRW into the FPGA, compress the data, and push the data to a USB host 904 which delivers it to the OASIS(Nomad 2) decoder. The entire operation of this device is independent of a PC.

The design ofthe FPGA uses the "Handel-C" compiler, described above, from

Embedded Solutions Limited (ESL). The EDA tool provided by ESL is intended to ■ rapidly deploy and modify software algorithms through the use of FPGAs without the need to redevelop silicon. Therefore the ESL tools can be utilized as an alternative to silicon development and can be used in a broader range of products.

Feature Overview

The FGPA preferably contains the necessary logic for the following:

- MP3 Encoder 906

- User Command Look Up Table - play - pause

- eject

- stop

- _. skip song (forward / reverse) - scan song (forward / reverse)

- record (rip to MP3) -> OASIS Unit

- ATAPI command and control

- command FIFO - data bus command bus

- (2) 64 sample FIFOs (16bit * 44.100 kHz)

- Serial Port (16550 UART) optionally EEPROM Interface (I2C & I2S)

- USB Interface to host controller - SDRAM controller

- 32-bit ARM or RISC processor

In addition to the FPGA the following is preferably provided:

- USB Host / Hub controller (2 USB ports) - 4MB SDRAM

- 128K EEPROM

- 9-pin serial port 6 control buttons.

- 40-Pin IDE Interface for CD or CDRW

Interfaces

ATAPI (IDE) Interface

User Interface USB Interface

While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any ofthe above described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. A method for managing resources of a system, comprising the steps of: (a) utilizing a communications driver for allowing at least two field programmable gate arrays to send messages to each other; (b) including an identification code with each message between the field programmable gate arrays, wherein a first portion ofthe identification code identifies a type ofthe message, wherein a second portion ofthe identification code identifies a request for a resource; (c) processing the identification code; and (d) calling a macro procedure based on the type of message and the identification ofthe request for the resource, wherein the macro procedure receives and processes the message.

2. A method as recited in claim 1 , wherein the field programmable gate arrays are allowed to access external memory.

3. A method as recited in claim 1 or 2, further comprising providing arbitration for preventing conflicts between the field programmable gate arrays when the field programmable gate arrays access the same resource.

4. A method as recited in claim 1, 2 or 3, further comprising locking shared resources from other processes while communications are in progress.

5. A method as recited in claim 1, 2, 3 or 4, wherein an application on one of the field programmable gate arrays is allowed to send a command to another ofthe field programmable gate arrays.

6. A method as recited in claim^' 1, 2, 3, 4 or 5, further comprising reconfiguring at least one ofthe field programmable gate arrays for accessing the resourced

7. A method as recited in claim 1, 2, 3, 4, 5 or 6, wherein the resource includes audio hardware.

8. A computer program embodied on a computer readable medium for managing resources of a system, comprising: (a) a code segment that utilizes a commumcations driver for allowing at least two field programmable gate arrays to send messages to each other;

(b) a code segment that includes an identification code with each message between the field programmable gate arrays, wherein a first portion ofthe identification code identifies a type ofthe message, wherein a second portion ofthe identification code identifies a request for a resource;

(c) a code segment that processes the identification code; and

(d) a code segment that calls a macro procedure based on the type of message and the identification ofthe request for the resource, wherein the macro procedure receives and processes the message.

9. A computer program as recited in claim 8, wherein the field programmable gate arrays are allowed to access external memory.

10. A computer program as recited in claim 8 or 9, further comprising a code segment that provides arbitration for preventing conflicts between the field programmable gate arrays when the field programmable gate arrays access the same resource.

11. A computer program as recited in claim 8, 9 or 10, further comprising a code segment that locks shared resources from other processes while communications are in progress.

12. A computer program as recited in claim 8, 9, 10 or 11, wherein an application on one ofthe field programmable gate arrays is allowed to send a command to another ofthe field programmable gate arrays.

13. A computer program as recited in claim 8, 9, 10, 11 or 12, further comprising a code segment that reconfigures at least one ofthe field programmable gate arrays for accessing the resource.

14. A computer program as recited in claim 8, 9, 10, 11, 12 or 13, wherein the resource includes audio hardware.

15. A system for managing resources of a system, comprising:

(a) logic that utilizes a communications driver for allowing at least two field programmable gate arrays to send messages to each other;

(b) logic that includes an identification code with each message between the field programmable gate arrays, wherein a first portion ofthe identification code identifies a type ofthe message, wherein a second portion ofthe identification code identifies a request for a resource;

(c) logic that processes the identification code; and

(d) logic that calls a macro procedure based on the type of message and the identification ofthe request for the resource, wherein the macro procedure receives and processes the message.

16. A system as recited in claim 15, wherein the field programmable gate arrays are allowed to access external memory.

17. A system as recited in claim 15 or 16, further comprising logic that provides arbitration for preventing conflicts between the field programmable gate arrays when the field programmable gate arrays access the same resource.

18. A system as recited in claim 15, 16 or 17, further comprising logic that locks shared resources from other processes while communications are in progress.

19. A system as recited in claim 15, 16, 17 or 18, wherein an application on one ofthe field programmable gate arrays is allowed to send a command to another ofthe field programmable gate arrays.

20. A system as recited in claim 15, 16, 17, 18 or 19, further comprising logic that reconfigures at least one ofthe field programmable gate arrays for

. accessing the resource.