Nostrum-SystemC-simulator

KO | EN

gitlite — search

#javascript #ai #llm #golang #android #machine-learning #docker #macos #java #windows #awesome #vue #mcp #openai

Nostrum-SystemC-simulator

(★ 14)

SystemC simulator of a highly customizable Nostrum network-on-chip (NoC).

Nostrum-SystemC-simulator Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Nostrum-SystemC-simulator
=========================

SystemC simulator of a highly customizable Nostrum network-on-chip (NoC).

INPUT FILES:
Follow the models included in the sw. There is not control on the correctness of the input files.

* indata5x5:
  start every new cycle with a line indicating the number n of the cycle: n-cycle.
  for every cycle specify row by row the inputs from the resources to the fifos.
  So, for example, if we have specified in the map file that the NoC is 5x5, we expect to find 5 lines for each row, specifying the inputs of the 5 resources each row.

Example: NoC 3x2 (3 rows, 2 columns)

1-cycle
  1-row
  //line 1 specifying inputs from resource in position (1,1)
  //line 2 specifying inputs from resource in position (1,2)
  2-row
  //line 1 specifying inputs from resource in position (2,1)
  //line 2 specifying inputs from resource in position (2,2)
  3-row
  //line 1 specifying inputs from resource in position (3,1)
  //line 2 specifying inputs from resource in position (3,2)
  2-cycle
  1-row
  ...
  
  every input packet is specified in this way:
  empty_bit | destination_addr_row | destination_addr_col | payload
      1 		-4 			4 		101
  
  with a single space between the numbers

1-cycle
  1-row
  1 -4 4 101
  ...
  
* map.txt: 
  in this file we give the informations about how the NoC is configured.

First line: it specifies the total dimension of the NoC. It needs 3 words (in the example, "dimensione totale rete(row,col):").
  We could also write "total NoC dimension(row,col):". Then 2 numbers divided by spaces must follow: the first is the rows number, the second the columns number.

Second line: 3 words ("number of subnets:") and 1 number representing it.

Following lines: for each subnet we need to specify 4 lines.
    1) 3 words ("subnet 0 dimension(row,col):") and the subnet dimension as 2 numbers;
    2) 3 words ("subnet 0 position(row,col):") and then 2 numbers indicating the coordinates (row,col) of the top left switch of the subnet;
    3) 3 words ("subnet 0 clock period(SC_NS):") and the number specifying N
    4) 3 words ("subnet 0 N:") and the number specifying N

the example attached to the sw create a noc like the following:

22333
    22333
    55544
    55544

OUTPUT FILES:

* example.txt: main output file, describing time step by time step how each switch looks like (which packets are in, which packets are out)
  Used to check traffic in the network with low level details!

* fifo.txt: describes time step by time step how each fifo looks like (which packets are in, which packets are out)

* tx_file.txt: file showing how to debug / analyze GRLS wrapper

* wave.vcd, wave2.vcd: visualize how packets go through the GRLS wrapper 
    
HOW TO COMPILE

* run the makefile. If SystemC is not in the path of your shell, you can add it 
  or modify the makefile following the instruction provided in the "Makefile" file.
  
HOW TO RUN

* as it is today, a successful compilation generates an executable named "run.x" 
  Running the executable without any flag (./run.x) is enough to run the simulation. 
  
* as it is today, input files are "hardcoded" in the C code. Future work is to pass them 
  as parameters, eventually setting flags to decide what to generate (between the output files) 
  so that the simulation time can be reduced. 
  
COMPARISON WITH SIMILAR PROJECTS:

The most similar project is the Semla simulator: http://www.ict.kth.se/nostrum/NNSE/

Semla additional features: 
  * permits to model an application (transport layer), not only packets!
  * more abstract model of the NoC-based system (divided in layers), simulator optimized for speed.
  * check their routing algorithm, if it is exactly the same!
  
Our additional features:
  * GRLS supprt
  * it is a lower abstraction level (network layer) but higher details (which details on each packet, where it is located in a specific time slot)

Nostrum-SystemC-simulator

Nostrum-SystemC-simulator Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Nostrum-SystemC-simulator

Nostrum-SystemC-simulator Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README