6.3.10 · D1Interconnects, Buses & SoC

Foundations — IP cores and SoC bus fabric

2,454 words11 min readBack to topic

This page assumes you have seen nothing. Before you meet a single AXI channel or crossbar formula in the parent note, you must own every word and symbol it throws at you. We build them one at a time, each on top of the last.


1. A chip, a block, and a wire

If we drew a wire from every building to every other building by hand, the city would be nothing but tangled roads. That tangle is exactly the problem this topic solves — so hold that picture.

Figure — IP cores and SoC bus fabric

Look at the left panel: buildings with private wires between every pair — chaos that grows fast. The right panel replaces them with one shared road every building taps into. That shared road is the seed of a bus.


2. IP core — a pre-built building

Why does the topic need this word? Because the whole point of an SoC is reuse. You do not design a USB controller from scratch; you buy the "USB building" and place it.

The parent note grades IP cores by how finished the building is when it arrives:

Word Plain meaning Picture
Soft IP arrives as source text (Verilog/VHDL) you still shape architect's blueprint — reshape freely
Firm IP arrives as a gate netlist (a wiring list of logic gates) pre-cut lumber — some shape fixed
Hard IP arrives as a fixed physical layout (exact transistor positions) finished concrete building — cannot move a wall

Two words above need their own definitions before we go on.


3. Master and slave — who starts a conversation

Every communication needs a starter and a responder. Hardware uses two blunt words.

The parent note names three common master IPs and their jobs — link them so you know what each building actually does:

  • DMA — a mover that shuttles data without bothering the CPU.
  • DRAM Controllers — the building that talks to main memory chips.
  • PCIe — a high-speed link to devices outside the chip.

4. Address, decoding, routing — how a parcel finds its door

The idea that "a location number tells hardware which block responds" has its own name in the vault: Memory-Mapped I/O. Every peripheral pretends to be a stretch of memory addresses.

Figure — IP cores and SoC bus fabric

The figure shows one address 0x1400 entering the decoder. Each slave carries a range sign; the decoder lights up the one slave whose range contains 0x1400 (the pink RAM), and routing opens that path only.


5. From one road to many — bus, arbitration, fabric

If two masters both want the road on the same tick, someone must referee.

Now the key upgrade the whole topic is built around:

Figure — IP cores and SoC bus fabric

Count the closed switches (yellow dots) in the figure: master M1 reaches slave S3 while M2 independently reaches S1 — two parcels, same instant. That parallelism is impossible on a single bus. The grid of dots is why the parent's formula counts switches.

Two more words the parent uses freely:

The vault has a whole page on the shapes these networks take: Interconnect Topologies.


6. Big-O — how cost grows, in one symbol

Why this tool and not a plain number? Because we care about the trend, not one instance — Big-O answers "will this still work when the chip doubles in size?" A single number can't answer that; a growth law can.


7. Clock, cycle, throughput — measuring speed


8. Pipelining, bursts, channels — the words that make AXI fast

Recall Why separate address and data channels?

Because their timings differ — the slave can accept an address and prepare while the master is still gathering the data. Separate belts let both happen at once instead of one blocking the other.


9. QoS — priority on the roads

One more prerequisite word the parent leans on when many masters share memory:


How the foundations feed the topic

chip and functional block

IP core

bus one shared road

master and slave roles

transaction

address

decoding and routing

arbitration

bus fabric

crossbar N x M

Big-O cost growth

clock cycle bit byte

throughput

pipelining bursts channels

AXI AHB APB

QoS priority

SoC bus fabric topic


Equipment checklist

Cover the right side and test yourself. If any answer is fuzzy, re-read its section.

What is an IP core, in one line?
A pre-designed, pre-tested functional block you license and drop into a chip — a pre-fab building.
Soft vs Hard IP — which is more flexible, which is faster?
Soft is most flexible (source text you reshape); Hard is fastest/smallest (fixed physical layout).
Who speaks first, master or slave?
The master — it starts the transaction; the slave only responds.
What does address decoding decide?
Which slave owns the address, so the request is routed to the correct door.
Why does a plain bus limit performance?
Only one transaction can use the single shared road at a time.
What does a bus fabric add over a bus?
Parallel paths plus decoders and arbiters, so several transactions run simultaneously.
How many switches does an N×M crossbar need, and why?
N × M — one crosspoint switch for every master–slave pair (area of the grid).
What does tell you?
Cost grows in proportion to the product N·M, so flat crossbars explode as the SoC scales.
Write the throughput formula.
(bits per transfer ÷ cycles per transfer) × clock rate.
Why does AXI use 5 separate channels?
Dedicated wires per traffic type let address, data, and response flow in parallel (pipelining).
What is a burst?
One address followed by many data words back-to-back, amortising the address overhead.
What does QoS provide on the fabric?
Priority arbitration so time-critical traffic wins the road over low-priority traffic.