ScholarQuill logoScholarQuillUniversity Notes
  • Notes
  • Past Papers
  • Blogs
  • Todo
Login
ScholarQuill logoScholarQuillUniversity Notes
Login
NotesPast PapersBlogsTodo
More
SubjectsDiscussionCGPA CalculatorGPA CalculatorStudent PortalCourse Outline
About
About usPrivacy PolicyReportContact
Notes
Past Papers
Blogs
Todo
Analytics
    Current Subject
    🧩
    Computer Organization and Assembly Language
    COMP3137
    Progress0 / 73 topics
    Topics
    1. Introduction to Computer Organization2. Assembly Language3. Comparison of Low-Level and High-Level Languages4. Register Types (16-bit): General Purpose and Special Purpose Registers5. Introduction and Usage of RAM6. Processor7. Registers8. System Bus9. Instruction Execution Cycle10. Assembly and Machine Language11. Assembler12. Linker and Link Libraries13. Programmer's View of a Computer System14. RISC and CISC Architecture15. Physical Address Calculation16. Basic Memory Organization17. CPU Organization18. Top Level View of Computer Function and Interconnection19. Assembler Instruction Cycle20. Execute Cycle21. Interrupts22. Interrupt Cycle23. Memory Connection24. Input/Output Connection25. CPU Connection26. MASM27. MIPS28. Defining Data in MASM Assembler29. Elements of Assembly Language30. Integer Constants31. Integer Expressions32. Real Number Constants33. Character Constants34. String Constants35. Reserved Words36. Identifiers37. Directives38. Instructions39. The NOP (No Operation) Instruction40. Adding and Subtracting Integer41. INC and DEC Instructions42. NEG Instruction43. How to Move Integer Number in Register44. Adding and Subtracting Numbers in Registers45. Declaration and Initialization of Variables46. Moving Data from Variable to Register47. Data Definition Statement48. BYTE and SBYTE Data49. WORD and SWORD Data50. Defining DWORD and SDWORD Data51. Knowledge about Different Data Types52. Operations, Array & Loops53. Division and Multiplication in Assembly54. Jumps Based on Specific Flags55. Jumps Based on Equality56. Simple Jump Statements57. Jumps Based on Specific Condition58. Code Examples59. Practice on MASM60. Procedures61. File Operations Procedures62. Labels in Procedures63. Stack64. Runtime Stack65. Conditional Control Flow Directives66. Compound Expressions67. Data Representation & Conversion68. Architecture69. Data Path70. Control Unit71. Critical Path72. General Principles of Pipelining73. Pipelined Y86 Implementations
    COMP3137›System Bus
    Computer Organization and Assembly LanguageTopic 8 of 73

    System Bus

    8 minread
    1,290words
    Intermediatelevel

    System Bus in Computer Architecture

    The system bus is a collection of pathways or lines used to transfer data between different components of a computer system. It is the primary communication channel between the CPU, memory, and I/O devices (input/output devices) and enables the exchange of data, instructions, and control signals. In essence, the system bus acts as the data highway that connects all major parts of the computer, allowing them to communicate efficiently.


    Key Components of a System Bus

    The system bus is typically divided into three main types of buses, each with a specific role in the data transfer process:

    1. Data Bus (for transferring data)
    2. Address Bus (for specifying the memory addresses)
    3. Control Bus (for coordinating the operations and data flow)

    1. Data Bus

    • Function: The data bus carries the actual data between the CPU, memory, and other components of the system. It is the pathway for the transfer of data to and from the CPU, memory, and I/O devices.
    • Width: The width of the data bus (measured in bits) determines how much data can be transferred at once. For example, an 8-bit data bus can transfer 8 bits of data at a time, while a 32-bit or 64-bit data bus can transfer 32 or 64 bits, respectively.
    • Example: If the CPU needs to read data from memory, it will place the address of the memory location on the address bus and then fetch the data from that address over the data bus.

    2. Address Bus

    • Function: The address bus is used to carry the memory addresses of the locations where data is to be read from or written to. It tells the system where the data is located or should be stored.
    • Unidirectional: The address bus is typically unidirectional, meaning data flows in one direction—from the CPU to memory or I/O devices—indicating where the data should be fetched or stored.
    • Width: The width of the address bus determines the maximum amount of memory the system can access. For example, a 16-bit address bus can access 2^16 = 65,536 memory locations, or 64 KB of memory. A 32-bit address bus can access up to 4 GB of memory.
    • Example: When the CPU wants to fetch data from a specific location in memory, it places the memory address on the address bus, and memory reads the data from that address.

    3. Control Bus

    • Function: The control bus is responsible for coordinating the activities of the CPU, memory, and other peripherals by transmitting control signals. These signals tell the system which operation is being performed (e.g., read, write, interrupt), as well as timing signals for synchronization.
    • Bidirectional: The control bus is often bidirectional, allowing signals to travel in both directions. It carries signals like:
      • Read/Write signals: Tells whether the operation is a read or a write.
      • Clock signals: Synchronizes the timing of operations.
      • Interrupt signals: Indicate the need for attention from the CPU, often used for handling I/O requests.
      • Bus Request/Grant signals: Indicate whether a device is requesting access to the system bus.

    Bus Architecture: How It Works

    1. CPU to Memory Communication:

      • The CPU places the memory address it wants to access on the address bus.
      • It sends a control signal over the control bus to indicate whether it wants to read or write data.
      • If reading, the CPU waits for the data to be placed on the data bus by the memory.
      • If writing, the CPU places the data to be written on the data bus, and the memory stores it at the specified address.
    2. I/O Devices Communication:

      • When the CPU needs to communicate with an I/O device (like a keyboard, printer, or disk), the address bus is used to specify which device is being accessed.
      • The CPU sends control signals over the control bus to manage the flow of data between the CPU and the I/O device.
      • Data is transferred over the data bus.

    Bus Width and Data Transfer Rate

    • Bus Width: Refers to the number of lines (bits) in the data, address, and control buses. The width determines how much data can be transferred at once and also impacts the overall system performance.

      • Example: A 32-bit system bus means the data bus, address bus, and control bus are all 32 bits wide. This allows for faster data transfer and larger addressable memory compared to a 16-bit bus.
    • Data Transfer Rate: The speed at which data can be transferred across the system bus. The data transfer rate depends on the bus width and the clock speed of the CPU. A faster clock speed or wider bus width means higher data transfer rates and better performance.


    Bus Contention and Arbitration

    In systems with multiple devices, bus contention may occur, where more than one device wants to access the bus simultaneously. To resolve this issue, bus arbitration mechanisms are used. Arbitration is the process of determining which device gets access to the system bus at any given time.

    • Types of Arbitration:
      1. Centralized Arbitration: One central controller (usually the CPU) controls the access to the bus.
      2. Distributed Arbitration: Each device has equal control and competes to access the bus. Devices follow a protocol to decide the order of access.

    Types of System Buses

    1. Single Bus Architecture:

      • In simpler systems, a single bus is shared by the CPU, memory, and I/O devices.
      • This architecture is easier and cheaper but can lead to performance bottlenecks since all components must share the same bus for data transfer.
    2. Multiple Bus Architecture:

      • In more advanced systems, multiple buses may be used, with different buses handling communication between the CPU and memory, or between the CPU and I/O devices, or other subsystems.
      • This reduces contention and allows for higher performance by allowing parallel data transfers.

    Example of System Bus in Action (Simplified)

    Let’s say the CPU wants to read a value from memory:

    1. The CPU places the memory address (where the data is located) on the address bus.
    2. The CPU sends a control signal over the control bus to tell memory to perform a read operation.
    3. Memory responds by placing the requested data on the data bus.
    4. The CPU reads the data from the data bus.

    Similarly, if the CPU wants to write data to memory, the process is reversed. The CPU places the data on the data bus, sends a write control signal, and memory stores the data at the specified address.


    System Bus vs. External Bus

    • System Bus: Refers to the bus that connects the CPU to internal components like RAM and I/O devices within the computer's motherboard.
    • External Bus: Refers to the bus that connects the computer to external devices (e.g., printers, monitors, external storage) or other computers in a network. External buses can include USB, PCIe, Thunderbolt, and more.

    Summary

    The system bus is the primary communication pathway that enables different components of a computer to interact with each other. It consists of three main components:

    • Data Bus: Transfers actual data.
    • Address Bus: Specifies where the data should go.
    • Control Bus: Coordinates the flow of data and operations.

    The width and speed of the system bus are crucial for determining the performance of a computer system, as a wider and faster bus allows quicker data transfer. Bus contention (when multiple devices compete for the same bus) is a potential issue, which is managed through bus arbitration.

    In summary, the system bus is a central element of computer architecture, facilitating communication between the processor, memory, and I/O devices, and directly impacting the overall performance of the system.

    Previous topic 7
    Registers
    Next topic 9
    Instruction Execution Cycle

    Past Papers

    Open this section to load past papers

    Click on Show Past Papers to see past papers.
    On This Page
      Reading Stats
      Est. reading time8 min
      Word count1,290
      Code examples0
      DifficultyIntermediate