crypto_router_asic.mdwn

   1 # Crypto-router ASIC
   2
   3 <img src="https://www.ngi.eu/wp-content/uploads/sites/48/2020/04/Logo_Pointer.png" width="200px" />
   4 <img src="https://ngi.eu/wp-content/uploads/sites/77/2017/10/bandiera_stelle.png" width="50px" />
   5
   6 **This project has received funding from the European Union’s Horizon 2020 research and innovation programme within the framework of the NGI-POINTER Project funded under grant agreement No 871528**
   7
   8 * NLnet page: [[nlnet_2021_crypto_router]]
   9 * Top-level bugreport: <https://bugs.libre-soc.org/show_bug.cgi?id=589>
  10 * Pinmux page: [[crypto_router_pinmux]]
  11
  12 # Specifications
  13
  14 All of these are entirely Libre-Licensed or are to be written as Libre-Licensed:
  15
  16 * 300 mhz single-core,
  17   [Libre-SOC](https://git.libre-soc.org/?p=soc.git;a=blob;f=README.md;hb=HEAD)
  18   OpenPOWER CPU with
  19   [[openpower/sv/bitmanip]] extensions
  20 * 180/130 nm (TBD)
  21 * 5x [[shakti/m_class/RGMII]] Gigabit Ethernet PHYs with
  22   [SRAM](https://github.com/adamgreig/daqnet/blob/master/gateware/daqnet/ethernet/rmii.py)
  23    on-chip, built-in.
  24 * 2x USB [[shakti/m_class/ULPI]] PHYs
  25 * Direct DMA interface (independent bulk transfer)
  26 * [JTAG](https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/debug/jtag.py;hb=HEAD),
  27   GPIO, I2C, PWM, UART, SPI, QSPI, SD/MMC
  28 * On-board Dual-ported SRAM (for Packet Buffers)
  29 * Opencores [[shakti/m_class/sdram]]
  30 * Wishbone interfaces to all peripherals
  31 * [XICS ICP / ICS](https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/interrupts/xics.py;hb=HEAD)
  32   Interrupt Controller
  33
  34
  35
  36 # Example packet transfer
  37
  38 * Packet comes in on RGMII port 1.  Each PHY has its own dual-ported SRAM
  39 * Packet is **directly** stored in internal (dual-ported SRAM) by
  40   the RGMII PHY itself
  41 * Interrupt notification is sent to the processor (XICS)
  42 * Processor inspects packet over Wishbone interface directly
  43   connected to 2nd SRAM port.
  44 * Processor computes, based on decoding the ETH Frame, where the
  45   packet must be sent to (which other RGM-II port: e.g. Port 2)
  46 * Processor initiates Memory-to-Memory DMA transfer
  47 * DMA Memory-to-Memory transfer, using Wishbone Bus, copies the ETH Frame
  48   from one on-board SRAM to the target on-board SRAM associated with Port 2.
  49 * DMA Engine generates interrupt (XICS) to the CPU to say it is completed
  50 * Processor notifies target RGM-II PHY to activate "send" of frame out
  51   through target RGM-II port 2.
  52
  53 # Testing and Verification
  54
  55 We will need full HDL simulations as well as post P&R simulations.
  56 These may be achieved as follows:
  57
  58 * ISA-level unit tests as well as Formal Correctness Proofs.
  59   Example [bpermd proof](https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/logical/formal/proof_bpermd.py;hb=HEAD)
  60   and individual unit tests for the
  61   [Logical pipeline](https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/logical/test/test_pipe_caller.py;hb=HEAD)
  62 * simulation
  63   with some peripherals developed in c++ as verilator modules
  64 * nmigen-based OpenPOWER Libre-SOC core co-simulation such as
  65   this unit test,
  66   [test_issuer.py](https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/simple/test/test_issuer.py;hb=HEAD)
  67 * [cocotb pre/post PnR](https://git.libre-soc.org/?p=soc-cocotb-sim.git;a=tree;f=ls180;hb=HEAD) including GHDL, Icarus and Verilator
  68   (where best suited)
  69
  70 Actual instructions being developed (bitmanip) may therefore be
  71 unit tested prior to deployment.  Following that, rapid simulations
  72 may be achieved by running Litex (the same HDL may also easily
  73 be uploaded to an FPGA).  When it comes to Place-and-Route of the
  74 ASIC, the cocotb simulations may be used to verify that the GDS-II
  75 layout has not been "damaged" by the PnR tools.
  76
  77 Peripherals functionality tests must also be part of the simulations,
  78 particularly using cocotb, to ensure that they remain functional after PnR.
  79 Supercomputer access for compilation of verilator and/or cxxrtl is available
  80 through [[fed4fire]]
  81