← Back to projects

Project case study

SystemC Router Network Simulation

Academic router-network simulation with YAML configuration

SystemCC++CMakeYAMLRouting Simulation
Summary

Quick overview

Academic SystemC project simulating packet routing across configurable router networks, including CPU-to-memory transactions, multi-router topologies, YAML-driven configuration, routing policies, and TTL handling.

Professional or private work. Details are summarized without exposing internal code, client data, or proprietary implementation details. Screenshots or private demo can be shared on request when available.

Problem

What needed to be solved

Built as a university project for modeling an interconnection system where packets are routed through networks of SystemC routers, with both end-to-end CPU-to-memory behavior and focused verification executables.
Implementation

What I worked on

Implemented and documented the router simulation behavior, configuration flow, packet forwarding logic, topology setup, and verification scenarios across one-router and multi-router networks.
Technical decisions

Responsibilities, systems, and engineering trade-offs

  • Packet model with source, destination, payload, and optional TTL fields
  • Router data ports modeled with FIFO-based input/output behavior and configurable internal queues
  • Routing tables mapping destinations to output ports
  • Priority and round-robin arbitration policies
  • YAML-driven configuration for routers, links, CPU attachments, memory attachments, queues, routes, and TTL behavior
  • Configurator and ConfigBus flow for broadcasting router configuration messages
  • CPU/MEM demo protocol using WR, RD, WR_ACK, and RD_RSP payloads
  • Verification executables for 1-router, 8-router, 16-router, TTL, and diagram-based mixed CPU/MEM topologies
  • Hop-by-hop test logs for observing packet propagation through multi-router links
  • Safety timeouts and TTL drop behavior to avoid infinite packet forwarding
Result

Result and value

Validated routing correctness, deterministic multi-hop propagation, configurable topology behavior, TTL-based packet dropping, and mixed CPU/MEM transactions across SystemC router networks.
What I learned

Practical takeaway

Simulation work becomes easier to trust when topology, routing, observability, and safety behavior are all configurable and testable.