-
+
←
🆒 Getting start
+ >👩🏼🏫 准备清单
May 1, 2024
diff --git a/public/device/cnc_manual/index.html b/public/device/cnc_manual/index.html
index 5b56e11..b53afa1 100644
--- a/public/device/cnc_manual/index.html
+++ b/public/device/cnc_manual/index.html
@@ -1,6 +1,6 @@
-
@@ -4169,30 +4169,6 @@
href="/device/contributing/"
>🎉 How to contribute
-
-
- - 👍Hardware：Build the CaaS Device
-
-
-
- 👩🏼🏫 准备清单
-
-
-
- 💦 Software:Time Sync + Config for CaaS Device
- 📕 ZIGGO Device使用手册
+
+
+
- 💦 Software:Time Sync + Config for CaaS Device
+
+
+
- 👍Hardware：Build the CaaS Device
- 🆒 Getting start
+
+
+
- 👩🏼🏫 准备清单
- 🎉 How to contribute
-
-
-
- 👩🏼🏫 准备清单
- 🧠 基础知识列表
+
+
+
- 👩🏼🏫 准备清单
@@ -4363,17 +4363,17 @@
@@ -4333,17 +4333,17 @@
-
+
👍Hardware：Build the CaaS Device💦 互联互通测试TestBed搭建流程
diff --git a/public/device/getting-started/index.html b/public/device/getting-started/index.html
index 8e4d80a..45d1053 100644
--- a/public/device/getting-started/index.html
+++ b/public/device/getting-started/index.html
@@ -1,6 +1,6 @@
-
@@ -4174,49 +4174,41 @@
- 👍Hardware：Build the CaaS Device
-
-
-
- 👩🏼🏫 准备清单
+ >💦 互联互通测试TestBed搭建流程
- 💦 Software:Time Sync + Config for CaaS Device
+ >📕 CNC脚本使用指南
- 💦 互联互通测试TestBed搭建流程
+ >📕 ZIGGO Device使用手册
- 📕 CNC脚本使用指南
+ >💦 Software:Time Sync + Config for CaaS Device
- 📕 ZIGGO Device使用手册
+ >👍Hardware：Build the CaaS Device
-
+
- 👩🏼🏫 准备清单
+
+
- 🎉 How to contribute
-
-
-
- 👩🏼🏫 准备清单
- 🧠 基础知识列表
+
+
+
- 👩🏼🏫 准备清单
@@ -4345,17 +4345,17 @@
- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
- Building and Starting the TSNPerf
- + 🧠 基础知识列表👩🏼🏫 准备清单 diff --git a/public/device/hardware-build/index.html b/public/device/hardware-build/index.html index 0813f3c..ca44fd4 100644 --- a/public/device/hardware-build/index.html +++ b/public/device/hardware-build/index.html @@ -1,6 +1,6 @@ - @@ -4169,6 +4169,38 @@ href="/device/contributing/" >🎉 How to contribute + + +
- 💦 互联互通测试TestBed搭建流程 + + +
- 📕 CNC脚本使用指南 + + +
- 📕 ZIGGO Device使用手册 + + +
- 💦 Software:Time Sync + Config for CaaS Device
- 👩🏼🏫 准备清单 - - -
- 💦 Software:Time Sync + Config for CaaS Device - - -
- 💦 互联互通测试TestBed搭建流程 - - -
- 📕 CNC脚本使用指南 - - -
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4357,17 +4357,17 @@- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
- 4. Run the Software
- + ← 🎉 How to contribute + >💦 Software:Time Sync + Config for CaaS Device May 1, 2024 @@ -5279,11 +5279,11 @@
4. Run the Software
- + 👩🏼🏫 准备清单🔨 System Design —— PL & PS Co-operate diff --git a/public/device/index.html b/public/device/index.html index b692be1..1e73a71 100644 --- a/public/device/index.html +++ b/public/device/index.html @@ -1,6 +1,6 @@ - @@ -4190,19 +4190,19 @@ZIGGO Device
- +@@ -4218,19 +4218,19 @@-
+ 
-🆒 Getting start+👩🏼🏫 准备清单- ZIGGO device get start document
+ ZIGGO 软硬件准备清单May 1, 2024
ZIGGO Device
- +@@ -4246,19 +4246,19 @@-
+
-🔨 System Design —— PL & PS Co-operate+🆒 Getting start- ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.
+ ZIGGO device get start documentMay 1, 2024
ZIGGO Device
- +@@ -4274,19 +4274,19 @@-
+
-📕 ZIGGO Device使用手册+🔨 System Design —— PL & PS Co-operate- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.May 1, 2024
ZIGGO Device
- +@@ -4302,19 +4302,19 @@-
+ 
-📕 CNC脚本使用指南+👍Hardware：Build the CaaS Device- 使用CNC脚本运行ZIGGO系统的7步指南
+ How to build the Caas Device Hardware step by step.May 1, 2024
ZIGGO Device
- +@@ -4330,19 +4330,19 @@-
+ 
-💦 互联互通测试TestBed搭建流程+💦 Software:Time Sync + Config for CaaS Device- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ Docs to enable CaaS Device' time synchronization logic and set up pkt gen.May 1, 2024
ZIGGO Device
- +@@ -4358,19 +4358,19 @@-
+
-💦 Software:Time Sync + Config for CaaS Device+📕 ZIGGO Device使用手册- Docs to enable CaaS Device' time synchronization logic and set up pkt gen.
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
ZIGGO Device
- +@@ -4386,19 +4386,19 @@-
+
-👩🏼🏫 准备清单+📕 CNC脚本使用指南- ZIGGO 软硬件准备清单
+ 使用CNC脚本运行ZIGGO系统的7步指南May 1, 2024
ZIGGO Device
- +diff --git a/public/device/index.xml b/public/device/index.xml index 1e869a1..23fca7c 100644 --- a/public/device/index.xml +++ b/public/device/index.xml @@ -43,72 +43,40 @@-
+
-👍Hardware：Build the CaaS Device+💦 互联互通测试TestBed搭建流程- How to build the Caas Device Hardware step by step.
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
- -
+ +👍Hardware：Build the CaaS Device - http://localhost:1313/device/hardware-build/ +💦 互联互通测试TestBed搭建流程 + http://localhost:1313/device/testbed/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/hardware-build/ -<h2 id="before-start">Before Start</h2> -<p>If you just want to teach the board to run instead of modifying it, and you use the hardware files we provide, you can skip directly to step <a href="#6-sd-card-partition-and-copy-file">SD card partition and copy file</a>.</p> -<h2 id="table-of-content">Table of Content</h2> -<ul> -<li><a href="#before-start">Before Start</a></li> -<li><a href="#table-of-content">Table of Content</a></li> -<li><a href="#install-vivado">Install Vivado</a></li> -<li><a href="#vivado-project-construction">Vivado project construction</a></li> -<li><a href="#petalinux">Petalinux</a> + http://localhost:1313/device/testbed/ +<h2 id="目录">目录</h2> <ul> -<li><a href="#1install-ubuntu-os">1.install ubuntu OS</a></li> -<li><a href="#2download-petalinux-related-image-files-in-advance">2.Download PetaLinux related image files in advance</a></li> -<li><a href="#3activate-the-petalinux-environment">3.Activate the PetaLinux environment</a></li> -<li><a href="#4create-petalinux-project">4.Create PetaLinux Project</a></li> -<li><a href="#5petalinux-configuration">5.Petalinux Configuration</a></li> -<li><a href="#6-sd-card-partition-and-copy-file">6. SD card partition and copy file</a> +<li><a href="#%e7%9b%ae%e5%bd%95">目录</a></li> +<li><a href="#testbed%e7%ae%80%e5%8d%95%e4%bb%8b%e7%bb%8d">TestBed简单介绍</a></li> +<li><a href="#%e4%ba%92%e8%81%94%e4%ba%92%e9%80%9a%e6%b5%8b%e8%af%95%e9%a1%b9%e7%9b%ae%e4%bb%8b%e7%bb%8d">互联互通测试项目介绍</a> <ul> -<li><a href="#file-downloading">File downloading</a></li> -<li><a href="#sd-card-partition">SD card partition</a></li> -<li><a href="#copy-files-into-sd-card">Copy files into SD card</a></li> +<li><a href="#1-%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">1. 基准测试</a></li> +<li><a href="#2-%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">2. 门控能力</a></li> +<li><a href="#3-%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">3. 带宽保证</a></li> +<li><a href="#4-%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">4. 门控精度</a></li> </ul> </li> +<li><a href="#%e8%ae%be%e5%a4%87%e5%8f%82%e6%95%b0%e8%ae%be%e7%bd%ae%e4%b8%8e%e9%83%a8%e7%bd%b2">设备参数设置与部署</a></li> +<li><a href="#testbed%e8%bf%90%e8%a1%8c%e6%b5%81%e7%a8%8b">TestBed运行流程</a> +<ul> +<li><a href="#%e5%87%86%e5%a4%87%e5%b7%a5%e4%bd%9c">准备工作</a> +<ul> +<li><a href="#%e6%8e%a7%e5%88%b6%e8%84%9a%e6%9c%ac%e5%87%86%e5%a4%87">控制脚本准备</a></li> +<li><a href="#%e8%83%8c%e6%99%af%e6%b5%81%e9%87%8f%e5%8f%91%e9%80%81">背景流量发送</a></li> </ul> </li> -<li><a href="#launch-the-board-and-log-in">Launch the Board and log in</a> -<ul> -<li><a href="#1-launch-the-board">1. Launch the Board</a></li> -<li><a href="#2-initialize-ps">2. Initialize PS</a></li> -<li><a href="#3-connect-to-internet">3. Connect to Internet</a></li> -<li><a href="#4-run-the-software">4. Run the Software</a></li> +<li><a href="#%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">基准测试</a></li> +<li><a href="#%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">门控能力</a></li> +<li><a href="#%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">带宽保证</a></li> +<li><a href="#%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">门控精度</a></li> </ul> </li> </ul> -<h2 id="install-vivado">Install Vivado</h2> -<p>You can download Vivado <a href="https://www.xilinx.com/products/design-tools/vivado.html" target="_blank" rel="noopener">here</a>.</p> -<p>We are using Vivado version 2020.1 (note: a unified version is required, otherwise running may cause problems).</p> -<h2 id="vivado-project-construction">Vivado project construction</h2> -<ol> -<li>clone the git repository for the hardware part.</li> -<li>Open Vivado and enter the command <code>cd Porject_Dir</code> in Tcl Console and <code>source ./tsn_device.tcl</code>. After the command is executed, Vivado will automatically open the created project. Here, we will first close Vivado and rename the folder where the project is located to <code>Work_ Dir</code>, so that git can correctly ignore this directory and enter <code>Work_ Dir</code>, double-click the <code>.xpr</code> file to open the project again.</li> -</ol> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./vivado_tcl_console.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> +<h2 id="testbed简单介绍">TestBed简单介绍</h2> +<p>我们内部对自己研发的CaaS-Switch进行了互联互通测试，采用的网络拓扑如下所示。</p> <p> @@ -127,49 +95,91 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./vivado_workdir.png" alt="" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./topo.PNG" alt="topo" loading="lazy" data-zoomable /></div> </div></figure> </p> +<p>本Demo需要4个FPGA开发板（2个TSNPerf、2个CaaS-Switch）和1台普通PC。如果条件有限/考虑简化拓扑，可以删去一个CaaS-Switch。PC负责发送背景流量，路径为黑色箭头；左侧TSNPerf负责发送测试流量（关键流量），路径为红色箭头。</p> +<p>所有测试项目的流程大致可以分为两个阶段：</p> <ol> -<li>Click <code>Generate Bitstream</code></li> +<li> +<p>时间同步：启动时间同步，保证TSNPerf、CaaS-Switch在一个时钟域下。</p> +<p>注：时间同步程序运行在TSNPerf、CaaS-Switch的系统中。</p> +</li> +<li> +<p>发送测试流量：根据schedule.json文件，TSNPerf进行测试流量发送。</p> +</li> </ol> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./vivado_bitstream.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> +<h2 id="互联互通测试项目介绍">互联互通测试项目介绍</h2> +<h3 id="1-基准测试">1. 基准测试</h3> +<ul> +<li>目的：测试无背景流量情况下，高优先级流量的两跳端到端延迟、丢包率、抖动，作为比较基准。</li> +<li>预期：延迟符合规划，抖动较低（100ns左右）。</li> +</ul> +<h3 id="2-门控能力">2. 门控能力</h3> +<ul> +<li>目的：测试通用情况下流量调度效果，和两个交换机的门控对接能力。</li> +<li>方案： +背景流量（VLAN priority = 0）打到线速，每个调度周期预留长度为 3 的时隙给高优先级流量， <ol> -<li> -<p>Export the xsa file. In Vivado, File Export Export Hardware. Select Fixed for Platform type. Select include bitstream for Output. Click Finish to export the xsa file.</p> -<p>Exported xsa file path: <code>Work_Dir/tns+tsn_device.xsa</code></p> +<li>每个周期定时发送 4 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录端到端平均延迟、抖动、丢包率、到达顺序</li> +<li>每个周期定时发送 8 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过且仅 n 个包</li> +</ol> </li> +<li>预期： +<ol> +<li>延迟、抖动、丢包率和基准一致</li> +<li>每个周期定时发送 4 个数据包时，丢包率为0</li> +<li>每个周期定时发送 8 个数据包时，每个周期通过且仅通过 5 个包（每8个包丢3个，因为每个时隙里恰好可以把第五个包发出去，余下三个包丢掉），丢包率为37.5%</li> </ol> -<h2 id="petalinux">Petalinux</h2> -<h3 id="1install-ubuntu-os">1.install ubuntu OS</h3> -<p>The following compilation processes are all completed within the virtual machine.</p> -<p>We recommend using the following configuration:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Virtual machine version: VMware Workstation 16 Pro -</span></span><span class="line"><span class="cl">Ubuntu version: ubuntu-16.04.3-desktop-amd64.iso -</span></span></code></pre></div><h3 id="2download-petalinux-related-image-files-in-advance">2.Download PetaLinux related image files in advance</h3> -<p>Enter website: <a href="https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools/archive.html" target="_blank" rel="noopener">https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools/archive.html</a></p> -<p>Select 2020.1 to find <code>PetaLinux Tools sstate-cache artifacts</code> and download <code>sstate_ arm_ 2020.1</code> and <code>downloads</code> and save the downloads in a specified directory in the virtual machine on January 2021 (the directory for this document is set to/home/alinx/data/)</p> -<p> +</li> +</ul> +<h3 id="3-带宽保证">3. 带宽保证</h3> +<ul> +<li>目的：测试交换机能够进行带宽预留，且两个交换机优先级映射、运行 cycle 和 offset 基本一致。</li> +<li>方案： +背景流量（VLAN priority = 0）打到线速（1Gbps），配置交换机预留 50% 时隙给高优先级流量（VLAN priority = 1），其余 50% 只允许低优先级流量， +<ol> +<li>测试流量高优先级（VLAN priority = 1）情况下打到线速（经测试，每个周期[33ms]连续发送2752个1500B的包，基本达到1000Mbps），记录端到端平均延迟、抖动、丢包率、到达顺序</li> +<li>测试流量高优先级（VLAN priority = 1）情况下打到50%线速（每个周期[33ms]连续发送1376个1500B的包），记录端到端平均延迟、抖动、丢包率、到达顺序</li> +</ol> +</li> +<li>预期： +<ol> +<li>高优先级测试流量100%线速：延迟、抖动和基准一致，丢包率 50% 左右</li> +<li>高优先级测试流量50%线速：延迟、抖动和基准一致，0丢包率</li> +</ol> +</li> +</ul> +<h3 id="4-门控精度">4. 门控精度</h3> +<ul> +<li>目的：测试门控时隙长度的设置精度</li> +<li>方案：(n=1,2,4,8,…) +<ol> +<li>每个调度周期预留长度为 1 的时隙给高优先级流量</li> +<li>每个周期发送 n 个数据包长度为1/n*1500Byte的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过 n 个包 +<ol> +<li>n=1,</li> +</ol> +</li> +</ol> +</li> +<li>预期： +<ol> +<li>n=1,2,4,8 情况下都能每个周期通过且仅通过 n 个包</li> +</ol> +</li> +</ul> +<blockquote> +<p>如果您按照下文的配置使用我们开源的ZIGGO交换机和TSNPerf，则您可以在上面四个测试中得到和预期相类似的效果。如果出现了任何问题，欢迎在github上提出issue。</p> +</blockquote> +<h2 id="设备参数设置与部署">设备参数设置与部署</h2> +<p>Switch软硬件代码在仓库 <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch" target="_blank" rel="noopener">ZIGGO-Caas-Switch</a> 中，使用主分支即可。</p> +<p>TSNPerf的软硬件代码在本仓库。</p> +<blockquote> +<p>注意：带宽能力测试中的TSNPerf需要使用offline_analyze分支，门控精度测试中的TSNPerf需要使用packet_resize分支【用于自定义测试包大小】。测试中请勿忘记切换分支。</p> +</blockquote> +<p>所有设备的IP、MAC和ID如下所示，与本文档后面提供的JSON配置文件对应：</p> +<p> @@ -187,221 +197,221 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./download_petalinux.png" alt="" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./topo_config.png" alt="topo config" loading="lazy" data-zoomable /></div> </div></figure> </p> -<h3 id="3activate-the-petalinux-environment">3.Activate the PetaLinux environment</h3> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">source</span> /opt/pkg/petalinux/settings.sh -</span></span></code></pre></div><p> Automatically activate the PetaLinux environment every time Terminal is started.</p> -<h3 id="4create-petalinux-project">4.Create PetaLinux Project</h3> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-create --type project --template zynq --name <project_name> -</span></span><span class="line"><span class="cl"><span class="nb">cd</span> <project_name> -</span></span></code></pre></div><h3 id="5petalinux-configuration">5.Petalinux Configuration</h3> +<p>对应的config文件可见<code>config.json</code></p> +<h2 id="testbed运行流程">TestBed运行流程</h2> +<h3 id="准备工作">准备工作</h3> +<h4 id="控制脚本准备">控制脚本准备</h4> +<p>可以参考 <a href="http://localhost:1313/device/cnc_manual/">CNC-User-Manual</a></p> +<h4 id="背景流量发送">背景流量发送</h4> +<p>可以直接在Linux PC中运行<code>send.py</code>脚本。（需要安装scapy,tcpreplay）</p> +<h3 id="基准测试">基准测试</h3> +<p>Switch、TSNPerf 的软硬件都使用主分支。</p> +<p>测试步骤：</p> <ol> -<li>Import Hardware Configuration</li> +<li>修改batch.mjs修改正确的配置文件名</li> +<li>./batch.mjs pull（注意分支正确）</li> +<li>./batch.mjs distribute +Device每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： +<code>base/d3s2-baseline-3t-config.json</code>， +<code>base/d3s2-baseline-3t-schedule-base.json</code></li> +<li>./batch.mjs launch （包括了时间同步和数据包发送）</li> +<li>./batch.mjs collect</li> </ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-config --get-hw-description <PATH-TO-XSA Directory> -</span></span></code></pre></div><p>Then you will enter the menuconfig page and configure as follows:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gdscript3" data-lang="gdscript3"><span class="line"><span class="cl"><span class="n">Subsystem</span> <span class="n">AUTO</span> <span class="n">Hardware</span> <span class="n">Settings</span> -</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Ethernet</span> <span class="n">Settings</span> -</span></span><span class="line"><span class="cl"> <span class="o">-></span> <span class="p">[</span><span class="o">*</span><span class="p">]</span> <span class="n">Randomise</span> <span class="n">MAC</span> <span class="n">address</span> -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"><span class="ne">Image</span> <span class="n">Packaging</span> <span class="n">Configurations</span> -</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Root</span> <span class="n">filesystem</span> <span class="n">type</span> -</span></span><span class="line"><span class="cl"> <span class="o">-></span> <span class="p">[</span><span class="o">*</span><span class="p">]</span> <span class="n">EXT4</span> <span class="p">(</span><span class="n">SD</span><span class="o">/</span><span class="n">eMMC</span><span class="o">/</span><span class="n">SATA</span><span class="o">/</span><span class="n">USB</span><span class="p">)</span> -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"><span class="n">Yocto</span> <span class="n">Settings</span> <span class="p">(</span><span class="n">Use</span> <span class="n">downloaded</span> <span class="n">image</span><span class="p">)</span> -</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Local</span> <span class="n">sstate</span> <span class="n">feeds</span> <span class="n">settings</span><span class="p">:</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">alinx</span><span class="o">/</span><span class="n">data</span><span class="o">/</span><span class="n">sstate_arm_2020</span><span class="o">.</span><span class="mi">1</span><span class="o">/</span><span class="n">arm</span> -</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Add</span> <span class="n">pre</span><span class="o">-</span><span class="n">mirror</span> <span class="n">url</span><span class="p">:</span> <span class="n">file</span><span class="p">:</span><span class="o">///</span><span class="n">home</span><span class="o">/</span><span class="n">alinx</span><span class="o">/</span><span class="n">data</span><span class="o">/</span><span class="n">downloads</span> -</span></span></code></pre></div><ol start="2"> -<li>make <code>Kernel Module</code></li> +<h3 id="门控能力">门控能力</h3> +<p>Switch、TSNPerf 的软硬件都使用主分支。</p> +<ol> +<li>让背景流量Device发包（基准测试不需要发送背景流量）</li> +<li>修改batch.mjs修改正确的配置文件名</li> +<li>./batch.mjs pull（注意分支正确）</li> +<li>./batch.mjs distribute +Device1每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： +<code>gate/d3s2-baseline-3t-config.json</code>， +<code>gate/d3s2-baseline-3t-schedule-gate.json</code></li> +<li>./batch.mjs launch</li> +<li>./batch.mjs collect</li> +<li>将上述的schedule.json中的Device发包个数从4改为8，再从上述步骤4重新测试，修改后的schedule.json如下所示</li> </ol> -<p> make a module named “<code>dma proxy</code>”:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-create -t modules -n dma-proxy --enable -</span></span></code></pre></div><p> replace the dma-proxy folder:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">rm -rf project-spec/meta-user/recipes-modules/* -</span></span></code></pre></div><p>download our dma-proxy (from <a href="https://cloud.tsinghua.edu.cn/f/85cfd8e8174e4689b79b/" target="_blank" rel="noopener">here</a>) and unzip in <code>project-spec/meta-user/recipes-modules/</code></p> -<ol start="3"> -<li>Configuring the kernel</li> -</ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-config -c kernel -</span></span></code></pre></div><p>Entering the <code>menuconfig</code> page, and do:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">Device Drivers -</span></span><span class="line"><span class="cl">-> Userspace I/O drivers -</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Userspace I/O platform driver with generic IRQ handling -</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Userspace platform driver with generic irq and dynamic memory -</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Xilinx AI Engine driverDevice Drivers -</span></span><span class="line"><span class="cl">-> Dma Engine Support -</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Xilinx DMA Engines -</span></span><span class="line"><span class="cl">-> Network device support -</span></span><span class="line"><span class="cl"> -> Ethernet driver support -</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Cadence devices -</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Cadence MACB/GEM support -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl">General setup -</span></span><span class="line"><span class="cl">-> Preemption Model -</span></span><span class="line"><span class="cl"> -> <span class="o">(</span>X<span class="o">)</span> No Forced Preemption <span class="o">(</span>Server<span class="o">)</span> -</span></span></code></pre></div><ol start="4"> -<li>Configuring rootfs</li> -</ol> -<p>Edit file <code>project-spec/meta-user/conf/user-rootfsconfig</code>, and <em><strong>add</strong></em> the following configuration:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">CONFIG_sudo -</span></span><span class="line"><span class="cl">CONFIG_sudo-dev -</span></span><span class="line"><span class="cl">CONFIG_dnf -</span></span><span class="line"><span class="cl">CONFIG_packagegroup-core-buildessential -</span></span><span class="line"><span class="cl">CONFIG_packagegroup-core-buildessential-dev -</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted -</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted-dev -</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted-sdk-dev -</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted-sdk -</span></span><span class="line"><span class="cl">CONFIG_python3 -</span></span><span class="line"><span class="cl">CONFIG_autoconf -</span></span><span class="line"><span class="cl">CONFIG_autoconf-dev -</span></span><span class="line"><span class="cl">CONFIG_automake -</span></span><span class="line"><span class="cl">CONFIG_automake-dev -</span></span><span class="line"><span class="cl">CONFIG_bison -</span></span><span class="line"><span class="cl">CONFIG_bison-dev -</span></span><span class="line"><span class="cl">CONFIG_flex -</span></span><span class="line"><span class="cl">CONFIG_flex-dev -</span></span><span class="line"><span class="cl">CONFIG_make -</span></span><span class="line"><span class="cl">CONFIG_make-dev -</span></span><span class="line"><span class="cl">CONFIG_python -</span></span><span class="line"><span class="cl">CONFIG_libtool -</span></span><span class="line"><span class="cl">CONFIG_libtool-dev -</span></span><span class="line"><span class="cl">CONFIG_sqlite3 -</span></span><span class="line"><span class="cl">CONFIG_cmake -</span></span><span class="line"><span class="cl">CONFIG_util-linux -</span></span><span class="line"><span class="cl">CONFIG_net-tools -</span></span></code></pre></div><p>Save and exit.</p> -<p>Input:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-config -c rootfs -</span></span></code></pre></div><p>Then you will enter the menuconfig page and configure as follows:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="nx">Image</span> <span class="nx">Features</span> -</span></span><span class="line"><span class="cl"><span class="o">-</span><span class="p">></span> <span class="p">[</span><span class="o">*</span><span class="p">]</span> <span class="kn">package</span> <span class="nx">management</span> -</span></span><span class="line"><span class="cl"> <span class="o">-</span><span class="p">></span> <span class="p">(</span><span class="nx">http</span><span class="p">:</span><span class="c1">//petalinux.xilinx.com/sswreleases/rel-v2020/feeds/zc702-zynq7/) Package feed url. -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="nx">user</span> <span class="nx">packages</span> -</span></span><span class="line"><span class="cl"><span class="o">-</span><span class="p">></span> <span class="nx">SELECT</span> <span class="nx">ALL</span> -</span></span></code></pre></div><ol start="5"> -<li>Compile the device tree</li> -</ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">petalinux-build -c device-tree -</span></span></code></pre></div><ol start="6"> -<li>Modify the device tree</li> -</ol> -<p>The generated device tree is located in <code>components/plnx_workspace/device tree/device tree/pl.dtsi</code> directory, we need to make modifications based on this file to meet some of our peripheral needs. The modified files are stored in the <code>project-spec/meta user/recipes bsp/device tree/files/system-user.dtsi</code> directory.</p> -<blockquote> -<p>Note: Between the <code>//>>></code> and <code>//<<<</code> is the content added between the comments.</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C" data-lang="C"><span class="line"><span class="cl"><span class="o">/</span><span class="n">include</span><span class="o">/</span> <span class="s">"system-conf.dtsi"</span> -</span></span><span class="line"><span class="cl"><span class="o">/</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nl">amba_pl</span><span class="p">:</span> <span class="n">amba_pl</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">dma_proxy</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span><span class="s">"xlnx,dma_proxy"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">dmas</span> <span class="o">=</span> <span class="o"><&</span><span class="n">axi_dma_0</span> <span class="mi">0</span> <span class="o">&</span><span class="n">axi_dma_0</span> <span class="mi">1</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">dma</span><span class="o">-</span><span class="n">names</span> <span class="o">=</span> <span class="s">"dma_proxy_tx"</span><span class="p">,</span> <span class="s">"dma_proxy_rx"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="nl">pkt_gen_controller_0</span><span class="p">:</span> <span class="n">pkt_gen_controller</span><span class="err">@</span><span class="mi">43</span><span class="n">c00000</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c00000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="nl">rtc0</span><span class="p">:</span> <span class="n">time_sync_uio</span><span class="err">@</span><span class="mi">43</span><span class="n">c10000</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c10000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="n">chosen</span><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">bootargs</span> <span class="o">=</span> <span class="s">"console=ttyPS0,115200 earlyprintk cma=256M uio_pdrv_genirq.of_id=generic-uio root=/dev/mmcblk0p2 rw rootwait"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">stdout</span><span class="o">-</span><span class="n">path</span> <span class="o">=</span> <span class="s">"serial0:115200n8"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"><span class="p">};</span> -</span></span><span class="line"><span class="cl"><span class="o">&</span><span class="n">gem1</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">local</span><span class="o">-</span><span class="n">mac</span><span class="o">-</span><span class="n">address</span> <span class="o">=</span> <span class="p">[</span><span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">02</span> <span class="mo">01</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">phy</span><span class="o">-</span><span class="n">mode</span> <span class="o">=</span> <span class="s">"gmii"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">fixed</span><span class="o">-</span><span class="n">link</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">speed</span> <span class="o">=</span> <span class="o"><</span><span class="mi">1000</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">full</span><span class="o">-</span><span class="n">duplex</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"><span class="p">};</span> -</span></span></code></pre></div><ol start="7"> -<li>Complie</li> -</ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-build -</span></span></code></pre></div><ol start="8"> -<li>Pack</li> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">8</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">1</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span><span class="err">,</span> +</span></span></code></pre></div><h3 id="带宽保证">带宽保证</h3> +<p>Switch代码使用主分支，TSNPerf代码使用offline_analyze分支。</p> +<p>测试步骤：</p> +<ol> +<li> +<p>让背景流量Device发包（基准测试不需要发送背景流量）</p> +</li> +<li> +<p>修改batch.mjs修改正确的配置文件名</p> +</li> +<li> +<p>./batch.mjs pull（注意分支正确）</p> +</li> +<li> +<p>./batch.mjs distribute +Device1每次发送1376个数据包，每个Switch都预留了1024个时隙，将以下两个配置文件下发即可： +<code>bandwidth/d3s2-baseline-50%t-config.json</code>， +<code>bandwidth/d3s2-baseline-50%t-schedule.json</code></p> +</li> +<li> +<p>./batch.mjs launch</p> +</li> +<li> +<p>使用离线分析</p> +</li> +<li> +<p>将上述的schedule.json中的Device发包个数从1376改为2752，再从上述步骤4重新测试，修改后的schedule.json如下所示</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">2752</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">1</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span><span class="err">,</span> +</span></span></code></pre></div></li> </ol> -<p>Here, you need to copy the bitstream file generated by Vivado to the virtual machine. (You can export bitstream file to where you want).</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./export_bitstream.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>Then:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">cd</span> images/linux -</span></span><span class="line"><span class="cl">petalinux-package --boot --fsbl zynq_fsbl.elf --fpga <FPGA bitstream path> --u-boot --force -</span></span></code></pre></div><p>After that, you can get 4 key file: <code>BOOT.BIN</code> <code>boot.scr</code> <code>image.ub</code> <code>rootfs.tar.gz</code></p> -<h3 id="6-sd-card-partition-and-copy-file">6. SD card partition and copy file</h3> -<h4 id="file-downloading">File downloading</h4> -<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/0bbc00543e5b4b82a6ea/" target="_blank" rel="noopener">this</a> public link or from preceding steps:</p> -<ul> -<li>BOOT.BIN</li> -<li>boot.scr</li> -<li>image.ub</li> -<li>rootfs.tar.gz</li> -</ul> -<h4 id="sd-card-partition">SD card partition</h4> -<p>In order to boot the TSNPerf, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted -</span></span><span class="line"><span class="cl">sudo gparted -</span></span></code></pre></div><p>Parition it into two partition below</p> -<ul> +<h3 id="门控精度">门控精度</h3> +<p>Switch代码使用主分支，TSNPerf代码使用packet_resize分支。</p> +<ol> <li> -<p>BOOT: store boot files from petalinux</p> -<p>Free space preceding (MiB): 4</p> -<p>New size (MiB): 500</p> -<p>File system: fat32</p> -<p>Label: BOOT</p> +<p>修改batch.mjs修改正确的配置文件名</p> </li> <li> -<p>ROOTFS: store debian system rootfs</p> -<p>Free space preceding (MiB): 0</p> -<p>Free space following (MiB): 0</p> -<p>File system: ext4</p> -<p>Label: ROOTFS</p> +<p>./batch.mjs pull（注意分支正确）</p> </li> -</ul> -<h4 id="copy-files-into-sd-card">Copy files into SD card</h4> -<p>Mound SD card:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ -</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ -</span></span></code></pre></div><p>Remove original files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* -</span></span></code></pre></div><p>Copy files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT +<li> +<p>./batch.mjs distribute +Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙，将以下两个配置文件下发即可： +<code>accuracy/d3s2-baseline-1t-config.json</code>， +<code>accuracy/d3s2-baseline-1t-schedule.json</code></p> +</li> +<li> +<p>./batch.mjs launch</p> +</li> +<li> +<p>./batch.mjs collect</p> +</li> +<li> +<p>将上述的schedule.json中的Device发包个数从1分别改为2,4,8，包长度分别改为750, 375和187，再从上述步骤4重新测试，发包个数修改为2后的schedule.json如下所示</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">750</span><span class="p">,</span> <span class="c1">// 1500/2 = 750 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">1</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span><span class="err">,</span> +</span></span></code></pre></div></li> +</ol> + +- +
+ +📕 CNC脚本使用指南 + http://localhost:1313/device/cnc_manual/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/cnc_manual/ +<h2 id="1-运行脚本前在batchmjs中要配置好以下变量">1. 运行脚本前，在batch.mjs中要配置好以下变量：</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// IP address format: 192.168.137.* +</span></span></span><span class="line"><span class="cl"><span class="c1">// 测试数据 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">conf_default</span> <span class="o">=</span> <span class="s2">"<需要执行的配置名称>"</span> +</span></span><span class="line"><span class="cl"><span class="c1">// 时钟主节点 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">master</span> <span class="o">=</span> <span class="mi">40</span> </span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh -</span></span><span class="line"><span class="cl">sync -</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS -</span></span></code></pre></div><h2 id="launch-the-board-and-log-in">Launch the Board and log in</h2> -<h3 id="1-launch-the-board">1. Launch the Board</h3> -<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> +</span></span><span class="line"><span class="cl"><span class="kr">const</span> <span class="nx">hosts</span> <span class="o">=</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nx">device</span><span class="o">:</span> <span class="p">[</span><span class="mi">43</span><span class="p">,</span> <span class="mi">44</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="k">switch</span><span class="o">:</span> <span class="p">[</span><span class="mi">40</span><span class="p">,</span> <span class="mi">41</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">安装好需要的依赖： +</span></span><span class="line"><span class="cl">```bash +</span></span><span class="line"><span class="cl">sudo npm install -g zx@4.3.0 +</span></span><span class="line"><span class="cl">pip install -r requirements.txt +</span></span><span class="line"><span class="cl">npm install +</span></span></code></pre></div><p>配置好环境变量，在.bashrc中加入：</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">export</span> <span class="nv">PYTHONPATH</span><span class="o">=</span><span class="s2">"/home/<用户名>/scripts"</span> +</span></span></code></pre></div><h2 id="2-下载好switch和tsnperf的软件代码">2. 下载好Switch和TSNPerf的软件代码</h2> +<blockquote> +<p>（记得提前配置好树莓派和所有板子之间的ssh public key，方便免密登录）</p> +</blockquote> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs clone +</span></span></code></pre></div><h2 id="3-拉取最新的软件代码并同步到远程板子上">3. 拉取最新的软件代码并同步到远程板子上</h2> +<blockquote> +<p>默认时master分支，如果需要指定分支，需要修改batch.mjs文件中的pull()函数，具体参考注释的部分</p> +</blockquote> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// pull all the latest code +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">pull</span> <span class="o">=</span> <span class="kr">async</span> <span class="p">()</span> <span class="p">=></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"><span class="nx">cd</span><span class="p">(</span><span class="sb">`</span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="p">()</span><span class="si">}</span><span class="sb">/repos`</span><span class="p">)</span> +</span></span><span class="line"><span class="cl"><span class="c1">// 如果需要指定分支，类似下面指定qbv-test分支的操作 +</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd pkt_gen_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` +</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd time_sync_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"><span class="kr">await</span> <span class="nb">Promise</span><span class="p">.</span><span class="nx">all</span><span class="p">(</span><span class="nx">hosts</span><span class="p">.</span><span class="nx">all</span><span class="p">.</span><span class="nx">map</span><span class="p">(</span><span class="nx">host</span> <span class="p">=></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="kr">const</span> <span class="nx">type</span> <span class="o">=</span> <span class="nx">hosts</span><span class="p">.</span><span class="nx">device</span><span class="p">.</span><span class="nx">includes</span><span class="p">(</span><span class="nx">host</span><span class="p">)</span> <span class="o">?</span> <span class="s1">'device'</span> <span class="o">:</span> <span class="s1">'switch'</span> +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'device'</span><span class="p">)</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/pkt_gen_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/`</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> <span class="k">else</span> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'switch'</span><span class="p">)</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/time_sync_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/;`</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"><span class="p">}))</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><p>同步到所有板子上：</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs pull +</span></span></code></pre></div><h2 id="4-使远程所有板子编译代码">4. 使远程所有板子编译代码</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs build +</span></span></code></pre></div><h2 id="5-将配置文件下发到所有板子上">5. 将配置文件下发到所有板子上</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs distribute +</span></span></code></pre></div><h2 id="6-开始启动所有板子的程序">6. 开始启动所有板子的程序</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs launch +</span></span></code></pre></div><h2 id="7-收集延迟和抖动的统计信息">7. 收集延迟和抖动的统计信息</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs collect +</span></span></code></pre></div> +- +
- -📕 ZIGGO Device使用手册 + http://localhost:1313/device/ziggo_device_manual/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/ziggo_device_manual/ +<p>There are two analysis methods for ZIGGO Device:</p> +<blockquote> +<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +</blockquote> +<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> <p> @@ -420,12 +430,10 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> </div></figure> -</p> -<h3 id="2-initialize-ps">2. Initialize PS</h3> -<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> -<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> +</p> +<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> <p> @@ -444,47 +452,46 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>The default username and password are as follows:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> -</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> -</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment. (<code>hardware/init_os.sh</code>)</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh -</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> -<h3 id="3-connect-to-internet">3. Connect to Internet</h3> -<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> -<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> -<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> -<h3 id="4-run-the-software">4. Run the Software</h3> -<p>Please refer to the software part of this repo for further instructions.</p> - -- -
@@ -553,40 +560,51 @@👩🏼🏫 准备清单 - http://localhost:1313/device/require/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/require/ -<h2 id="软件环境清单">软件环境清单</h2> -<h3 id="vivada-开发环境">Vivada 开发环境</h3> -<p>Vivado 是开发板的硬件开发程序。</p> -<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> -<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> -<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> -<h3 id="mobaxterm">MobaXterm</h3> -<p>MobaXterm是串口连接工具，我们在<a href="./hardware_build.md">hardware_build.md</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> -<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> -<h2 id="硬件准备清单">硬件准备清单</h2> -<h3 id="alinx7021开发板">Alinx7021开发板</h3> -<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> -<h3 id="sd启动卡">SD启动卡</h3> -<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> -<h3 id="必要的线材">必要的线材</h3> -<p>包括网线、数据线等。</p> -<h3 id="普通交换机">普通交换机</h3> -<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> +<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> +<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> +<p>Example of <code>packet_log.csv</code>:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency +</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 +</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 +</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 +</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 +</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 +</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 +</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 +</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 +</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 +</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 +</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance +</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 +</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 +</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 +</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 +</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 +</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 +</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 +</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 +</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 +</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 +</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 +</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 +</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> +<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> +<p>Example of packet capture command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng +</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> +<p>Code for analyzing programs is <code>analyze_packet.py</code></p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> +</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> - -
- -💦 互联互通测试TestBed搭建流程 - http://localhost:1313/device/testbed/ +👍Hardware：Build the CaaS Device + http://localhost:1313/device/hardware-build/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/testbed/ -<h2 id="目录">目录</h2> + http://localhost:1313/device/hardware-build/ +<h2 id="before-start">Before Start</h2> +<p>If you just want to teach the board to run instead of modifying it, and you use the hardware files we provide, you can skip directly to step <a href="#6-sd-card-partition-and-copy-file">SD card partition and copy file</a>.</p> +<h2 id="table-of-content">Table of Content</h2> <ul> -<li><a href="#%e7%9b%ae%e5%bd%95">目录</a></li> -<li><a href="#testbed%e7%ae%80%e5%8d%95%e4%bb%8b%e7%bb%8d">TestBed简单介绍</a></li> -<li><a href="#%e4%ba%92%e8%81%94%e4%ba%92%e9%80%9a%e6%b5%8b%e8%af%95%e9%a1%b9%e7%9b%ae%e4%bb%8b%e7%bb%8d">互联互通测试项目介绍</a> +<li><a href="#before-start">Before Start</a></li> +<li><a href="#table-of-content">Table of Content</a></li> +<li><a href="#install-vivado">Install Vivado</a></li> +<li><a href="#vivado-project-construction">Vivado project construction</a></li> +<li><a href="#petalinux">Petalinux</a> <ul> -<li><a href="#1-%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">1. 基准测试</a></li> -<li><a href="#2-%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">2. 门控能力</a></li> -<li><a href="#3-%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">3. 带宽保证</a></li> -<li><a href="#4-%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">4. 门控精度</a></li> +<li><a href="#1install-ubuntu-os">1.install ubuntu OS</a></li> +<li><a href="#2download-petalinux-related-image-files-in-advance">2.Download PetaLinux related image files in advance</a></li> +<li><a href="#3activate-the-petalinux-environment">3.Activate the PetaLinux environment</a></li> +<li><a href="#4create-petalinux-project">4.Create PetaLinux Project</a></li> +<li><a href="#5petalinux-configuration">5.Petalinux Configuration</a></li> +<li><a href="#6-sd-card-partition-and-copy-file">6. SD card partition and copy file</a> +<ul> +<li><a href="#file-downloading">File downloading</a></li> +<li><a href="#sd-card-partition">SD card partition</a></li> +<li><a href="#copy-files-into-sd-card">Copy files into SD card</a></li> </ul> </li> -<li><a href="#%e8%ae%be%e5%a4%87%e5%8f%82%e6%95%b0%e8%ae%be%e7%bd%ae%e4%b8%8e%e9%83%a8%e7%bd%b2">设备参数设置与部署</a></li> -<li><a href="#testbed%e8%bf%90%e8%a1%8c%e6%b5%81%e7%a8%8b">TestBed运行流程</a> -<ul> -<li><a href="#%e5%87%86%e5%a4%87%e5%b7%a5%e4%bd%9c">准备工作</a> -<ul> -<li><a href="#%e6%8e%a7%e5%88%b6%e8%84%9a%e6%9c%ac%e5%87%86%e5%a4%87">控制脚本准备</a></li> -<li><a href="#%e8%83%8c%e6%99%af%e6%b5%81%e9%87%8f%e5%8f%91%e9%80%81">背景流量发送</a></li> </ul> </li> -<li><a href="#%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">基准测试</a></li> -<li><a href="#%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">门控能力</a></li> -<li><a href="#%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">带宽保证</a></li> -<li><a href="#%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">门控精度</a></li> +<li><a href="#launch-the-board-and-log-in">Launch the Board and log in</a> +<ul> +<li><a href="#1-launch-the-board">1. Launch the Board</a></li> +<li><a href="#2-initialize-ps">2. Initialize PS</a></li> +<li><a href="#3-connect-to-internet">3. Connect to Internet</a></li> +<li><a href="#4-run-the-software">4. Run the Software</a></li> </ul> </li> </ul> -<h2 id="testbed简单介绍">TestBed简单介绍</h2> -<p>我们内部对自己研发的CaaS-Switch进行了互联互通测试，采用的网络拓扑如下所示。</p> +<h2 id="install-vivado">Install Vivado</h2> +<p>You can download Vivado <a href="https://www.xilinx.com/products/design-tools/vivado.html" target="_blank" rel="noopener">here</a>.</p> +<p>We are using Vivado version 2020.1 (note: a unified version is required, otherwise running may cause problems).</p> +<h2 id="vivado-project-construction">Vivado project construction</h2> +<ol> +<li>clone the git repository for the hardware part.</li> +<li>Open Vivado and enter the command <code>cd Porject_Dir</code> in Tcl Console and <code>source ./tsn_device.tcl</code>. After the command is executed, Vivado will automatically open the created project. Here, we will first close Vivado and rename the folder where the project is located to <code>Work_ Dir</code>, so that git can correctly ignore this directory and enter <code>Work_ Dir</code>, double-click the <code>.xpr</code> file to open the project again.</li> +</ol> <p> @@ -605,90 +623,33 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./topo.PNG" alt="topo" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./vivado_tcl_console.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./vivado_workdir.png" alt="" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>本Demo需要4个FPGA开发板（2个TSNPerf、2个CaaS-Switch）和1台普通PC。如果条件有限/考虑简化拓扑，可以删去一个CaaS-Switch。PC负责发送背景流量，路径为黑色箭头；左侧TSNPerf负责发送测试流量（关键流量），路径为红色箭头。</p> -<p>所有测试项目的流程大致可以分为两个阶段：</p> -<ol> -<li> -<p>时间同步：启动时间同步，保证TSNPerf、CaaS-Switch在一个时钟域下。</p> -<p>注：时间同步程序运行在TSNPerf、CaaS-Switch的系统中。</p> -</li> -<li> -<p>发送测试流量：根据schedule.json文件，TSNPerf进行测试流量发送。</p> -</li> -</ol> -<h2 id="互联互通测试项目介绍">互联互通测试项目介绍</h2> -<h3 id="1-基准测试">1. 基准测试</h3> -<ul> -<li>目的：测试无背景流量情况下，高优先级流量的两跳端到端延迟、丢包率、抖动，作为比较基准。</li> -<li>预期：延迟符合规划，抖动较低（100ns左右）。</li> -</ul> -<h3 id="2-门控能力">2. 门控能力</h3> -<ul> -<li>目的：测试通用情况下流量调度效果，和两个交换机的门控对接能力。</li> -<li>方案： -背景流量（VLAN priority = 0）打到线速，每个调度周期预留长度为 3 的时隙给高优先级流量， -<ol> -<li>每个周期定时发送 4 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录端到端平均延迟、抖动、丢包率、到达顺序</li> -<li>每个周期定时发送 8 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过且仅 n 个包</li> -</ol> -</li> -<li>预期： -<ol> -<li>延迟、抖动、丢包率和基准一致</li> -<li>每个周期定时发送 4 个数据包时，丢包率为0</li> -<li>每个周期定时发送 8 个数据包时，每个周期通过且仅通过 5 个包（每8个包丢3个，因为每个时隙里恰好可以把第五个包发出去，余下三个包丢掉），丢包率为37.5%</li> -</ol> -</li> -</ul> -<h3 id="3-带宽保证">3. 带宽保证</h3> -<ul> -<li>目的：测试交换机能够进行带宽预留，且两个交换机优先级映射、运行 cycle 和 offset 基本一致。</li> -<li>方案： -背景流量（VLAN priority = 0）打到线速（1Gbps），配置交换机预留 50% 时隙给高优先级流量（VLAN priority = 1），其余 50% 只允许低优先级流量， -<ol> -<li>测试流量高优先级（VLAN priority = 1）情况下打到线速（经测试，每个周期[33ms]连续发送2752个1500B的包，基本达到1000Mbps），记录端到端平均延迟、抖动、丢包率、到达顺序</li> -<li>测试流量高优先级（VLAN priority = 1）情况下打到50%线速（每个周期[33ms]连续发送1376个1500B的包），记录端到端平均延迟、抖动、丢包率、到达顺序</li> -</ol> -</li> -<li>预期： -<ol> -<li>高优先级测试流量100%线速：延迟、抖动和基准一致，丢包率 50% 左右</li> -<li>高优先级测试流量50%线速：延迟、抖动和基准一致，0丢包率</li> -</ol> -</li> -</ul> -<h3 id="4-门控精度">4. 门控精度</h3> -<ul> -<li>目的：测试门控时隙长度的设置精度</li> -<li>方案：(n=1,2,4,8,…) -<ol> -<li>每个调度周期预留长度为 1 的时隙给高优先级流量</li> -<li>每个周期发送 n 个数据包长度为1/n*1500Byte的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过 n 个包 -<ol> -<li>n=1,</li> -</ol> -</li> -</ol> -</li> -<li>预期： <ol> -<li>n=1,2,4,8 情况下都能每个周期通过且仅通过 n 个包</li> +<li>Click <code>Generate Bitstream</code></li> </ol> -</li> -</ul> -<blockquote> -<p>如果您按照下文的配置使用我们开源的ZIGGO交换机和TSNPerf，则您可以在上面四个测试中得到和预期相类似的效果。如果出现了任何问题，欢迎在github上提出issue。</p> -</blockquote> -<h2 id="设备参数设置与部署">设备参数设置与部署</h2> -<p>Switch软硬件代码在仓库 <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch" target="_blank" rel="noopener">ZIGGO-Caas-Switch</a> 中，使用主分支即可。</p> -<p>TSNPerf的软硬件代码在本仓库。</p> -<blockquote> -<p>注意：带宽能力测试中的TSNPerf需要使用offline_analyze分支，门控精度测试中的TSNPerf需要使用packet_resize分支【用于自定义测试包大小】。测试中请勿忘记切换分支。</p> -</blockquote> -<p>所有设备的IP、MAC和ID如下所示，与本文档后面提供的JSON配置文件对应：</p> <p> @@ -707,221 +668,257 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./topo_config.png" alt="topo config" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./vivado_bitstream.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<ol> +<li> +<p>Export the xsa file. In Vivado, File Export Export Hardware. Select Fixed for Platform type. Select include bitstream for Output. Click Finish to export the xsa file.</p> +<p>Exported xsa file path: <code>Work_Dir/tns+tsn_device.xsa</code></p> +</li> +</ol> +<h2 id="petalinux">Petalinux</h2> +<h3 id="1install-ubuntu-os">1.install ubuntu OS</h3> +<p>The following compilation processes are all completed within the virtual machine.</p> +<p>We recommend using the following configuration:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Virtual machine version: VMware Workstation 16 Pro +</span></span><span class="line"><span class="cl">Ubuntu version: ubuntu-16.04.3-desktop-amd64.iso +</span></span></code></pre></div><h3 id="2download-petalinux-related-image-files-in-advance">2.Download PetaLinux related image files in advance</h3> +<p>Enter website: <a href="https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools/archive.html" target="_blank" rel="noopener">https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools/archive.html</a></p> +<p>Select 2020.1 to find <code>PetaLinux Tools sstate-cache artifacts</code> and download <code>sstate_ arm_ 2020.1</code> and <code>downloads</code> and save the downloads in a specified directory in the virtual machine on January 2021 (the directory for this document is set to/home/alinx/data/)</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./download_petalinux.png" alt="" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>对应的config文件可见<code>config.json</code></p> -<h2 id="testbed运行流程">TestBed运行流程</h2> -<h3 id="准备工作">准备工作</h3> -<h4 id="控制脚本准备">控制脚本准备</h4> -<p>可以参考 <a href="http://localhost:1313/device/cnc_manual/">CNC-User-Manual</a></p> -<h4 id="背景流量发送">背景流量发送</h4> -<p>可以直接在Linux PC中运行<code>send.py</code>脚本。（需要安装scapy,tcpreplay）</p> -<h3 id="基准测试">基准测试</h3> -<p>Switch、TSNPerf 的软硬件都使用主分支。</p> -<p>测试步骤：</p> +<h3 id="3activate-the-petalinux-environment">3.Activate the PetaLinux environment</h3> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">source</span> /opt/pkg/petalinux/settings.sh +</span></span></code></pre></div><p> Automatically activate the PetaLinux environment every time Terminal is started.</p> +<h3 id="4create-petalinux-project">4.Create PetaLinux Project</h3> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-create --type project --template zynq --name <project_name> +</span></span><span class="line"><span class="cl"><span class="nb">cd</span> <project_name> +</span></span></code></pre></div><h3 id="5petalinux-configuration">5.Petalinux Configuration</h3> <ol> -<li>修改batch.mjs修改正确的配置文件名</li> -<li>./batch.mjs pull（注意分支正确）</li> -<li>./batch.mjs distribute -Device每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： -<code>base/d3s2-baseline-3t-config.json</code>， -<code>base/d3s2-baseline-3t-schedule-base.json</code></li> -<li>./batch.mjs launch （包括了时间同步和数据包发送）</li> -<li>./batch.mjs collect</li> +<li>Import Hardware Configuration</li> </ol> -<h3 id="门控能力">门控能力</h3> -<p>Switch、TSNPerf 的软硬件都使用主分支。</p> -<ol> -<li>让背景流量Device发包（基准测试不需要发送背景流量）</li> -<li>修改batch.mjs修改正确的配置文件名</li> -<li>./batch.mjs pull（注意分支正确）</li> -<li>./batch.mjs distribute -Device1每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： -<code>gate/d3s2-baseline-3t-config.json</code>， -<code>gate/d3s2-baseline-3t-schedule-gate.json</code></li> -<li>./batch.mjs launch</li> -<li>./batch.mjs collect</li> -<li>将上述的schedule.json中的Device发包个数从4改为8，再从上述步骤4重新测试，修改后的schedule.json如下所示</li> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-config --get-hw-description <PATH-TO-XSA Directory> +</span></span></code></pre></div><p>Then you will enter the menuconfig page and configure as follows:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gdscript3" data-lang="gdscript3"><span class="line"><span class="cl"><span class="n">Subsystem</span> <span class="n">AUTO</span> <span class="n">Hardware</span> <span class="n">Settings</span> +</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Ethernet</span> <span class="n">Settings</span> +</span></span><span class="line"><span class="cl"> <span class="o">-></span> <span class="p">[</span><span class="o">*</span><span class="p">]</span> <span class="n">Randomise</span> <span class="n">MAC</span> <span class="n">address</span> +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl"><span class="ne">Image</span> <span class="n">Packaging</span> <span class="n">Configurations</span> +</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Root</span> <span class="n">filesystem</span> <span class="n">type</span> +</span></span><span class="line"><span class="cl"> <span class="o">-></span> <span class="p">[</span><span class="o">*</span><span class="p">]</span> <span class="n">EXT4</span> <span class="p">(</span><span class="n">SD</span><span class="o">/</span><span class="n">eMMC</span><span class="o">/</span><span class="n">SATA</span><span class="o">/</span><span class="n">USB</span><span class="p">)</span> +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl"><span class="n">Yocto</span> <span class="n">Settings</span> <span class="p">(</span><span class="n">Use</span> <span class="n">downloaded</span> <span class="n">image</span><span class="p">)</span> +</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Local</span> <span class="n">sstate</span> <span class="n">feeds</span> <span class="n">settings</span><span class="p">:</span> <span class="o">/</span><span class="n">home</span><span class="o">/</span><span class="n">alinx</span><span class="o">/</span><span class="n">data</span><span class="o">/</span><span class="n">sstate_arm_2020</span><span class="o">.</span><span class="mi">1</span><span class="o">/</span><span class="n">arm</span> +</span></span><span class="line"><span class="cl"><span class="o">-></span> <span class="n">Add</span> <span class="n">pre</span><span class="o">-</span><span class="n">mirror</span> <span class="n">url</span><span class="p">:</span> <span class="n">file</span><span class="p">:</span><span class="o">///</span><span class="n">home</span><span class="o">/</span><span class="n">alinx</span><span class="o">/</span><span class="n">data</span><span class="o">/</span><span class="n">downloads</span> +</span></span></code></pre></div><ol start="2"> +<li>make <code>Kernel Module</code></li> </ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">8</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">1</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span><span class="err">,</span> -</span></span></code></pre></div><h3 id="带宽保证">带宽保证</h3> -<p>Switch代码使用主分支，TSNPerf代码使用offline_analyze分支。</p> -<p>测试步骤：</p> -<ol> -<li> -<p>让背景流量Device发包（基准测试不需要发送背景流量）</p> -</li> -<li> -<p>修改batch.mjs修改正确的配置文件名</p> -</li> -<li> -<p>./batch.mjs pull（注意分支正确）</p> -</li> -<li> -<p>./batch.mjs distribute -Device1每次发送1376个数据包，每个Switch都预留了1024个时隙，将以下两个配置文件下发即可： -<code>bandwidth/d3s2-baseline-50%t-config.json</code>， -<code>bandwidth/d3s2-baseline-50%t-schedule.json</code></p> -</li> -<li> -<p>./batch.mjs launch</p> -</li> -<li> -<p>使用离线分析</p> -</li> -<li> -<p>将上述的schedule.json中的Device发包个数从1376改为2752，再从上述步骤4重新测试，修改后的schedule.json如下所示</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">2752</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">1</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span><span class="err">,</span> -</span></span></code></pre></div></li> +<p> make a module named “<code>dma proxy</code>”:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-create -t modules -n dma-proxy --enable +</span></span></code></pre></div><p> replace the dma-proxy folder:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">rm -rf project-spec/meta-user/recipes-modules/* +</span></span></code></pre></div><p>download our dma-proxy (from <a href="https://cloud.tsinghua.edu.cn/f/85cfd8e8174e4689b79b/" target="_blank" rel="noopener">here</a>) and unzip in <code>project-spec/meta-user/recipes-modules/</code></p> +<ol start="3"> +<li>Configuring the kernel</li> </ol> -<h3 id="门控精度">门控精度</h3> -<p>Switch代码使用主分支，TSNPerf代码使用packet_resize分支。</p> -<ol> -<li> -<p>修改batch.mjs修改正确的配置文件名</p> -</li> -<li> -<p>./batch.mjs pull（注意分支正确）</p> -</li> -<li> -<p>./batch.mjs distribute -Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙，将以下两个配置文件下发即可： -<code>accuracy/d3s2-baseline-1t-config.json</code>， -<code>accuracy/d3s2-baseline-1t-schedule.json</code></p> -</li> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-config -c kernel +</span></span></code></pre></div><p>Entering the <code>menuconfig</code> page, and do:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">Device Drivers +</span></span><span class="line"><span class="cl">-> Userspace I/O drivers +</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Userspace I/O platform driver with generic IRQ handling +</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Userspace platform driver with generic irq and dynamic memory +</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Xilinx AI Engine driverDevice Drivers +</span></span><span class="line"><span class="cl">-> Dma Engine Support +</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Xilinx DMA Engines +</span></span><span class="line"><span class="cl">-> Network device support +</span></span><span class="line"><span class="cl"> -> Ethernet driver support +</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Cadence devices +</span></span><span class="line"><span class="cl"> -> <span class="o">[</span>*<span class="o">]</span> Cadence MACB/GEM support +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl">General setup +</span></span><span class="line"><span class="cl">-> Preemption Model +</span></span><span class="line"><span class="cl"> -> <span class="o">(</span>X<span class="o">)</span> No Forced Preemption <span class="o">(</span>Server<span class="o">)</span> +</span></span></code></pre></div><ol start="4"> +<li>Configuring rootfs</li> +</ol> +<p>Edit file <code>project-spec/meta-user/conf/user-rootfsconfig</code>, and <em><strong>add</strong></em> the following configuration:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">CONFIG_sudo +</span></span><span class="line"><span class="cl">CONFIG_sudo-dev +</span></span><span class="line"><span class="cl">CONFIG_dnf +</span></span><span class="line"><span class="cl">CONFIG_packagegroup-core-buildessential +</span></span><span class="line"><span class="cl">CONFIG_packagegroup-core-buildessential-dev +</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted +</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted-dev +</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted-sdk-dev +</span></span><span class="line"><span class="cl">CONFIG_packagegroup-self-hosted-sdk +</span></span><span class="line"><span class="cl">CONFIG_python3 +</span></span><span class="line"><span class="cl">CONFIG_autoconf +</span></span><span class="line"><span class="cl">CONFIG_autoconf-dev +</span></span><span class="line"><span class="cl">CONFIG_automake +</span></span><span class="line"><span class="cl">CONFIG_automake-dev +</span></span><span class="line"><span class="cl">CONFIG_bison +</span></span><span class="line"><span class="cl">CONFIG_bison-dev +</span></span><span class="line"><span class="cl">CONFIG_flex +</span></span><span class="line"><span class="cl">CONFIG_flex-dev +</span></span><span class="line"><span class="cl">CONFIG_make +</span></span><span class="line"><span class="cl">CONFIG_make-dev +</span></span><span class="line"><span class="cl">CONFIG_python +</span></span><span class="line"><span class="cl">CONFIG_libtool +</span></span><span class="line"><span class="cl">CONFIG_libtool-dev +</span></span><span class="line"><span class="cl">CONFIG_sqlite3 +</span></span><span class="line"><span class="cl">CONFIG_cmake +</span></span><span class="line"><span class="cl">CONFIG_util-linux +</span></span><span class="line"><span class="cl">CONFIG_net-tools +</span></span></code></pre></div><p>Save and exit.</p> +<p>Input:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-config -c rootfs +</span></span></code></pre></div><p>Then you will enter the menuconfig page and configure as follows:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="nx">Image</span> <span class="nx">Features</span> +</span></span><span class="line"><span class="cl"><span class="o">-</span><span class="p">></span> <span class="p">[</span><span class="o">*</span><span class="p">]</span> <span class="kn">package</span> <span class="nx">management</span> +</span></span><span class="line"><span class="cl"> <span class="o">-</span><span class="p">></span> <span class="p">(</span><span class="nx">http</span><span class="p">:</span><span class="c1">//petalinux.xilinx.com/sswreleases/rel-v2020/feeds/zc702-zynq7/) Package feed url. +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="nx">user</span> <span class="nx">packages</span> +</span></span><span class="line"><span class="cl"><span class="o">-</span><span class="p">></span> <span class="nx">SELECT</span> <span class="nx">ALL</span> +</span></span></code></pre></div><ol start="5"> +<li>Compile the device tree</li> +</ol> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">petalinux-build -c device-tree +</span></span></code></pre></div><ol start="6"> +<li>Modify the device tree</li> +</ol> +<p>The generated device tree is located in <code>components/plnx_workspace/device tree/device tree/pl.dtsi</code> directory, we need to make modifications based on this file to meet some of our peripheral needs. The modified files are stored in the <code>project-spec/meta user/recipes bsp/device tree/files/system-user.dtsi</code> directory.</p> +<blockquote> +<p>Note: Between the <code>//>>></code> and <code>//<<<</code> is the content added between the comments.</p> +</blockquote> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C" data-lang="C"><span class="line"><span class="cl"><span class="o">/</span><span class="n">include</span><span class="o">/</span> <span class="s">"system-conf.dtsi"</span> +</span></span><span class="line"><span class="cl"><span class="o">/</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nl">amba_pl</span><span class="p">:</span> <span class="n">amba_pl</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">dma_proxy</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span><span class="s">"xlnx,dma_proxy"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">dmas</span> <span class="o">=</span> <span class="o"><&</span><span class="n">axi_dma_0</span> <span class="mi">0</span> <span class="o">&</span><span class="n">axi_dma_0</span> <span class="mi">1</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">dma</span><span class="o">-</span><span class="n">names</span> <span class="o">=</span> <span class="s">"dma_proxy_tx"</span><span class="p">,</span> <span class="s">"dma_proxy_rx"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="nl">pkt_gen_controller_0</span><span class="p">:</span> <span class="n">pkt_gen_controller</span><span class="err">@</span><span class="mi">43</span><span class="n">c00000</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c00000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="nl">rtc0</span><span class="p">:</span> <span class="n">time_sync_uio</span><span class="err">@</span><span class="mi">43</span><span class="n">c10000</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c10000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="n">chosen</span><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">bootargs</span> <span class="o">=</span> <span class="s">"console=ttyPS0,115200 earlyprintk cma=256M uio_pdrv_genirq.of_id=generic-uio root=/dev/mmcblk0p2 rw rootwait"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">stdout</span><span class="o">-</span><span class="n">path</span> <span class="o">=</span> <span class="s">"serial0:115200n8"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"><span class="p">};</span> +</span></span><span class="line"><span class="cl"><span class="o">&</span><span class="n">gem1</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">local</span><span class="o">-</span><span class="n">mac</span><span class="o">-</span><span class="n">address</span> <span class="o">=</span> <span class="p">[</span><span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">02</span> <span class="mo">01</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">phy</span><span class="o">-</span><span class="n">mode</span> <span class="o">=</span> <span class="s">"gmii"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">fixed</span><span class="o">-</span><span class="n">link</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">speed</span> <span class="o">=</span> <span class="o"><</span><span class="mi">1000</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">full</span><span class="o">-</span><span class="n">duplex</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"><span class="p">};</span> +</span></span></code></pre></div><ol start="7"> +<li>Complie</li> +</ol> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-build +</span></span></code></pre></div><ol start="8"> +<li>Pack</li> +</ol> +<p>Here, you need to copy the bitstream file generated by Vivado to the virtual machine. (You can export bitstream file to where you want).</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./export_bitstream.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>Then:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">cd</span> images/linux +</span></span><span class="line"><span class="cl">petalinux-package --boot --fsbl zynq_fsbl.elf --fpga <FPGA bitstream path> --u-boot --force +</span></span></code></pre></div><p>After that, you can get 4 key file: <code>BOOT.BIN</code> <code>boot.scr</code> <code>image.ub</code> <code>rootfs.tar.gz</code></p> +<h3 id="6-sd-card-partition-and-copy-file">6. SD card partition and copy file</h3> +<h4 id="file-downloading">File downloading</h4> +<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/0bbc00543e5b4b82a6ea/" target="_blank" rel="noopener">this</a> public link or from preceding steps:</p> +<ul> +<li>BOOT.BIN</li> +<li>boot.scr</li> +<li>image.ub</li> +<li>rootfs.tar.gz</li> +</ul> +<h4 id="sd-card-partition">SD card partition</h4> +<p>In order to boot the TSNPerf, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted +</span></span><span class="line"><span class="cl">sudo gparted +</span></span></code></pre></div><p>Parition it into two partition below</p> +<ul> <li> -<p>./batch.mjs launch</p> +<p>BOOT: store boot files from petalinux</p> +<p>Free space preceding (MiB): 4</p> +<p>New size (MiB): 500</p> +<p>File system: fat32</p> +<p>Label: BOOT</p> </li> <li> -<p>./batch.mjs collect</p> +<p>ROOTFS: store debian system rootfs</p> +<p>Free space preceding (MiB): 0</p> +<p>Free space following (MiB): 0</p> +<p>File system: ext4</p> +<p>Label: ROOTFS</p> </li> -<li> -<p>将上述的schedule.json中的Device发包个数从1分别改为2,4,8，包长度分别改为750, 375和187，再从上述步骤4重新测试，发包个数修改为2后的schedule.json如下所示</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">750</span><span class="p">,</span> <span class="c1">// 1500/2 = 750 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">1</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span><span class="err">,</span> -</span></span></code></pre></div></li> -</ol> - -- -
- -📕 CNC脚本使用指南 - http://localhost:1313/device/cnc_manual/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/cnc_manual/ -<h2 id="1-运行脚本前在batchmjs中要配置好以下变量">1. 运行脚本前，在batch.mjs中要配置好以下变量：</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// IP address format: 192.168.137.* -</span></span></span><span class="line"><span class="cl"><span class="c1">// 测试数据 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">conf_default</span> <span class="o">=</span> <span class="s2">"<需要执行的配置名称>"</span> -</span></span><span class="line"><span class="cl"><span class="c1">// 时钟主节点 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">master</span> <span class="o">=</span> <span class="mi">40</span> -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"><span class="kr">const</span> <span class="nx">hosts</span> <span class="o">=</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nx">device</span><span class="o">:</span> <span class="p">[</span><span class="mi">43</span><span class="p">,</span> <span class="mi">44</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="k">switch</span><span class="o">:</span> <span class="p">[</span><span class="mi">40</span><span class="p">,</span> <span class="mi">41</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">安装好需要的依赖： -</span></span><span class="line"><span class="cl">```bash -</span></span><span class="line"><span class="cl">sudo npm install -g zx@4.3.0 -</span></span><span class="line"><span class="cl">pip install -r requirements.txt -</span></span><span class="line"><span class="cl">npm install -</span></span></code></pre></div><p>配置好环境变量，在.bashrc中加入：</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">export</span> <span class="nv">PYTHONPATH</span><span class="o">=</span><span class="s2">"/home/<用户名>/scripts"</span> -</span></span></code></pre></div><h2 id="2-下载好switch和tsnperf的软件代码">2. 下载好Switch和TSNPerf的软件代码</h2> -<blockquote> -<p>（记得提前配置好树莓派和所有板子之间的ssh public key，方便免密登录）</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs clone -</span></span></code></pre></div><h2 id="3-拉取最新的软件代码并同步到远程板子上">3. 拉取最新的软件代码并同步到远程板子上</h2> -<blockquote> -<p>默认时master分支，如果需要指定分支，需要修改batch.mjs文件中的pull()函数，具体参考注释的部分</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// pull all the latest code -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">pull</span> <span class="o">=</span> <span class="kr">async</span> <span class="p">()</span> <span class="p">=></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"><span class="nx">cd</span><span class="p">(</span><span class="sb">`</span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="p">()</span><span class="si">}</span><span class="sb">/repos`</span><span class="p">)</span> -</span></span><span class="line"><span class="cl"><span class="c1">// 如果需要指定分支，类似下面指定qbv-test分支的操作 -</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd pkt_gen_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` -</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd time_sync_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"><span class="kr">await</span> <span class="nb">Promise</span><span class="p">.</span><span class="nx">all</span><span class="p">(</span><span class="nx">hosts</span><span class="p">.</span><span class="nx">all</span><span class="p">.</span><span class="nx">map</span><span class="p">(</span><span class="nx">host</span> <span class="p">=></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="kr">const</span> <span class="nx">type</span> <span class="o">=</span> <span class="nx">hosts</span><span class="p">.</span><span class="nx">device</span><span class="p">.</span><span class="nx">includes</span><span class="p">(</span><span class="nx">host</span><span class="p">)</span> <span class="o">?</span> <span class="s1">'device'</span> <span class="o">:</span> <span class="s1">'switch'</span> +</ul> +<h4 id="copy-files-into-sd-card">Copy files into SD card</h4> +<p>Mound SD card:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ +</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ +</span></span></code></pre></div><p>Remove original files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* +</span></span></code></pre></div><p>Copy files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT </span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'device'</span><span class="p">)</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/pkt_gen_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/`</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> <span class="k">else</span> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'switch'</span><span class="p">)</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/time_sync_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/;`</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"><span class="p">}))</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><p>同步到所有板子上：</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs pull -</span></span></code></pre></div><h2 id="4-使远程所有板子编译代码">4. 使远程所有板子编译代码</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs build -</span></span></code></pre></div><h2 id="5-将配置文件下发到所有板子上">5. 将配置文件下发到所有板子上</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs distribute -</span></span></code></pre></div><h2 id="6-开始启动所有板子的程序">6. 开始启动所有板子的程序</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs launch -</span></span></code></pre></div><h2 id="7-收集延迟和抖动的统计信息">7. 收集延迟和抖动的统计信息</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs collect -</span></span></code></pre></div> -- -
@@ -1350,6 +1324,32 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， +📕 ZIGGO Device使用手册 - http://localhost:1313/device/ziggo_device_manual/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/ziggo_device_manual/ -<p>There are two analysis methods for ZIGGO Device:</p> -<blockquote> -<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> -</blockquote> -<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> +</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh +</span></span><span class="line"><span class="cl">sync +</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS +</span></span></code></pre></div><h2 id="launch-the-board-and-log-in">Launch the Board and log in</h2> +<h3 id="1-launch-the-board">1. Launch the Board</h3> +<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> <p> @@ -940,10 +937,12 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<h3 id="2-initialize-ps">2. Initialize PS</h3> +<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> +<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> <p> @@ -962,46 +961,21 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> </div></figure> </p> -<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> -<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> -<p>Example of <code>packet_log.csv</code>:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency -</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 -</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 -</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 -</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 -</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 -</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 -</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 -</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 -</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 -</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 -</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance -</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 -</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 -</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 -</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 -</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 -</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 -</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 -</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 -</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 -</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 -</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 -</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 -</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> -<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> -<p>Example of packet capture command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng -</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> -<p>Code for analyzing programs is <code>analyze_packet.py</code></p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> -</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> +<p>The default username and password are as follows:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> +</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> +</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment. (<code>hardware/init_os.sh</code>)</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh +</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> +<h3 id="3-connect-to-internet">3. Connect to Internet</h3> +<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> +<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> +<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> +<h3 id="4-run-the-software">4. Run the Software</h3> +<p>Please refer to the software part of this repo for further instructions.</p> - +
+👩🏼🏫 准备清单 + http://localhost:1313/device/require/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/require/ +<h2 id="软件环境清单">软件环境清单</h2> +<h3 id="vivada-开发环境">Vivada 开发环境</h3> +<p>Vivado 是开发板的硬件开发程序。</p> +<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> +<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> +<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> +<h3 id="mobaxterm">MobaXterm</h3> +<p>MobaXterm是串口连接工具，我们在<a href="./hardware_build.md">hardware_build.md</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> +<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> +<h2 id="硬件准备清单">硬件准备清单</h2> +<h3 id="alinx7021开发板">Alinx7021开发板</h3> +<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> +<h3 id="sd启动卡">SD启动卡</h3> +<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> +<h3 id="必要的线材">必要的线材</h3> +<p>包括网线、数据线等。</p> +<h3 id="普通交换机">普通交换机</h3> +<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> + +🧠 基础知识列表 http://localhost:1313/device/basic_knowledge/ diff --git a/public/device/require/index.html b/public/device/require/index.html index fea4f05..04a2861 100644 --- a/public/device/require/index.html +++ b/public/device/require/index.html @@ -1,6 +1,6 @@ - @@ -4174,64 +4174,41 @@- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程 -
- 👩🏼🏫 准备清单 - - - - -
- 💦 Software:Time Sync + Config for CaaS Device + >📕 CNC脚本使用指南
- 💦 互联互通测试TestBed搭建流程 + >📕 ZIGGO Device使用手册
- 📕 CNC脚本使用指南 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 ZIGGO Device使用手册 + >👍Hardware：Build the CaaS Device
- 🆒 Getting start +
- 👩🏼🏫 准备清单 + + + + +
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4333,17 +4333,17 @@- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
- 普通交换机
- + 💦 Software:Time Sync + Config for CaaS Device🧠 基础知识列表 diff --git a/public/device/software-build/index.html b/public/device/software-build/index.html index 0aba316..254d785 100644 --- a/public/device/software-build/index.html +++ b/public/device/software-build/index.html @@ -1,6 +1,6 @@ - @@ -4174,17 +4174,25 @@diff --git a/public/switch/software_build/index.html b/public/switch/software_build/index.html index c4da94b..46f9410 100644 --- a/public/switch/software_build/index.html +++ b/public/switch/software_build/index.html @@ -1,6 +1,6 @@ - @@ -4174,65 +4174,65 @@
- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南 + + +
- 📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 - - -
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4351,17 +4351,17 @@- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
- 4.1 TSNPerf directly an
- + 💦 互联互通测试TestBed搭建流程👍Hardware：Build the CaaS Device diff --git a/public/device/system-design/index.html b/public/device/system-design/index.html index 23b81c3..d04c45f 100644 --- a/public/device/system-design/index.html +++ b/public/device/system-design/index.html @@ -1,6 +1,6 @@ - @@ -4174,49 +4174,41 @@diff --git a/public/switch/contributing/index.html b/public/switch/contributing/index.html index 3a46af0..f624bb3 100644 --- a/public/switch/contributing/index.html +++ b/public/switch/contributing/index.html @@ -1,6 +1,6 @@ - @@ -4174,65 +4174,65 @@
- 👍Hardware：Build the CaaS Device - - -
- 👩🏼🏫 准备清单 + >💦 互联互通测试TestBed搭建流程
- 💦 Software:Time Sync + Config for CaaS Device + >📕 CNC脚本使用指南
- 💦 互联互通测试TestBed搭建流程 + >📕 ZIGGO Device使用手册
- 📕 CNC脚本使用指南 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 ZIGGO Device使用手册 + >👍Hardware：Build the CaaS Device
- 🆒 Getting start + + +
- 👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4345,17 +4345,17 @@- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- -
- 👩🏼🏫 准备清单 - -
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4333,17 +4333,17 @@- + 👩🏼🏫 准备清单💦 Software:Time Sync + Config for CaaS Switches diff --git a/public/switch/hardware-build/index.html b/public/switch/hardware-build/index.html index 3e1bb03..b309f8a 100644 --- a/public/switch/hardware-build/index.html +++ b/public/switch/hardware-build/index.html @@ -1,6 +1,6 @@ - @@ -4174,65 +4174,65 @@- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4345,17 +4345,17 @@- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
-
-
@@ -4162,19 +4162,19 @@
ZIGGO Switch
- +@@ -4190,19 +4190,19 @@-
+ 
-🧠 基础知识列表+👩🏼🏫 准备清单- 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表
+ ZIGGO 软硬件准备清单May 1, 2024
ZIGGO Switch
- +@@ -4218,19 +4218,19 @@-
+
-🔨 System Design —— PL & PS Co-operate+🧠 基础知识列表- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表May 1, 2024
ZIGGO Switch
- +@@ -4246,19 +4246,19 @@-
+
-💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit+🔨 System Design —— PL & PS Co-operate- Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
ZIGGO Switch
- +@@ -4274,19 +4274,19 @@-
+
-💦 Software:Time Sync + Config for CaaS Switches+💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation ToolkitMay 1, 2024
ZIGGO Switch
- +diff --git a/public/switch/index.xml b/public/switch/index.xml index b25c5bc..25ee103 100644 --- a/public/switch/index.xml +++ b/public/switch/index.xml @@ -42,32 +42,6 @@ --
+
-👩🏼🏫 准备清单+💦 Software:Time Sync + Config for CaaS Switches- ZIGGO 软硬件准备清单
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
- -
-👩🏼🏫 准备清单 - http://localhost:1313/switch/require/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/require/ -<h2 id="软件环境清单">软件环境清单</h2> -<h3 id="vivada-开发环境">Vivada 开发环境</h3> -<p>Vivado 是开发板的硬件开发程序。</p> -<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> -<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> -<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> -<h3 id="mobaxterm">MobaXterm</h3> -<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> -<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> -<h2 id="硬件准备清单">硬件准备清单</h2> -<h3 id="alinx7021开发板">Alinx7021开发板</h3> -<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> -<h3 id="sd启动卡">SD启动卡</h3> -<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> -<h3 id="必要的线材">必要的线材</h3> -<p>包括网线、数据线等。</p> -<h3 id="普通交换机">普通交换机</h3> -<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> - -💦 Software:Time Sync + Config for CaaS Switches http://localhost:1313/switch/software_build/ @@ -674,6 +648,32 @@ Our GCL is represented by 9 bits, with the highest bit representing whether the <li>tcl脚本</li> <li>良好的英语阅读基础</li> </ul> + +- +
diff --git a/public/switch/require/index.html b/public/switch/require/index.html index 0abba06..4ac4f38 100644 --- a/public/switch/require/index.html +++ b/public/switch/require/index.html @@ -1,6 +1,6 @@ - @@ -4174,65 +4174,65 @@👩🏼🏫 准备清单 + http://localhost:1313/switch/require/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/require/ +<h2 id="软件环境清单">软件环境清单</h2> +<h3 id="vivada-开发环境">Vivada 开发环境</h3> +<p>Vivado 是开发板的硬件开发程序。</p> +<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> +<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> +<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> +<h3 id="mobaxterm">MobaXterm</h3> +<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> +<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> +<h2 id="硬件准备清单">硬件准备清单</h2> +<h3 id="alinx7021开发板">Alinx7021开发板</h3> +<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> +<h3 id="sd启动卡">SD启动卡</h3> +<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> +<h3 id="必要的线材">必要的线材</h3> +<p>包括网线、数据线等。</p> +<h3 id="普通交换机">普通交换机</h3> +<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> - -
- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute -
- 👩🏼🏫 准备清单 - - - - -
- 🧠 基础知识列表 +
- 👩🏼🏫 准备清单 + + + + +
- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
- 普通交换机
- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4339,17 +4339,17 @@- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
- Run
- + ← 👩🏼🏫 准备清单 + >🎉 How to contribute May 1, 2024 diff --git a/public/switch/system_design/index.html b/public/switch/system_design/index.html index 1a89340..fc0d16c 100644 --- a/public/switch/system_design/index.html +++ b/public/switch/system_design/index.html @@ -1,6 +1,6 @@ - @@ -4174,65 +4174,65 @@
- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4333,17 +4333,17 @@- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
-
-
@@ -4162,19 +4162,19 @@
Basic
- +@@ -4190,13 +4190,13 @@-
+
-🧠 基础知识列表+👩🏼🏫 准备清单- 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表
+ ZIGGO 软硬件准备清单May 1, 2024
Basic
- +-
+
@@ -4218,19 +4218,19 @@Basic
- +@@ -4246,19 +4246,19 @@-
+ 
-🆒 Getting start+🎉 How to contribute- ZIGGO device get start document
+ How to report a bug or contribute to ZIGGO's codeMay 1, 2024
Basic
- +@@ -4274,13 +4274,13 @@-
+
-📕 CNC脚本使用指南+🧠 基础知识列表- 使用CNC脚本运行ZIGGO系统的7步指南
+ 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表May 1, 2024
Basic
- +-
+
@@ -4302,19 +4302,19 @@Basic
- +@@ -4358,19 +4358,19 @@-
+
-👩🏼🏫 准备清单+🆒 Getting start- ZIGGO 软硬件准备清单
+ ZIGGO device get start documentMay 1, 2024
Basic
- +diff --git a/public/tag/basic/index.xml b/public/tag/basic/index.xml index 7adde4b..e3a94f4 100644 --- a/public/tag/basic/index.xml +++ b/public/tag/basic/index.xml @@ -43,33 +43,65 @@-
+
-🎉 How to contribute+📕 CNC脚本使用指南- How to report a bug or contribute to ZIGGO's code
+ 使用CNC脚本运行ZIGGO系统的7步指南May 1, 2024
- -
🎉 How to contribute - http://localhost:1313/switch/contributing/ +📕 CNC脚本使用指南 + http://localhost:1313/device/cnc_manual/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/contributing/ -<h2 id="reporting-a-bug">Reporting a bug</h2> -<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> -<ul> -<li>Search existing issues first, make sure yours hasn’t already been reported.</li> -<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> -<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> -<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> -</ul> + http://localhost:1313/device/cnc_manual/ +<h2 id="1-运行脚本前在batchmjs中要配置好以下变量">1. 运行脚本前，在batch.mjs中要配置好以下变量：</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// IP address format: 192.168.137.* +</span></span></span><span class="line"><span class="cl"><span class="c1">// 测试数据 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">conf_default</span> <span class="o">=</span> <span class="s2">"<需要执行的配置名称>"</span> +</span></span><span class="line"><span class="cl"><span class="c1">// 时钟主节点 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">master</span> <span class="o">=</span> <span class="mi">40</span> +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl"><span class="kr">const</span> <span class="nx">hosts</span> <span class="o">=</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nx">device</span><span class="o">:</span> <span class="p">[</span><span class="mi">43</span><span class="p">,</span> <span class="mi">44</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="k">switch</span><span class="o">:</span> <span class="p">[</span><span class="mi">40</span><span class="p">,</span> <span class="mi">41</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">安装好需要的依赖： +</span></span><span class="line"><span class="cl">```bash +</span></span><span class="line"><span class="cl">sudo npm install -g zx@4.3.0 +</span></span><span class="line"><span class="cl">pip install -r requirements.txt +</span></span><span class="line"><span class="cl">npm install +</span></span></code></pre></div><p>配置好环境变量，在.bashrc中加入：</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">export</span> <span class="nv">PYTHONPATH</span><span class="o">=</span><span class="s2">"/home/<用户名>/scripts"</span> +</span></span></code></pre></div><h2 id="2-下载好switch和tsnperf的软件代码">2. 下载好Switch和TSNPerf的软件代码</h2> <blockquote> -<p>The development team will only answer questions on github issues and reject other forms of questions.</p> +<p>（记得提前配置好树莓派和所有板子之间的ssh public key，方便免密登录）</p> </blockquote> -<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> -<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> -<ul> -<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> -<li>Bug fixes are always welcome.</li> -<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> -<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> -<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> -<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> -<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> -</ul> - +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs clone +</span></span></code></pre></div><h2 id="3-拉取最新的软件代码并同步到远程板子上">3. 拉取最新的软件代码并同步到远程板子上</h2> +<blockquote> +<p>默认时master分支，如果需要指定分支，需要修改batch.mjs文件中的pull()函数，具体参考注释的部分</p> +</blockquote> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// pull all the latest code +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">pull</span> <span class="o">=</span> <span class="kr">async</span> <span class="p">()</span> <span class="p">=></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"><span class="nx">cd</span><span class="p">(</span><span class="sb">`</span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="p">()</span><span class="si">}</span><span class="sb">/repos`</span><span class="p">)</span> +</span></span><span class="line"><span class="cl"><span class="c1">// 如果需要指定分支，类似下面指定qbv-test分支的操作 +</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd pkt_gen_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` +</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd time_sync_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"><span class="kr">await</span> <span class="nb">Promise</span><span class="p">.</span><span class="nx">all</span><span class="p">(</span><span class="nx">hosts</span><span class="p">.</span><span class="nx">all</span><span class="p">.</span><span class="nx">map</span><span class="p">(</span><span class="nx">host</span> <span class="p">=></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="kr">const</span> <span class="nx">type</span> <span class="o">=</span> <span class="nx">hosts</span><span class="p">.</span><span class="nx">device</span><span class="p">.</span><span class="nx">includes</span><span class="p">(</span><span class="nx">host</span><span class="p">)</span> <span class="o">?</span> <span class="s1">'device'</span> <span class="o">:</span> <span class="s1">'switch'</span> +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'device'</span><span class="p">)</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/pkt_gen_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/`</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> <span class="k">else</span> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'switch'</span><span class="p">)</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/time_sync_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/;`</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"><span class="p">}))</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><p>同步到所有板子上：</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs pull +</span></span></code></pre></div><h2 id="4-使远程所有板子编译代码">4. 使远程所有板子编译代码</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs build +</span></span></code></pre></div><h2 id="5-将配置文件下发到所有板子上">5. 将配置文件下发到所有板子上</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs distribute +</span></span></code></pre></div><h2 id="6-开始启动所有板子的程序">6. 开始启动所有板子的程序</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs launch +</span></span></code></pre></div><h2 id="7-收集延迟和抖动的统计信息">7. 收集延迟和抖动的统计信息</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs collect +</span></span></code></pre></div>- @@ -492,120 +524,6 @@
-- -
- -👩🏼🏫 准备清单 - http://localhost:1313/device/require/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/require/ -<h2 id="软件环境清单">软件环境清单</h2> -<h3 id="vivada-开发环境">Vivada 开发环境</h3> -<p>Vivado 是开发板的硬件开发程序。</p> -<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> -<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> -<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> -<h3 id="mobaxterm">MobaXterm</h3> -<p>MobaXterm是串口连接工具，我们在<a href="./hardware_build.md">hardware_build.md</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> -<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> -<h2 id="硬件准备清单">硬件准备清单</h2> -<h3 id="alinx7021开发板">Alinx7021开发板</h3> -<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> -<h3 id="sd启动卡">SD启动卡</h3> -<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> -<h3 id="必要的线材">必要的线材</h3> -<p>包括网线、数据线等。</p> -<h3 id="普通交换机">普通交换机</h3> -<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> - -- -
- -👩🏼🏫 准备清单 - http://localhost:1313/switch/require/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/require/ -<h2 id="软件环境清单">软件环境清单</h2> -<h3 id="vivada-开发环境">Vivada 开发环境</h3> -<p>Vivado 是开发板的硬件开发程序。</p> -<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> -<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> -<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> -<h3 id="mobaxterm">MobaXterm</h3> -<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> -<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> -<h2 id="硬件准备清单">硬件准备清单</h2> -<h3 id="alinx7021开发板">Alinx7021开发板</h3> -<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> -<h3 id="sd启动卡">SD启动卡</h3> -<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> -<h3 id="必要的线材">必要的线材</h3> -<p>包括网线、数据线等。</p> -<h3 id="普通交换机">普通交换机</h3> -<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> - -- -
-📕 CNC脚本使用指南 - http://localhost:1313/device/cnc_manual/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/cnc_manual/ -<h2 id="1-运行脚本前在batchmjs中要配置好以下变量">1. 运行脚本前，在batch.mjs中要配置好以下变量：</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// IP address format: 192.168.137.* -</span></span></span><span class="line"><span class="cl"><span class="c1">// 测试数据 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">conf_default</span> <span class="o">=</span> <span class="s2">"<需要执行的配置名称>"</span> -</span></span><span class="line"><span class="cl"><span class="c1">// 时钟主节点 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">master</span> <span class="o">=</span> <span class="mi">40</span> -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"><span class="kr">const</span> <span class="nx">hosts</span> <span class="o">=</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nx">device</span><span class="o">:</span> <span class="p">[</span><span class="mi">43</span><span class="p">,</span> <span class="mi">44</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="k">switch</span><span class="o">:</span> <span class="p">[</span><span class="mi">40</span><span class="p">,</span> <span class="mi">41</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">安装好需要的依赖： -</span></span><span class="line"><span class="cl">```bash -</span></span><span class="line"><span class="cl">sudo npm install -g zx@4.3.0 -</span></span><span class="line"><span class="cl">pip install -r requirements.txt -</span></span><span class="line"><span class="cl">npm install -</span></span></code></pre></div><p>配置好环境变量，在.bashrc中加入：</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">export</span> <span class="nv">PYTHONPATH</span><span class="o">=</span><span class="s2">"/home/<用户名>/scripts"</span> -</span></span></code></pre></div><h2 id="2-下载好switch和tsnperf的软件代码">2. 下载好Switch和TSNPerf的软件代码</h2> -<blockquote> -<p>（记得提前配置好树莓派和所有板子之间的ssh public key，方便免密登录）</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs clone -</span></span></code></pre></div><h2 id="3-拉取最新的软件代码并同步到远程板子上">3. 拉取最新的软件代码并同步到远程板子上</h2> -<blockquote> -<p>默认时master分支，如果需要指定分支，需要修改batch.mjs文件中的pull()函数，具体参考注释的部分</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// pull all the latest code -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">pull</span> <span class="o">=</span> <span class="kr">async</span> <span class="p">()</span> <span class="p">=></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"><span class="nx">cd</span><span class="p">(</span><span class="sb">`</span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="p">()</span><span class="si">}</span><span class="sb">/repos`</span><span class="p">)</span> -</span></span><span class="line"><span class="cl"><span class="c1">// 如果需要指定分支，类似下面指定qbv-test分支的操作 -</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd pkt_gen_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` -</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd time_sync_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"><span class="kr">await</span> <span class="nb">Promise</span><span class="p">.</span><span class="nx">all</span><span class="p">(</span><span class="nx">hosts</span><span class="p">.</span><span class="nx">all</span><span class="p">.</span><span class="nx">map</span><span class="p">(</span><span class="nx">host</span> <span class="p">=></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="kr">const</span> <span class="nx">type</span> <span class="o">=</span> <span class="nx">hosts</span><span class="p">.</span><span class="nx">device</span><span class="p">.</span><span class="nx">includes</span><span class="p">(</span><span class="nx">host</span><span class="p">)</span> <span class="o">?</span> <span class="s1">'device'</span> <span class="o">:</span> <span class="s1">'switch'</span> -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'device'</span><span class="p">)</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/pkt_gen_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/`</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> <span class="k">else</span> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'switch'</span><span class="p">)</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/time_sync_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/;`</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"><span class="p">}))</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><p>同步到所有板子上：</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs pull -</span></span></code></pre></div><h2 id="4-使远程所有板子编译代码">4. 使远程所有板子编译代码</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs build -</span></span></code></pre></div><h2 id="5-将配置文件下发到所有板子上">5. 将配置文件下发到所有板子上</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs distribute -</span></span></code></pre></div><h2 id="6-开始启动所有板子的程序">6. 开始启动所有板子的程序</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs launch -</span></span></code></pre></div><h2 id="7-收集延迟和抖动的统计信息">7. 收集延迟和抖动的统计信息</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs collect -</span></span></code></pre></div> -🆒 Getting start http://localhost:1313/device/getting-started/ @@ -688,6 +606,32 @@- +
+👩🏼🏫 准备清单 + http://localhost:1313/device/require/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/require/ +<h2 id="软件环境清单">软件环境清单</h2> +<h3 id="vivada-开发环境">Vivada 开发环境</h3> +<p>Vivado 是开发板的硬件开发程序。</p> +<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> +<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> +<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> +<h3 id="mobaxterm">MobaXterm</h3> +<p>MobaXterm是串口连接工具，我们在<a href="./hardware_build.md">hardware_build.md</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> +<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> +<h2 id="硬件准备清单">硬件准备清单</h2> +<h3 id="alinx7021开发板">Alinx7021开发板</h3> +<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> +<h3 id="sd启动卡">SD启动卡</h3> +<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> +<h3 id="必要的线材">必要的线材</h3> +<p>包括网线、数据线等。</p> +<h3 id="普通交换机">普通交换机</h3> +<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> + +🧠 基础知识列表 http://localhost:1313/device/basic_knowledge/ @@ -716,6 +660,36 @@- +
+🎉 How to contribute + http://localhost:1313/switch/contributing/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/contributing/ +<h2 id="reporting-a-bug">Reporting a bug</h2> +<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> +<ul> +<li>Search existing issues first, make sure yours hasn’t already been reported.</li> +<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> +<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> +<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> +</ul> +<blockquote> +<p>The development team will only answer questions on github issues and reject other forms of questions.</p> +</blockquote> +<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> +<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> +<ul> +<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> +<li>Bug fixes are always welcome.</li> +<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> +<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> +<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> +<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> +<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> +</ul> + +🧠 基础知识列表 http://localhost:1313/switch/basic_knowledge/ @@ -741,6 +715,32 @@ <li>tcl脚本</li> <li>良好的英语阅读基础</li> </ul> + +- +
diff --git a/public/tag/cnc/index.html b/public/tag/cnc/index.html index b785869..fc902ac 100644 --- a/public/tag/cnc/index.html +++ b/public/tag/cnc/index.html @@ -1,6 +1,6 @@ - diff --git a/public/tag/markdown/index.html b/public/tag/markdown/index.html index 866cf3b..caa641f 100644 --- a/public/tag/markdown/index.html +++ b/public/tag/markdown/index.html @@ -1,6 +1,6 @@ - @@ -4162,19 +4162,19 @@👩🏼🏫 准备清单 + http://localhost:1313/switch/require/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/require/ +<h2 id="软件环境清单">软件环境清单</h2> +<h3 id="vivada-开发环境">Vivada 开发环境</h3> +<p>Vivado 是开发板的硬件开发程序。</p> +<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> +<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> +<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> +<h3 id="mobaxterm">MobaXterm</h3> +<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> +<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> +<h2 id="硬件准备清单">硬件准备清单</h2> +<h3 id="alinx7021开发板">Alinx7021开发板</h3> +<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> +<h3 id="sd启动卡">SD启动卡</h3> +<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> +<h3 id="必要的线材">必要的线材</h3> +<p>包括网线、数据线等。</p> +<h3 id="普通交换机">普通交换机</h3> +<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> Markdown
- +@@ -4190,19 +4190,19 @@-
+ 
-🔨 System Design —— PL & PS Co-operate+📈 TSNPerf 设计原理- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动May 1, 2024
Markdown
- +@@ -4218,19 +4218,19 @@-
+
🔨 System Design —— PL & PS Co-operate- ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
Markdown
- +@@ -4246,19 +4246,19 @@-
+
-📕 ZIGGO Device使用手册+💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation ToolkitMay 1, 2024
Markdown
- +@@ -4302,19 +4302,19 @@-
+
-📈 TSNPerf 设计原理+💦 Software:Time Sync + Config for CaaS Switches- TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
Markdown
- +@@ -4330,19 +4330,19 @@-
+
-💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit+🔨 System Design —— PL & PS Co-operate- Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit
+ ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.May 1, 2024
Markdown
- +@@ -4358,17 +4358,17 @@-
+
-💦 互联互通测试TestBed搭建流程+💦 Software:Time Sync + Config for CaaS Device- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ Docs to enable CaaS Device' time synchronization logic and set up pkt gen.May 1, 2024
Markdown
- +-
+
-💦 Software:Time Sync + Config for CaaS Switches+📕 ZIGGO Device使用手册Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
May 1, 2024
@@ -4386,19 +4386,19 @@Markdown
- +@@ -4414,15 +4414,19 @@-
+
-💦 Software:Time Sync + Config for CaaS Device+💦 互联互通测试TestBed搭建流程- Docs to enable CaaS Device' time synchronization logic and set up pkt gen.
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
Markdown
- +diff --git a/public/tag/markdown/index.xml b/public/tag/markdown/index.xml index b868154..cfdd9db 100644 --- a/public/tag/markdown/index.xml +++ b/public/tag/markdown/index.xml @@ -12,6 +12,15 @@ http://localhost:1313/tag/markdown/ ++ + +
+
-☀ 某品牌交换机报告+⌚ TSNPerf 检测内容及使用表- TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动
+ 时间同步测试，流量整形测试，网络配置测试May 1, 2024
- +
+☀ 某品牌交换机报告 + http://localhost:1313/tsnperf/report/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/tsnperf/report/ +<p>详细报告请查看<a href="http://localhost:1313/pdf/switch_report.pdf">这里</a>。</p> + +⌚ TSNPerf 检测内容及使用表 http://localhost:1313/tsnperf/manual/ @@ -168,84 +177,142 @@- -
- -💦 Software:Time Sync + Config for CaaS Device - http://localhost:1313/device/software-build/ +💦 互联互通测试TestBed搭建流程 + http://localhost:1313/device/testbed/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/software-build/ -<p>This repo contains source code to enable TSN/CaaS TSNPerf’ time synchronization logic and set up packet generation plan.</p> -<h2 id="table-of-content">Table of Content</h2> + http://localhost:1313/device/testbed/ +<h2 id="目录">目录</h2> <ul> -<li><a href="#table-of-content">Table of Content</a></li> -<li><a href="#1-build">1. Build</a></li> -<li><a href="#2-config">2. Config</a></li> -<li><a href="#3-run">3. Run</a></li> -<li><a href="#4-analyze">4. Analyze</a> +<li><a href="#%e7%9b%ae%e5%bd%95">目录</a></li> +<li><a href="#testbed%e7%ae%80%e5%8d%95%e4%bb%8b%e7%bb%8d">TestBed简单介绍</a></li> +<li><a href="#%e4%ba%92%e8%81%94%e4%ba%92%e9%80%9a%e6%b5%8b%e8%af%95%e9%a1%b9%e7%9b%ae%e4%bb%8b%e7%bb%8d">互联互通测试项目介绍</a> <ul> -<li><a href="#41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</a></li> -<li><a href="#42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</a></li> +<li><a href="#1-%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">1. 基准测试</a></li> +<li><a href="#2-%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">2. 门控能力</a></li> +<li><a href="#3-%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">3. 带宽保证</a></li> +<li><a href="#4-%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">4. 门控精度</a></li> +</ul> +</li> +<li><a href="#%e8%ae%be%e5%a4%87%e5%8f%82%e6%95%b0%e8%ae%be%e7%bd%ae%e4%b8%8e%e9%83%a8%e7%bd%b2">设备参数设置与部署</a></li> +<li><a href="#testbed%e8%bf%90%e8%a1%8c%e6%b5%81%e7%a8%8b">TestBed运行流程</a> +<ul> +<li><a href="#%e5%87%86%e5%a4%87%e5%b7%a5%e4%bd%9c">准备工作</a> +<ul> +<li><a href="#%e6%8e%a7%e5%88%b6%e8%84%9a%e6%9c%ac%e5%87%86%e5%a4%87">控制脚本准备</a></li> +<li><a href="#%e8%83%8c%e6%99%af%e6%b5%81%e9%87%8f%e5%8f%91%e9%80%81">背景流量发送</a></li> </ul> </li> +<li><a href="#%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">基准测试</a></li> +<li><a href="#%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">门控能力</a></li> +<li><a href="#%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">带宽保证</a></li> +<li><a href="#%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">门控精度</a></li> </ul> -<h2 id="1-build">1. Build</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build -</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build -</span></span><span class="line"><span class="cl">cmake .. -</span></span><span class="line"><span class="cl">make -</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync” & “pkt_gen”</p> -<h2 id="2-config">2. Config</h2> -<p>The “build” directory contains topology & TSN/CaaS schedule results.</p> +</li> +</ul> +<h2 id="testbed简单介绍">TestBed简单介绍</h2> +<p>我们内部对自己研发的CaaS-Switch进行了互联互通测试，采用的网络拓扑如下所示。</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./topo.PNG" alt="topo" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>本Demo需要4个FPGA开发板（2个TSNPerf、2个CaaS-Switch）和1台普通PC。如果条件有限/考虑简化拓扑，可以删去一个CaaS-Switch。PC负责发送背景流量，路径为黑色箭头；左侧TSNPerf负责发送测试流量（关键流量），路径为红色箭头。</p> +<p>所有测试项目的流程大致可以分为两个阶段：</p> +<ol> +<li> +<p>时间同步：启动时间同步，保证TSNPerf、CaaS-Switch在一个时钟域下。</p> +<p>注：时间同步程序运行在TSNPerf、CaaS-Switch的系统中。</p> +</li> +<li> +<p>发送测试流量：根据schedule.json文件，TSNPerf进行测试流量发送。</p> +</li> +</ol> +<h2 id="互联互通测试项目介绍">互联互通测试项目介绍</h2> +<h3 id="1-基准测试">1. 基准测试</h3> <ul> -<li>config.json: topology file, contains node info (type, mac, ptp ports), link between nodes (with ports), and forwarding table.</li> -<li>schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</li> +<li>目的：测试无背景流量情况下，高优先级流量的两跳端到端延迟、丢包率、抖动，作为比较基准。</li> +<li>预期：延迟符合规划，抖动较低（100ns左右）。</li> </ul> -<p>(Hints: This is similar to a Ziggo Switch)</p> -<h2 id="3-run">3. Run</h2> +<h3 id="2-门控能力">2. 门控能力</h3> <ul> -<li>Start time syncronization</li> +<li>目的：测试通用情况下流量调度效果，和两个交换机的门控对接能力。</li> +<li>方案： +背景流量（VLAN priority = 0）打到线速，每个调度周期预留长度为 3 的时隙给高优先级流量， +<ol> +<li>每个周期定时发送 4 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录端到端平均延迟、抖动、丢包率、到达顺序</li> +<li>每个周期定时发送 8 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过且仅 n 个包</li> +</ol> +</li> +<li>预期： +<ol> +<li>延迟、抖动、丢包率和基准一致</li> +<li>每个周期定时发送 4 个数据包时，丢包率为0</li> +<li>每个周期定时发送 8 个数据包时，每个周期通过且仅通过 5 个包（每8个包丢3个，因为每个时隙里恰好可以把第五个包发出去，余下三个包丢掉），丢包率为37.5%</li> +</ol> +</li> </ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./time_sync -</span></span></code></pre></div><ul> -<li>Start device critical packet generation</li> +<h3 id="3-带宽保证">3. 带宽保证</h3> +<ul> +<li>目的：测试交换机能够进行带宽预留，且两个交换机优先级映射、运行 cycle 和 offset 基本一致。</li> +<li>方案： +背景流量（VLAN priority = 0）打到线速（1Gbps），配置交换机预留 50% 时隙给高优先级流量（VLAN priority = 1），其余 50% 只允许低优先级流量， +<ol> +<li>测试流量高优先级（VLAN priority = 1）情况下打到线速（经测试，每个周期[33ms]连续发送2752个1500B的包，基本达到1000Mbps），记录端到端平均延迟、抖动、丢包率、到达顺序</li> +<li>测试流量高优先级（VLAN priority = 1）情况下打到50%线速（每个周期[33ms]连续发送1376个1500B的包），记录端到端平均延迟、抖动、丢包率、到达顺序</li> +</ol> +</li> +<li>预期： +<ol> +<li>高优先级测试流量100%线速：延迟、抖动和基准一致，丢包率 50% 左右</li> +<li>高优先级测试流量50%线速：延迟、抖动和基准一致，0丢包率</li> +</ol> +</li> +</ul> +<h3 id="4-门控精度">4. 门控精度</h3> +<ul> +<li>目的：测试门控时隙长度的设置精度</li> +<li>方案：(n=1,2,4,8,…) +<ol> +<li>每个调度周期预留长度为 1 的时隙给高优先级流量</li> +<li>每个周期发送 n 个数据包长度为1/n*1500Byte的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过 n 个包 +<ol> +<li>n=1,</li> +</ol> +</li> +</ol> +</li> +<li>预期： +<ol> +<li>n=1,2,4,8 情况下都能每个周期通过且仅通过 n 个包</li> +</ol> +</li> </ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./pkt_gen -</span></span></code></pre></div><h2 id="4-analyze">4. Analyze</h2> -<p>There are two analysis methods for TSNPerf:</p> <blockquote> -<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +<p>如果您按照下文的配置使用我们开源的ZIGGO交换机和TSNPerf，则您可以在上面四个测试中得到和预期相类似的效果。如果出现了任何问题，欢迎在github上提出issue。</p> </blockquote> -<p>One method is to directly analyze latency and jitter on the TSNPerf.</p> -<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> -<h3 id="41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</h3> -<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> -<p>You can display the content of the header and the last 5 lines using the following command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 -</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 -</span></span></code></pre></div><h3 id="42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</h3> -<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> -<p>Example of packet capture command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng -</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> -<p>Code for analyzing programs is <code>analyze_packet.py</code></p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> -</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> - -- -
- -💦 Software:Time Sync + Config for CaaS Switches - http://localhost:1313/switch/software_build/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/software_build/ -<p>This repo contains source code to enable CaaS Switches’ time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).</p> -<h2 id="build">Build</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build -</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build -</span></span><span class="line"><span class="cl">cmake .. -</span></span><span class="line"><span class="cl">make -</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync_app” & “switch_config”</p> -<h2 id="config">Config</h2> -<p>The “config” directory contains topology & TSN/CaaS schedule results.</p> -<p>This document takes the following topology as an example to give example configurations:</p> +<h2 id="设备参数设置与部署">设备参数设置与部署</h2> +<p>Switch软硬件代码在仓库 <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch" target="_blank" rel="noopener">ZIGGO-Caas-Switch</a> 中，使用主分支即可。</p> +<p>TSNPerf的软硬件代码在本仓库。</p> +<blockquote> +<p>注意：带宽能力测试中的TSNPerf需要使用offline_analyze分支，门控精度测试中的TSNPerf需要使用packet_resize分支【用于自定义测试包大小】。测试中请勿忘记切换分支。</p> +</blockquote> +<p>所有设备的IP、MAC和ID如下所示，与本文档后面提供的JSON配置文件对应：</p> <p> @@ -264,395 +331,50 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./example_topology.png" alt="topology" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./topo_config.png" alt="topo config" loading="lazy" data-zoomable /></div> </div></figure> </p> -<ul> -<li> -<p>***-config.json: Mainly describes the network’s topology, including the type of each node (device or switch), MAC address, PTP port status, and other node information, topology information, and MAC forwarding table. Example and explanation are as follows (note that the comments in the file are just for explanation, do not have such comments in actual use):</p> +<p>对应的config文件可见<code>config.json</code></p> +<h2 id="testbed运行流程">TestBed运行流程</h2> +<h3 id="准备工作">准备工作</h3> +<h4 id="控制脚本准备">控制脚本准备</h4> +<p>可以参考 <a href="http://localhost:1313/device/cnc_manual/">CNC-User-Manual</a></p> +<h4 id="背景流量发送">背景流量发送</h4> +<p>可以直接在Linux PC中运行<code>send.py</code>脚本。（需要安装scapy,tcpreplay）</p> +<h3 id="基准测试">基准测试</h3> +<p>Switch、TSNPerf 的软硬件都使用主分支。</p> +<p>测试步骤：</p> +<ol> +<li>修改batch.mjs修改正确的配置文件名</li> +<li>./batch.mjs pull（注意分支正确）</li> +<li>./batch.mjs distribute +Device每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： +<code>base/d3s2-baseline-3t-config.json</code>， +<code>base/d3s2-baseline-3t-schedule-base.json</code></li> +<li>./batch.mjs launch （包括了时间同步和数据包发送）</li> +<li>./batch.mjs collect</li> +</ol> +<h3 id="门控能力">门控能力</h3> +<p>Switch、TSNPerf 的软硬件都使用主分支。</p> +<ol> +<li>让背景流量Device发包（基准测试不需要发送背景流量）</li> +<li>修改batch.mjs修改正确的配置文件名</li> +<li>./batch.mjs pull（注意分支正确）</li> +<li>./batch.mjs distribute +Device1每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： +<code>gate/d3s2-baseline-3t-config.json</code>， +<code>gate/d3s2-baseline-3t-schedule-gate.json</code></li> +<li>./batch.mjs launch</li> +<li>./batch.mjs collect</li> +<li>将上述的schedule.json中的Device发包个数从4改为8，再从上述步骤4重新测试，修改后的schedule.json如下所示</li> +</ol> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Used to describe the information of each node in the network -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">3</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Node's PTP port status -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// The quintuple represents the clock status of [local, ETH1, ETH2, ETH3, ETH4] -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Number meaning: (0: MASTER, 1: SLAVE, 2: PASSIVE, 3: DISABLED) -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 1, it means that the node is the master clock node; -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 0, it means that the node is the slave clock node. -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:14"</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:15"</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Topology information, composed of each link, each link is a directed edge -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// link ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Port number of the source node -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// port 0,1,2,3 correspond to ETH1,2,3,4 in reality -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Port number of the destination node -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">2</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Forwarding table, which can be generated by the scheduling algorithm in CNC -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// In the forwarding table where you send to yourself, the port is 4 (caas) / 5 (PS ETH for new hardware) -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Current node ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Output port number -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Entry ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Destination node ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><p>If the master clock selection algorithm is used, only the configuration of nodes is different, and the rest are the same. The newly added <code>externalPortConfigurationEnabled</code> and <code>system_identity</code> fields are optional items, as shown in the example below:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:00:00:00:02:01"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"externalPortConfigurationEnabled"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> <span class="c1">// 1: Manually configure the master-slave relationship, 0: Configure the master-slave relationship through the master clock selection algorithm, if this item is not written, the default is 0, that is, configure the master-slave relationship through the master clock selection -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"system_identity"</span><span class="p">:</span> <span class="p">{</span> <span class="c1">// Clock node's clock parameters, used for comparison in the master clock selection algorithm, if this item is not written, the default is the configuration written below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority1"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// First priority -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockClass"</span><span class="p">:</span> <span class="mi">248</span><span class="p">,</span> <span class="c1">// Clock level -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockAccuracy"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// Clock accuracy -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"offsetScaledLogVariance"</span><span class="p">:</span> <span class="mi">17258</span><span class="p">,</span> <span class="c1">// Clock variance -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority2"</span><span class="p">:</span> <span class="mi">247</span><span class="p">,</span> <span class="c1">// Second priority -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clock_identity"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">]</span> <span class="c1">// Clock identifier, different clocks should have different parameters -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div></li> -<li> -<p>***-schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span><span class="c1">// All switches need to be listed to facilitate software recognition of configuration information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Can be empty, not used -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> <span class="c1">// Type is link, used to describe scheduling information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Output port number -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Scheduling information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> <span class="c1">// Scheduling cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Start time relative to the entire cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">5</span><span class="p">,</span> <span class="c1">// End time relative to the entire cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Job ID in CaaS, if not needed, it can be omitted -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Data stream ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">6</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">1500</span> <span class="c1">// Packet length, if not written, the default is 1500B, this item only exists on the path from Device to Switch -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"><span class="p">]</span> -</span></span></code></pre></div></li> -</ul> -<h2 id="run">Run</h2> -<ul> -<li>Copy topology & schedule file to build dir:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-config.json build/config.json -</span></span><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-schedule.json build/schedule.json -</span></span></code></pre></div><ul> -<li>Start time synchronization and initialize GCL and MAC forwarding table according to the configuration (it is recommended to run the time synchronization program on a core (with <code>taskset -c 1</code> command) to prevent kernel errors and crashes due to time synchronization):</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -</span></span></code></pre></div><ul> -<li>The log output level is categorized into three types: WARN, INFO, and TRACE. The default log output level is TRACE (the most comprehensive output information, including DEBUG logs). The log output level can be set with the -l parameter:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l w <span class="c1"># WARN level</span> -</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l i <span class="c1"># INFO level</span> -</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l t <span class="c1"># TRACE level</span> -</span></span></code></pre></div><p><em>Notice that the time sync logic is supposed to run indefinitely as the node should sync to its neighbors again and again.</em></p> -<ul> -<li>Update GCL & switch forwarding rules:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./switch_config -</span></span></code></pre></div> -- -
💦 互联互通测试TestBed搭建流程 - http://localhost:1313/device/testbed/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/testbed/ -<h2 id="目录">目录</h2> -<ul> -<li><a href="#%e7%9b%ae%e5%bd%95">目录</a></li> -<li><a href="#testbed%e7%ae%80%e5%8d%95%e4%bb%8b%e7%bb%8d">TestBed简单介绍</a></li> -<li><a href="#%e4%ba%92%e8%81%94%e4%ba%92%e9%80%9a%e6%b5%8b%e8%af%95%e9%a1%b9%e7%9b%ae%e4%bb%8b%e7%bb%8d">互联互通测试项目介绍</a> -<ul> -<li><a href="#1-%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">1. 基准测试</a></li> -<li><a href="#2-%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">2. 门控能力</a></li> -<li><a href="#3-%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">3. 带宽保证</a></li> -<li><a href="#4-%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">4. 门控精度</a></li> -</ul> -</li> -<li><a href="#%e8%ae%be%e5%a4%87%e5%8f%82%e6%95%b0%e8%ae%be%e7%bd%ae%e4%b8%8e%e9%83%a8%e7%bd%b2">设备参数设置与部署</a></li> -<li><a href="#testbed%e8%bf%90%e8%a1%8c%e6%b5%81%e7%a8%8b">TestBed运行流程</a> -<ul> -<li><a href="#%e5%87%86%e5%a4%87%e5%b7%a5%e4%bd%9c">准备工作</a> -<ul> -<li><a href="#%e6%8e%a7%e5%88%b6%e8%84%9a%e6%9c%ac%e5%87%86%e5%a4%87">控制脚本准备</a></li> -<li><a href="#%e8%83%8c%e6%99%af%e6%b5%81%e9%87%8f%e5%8f%91%e9%80%81">背景流量发送</a></li> -</ul> -</li> -<li><a href="#%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">基准测试</a></li> -<li><a href="#%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">门控能力</a></li> -<li><a href="#%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">带宽保证</a></li> -<li><a href="#%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">门控精度</a></li> -</ul> -</li> -</ul> -<h2 id="testbed简单介绍">TestBed简单介绍</h2> -<p>我们内部对自己研发的CaaS-Switch进行了互联互通测试，采用的网络拓扑如下所示。</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./topo.PNG" alt="topo" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>本Demo需要4个FPGA开发板（2个TSNPerf、2个CaaS-Switch）和1台普通PC。如果条件有限/考虑简化拓扑，可以删去一个CaaS-Switch。PC负责发送背景流量，路径为黑色箭头；左侧TSNPerf负责发送测试流量（关键流量），路径为红色箭头。</p> -<p>所有测试项目的流程大致可以分为两个阶段：</p> -<ol> -<li> -<p>时间同步：启动时间同步，保证TSNPerf、CaaS-Switch在一个时钟域下。</p> -<p>注：时间同步程序运行在TSNPerf、CaaS-Switch的系统中。</p> -</li> -<li> -<p>发送测试流量：根据schedule.json文件，TSNPerf进行测试流量发送。</p> -</li> -</ol> -<h2 id="互联互通测试项目介绍">互联互通测试项目介绍</h2> -<h3 id="1-基准测试">1. 基准测试</h3> -<ul> -<li>目的：测试无背景流量情况下，高优先级流量的两跳端到端延迟、丢包率、抖动，作为比较基准。</li> -<li>预期：延迟符合规划，抖动较低（100ns左右）。</li> -</ul> -<h3 id="2-门控能力">2. 门控能力</h3> -<ul> -<li>目的：测试通用情况下流量调度效果，和两个交换机的门控对接能力。</li> -<li>方案： -背景流量（VLAN priority = 0）打到线速，每个调度周期预留长度为 3 的时隙给高优先级流量， -<ol> -<li>每个周期定时发送 4 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录端到端平均延迟、抖动、丢包率、到达顺序</li> -<li>每个周期定时发送 8 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过且仅 n 个包</li> -</ol> -</li> -<li>预期： -<ol> -<li>延迟、抖动、丢包率和基准一致</li> -<li>每个周期定时发送 4 个数据包时，丢包率为0</li> -<li>每个周期定时发送 8 个数据包时，每个周期通过且仅通过 5 个包（每8个包丢3个，因为每个时隙里恰好可以把第五个包发出去，余下三个包丢掉），丢包率为37.5%</li> -</ol> -</li> -</ul> -<h3 id="3-带宽保证">3. 带宽保证</h3> -<ul> -<li>目的：测试交换机能够进行带宽预留，且两个交换机优先级映射、运行 cycle 和 offset 基本一致。</li> -<li>方案： -背景流量（VLAN priority = 0）打到线速（1Gbps），配置交换机预留 50% 时隙给高优先级流量（VLAN priority = 1），其余 50% 只允许低优先级流量， -<ol> -<li>测试流量高优先级（VLAN priority = 1）情况下打到线速（经测试，每个周期[33ms]连续发送2752个1500B的包，基本达到1000Mbps），记录端到端平均延迟、抖动、丢包率、到达顺序</li> -<li>测试流量高优先级（VLAN priority = 1）情况下打到50%线速（每个周期[33ms]连续发送1376个1500B的包），记录端到端平均延迟、抖动、丢包率、到达顺序</li> -</ol> -</li> -<li>预期： -<ol> -<li>高优先级测试流量100%线速：延迟、抖动和基准一致，丢包率 50% 左右</li> -<li>高优先级测试流量50%线速：延迟、抖动和基准一致，0丢包率</li> -</ol> -</li> -</ul> -<h3 id="4-门控精度">4. 门控精度</h3> -<ul> -<li>目的：测试门控时隙长度的设置精度</li> -<li>方案：(n=1,2,4,8,…) -<ol> -<li>每个调度周期预留长度为 1 的时隙给高优先级流量</li> -<li>每个周期发送 n 个数据包长度为1/n*1500Byte的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过 n 个包 -<ol> -<li>n=1,</li> -</ol> -</li> -</ol> -</li> -<li>预期： -<ol> -<li>n=1,2,4,8 情况下都能每个周期通过且仅通过 n 个包</li> -</ol> -</li> -</ul> -<blockquote> -<p>如果您按照下文的配置使用我们开源的ZIGGO交换机和TSNPerf，则您可以在上面四个测试中得到和预期相类似的效果。如果出现了任何问题，欢迎在github上提出issue。</p> -</blockquote> -<h2 id="设备参数设置与部署">设备参数设置与部署</h2> -<p>Switch软硬件代码在仓库 <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch" target="_blank" rel="noopener">ZIGGO-Caas-Switch</a> 中，使用主分支即可。</p> -<p>TSNPerf的软硬件代码在本仓库。</p> -<blockquote> -<p>注意：带宽能力测试中的TSNPerf需要使用offline_analyze分支，门控精度测试中的TSNPerf需要使用packet_resize分支【用于自定义测试包大小】。测试中请勿忘记切换分支。</p> -</blockquote> -<p>所有设备的IP、MAC和ID如下所示，与本文档后面提供的JSON配置文件对应：</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./topo_config.png" alt="topo config" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>对应的config文件可见<code>config.json</code></p> -<h2 id="testbed运行流程">TestBed运行流程</h2> -<h3 id="准备工作">准备工作</h3> -<h4 id="控制脚本准备">控制脚本准备</h4> -<p>可以参考 <a href="http://localhost:1313/device/cnc_manual/">CNC-User-Manual</a></p> -<h4 id="背景流量发送">背景流量发送</h4> -<p>可以直接在Linux PC中运行<code>send.py</code>脚本。（需要安装scapy,tcpreplay）</p> -<h3 id="基准测试">基准测试</h3> -<p>Switch、TSNPerf 的软硬件都使用主分支。</p> -<p>测试步骤：</p> -<ol> -<li>修改batch.mjs修改正确的配置文件名</li> -<li>./batch.mjs pull（注意分支正确）</li> -<li>./batch.mjs distribute -Device每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： -<code>base/d3s2-baseline-3t-config.json</code>， -<code>base/d3s2-baseline-3t-schedule-base.json</code></li> -<li>./batch.mjs launch （包括了时间同步和数据包发送）</li> -<li>./batch.mjs collect</li> -</ol> -<h3 id="门控能力">门控能力</h3> -<p>Switch、TSNPerf 的软硬件都使用主分支。</p> -<ol> -<li>让背景流量Device发包（基准测试不需要发送背景流量）</li> -<li>修改batch.mjs修改正确的配置文件名</li> -<li>./batch.mjs pull（注意分支正确）</li> -<li>./batch.mjs distribute -Device1每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： -<code>gate/d3s2-baseline-3t-config.json</code>， -<code>gate/d3s2-baseline-3t-schedule-gate.json</code></li> -<li>./batch.mjs launch</li> -<li>./batch.mjs collect</li> -<li>将上述的schedule.json中的Device发包个数从4改为8，再从上述步骤4重新测试，修改后的schedule.json如下所示</li> -</ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> </span></span><span class="line"><span class="cl"> <span class="p">{</span> </span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> </span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> @@ -753,57 +475,206 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， - -
+ +💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit - http://localhost:1313/switch/hardware-build/ +📕 ZIGGO Device使用手册 + http://localhost:1313/device/ziggo_device_manual/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/ziggo_device_manual/ +<p>There are two analysis methods for ZIGGO Device:</p> +<blockquote> +<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +</blockquote> +<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> +<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> +<p>Example of <code>packet_log.csv</code>:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency +</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 +</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 +</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 +</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 +</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 +</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 +</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 +</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 +</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 +</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 +</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance +</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 +</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 +</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 +</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 +</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 +</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 +</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 +</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 +</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 +</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 +</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 +</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 +</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> +<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> +<p>Example of packet capture command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng +</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> +<p>Code for analyzing programs is <code>analyze_packet.py</code></p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> +</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> + +- +
+ +💦 Software:Time Sync + Config for CaaS Device + http://localhost:1313/device/software-build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/software-build/ +<p>This repo contains source code to enable TSN/CaaS TSNPerf’ time synchronization logic and set up packet generation plan.</p> +<h2 id="table-of-content">Table of Content</h2> +<ul> +<li><a href="#table-of-content">Table of Content</a></li> +<li><a href="#1-build">1. Build</a></li> +<li><a href="#2-config">2. Config</a></li> +<li><a href="#3-run">3. Run</a></li> +<li><a href="#4-analyze">4. Analyze</a> +<ul> +<li><a href="#41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</a></li> +<li><a href="#42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</a></li> +</ul> +</li> +</ul> +<h2 id="1-build">1. Build</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build +</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build +</span></span><span class="line"><span class="cl">cmake .. +</span></span><span class="line"><span class="cl">make +</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync” & “pkt_gen”</p> +<h2 id="2-config">2. Config</h2> +<p>The “build” directory contains topology & TSN/CaaS schedule results.</p> +<ul> +<li>config.json: topology file, contains node info (type, mac, ptp ports), link between nodes (with ports), and forwarding table.</li> +<li>schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</li> +</ul> +<p>(Hints: This is similar to a Ziggo Switch)</p> +<h2 id="3-run">3. Run</h2> +<ul> +<li>Start time syncronization</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./time_sync +</span></span></code></pre></div><ul> +<li>Start device critical packet generation</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./pkt_gen +</span></span></code></pre></div><h2 id="4-analyze">4. Analyze</h2> +<p>There are two analysis methods for TSNPerf:</p> +<blockquote> +<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +</blockquote> +<p>One method is to directly analyze latency and jitter on the TSNPerf.</p> +<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<h3 id="41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</h3> +<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> +<p>You can display the content of the header and the last 5 lines using the following command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 +</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 +</span></span></code></pre></div><h3 id="42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</h3> +<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> +<p>Example of packet capture command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng +</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> +<p>Code for analyzing programs is <code>analyze_packet.py</code></p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> +</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> + +- +
@@ -1060,229 +1090,20 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙，🔨 System Design —— PL & PS Co-operate + http://localhost:1313/device/system-design/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/hardware-build/ -<p>This repo contains pre-build hardware & system rootfs to boot the <strong>Zynq AX7021</strong> FPGA board from SD card.</p> -<h2 id="file-downloading">File downloading</h2> -<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/8277c491a8bd4e6a8997/" target="_blank" rel="noopener">this</a> public link:</p> + http://localhost:1313/device/system-design/ +<p>ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ’s both hardware and software programmability.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./framework.jpg" alt="framework" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<h2 id="table-of-content">Table of Content</h2> <ul> -<li>BOOT.BIN</li> -<li>boot.scr</li> -<li>image.ub</li> -<li>rootfs.tar.gz</li> -</ul> -<h2 id="sd-card-partition">SD card partition</h2> -<p>In order to boot the CaaS Switch, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted -</span></span><span class="line"><span class="cl">sudo gparted -</span></span></code></pre></div><p>Parition it into two partition below</p> +<li><a href="#table-of-content">Table of Content</a></li> +<li><a href="#evaluation-method">Evaluation Method</a></li> +<li><a href="#test-data-frame-data-structure">Test data frame data structure</a></li> +<li><a href="#module-design">Module Design</a> <ul> -<li> -<p>BOOT: store boot files from petalinux</p> -<p>Free space preceding (MiB): 4</p> -<p>New size (MiB): 500</p> -<p>File system: fat32</p> -<p>Label: BOOT</p> -</li> -<li> -<p>ROOTFS: store debian system rootfs</p> -<p>Free space preceding (MiB): 0</p> -<p>Free space following (MiB): 0</p> -<p>File system: ext4</p> -<p>Label: ROOTFS</p> +<li><a href="#correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</a></li> +<li><a href="#offline-analysis-and-design">Offline Analysis and Design</a></li> +</ul> </li> </ul> -<h2 id="copy-files-into-sd-card">Copy files into SD card</h2> -<p>Mound SD card:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ -</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ -</span></span></code></pre></div><p>Remove original files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* -</span></span></code></pre></div><p>Copy files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh -</span></span><span class="line"><span class="cl">sync -</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS -</span></span></code></pre></div><h2 id="launch-the-switch">Launch the switch</h2> -<h3 id="1-launch-the-board">1. Launch the Board</h3> -<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> +<h2 id="evaluation-method">Evaluation Method</h2> +<p>The ZIGGO Evaluation Toolkit is used to send and receive test data frames for the purpose of ensuring <code>accurate delay calculations</code>.</p> +<p>To achieve this accuracy, the toolkit needs to <strong>synchronize its time</strong> with the TSN switch and record a <strong>global hardware timestamp</strong> in the test data frames.</p> +<p>As shown in the diagram below, in a data flow link with $n$ network nodes, Node $1$ serves as the source node to send test data frames, Node $n$ acts as the destination node to receive test data frames, and all the intermediate nodes (Node $2$ to Node $n-1$) are TSN switches.</p> +<p>When a test data frame is sent from the source node, the hardware records the timestamp $t^+$ of when the frame was sent in the data frame. Finally, when the data frame arrives at the destination node, the destination node records the timestamp $t^-$ of when the frame entered that node. By calculating $(t^−−t^+)$, we can determine the end-to-end latency of the data frame.</p> <p> @@ -822,12 +693,75 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./device_test_demo.png" alt="device_test_demo" loading="lazy" data-zoomable /></div> </div></figure> </p> -<h3 id="2-initialize-ps">2. Initialize PS</h3> -<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> -<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> +<blockquote> +<p>In this doc, $t^{dir}$ is used to represent the timestamp of data frames entering and leaving the hardware. Here, “dir” represents the direction of data frames entering or leaving the nodes, with " + " indicating data frames leaving the node and " − " indicating data frames entering the node.</p> +</blockquote> +<h2 id="test-data-frame-data-structure">Test data frame data structure</h2> +<p>In order to analyze the end-to-end latency of each data frame on complex network topologies, we have established specific guidelines for the content of data segments in the Ethernet frame structure. The structure of time-sensitive networking test data frames is as shown in the following table.</p> +<table> +<thead> +<tr> +<th>ield</th> +<th>Byte Length</th> +<th>Description</th> +</tr> +</thead> +<tbody> +<tr> +<td>Destination Address</td> +<td>6</td> +<td>Destination node MAC address</td> +</tr> +<tr> +<td>Source Address</td> +<td>6</td> +<td>Source node MAC address</td> +</tr> +<tr> +<td>VLAN Tag</td> +<td>4</td> +<td>Divided into four fields: VLAN Data Frame Type (0x8100), Priority, Canonical Format Indicator, and VLAN Number</td> +</tr> +<tr> +<td>Data Frame Type</td> +<td>2</td> +<td>Used to identify test data frames, set to 0x66ab</td> +</tr> +<tr> +<td>Reserved Bits</td> +<td>2</td> +<td></td> +</tr> +<tr> +<td><code>$t^+$ (TX Timestamp)</code></td> +<td>8</td> +<td>Timestamp when transmitted from the source node</td> +</tr> +<tr> +<td><code>$t^-$ (RX Timestamp)</code></td> +<td>8</td> +<td>Timestamp when received by the destination node</td> +</tr> +<tr> +<td>Data Stream ID (SEQ_ID)</td> +<td>2</td> +<td>Unique identifier for each data stream</td> +</tr> +<tr> +<td>Data Frame ID (PKT_ID)</td> +<td>4</td> +<td>Sequence number of data frames within each data stream, starting from 0</td> +</tr> +</tbody> +</table> +<h2 id="module-design">Module Design</h2> +<p>The overall module design for ZIGGO Evaluation Toolkit is depicted in the following diagram. The Time Synchronization module used by the Toolkit shares a design that is nearly identical to the Switch, and the diagram does not provide extensive details on the time synchronization-related modules.</p> +<p>The configuration module in the PS section (<code>software/pkt_gen_main.cpp</code>) communicates with the Data Frame Generation module by using the UIO driver and AXI4-Lite interface to send the transmission rules for the test data frames to relevant registers in the Data Frame Generation module (specifically, <code>hardware/IP_repo/pkt_gen_controller_v1.1/pkt_gen_controller_1.1/hdl/pkt_gen_controller_v1_1.v</code> is responsible for configuration, and <code>hardwire/HDL/axi_packet_generator.v</code> is responsible for generating and transmitting the data frames) using the global synchronized time as a reference for timing.</p> +<p>The Timestamp Marking module (<code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_tx.v</code> and <code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_rx.v</code>) is located at the send and receive ports of the Ziggo-Evaluation-Toolkit. It is used to record the hardware timestamps of sent and received data frames within the test data frames.</p> +<p>The received data frames are ultimately uploaded to the PS section via a DMA channel (in our design, we currently use a time-synchronized DMA channel for transmitting test data frames) for statistical analysis (handled in the <code>process_critical_frame</code> function in <code>software/pkt_gen_control/pkt_gen.c</code>).</p> <p> @@ -846,21 +780,117 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./device_arch.png" alt="device_arch" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>The default username and password are as follows:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> -</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> -</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh -</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> -<h3 id="3-connect-to-internet">3. Connect to Internet</h3> -<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> -<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> -<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> -<h3 id="4-run-the-software">4. Run the Software</h3> -<p>Please refer to the software part of this repo for further instructions.</p> +<p>The maximum frame transmission period (superperiod parameter in <code>pkt_gen_main.cpp</code>) refers to the upper limit on the periodicity for sending data streams from the toolkit. Within this maximum frame transmission period, the Data Frame Generation module allocates a maximum of 32 time slots for all data streams. Each time slot is used to send all the data frames for the corresponding data stream at the specified transmission time.</p> +<p>As illustrated in the diagram, the evaluation toolkit sends two types of data streams: Stream 𝐹1 with a transmission period of 2𝑇 and Stream 𝐹2 with a transmission period of 4𝑇. The maximum frame transmission period for the evaluation toolkit is 6𝑇. In this scenario, the Data Frame Generation module sets up 5 time slots within the maximum frame transmission period and sends test data frames in sequential order according to the specified time slots.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./example_pkt_gen_period.png" alt="example_pkt_gen_period" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>Users can configure the Ziggo-Evaluation-Toolkit to generate multiple data streams, and the configuration parameters for each data stream are as follows, with clear explanations provided in the comments of the <code>pkt_gen.h</code> header file:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// pkt_gen_app\pkt_gen_control\pkt_gen.h +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"><span class="cm">/** +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @brief Set the pkt gen slot object +</span></span></span><span class="line"><span class="cl"><span class="cm"> * +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param slot_id 0~31, indicate a slot in pkt_gen IP core +</span></span></span><span class="line"><span class="cl"><span class="cm"> * IMPORTANT: tx_offset for each slot id should be monotonic increasing +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param seq_id sequence ID that uniquely identify a stream +</span></span></span><span class="line"><span class="cl"><span class="cm"> * To further utilize this field, it may be {job_id: 8bit, flow_id: 8bit} +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_number number of packets in one sent, should be 1 +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_start start of pkt_id +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_update update of next pkt_id +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param tx_offset transmission time inside a period, in ns +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param src_mac 6Byte array +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param dest_mac 6Byte array +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @return int +</span></span></span><span class="line"><span class="cl"><span class="cm"> */</span> +</span></span><span class="line"><span class="cl"><span class="kt">int</span> <span class="nf">set_pkt_gen_slot</span> <span class="p">(</span><span class="kt">int</span> <span class="n">slot_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">seq_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">pkt_number</span><span class="p">,</span> <span class="kt">uint32_t</span> <span class="n">pkt_id_start</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="kt">uint32_t</span> <span class="n">pkt_id_update</span><span class="p">,</span> <span class="kt">int64_t</span> <span class="n">tx_offset</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">src_mac</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">dest_mac</span><span class="p">);</span> +</span></span></code></pre></div><p>The Timestamp Marking Module will write the timestamp of the current synchronized clock into the outgoing data frame just before it is transmitted by the MAC controller of the toolkit. When the MAC controller in the PL (Programmable Logic) receives the first bit of data in the frame from the physical link, the Timestamp Marking Module records the timestamp of the current synchronized clock. It subsequently writes this timestamp into the data frame during the packet reception process and hands it over to the statistical analysis module in the PS (Processing System) section for further analysis and processing.</p> +<h3 id="correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</h3> +<p>The correspondence in terms of time synchronization is the same as in the Ziggo TSN Switch.</p> +<p>In this section, we will primarily focus on the correspondence related to data frame transmission configuration. The software registers’ addresses can be found in <code>software/pkt_gen_control/pkt_gen.c</code>.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// define global register address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define GLOBAL_PERIOD_NS 0x00000000 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define GLOBAL_OFFSET_NS 0x00000008 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_VALID 0x00000010 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_ENABLE_VLAN 0x00000014 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITE_LOCK 0x00000018 +</span></span></span><span class="line"><span class="cl"><span class="cp"></span> +</span></span><span class="line"><span class="cl"><span class="c1">// define write lock value +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define NOT_WRITING 0x00000001 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITING 0x00000000 +</span></span></span><span class="line"><span class="cl"><span class="cp"></span> +</span></span><span class="line"><span class="cl"><span class="c1">// define address pointer for sequences +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define SEQ_CONTENT 0x0000001c +</span></span></span></code></pre></div><p>The hardware registers are located in <code>tsn_device\IP_repo\pkt_gen_controller_v1.1\pkt_gen_controller_1.1\hdl\pkt_gen_controller_v1_1_S00_AXI.v</code>.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"><span class="k">if</span> <span class="p">(</span><span class="n">slv_reg_wren</span><span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="k">case</span> <span class="p">(</span> <span class="n">axi_awaddr</span><span class="p">[</span><span class="n">ADDR_LSB</span><span class="o">+</span><span class="nl">OPT_MEM_ADDR_BITS</span><span class="p">:</span><span class="n">ADDR_LSB</span><span class="p">]</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h000</span><span class="p">:</span> +</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 0 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg0</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">end</span> +</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h001</span><span class="p">:</span> +</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 1 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg1</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">end</span> +</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h002</span><span class="p">:</span> +</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 2 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg2</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">end</span> +</span></span><span class="line"><span class="cl"><span class="p">...</span> +</span></span></code></pre></div><p>In this context, the hardware registers with names starting with “slv_reg” are each 32 bits wide, and their addresses are spaced by 4 bytes. So, for example, if the software-level address is $0x00000018$, you need to divide this address by 4, which results in $ 24/4 = 6$. Therefore, this address corresponds to the hardware register “<code>slv_reg6</code>” in the hardware module. This helps establish the correspondence between software and hardware registers.</p> +<h3 id="offline-analysis-and-design">Offline Analysis and Design</h3> +<p>In the <code>offline_analyze</code> branch of the Toolkit, we perform packet capture and analysis by forwarding packets from the Toolkit to a powerful desktop computer after the timestamps the incoming packets. This method ensures that even at gigabit speeds, no packets are dropped, and there are relatively minor hardware changes.</p> +<p>One aspect of the modification is that timestamps are not added to the data frames when they are transmitted from the toolkit. This can be seen in the <code>HDL/trimode_mac/simple_mac_no_shared.v</code> file where the “tsu_axis_tx” section is commented out.</p> +<p>Another aspect is the modification of the “frame_type” to change the direction of data frames. Previously, both PTP frames and test data frames were uploaded to the PS section via time-synchronized DMA, with IT traffic uploaded to PS_ETH. This split the traffic into two directions (“axis_switch_1_2”). Now, it has been split into three directions (“axis_switch_1_3”). For offline analysis, only PTP frames need to be transferred to the PS, while test data frames need to be separated and sent out from ETH2. This requires a finer-grained separation of traffic.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"> <span class="c1">// separate IT frames, ptp frames and critical frames +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="n">axis_switch_1_3</span> <span class="nf">axis_switch_1_3_inst</span> <span class="p">(</span> +</span></span><span class="line"><span class="cl"> <span class="p">.</span><span class="n">aclk</span><span class="p">(</span><span class="n">rx_fifo_clock</span><span class="p">),</span> <span class="c1">// input wire aclk +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">aresetn</span><span class="p">(</span><span class="n">rx_fifo_resetn</span><span class="p">),</span> <span class="c1">// input wire aresetn +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tvalid</span><span class="p">(</span><span class="n">rx_axis_fifo_tvalid_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tvalid +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tready</span><span class="p">(</span><span class="n">rx_axis_fifo_tready_8</span><span class="p">),</span> <span class="c1">// output wire [0 : 0] s_axis_tready +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdata</span><span class="p">(</span><span class="n">rx_axis_fifo_tdata_8</span><span class="p">),</span> <span class="c1">// input wire [7 : 0] s_axis_tdata +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tlast</span><span class="p">(</span><span class="n">rx_axis_fifo_tlast_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tlast +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdest</span><span class="p">(</span><span class="n">frame_type</span><span class="p">),</span> <span class="c1">// input wire [1 : 0] s_axis_tdest +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tvalid</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tvalid</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tvalid</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tvalid</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tvalid +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tready</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tready</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tready</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tready</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// input wire [2 : 0] m_axis_tready +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdata</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tdata</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tdata</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tdata</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [23 : 0] m_axis_tdata +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tlast</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tlast</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tlast</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tlast</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tlast +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdest</span><span class="p">(),</span> <span class="c1">// output wire [5 : 0] m_axis_tdest +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_decode_err</span><span class="p">()</span> <span class="c1">// output wire [0 : 0] s_decode_err +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="p">);</span> +</span></span></code></pre></div><p>The <code>tx_axis_fifo_legacy_tdata[1]</code> indicates sending from ETH2.</p> - -
- -📈 TSNPerf 设计原理 - http://localhost:1313/tsnperf/principle/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/tsnperf/principle/ -<h2 id="现有方案的局限">现有方案的局限</h2> -<p>TSNPerf是一款专为时间敏感网络（Time-Sensitive Networking, TSN）设计的性能评测工具。它提供了全面的TSN网络性能评测功能，能够帮助网络工程师和研究人员深入了解并验证TSN网络设备的性能特征。为此，TSNPerf需要能够精准地向网络中发送关键数据包，以测试设备的时间同步性能和流量整形能力。然而，Linux操作系统提供的<code>send()</code>函数只能达到微秒级的发包精度，难以满足TSNPerf对高精度发包的要求。</p> -<p>为了直观地展示<code>send()</code>函数的发包精度限制，我们进行了一项测试。在测试中，我们使用<code>send()</code>函数以1毫秒为设定间隔，连续发送了10000个数据包。然后，我们记录了每两个相邻数据包之间的实际时间间隔，并计算了它们与预期的1毫秒间隔之间的误差。结果显示，即使没有任何背景进程/流量的干扰，相邻数据包的间隔任然达到了<em><strong>最高14微秒</strong></em>左右。接下来我们分析该现象的原因。</p> -<p>如下图所示，在 $t_0$ 时刻，程序调用 <code>send()</code> 函数向网络发送数据包，但实际上，数据包在 $t_1$ 时刻才会被发送到网络中去。这是因为，操作系统的网络协议栈需要花费一定的时间处理该数据包。我们将 $t_1-t_0$ 称之为网络栈的处理时延，这个时延通常在微秒级别。</p> -<p> - - - - - - - - - - - - - - - -<figure id="figure-linux网络栈处理时延"> - <div class="flex justify-center "> - <div class="w-100" ><img src="./principle_basic.png" alt="Linux网络栈处理时延" loading="lazy" data-zoomable /></div> - </div><figcaption> - Linux网络栈处理时延 - </figcaption></figure> -</p> -<h2 id="解决方案">解决方案</h2> -<p>Intel 的 I210 / I225 / I226 网卡，提供了 LaunchTime 功能，可以精准地控制数据包离开网口的时间（理论精度在 32 纳秒级别）。</p> -<p> - - - - - - - - - - - - - - - -<figure id="figure-launchtime原理"> - <div class="flex justify-center "> - <div class="w-100" ><img src="./principle_advanced.png" alt="LaunchTime原理" loading="lazy" data-zoomable /></div> - </div><figcaption> - LaunchTime原理 - </figcaption></figure> -</p> -<p>利用 LaunchTime，可以提高数据包的发送精度。如上图所示，对于一个需要在 $t_0$ 时刻发出的数据包，我们预留一段时间给网络栈的处理流程，提前在 $t_2$ 时刻就调用 <code>send()</code> 函数，保证数据包在 $t_0$ 前就在网卡的出队列口等待，LaunchTime 会在$t_0$时刻打开出队列的门，将数据包发出。</p> -<h2 id="性能验证">性能验证</h2> -<p>类似地，我们开启 LaunchTime 功能，以1毫秒为设定间隔连续发送10000个数据包，记录每两个相邻数据包之间的实际时间间隔与1毫秒之间的误差。 -结果如下图所示，所有数据包的发送时间误差不超过100纳秒，达到了TSNPerf对发包精度的要求</p> -<p> - - - - - - - - - - - - - - - -<figure id="figure-launchtime实验结果"> - <div class="flex justify-center "> - <div class="w-100" ><img src="./principle_advanced_performance.png" alt="LaunchTime实验结果" loading="lazy" data-zoomable /></div> - </div><figcaption> - LaunchTime实验结果 - </figcaption></figure> -</p> - -- -
- -📕 ZIGGO Device使用手册 - http://localhost:1313/device/ziggo_device_manual/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/ziggo_device_manual/ -<p>There are two analysis methods for ZIGGO Device:</p> -<blockquote> -<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> -</blockquote> -<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> -<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> -<p>Example of <code>packet_log.csv</code>:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency -</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 -</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 -</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 -</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 -</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 -</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 -</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 -</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 -</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 -</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 -</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance -</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 -</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 -</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 -</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 -</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 -</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 -</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 -</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 -</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 -</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 -</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 -</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 -</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> -<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> -<p>Example of packet capture command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng -</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> -<p>Code for analyzing programs is <code>analyze_packet.py</code></p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> -</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> - -- -
+ +🔨 System Design —— PL & PS Co-operate - http://localhost:1313/device/system-design/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/system-design/ -<p>ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ’s both hardware and software programmability.</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./framework.jpg" alt="framework" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<h2 id="table-of-content">Table of Content</h2> -<ul> -<li><a href="#table-of-content">Table of Content</a></li> -<li><a href="#evaluation-method">Evaluation Method</a></li> -<li><a href="#test-data-frame-data-structure">Test data frame data structure</a></li> -<li><a href="#module-design">Module Design</a> -<ul> -<li><a href="#correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</a></li> -<li><a href="#offline-analysis-and-design">Offline Analysis and Design</a></li> -</ul> -</li> -</ul> -<h2 id="evaluation-method">Evaluation Method</h2> -<p>The ZIGGO Evaluation Toolkit is used to send and receive test data frames for the purpose of ensuring <code>accurate delay calculations</code>.</p> -<p>To achieve this accuracy, the toolkit needs to <strong>synchronize its time</strong> with the TSN switch and record a <strong>global hardware timestamp</strong> in the test data frames.</p> -<p>As shown in the diagram below, in a data flow link with $n$ network nodes, Node $1$ serves as the source node to send test data frames, Node $n$ acts as the destination node to receive test data frames, and all the intermediate nodes (Node $2$ to Node $n-1$) are TSN switches.</p> -<p>When a test data frame is sent from the source node, the hardware records the timestamp $t^+$ of when the frame was sent in the data frame. Finally, when the data frame arrives at the destination node, the destination node records the timestamp $t^-$ of when the frame entered that node. By calculating $(t^−−t^+)$, we can determine the end-to-end latency of the data frame.</p> + 💦 Software:Time Sync + Config for CaaS Switches + http://localhost:1313/switch/software_build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/software_build/ +<p>This repo contains source code to enable CaaS Switches’ time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).</p> +<h2 id="build">Build</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build +</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build +</span></span><span class="line"><span class="cl">cmake .. +</span></span><span class="line"><span class="cl">make +</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync_app” & “switch_config”</p> +<h2 id="config">Config</h2> +<p>The “config” directory contains topology & TSN/CaaS schedule results.</p> +<p>This document takes the following topology as an example to give example configurations:</p> <p> @@ -1301,75 +1122,248 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./device_test_demo.png" alt="device_test_demo" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./example_topology.png" alt="topology" loading="lazy" data-zoomable /></div> </div></figure> </p> -<blockquote> -<p>In this doc, $t^{dir}$ is used to represent the timestamp of data frames entering and leaving the hardware. Here, “dir” represents the direction of data frames entering or leaving the nodes, with " + " indicating data frames leaving the node and " − " indicating data frames entering the node.</p> -</blockquote> -<h2 id="test-data-frame-data-structure">Test data frame data structure</h2> -<p>In order to analyze the end-to-end latency of each data frame on complex network topologies, we have established specific guidelines for the content of data segments in the Ethernet frame structure. The structure of time-sensitive networking test data frames is as shown in the following table.</p> -<table> -<thead> -<tr> -<th>ield</th> -<th>Byte Length</th> -<th>Description</th> -</tr> -</thead> -<tbody> -<tr> -<td>Destination Address</td> -<td>6</td> -<td>Destination node MAC address</td> -</tr> -<tr> -<td>Source Address</td> -<td>6</td> -<td>Source node MAC address</td> -</tr> -<tr> -<td>VLAN Tag</td> -<td>4</td> -<td>Divided into four fields: VLAN Data Frame Type (0x8100), Priority, Canonical Format Indicator, and VLAN Number</td> -</tr> -<tr> -<td>Data Frame Type</td> -<td>2</td> -<td>Used to identify test data frames, set to 0x66ab</td> -</tr> -<tr> -<td>Reserved Bits</td> -<td>2</td> -<td></td> -</tr> -<tr> -<td><code>$t^+$ (TX Timestamp)</code></td> -<td>8</td> -<td>Timestamp when transmitted from the source node</td> -</tr> -<tr> -<td><code>$t^-$ (RX Timestamp)</code></td> -<td>8</td> -<td>Timestamp when received by the destination node</td> -</tr> -<tr> -<td>Data Stream ID (SEQ_ID)</td> -<td>2</td> -<td>Unique identifier for each data stream</td> -</tr> -<tr> -<td>Data Frame ID (PKT_ID)</td> -<td>4</td> -<td>Sequence number of data frames within each data stream, starting from 0</td> -</tr> -</tbody> -</table> -<h2 id="module-design">Module Design</h2> -<p>The overall module design for ZIGGO Evaluation Toolkit is depicted in the following diagram. The Time Synchronization module used by the Toolkit shares a design that is nearly identical to the Switch, and the diagram does not provide extensive details on the time synchronization-related modules.</p> -<p>The configuration module in the PS section (<code>software/pkt_gen_main.cpp</code>) communicates with the Data Frame Generation module by using the UIO driver and AXI4-Lite interface to send the transmission rules for the test data frames to relevant registers in the Data Frame Generation module (specifically, <code>hardware/IP_repo/pkt_gen_controller_v1.1/pkt_gen_controller_1.1/hdl/pkt_gen_controller_v1_1.v</code> is responsible for configuration, and <code>hardwire/HDL/axi_packet_generator.v</code> is responsible for generating and transmitting the data frames) using the global synchronized time as a reference for timing.</p> -<p>The Timestamp Marking module (<code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_tx.v</code> and <code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_rx.v</code>) is located at the send and receive ports of the Ziggo-Evaluation-Toolkit. It is used to record the hardware timestamps of sent and received data frames within the test data frames.</p> -<p>The received data frames are ultimately uploaded to the PS section via a DMA channel (in our design, we currently use a time-synchronized DMA channel for transmitting test data frames) for statistical analysis (handled in the <code>process_critical_frame</code> function in <code>software/pkt_gen_control/pkt_gen.c</code>).</p> +<ul> +<li> +<p>***-config.json: Mainly describes the network’s topology, including the type of each node (device or switch), MAC address, PTP port status, and other node information, topology information, and MAC forwarding table. Example and explanation are as follows (note that the comments in the file are just for explanation, do not have such comments in actual use):</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Used to describe the information of each node in the network +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">3</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Node's PTP port status +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// The quintuple represents the clock status of [local, ETH1, ETH2, ETH3, ETH4] +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Number meaning: (0: MASTER, 1: SLAVE, 2: PASSIVE, 3: DISABLED) +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 1, it means that the node is the master clock node; +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 0, it means that the node is the slave clock node. +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:14"</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:15"</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Topology information, composed of each link, each link is a directed edge +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// link ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Port number of the source node +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// port 0,1,2,3 correspond to ETH1,2,3,4 in reality +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Port number of the destination node +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">2</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Forwarding table, which can be generated by the scheduling algorithm in CNC +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// In the forwarding table where you send to yourself, the port is 4 (caas) / 5 (PS ETH for new hardware) +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Current node ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Output port number +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Entry ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Destination node ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><p>If the master clock selection algorithm is used, only the configuration of nodes is different, and the rest are the same. The newly added <code>externalPortConfigurationEnabled</code> and <code>system_identity</code> fields are optional items, as shown in the example below:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:00:00:00:02:01"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"externalPortConfigurationEnabled"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> <span class="c1">// 1: Manually configure the master-slave relationship, 0: Configure the master-slave relationship through the master clock selection algorithm, if this item is not written, the default is 0, that is, configure the master-slave relationship through the master clock selection +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"system_identity"</span><span class="p">:</span> <span class="p">{</span> <span class="c1">// Clock node's clock parameters, used for comparison in the master clock selection algorithm, if this item is not written, the default is the configuration written below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority1"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// First priority +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockClass"</span><span class="p">:</span> <span class="mi">248</span><span class="p">,</span> <span class="c1">// Clock level +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockAccuracy"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// Clock accuracy +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"offsetScaledLogVariance"</span><span class="p">:</span> <span class="mi">17258</span><span class="p">,</span> <span class="c1">// Clock variance +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority2"</span><span class="p">:</span> <span class="mi">247</span><span class="p">,</span> <span class="c1">// Second priority +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clock_identity"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">]</span> <span class="c1">// Clock identifier, different clocks should have different parameters +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div></li> +<li> +<p>***-schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span><span class="c1">// All switches need to be listed to facilitate software recognition of configuration information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Can be empty, not used +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> <span class="c1">// Type is link, used to describe scheduling information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Output port number +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Scheduling information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> <span class="c1">// Scheduling cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Start time relative to the entire cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">5</span><span class="p">,</span> <span class="c1">// End time relative to the entire cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Job ID in CaaS, if not needed, it can be omitted +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Data stream ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">6</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">1500</span> <span class="c1">// Packet length, if not written, the default is 1500B, this item only exists on the path from Device to Switch +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"><span class="p">]</span> +</span></span></code></pre></div></li> +</ul> +<h2 id="run">Run</h2> +<ul> +<li>Copy topology & schedule file to build dir:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-config.json build/config.json +</span></span><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-schedule.json build/schedule.json +</span></span></code></pre></div><ul> +<li>Start time synchronization and initialize GCL and MAC forwarding table according to the configuration (it is recommended to run the time synchronization program on a core (with <code>taskset -c 1</code> command) to prevent kernel errors and crashes due to time synchronization):</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync +</span></span></code></pre></div><ul> +<li>The log output level is categorized into three types: WARN, INFO, and TRACE. The default log output level is TRACE (the most comprehensive output information, including DEBUG logs). The log output level can be set with the -l parameter:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l w <span class="c1"># WARN level</span> +</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l i <span class="c1"># INFO level</span> +</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l t <span class="c1"># TRACE level</span> +</span></span></code></pre></div><p><em>Notice that the time sync logic is supposed to run indefinitely as the node should sync to its neighbors again and again.</em></p> +<ul> +<li>Update GCL & switch forwarding rules:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./switch_config +</span></span></code></pre></div> +- +
@@ -1748,5 +1670,92 @@ Our GCL is represented by 9 bits, with the highest bit representing whether the </span></span></code></pre></div> +💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit + http://localhost:1313/switch/hardware-build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/hardware-build/ +<p>This repo contains pre-build hardware & system rootfs to boot the <strong>Zynq AX7021</strong> FPGA board from SD card.</p> +<h2 id="file-downloading">File downloading</h2> +<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/8277c491a8bd4e6a8997/" target="_blank" rel="noopener">this</a> public link:</p> +<ul> +<li>BOOT.BIN</li> +<li>boot.scr</li> +<li>image.ub</li> +<li>rootfs.tar.gz</li> +</ul> +<h2 id="sd-card-partition">SD card partition</h2> +<p>In order to boot the CaaS Switch, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted +</span></span><span class="line"><span class="cl">sudo gparted +</span></span></code></pre></div><p>Parition it into two partition below</p> +<ul> +<li> +<p>BOOT: store boot files from petalinux</p> +<p>Free space preceding (MiB): 4</p> +<p>New size (MiB): 500</p> +<p>File system: fat32</p> +<p>Label: BOOT</p> +</li> +<li> +<p>ROOTFS: store debian system rootfs</p> +<p>Free space preceding (MiB): 0</p> +<p>Free space following (MiB): 0</p> +<p>File system: ext4</p> +<p>Label: ROOTFS</p> +</li> +</ul> +<h2 id="copy-files-into-sd-card">Copy files into SD card</h2> +<p>Mound SD card:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ +</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ +</span></span></code></pre></div><p>Remove original files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* +</span></span></code></pre></div><p>Copy files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh +</span></span><span class="line"><span class="cl">sync +</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS +</span></span></code></pre></div><h2 id="launch-the-switch">Launch the switch</h2> +<h3 id="1-launch-the-board">1. Launch the Board</h3> +<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> <p> @@ -1388,11 +1382,12 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./device_arch.png" alt="device_arch" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>The maximum frame transmission period (superperiod parameter in <code>pkt_gen_main.cpp</code>) refers to the upper limit on the periodicity for sending data streams from the toolkit. Within this maximum frame transmission period, the Data Frame Generation module allocates a maximum of 32 time slots for all data streams. Each time slot is used to send all the data frames for the corresponding data stream at the specified transmission time.</p> -<p>As illustrated in the diagram, the evaluation toolkit sends two types of data streams: Stream 𝐹1 with a transmission period of 2𝑇 and Stream 𝐹2 with a transmission period of 4𝑇. The maximum frame transmission period for the evaluation toolkit is 6𝑇. In this scenario, the Data Frame Generation module sets up 5 time slots within the maximum frame transmission period and sends test data frames in sequential order according to the specified time slots.</p> +<h3 id="2-initialize-ps">2. Initialize PS</h3> +<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> +<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> <p> @@ -1411,94 +1406,21 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./example_pkt_gen_period.png" alt="example_pkt_gen_period" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>Users can configure the Ziggo-Evaluation-Toolkit to generate multiple data streams, and the configuration parameters for each data stream are as follows, with clear explanations provided in the comments of the <code>pkt_gen.h</code> header file:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// pkt_gen_app\pkt_gen_control\pkt_gen.h -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"><span class="cm">/** -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @brief Set the pkt gen slot object -</span></span></span><span class="line"><span class="cl"><span class="cm"> * -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param slot_id 0~31, indicate a slot in pkt_gen IP core -</span></span></span><span class="line"><span class="cl"><span class="cm"> * IMPORTANT: tx_offset for each slot id should be monotonic increasing -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param seq_id sequence ID that uniquely identify a stream -</span></span></span><span class="line"><span class="cl"><span class="cm"> * To further utilize this field, it may be {job_id: 8bit, flow_id: 8bit} -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_number number of packets in one sent, should be 1 -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_start start of pkt_id -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_update update of next pkt_id -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param tx_offset transmission time inside a period, in ns -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param src_mac 6Byte array -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param dest_mac 6Byte array -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @return int -</span></span></span><span class="line"><span class="cl"><span class="cm"> */</span> -</span></span><span class="line"><span class="cl"><span class="kt">int</span> <span class="nf">set_pkt_gen_slot</span> <span class="p">(</span><span class="kt">int</span> <span class="n">slot_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">seq_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">pkt_number</span><span class="p">,</span> <span class="kt">uint32_t</span> <span class="n">pkt_id_start</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="kt">uint32_t</span> <span class="n">pkt_id_update</span><span class="p">,</span> <span class="kt">int64_t</span> <span class="n">tx_offset</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">src_mac</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">dest_mac</span><span class="p">);</span> -</span></span></code></pre></div><p>The Timestamp Marking Module will write the timestamp of the current synchronized clock into the outgoing data frame just before it is transmitted by the MAC controller of the toolkit. When the MAC controller in the PL (Programmable Logic) receives the first bit of data in the frame from the physical link, the Timestamp Marking Module records the timestamp of the current synchronized clock. It subsequently writes this timestamp into the data frame during the packet reception process and hands it over to the statistical analysis module in the PS (Processing System) section for further analysis and processing.</p> -<h3 id="correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</h3> -<p>The correspondence in terms of time synchronization is the same as in the Ziggo TSN Switch.</p> -<p>In this section, we will primarily focus on the correspondence related to data frame transmission configuration. The software registers’ addresses can be found in <code>software/pkt_gen_control/pkt_gen.c</code>.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// define global register address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define GLOBAL_PERIOD_NS 0x00000000 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define GLOBAL_OFFSET_NS 0x00000008 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_VALID 0x00000010 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_ENABLE_VLAN 0x00000014 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITE_LOCK 0x00000018 -</span></span></span><span class="line"><span class="cl"><span class="cp"></span> -</span></span><span class="line"><span class="cl"><span class="c1">// define write lock value -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define NOT_WRITING 0x00000001 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITING 0x00000000 -</span></span></span><span class="line"><span class="cl"><span class="cp"></span> -</span></span><span class="line"><span class="cl"><span class="c1">// define address pointer for sequences -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define SEQ_CONTENT 0x0000001c -</span></span></span></code></pre></div><p>The hardware registers are located in <code>tsn_device\IP_repo\pkt_gen_controller_v1.1\pkt_gen_controller_1.1\hdl\pkt_gen_controller_v1_1_S00_AXI.v</code>.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"><span class="k">if</span> <span class="p">(</span><span class="n">slv_reg_wren</span><span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="k">case</span> <span class="p">(</span> <span class="n">axi_awaddr</span><span class="p">[</span><span class="n">ADDR_LSB</span><span class="o">+</span><span class="nl">OPT_MEM_ADDR_BITS</span><span class="p">:</span><span class="n">ADDR_LSB</span><span class="p">]</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h000</span><span class="p">:</span> -</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 0 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg0</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">end</span> -</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h001</span><span class="p">:</span> -</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 1 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg1</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">end</span> -</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h002</span><span class="p">:</span> -</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 2 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg2</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">end</span> -</span></span><span class="line"><span class="cl"><span class="p">...</span> -</span></span></code></pre></div><p>In this context, the hardware registers with names starting with “slv_reg” are each 32 bits wide, and their addresses are spaced by 4 bytes. So, for example, if the software-level address is $0x00000018$, you need to divide this address by 4, which results in $ 24/4 = 6$. Therefore, this address corresponds to the hardware register “<code>slv_reg6</code>” in the hardware module. This helps establish the correspondence between software and hardware registers.</p> -<h3 id="offline-analysis-and-design">Offline Analysis and Design</h3> -<p>In the <code>offline_analyze</code> branch of the Toolkit, we perform packet capture and analysis by forwarding packets from the Toolkit to a powerful desktop computer after the timestamps the incoming packets. This method ensures that even at gigabit speeds, no packets are dropped, and there are relatively minor hardware changes.</p> -<p>One aspect of the modification is that timestamps are not added to the data frames when they are transmitted from the toolkit. This can be seen in the <code>HDL/trimode_mac/simple_mac_no_shared.v</code> file where the “tsu_axis_tx” section is commented out.</p> -<p>Another aspect is the modification of the “frame_type” to change the direction of data frames. Previously, both PTP frames and test data frames were uploaded to the PS section via time-synchronized DMA, with IT traffic uploaded to PS_ETH. This split the traffic into two directions (“axis_switch_1_2”). Now, it has been split into three directions (“axis_switch_1_3”). For offline analysis, only PTP frames need to be transferred to the PS, while test data frames need to be separated and sent out from ETH2. This requires a finer-grained separation of traffic.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"> <span class="c1">// separate IT frames, ptp frames and critical frames -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="n">axis_switch_1_3</span> <span class="nf">axis_switch_1_3_inst</span> <span class="p">(</span> -</span></span><span class="line"><span class="cl"> <span class="p">.</span><span class="n">aclk</span><span class="p">(</span><span class="n">rx_fifo_clock</span><span class="p">),</span> <span class="c1">// input wire aclk -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">aresetn</span><span class="p">(</span><span class="n">rx_fifo_resetn</span><span class="p">),</span> <span class="c1">// input wire aresetn -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tvalid</span><span class="p">(</span><span class="n">rx_axis_fifo_tvalid_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tvalid -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tready</span><span class="p">(</span><span class="n">rx_axis_fifo_tready_8</span><span class="p">),</span> <span class="c1">// output wire [0 : 0] s_axis_tready -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdata</span><span class="p">(</span><span class="n">rx_axis_fifo_tdata_8</span><span class="p">),</span> <span class="c1">// input wire [7 : 0] s_axis_tdata -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tlast</span><span class="p">(</span><span class="n">rx_axis_fifo_tlast_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tlast -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdest</span><span class="p">(</span><span class="n">frame_type</span><span class="p">),</span> <span class="c1">// input wire [1 : 0] s_axis_tdest -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tvalid</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tvalid</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tvalid</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tvalid</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tvalid -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tready</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tready</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tready</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tready</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// input wire [2 : 0] m_axis_tready -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdata</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tdata</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tdata</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tdata</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [23 : 0] m_axis_tdata -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tlast</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tlast</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tlast</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tlast</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tlast -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdest</span><span class="p">(),</span> <span class="c1">// output wire [5 : 0] m_axis_tdest -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_decode_err</span><span class="p">()</span> <span class="c1">// output wire [0 : 0] s_decode_err -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="p">);</span> -</span></span></code></pre></div><p>The <code>tx_axis_fifo_legacy_tdata[1]</code> indicates sending from ETH2.</p> +<p>The default username and password are as follows:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> +</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> +</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh +</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> +<h3 id="3-connect-to-internet">3. Connect to Internet</h3> +<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> +<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> +<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> +<h3 id="4-run-the-software">4. Run the Software</h3> +<p>Please refer to the software part of this repo for further instructions.</p> - +
+ diff --git a/public/tag/markdown/page/2/index.html b/public/tag/markdown/page/2/index.html index 4d56bcd..ff25f6f 100644 --- a/public/tag/markdown/page/2/index.html +++ b/public/tag/markdown/page/2/index.html @@ -1,6 +1,6 @@ - @@ -4162,19 +4162,19 @@📈 TSNPerf 设计原理 + http://localhost:1313/tsnperf/principle/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/tsnperf/principle/ +<h2 id="现有方案的局限">现有方案的局限</h2> +<p>TSNPerf是一款专为时间敏感网络（Time-Sensitive Networking, TSN）设计的性能评测工具。它提供了全面的TSN网络性能评测功能，能够帮助网络工程师和研究人员深入了解并验证TSN网络设备的性能特征。为此，TSNPerf需要能够精准地向网络中发送关键数据包，以测试设备的时间同步性能和流量整形能力。然而，Linux操作系统提供的<code>send()</code>函数只能达到微秒级的发包精度，难以满足TSNPerf对高精度发包的要求。</p> +<p>为了直观地展示<code>send()</code>函数的发包精度限制，我们进行了一项测试。在测试中，我们使用<code>send()</code>函数以1毫秒为设定间隔，连续发送了10000个数据包。然后，我们记录了每两个相邻数据包之间的实际时间间隔，并计算了它们与预期的1毫秒间隔之间的误差。结果显示，即使没有任何背景进程/流量的干扰，相邻数据包的间隔任然达到了<em><strong>最高14微秒</strong></em>左右。接下来我们分析该现象的原因。</p> +<p>如下图所示，在 $t_0$ 时刻，程序调用 <code>send()</code> 函数向网络发送数据包，但实际上，数据包在 $t_1$ 时刻才会被发送到网络中去。这是因为，操作系统的网络协议栈需要花费一定的时间处理该数据包。我们将 $t_1-t_0$ 称之为网络栈的处理时延，这个时延通常在微秒级别。</p> +<p> + + + + + + + + + + + + + + + +<figure id="figure-linux网络栈处理时延"> + <div class="flex justify-center "> + <div class="w-100" ><img src="./principle_basic.png" alt="Linux网络栈处理时延" loading="lazy" data-zoomable /></div> + </div><figcaption> + Linux网络栈处理时延 + </figcaption></figure> +</p> +<h2 id="解决方案">解决方案</h2> +<p>Intel 的 I210 / I225 / I226 网卡，提供了 LaunchTime 功能，可以精准地控制数据包离开网口的时间（理论精度在 32 纳秒级别）。</p> +<p> + + + + + + + + + + + + + + + +<figure id="figure-launchtime原理"> + <div class="flex justify-center "> + <div class="w-100" ><img src="./principle_advanced.png" alt="LaunchTime原理" loading="lazy" data-zoomable /></div> + </div><figcaption> + LaunchTime原理 + </figcaption></figure> +</p> +<p>利用 LaunchTime，可以提高数据包的发送精度。如上图所示，对于一个需要在 $t_0$ 时刻发出的数据包，我们预留一段时间给网络栈的处理流程，提前在 $t_2$ 时刻就调用 <code>send()</code> 函数，保证数据包在 $t_0$ 前就在网卡的出队列口等待，LaunchTime 会在$t_0$时刻打开出队列的门，将数据包发出。</p> +<h2 id="性能验证">性能验证</h2> +<p>类似地，我们开启 LaunchTime 功能，以1毫秒为设定间隔连续发送10000个数据包，记录每两个相邻数据包之间的实际时间间隔与1毫秒之间的误差。 +结果如下图所示，所有数据包的发送时间误差不超过100纳秒，达到了TSNPerf对发包精度的要求</p> +<p> + + + + + + + + + + + + + + + +<figure id="figure-launchtime实验结果"> + <div class="flex justify-center "> + <div class="w-100" ><img src="./principle_advanced_performance.png" alt="LaunchTime实验结果" loading="lazy" data-zoomable /></div> + </div><figcaption> + LaunchTime实验结果 + </figcaption></figure> +</p> + +Markdown
- +diff --git a/public/tag/test-case/index.html b/public/tag/test-case/index.html index 74e3306..16a1622 100644 --- a/public/tag/test-case/index.html +++ b/public/tag/test-case/index.html @@ -1,6 +1,6 @@ - diff --git a/public/tag/tsnperf/index.html b/public/tag/tsnperf/index.html index be96ddb..d5b9a76 100644 --- a/public/tag/tsnperf/index.html +++ b/public/tag/tsnperf/index.html @@ -1,6 +1,6 @@ - @@ -4162,19 +4162,19 @@-
+ 
-⌚ TSNPerf 检测内容及使用表+☀ 某品牌交换机报告- 时间同步测试，流量整形测试，网络配置测试
+ TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动May 1, 2024
TSNPerf
- +@@ -4190,13 +4190,13 @@-
+
-🧠 基础知识列表+👩🏼🏫 准备清单- 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表
+ ZIGGO 软硬件准备清单May 1, 2024
TSNPerf
- +-
+
@@ -4246,19 +4246,19 @@TSNPerf
- +@@ -4274,19 +4274,19 @@-
+
-📈 TSNPerf 使用指南+🎉 How to contribute- TSNPerf 硬件准备 系统准备 和 测试程序使用
+ How to report a bug or contribute to ZIGGO's codeMay 1, 2024
TSNPerf
- +@@ -4302,19 +4302,19 @@-
+
-👩🏼🏫 准备清单+📈 TSNPerf 使用指南- ZIGGO 软硬件准备清单
+ TSNPerf 硬件准备 系统准备 和 测试程序使用May 1, 2024
TSNPerf
- +@@ -4330,19 +4330,19 @@-
+
-👩🏼🏫 准备清单+🧠 基础知识列表- ZIGGO 软硬件准备清单
+ 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表May 1, 2024
TSNPerf
- +@@ -4358,19 +4358,19 @@-
+
-👍Hardware：Build the CaaS Device+👩🏼🏫 准备清单- How to build the Caas Device Hardware step by step.
+ ZIGGO 软硬件准备清单May 1, 2024
TSNPerf
- +@@ -4386,19 +4386,19 @@-
+
-🎉 How to contribute+👍Hardware：Build the CaaS Device- How to report a bug or contribute to ZIGGO's code
+ How to build the Caas Device Hardware step by step.May 1, 2024
TSNPerf
- +@@ -4414,15 +4414,19 @@-
+
-🎉 How to contribute+⌚ TSNPerf 检测内容及使用表- How to report a bug or contribute to ZIGGO's code
+ 时间同步测试，流量整形测试，网络配置测试May 1, 2024
TSNPerf
- +diff --git a/public/tag/tsnperf/index.xml b/public/tag/tsnperf/index.xml index 0529841..9244176 100644 --- a/public/tag/tsnperf/index.xml +++ b/public/tag/tsnperf/index.xml @@ -12,6 +12,45 @@ http://localhost:1313/tag/tsnperf/ ++ + +
+
-☀ 某品牌交换机报告+🎉 How to contribute- TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动
+ How to report a bug or contribute to ZIGGO's codeMay 1, 2024
- +
+ +☀ 某品牌交换机报告 + http://localhost:1313/tsnperf/report/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/tsnperf/report/ +<p>详细报告请查看<a href="http://localhost:1313/pdf/switch_report.pdf">这里</a>。</p> + +- +
+🎉 How to contribute + http://localhost:1313/device/contributing/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/contributing/ +<h2 id="reporting-a-bug">Reporting a bug</h2> +<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> +<ul> +<li>Search existing issues first, make sure yours hasn’t already been reported.</li> +<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> +<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> +<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> +</ul> +<blockquote> +<p>The development team will only answer questions on github issues and reject other forms of questions.</p> +</blockquote> +<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> +<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> +<ul> +<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> +<li>Bug fixes are always welcome.</li> +<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> +<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> +<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> +<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> +<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> +</ul> + +⌚ TSNPerf 检测内容及使用表 http://localhost:1313/tsnperf/manual/ @@ -167,66 +206,6 @@- -
- -🎉 How to contribute - http://localhost:1313/device/contributing/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/contributing/ -<h2 id="reporting-a-bug">Reporting a bug</h2> -<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> -<ul> -<li>Search existing issues first, make sure yours hasn’t already been reported.</li> -<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> -<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> -<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> -</ul> -<blockquote> -<p>The development team will only answer questions on github issues and reject other forms of questions.</p> -</blockquote> -<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> -<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> -<ul> -<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> -<li>Bug fixes are always welcome.</li> -<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> -<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> -<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> -<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> -<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> -</ul> - -- -
-🎉 How to contribute - http://localhost:1313/switch/contributing/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/contributing/ -<h2 id="reporting-a-bug">Reporting a bug</h2> -<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> -<ul> -<li>Search existing issues first, make sure yours hasn’t already been reported.</li> -<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> -<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> -<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> -</ul> -<blockquote> -<p>The development team will only answer questions on github issues and reject other forms of questions.</p> -</blockquote> -<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> -<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> -<ul> -<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> -<li>Bug fixes are always welcome.</li> -<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> -<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> -<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> -<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> -<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> -</ul> - -👍Hardware：Build the CaaS Device http://localhost:1313/device/hardware-build/ @@ -674,28 +653,30 @@- -
@@ -894,6 +875,36 @@ </span></span></code></pre></div> +👩🏼🏫 准备清单 - http://localhost:1313/switch/require/ +🧠 基础知识列表 + http://localhost:1313/device/basic_knowledge/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/require/ -<h2 id="软件环境清单">软件环境清单</h2> -<h3 id="vivada-开发环境">Vivada 开发环境</h3> -<p>Vivado 是开发板的硬件开发程序。</p> -<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> -<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> -<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> -<h3 id="mobaxterm">MobaXterm</h3> -<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> -<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> -<h2 id="硬件准备清单">硬件准备清单</h2> -<h3 id="alinx7021开发板">Alinx7021开发板</h3> -<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> -<h3 id="sd启动卡">SD启动卡</h3> -<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> -<h3 id="必要的线材">必要的线材</h3> -<p>包括网线、数据线等。</p> -<h3 id="普通交换机">普通交换机</h3> -<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> + http://localhost:1313/device/basic_knowledge/ +<p>我们再次重申，使用或者开发ZIGGO-CaaS-Switch或者ZIGGO-Device是有较高门槛的，您必须掌握一定的软硬件知识。如果您之间没有任何的硬件开发经验，您可能需要慎重考虑自己是否适合这个项目，因为学习这些知识是非常花时间的。</p> +<p>学习使用ZIGGO项目比学习FPGA、MCU、ARM等传统开发工具要求更高，想如臂指使一般地使用ZIGGO设备也不是一蹴而就的事情。</p> +<p>如果您希望使用ZIGGO项目，您至少应该有以下知识：</p> +<h2 id="硬件知识">硬件知识</h2> +<ul> +<li>计算机组成原理</li> +<li>C语言</li> +<li>数字电路基础</li> +<li>Verilog、VHDL语言</li> +<li>良好的英语阅读基础</li> +</ul> +<h2 id="软件知识">软件知识</h2> +<ul> +<li>计算机组成原理</li> +<li>计算机网络</li> +<li>计算机操作系统</li> +<li>C、C++语言</li> +<li>tcl脚本</li> +<li>良好的英语阅读基础</li> +</ul> - +
+🎉 How to contribute + http://localhost:1313/switch/contributing/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/contributing/ +<h2 id="reporting-a-bug">Reporting a bug</h2> +<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> +<ul> +<li>Search existing issues first, make sure yours hasn’t already been reported.</li> +<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> +<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> +<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> +</ul> +<blockquote> +<p>The development team will only answer questions on github issues and reject other forms of questions.</p> +</blockquote> +<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> +<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> +<ul> +<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> +<li>Bug fixes are always welcome.</li> +<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> +<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> +<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> +<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> +<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> +</ul> + +📈 TSNPerf 设计原理 http://localhost:1313/tsnperf/principle/ @@ -983,9 +994,9 @@🧠 基础知识列表 - http://localhost:1313/device/basic_knowledge/ + http://localhost:1313/switch/basic_knowledge/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/basic_knowledge/ +http://localhost:1313/switch/basic_knowledge/ <p>我们再次重申，使用或者开发ZIGGO-CaaS-Switch或者ZIGGO-Device是有较高门槛的，您必须掌握一定的软硬件知识。如果您之间没有任何的硬件开发经验，您可能需要慎重考虑自己是否适合这个项目，因为学习这些知识是非常花时间的。</p> <p>学习使用ZIGGO项目比学习FPGA、MCU、ARM等传统开发工具要求更高，想如臂指使一般地使用ZIGGO设备也不是一蹴而就的事情。</p> <p>如果您希望使用ZIGGO项目，您至少应该有以下知识：</p> @@ -1010,30 +1021,28 @@ - -
diff --git a/public/tag/tsnperf/page/2/index.html b/public/tag/tsnperf/page/2/index.html index e49db31..18bfc58 100644 --- a/public/tag/tsnperf/page/2/index.html +++ b/public/tag/tsnperf/page/2/index.html @@ -1,6 +1,6 @@ - @@ -4162,19 +4162,19 @@🧠 基础知识列表 - http://localhost:1313/switch/basic_knowledge/ +👩🏼🏫 准备清单 + http://localhost:1313/switch/require/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/basic_knowledge/ -<p>我们再次重申，使用或者开发ZIGGO-CaaS-Switch或者ZIGGO-Device是有较高门槛的，您必须掌握一定的软硬件知识。如果您之间没有任何的硬件开发经验，您可能需要慎重考虑自己是否适合这个项目，因为学习这些知识是非常花时间的。</p> -<p>学习使用ZIGGO项目比学习FPGA、MCU、ARM等传统开发工具要求更高，想如臂指使一般地使用ZIGGO设备也不是一蹴而就的事情。</p> -<p>如果您希望使用ZIGGO项目，您至少应该有以下知识：</p> -<h2 id="硬件知识">硬件知识</h2> -<ul> -<li>计算机组成原理</li> -<li>C语言</li> -<li>数字电路基础</li> -<li>Verilog、VHDL语言</li> -<li>良好的英语阅读基础</li> -</ul> -<h2 id="软件知识">软件知识</h2> -<ul> -<li>计算机组成原理</li> -<li>计算机网络</li> -<li>计算机操作系统</li> -<li>C、C++语言</li> -<li>tcl脚本</li> -<li>良好的英语阅读基础</li> -</ul> + http://localhost:1313/switch/require/ +<h2 id="软件环境清单">软件环境清单</h2> +<h3 id="vivada-开发环境">Vivada 开发环境</h3> +<p>Vivado 是开发板的硬件开发程序。</p> +<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> +<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> +<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> +<h3 id="mobaxterm">MobaXterm</h3> +<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> +<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> +<h2 id="硬件准备清单">硬件准备清单</h2> +<h3 id="alinx7021开发板">Alinx7021开发板</h3> +<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> +<h3 id="sd启动卡">SD启动卡</h3> +<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> +<h3 id="必要的线材">必要的线材</h3> +<p>包括网线、数据线等。</p> +<h3 id="普通交换机">普通交换机</h3> +<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> TSNPerf
- +diff --git a/public/tag/ziggo-device/index.html b/public/tag/ziggo-device/index.html index a7fa866..eb6846b 100644 --- a/public/tag/ziggo-device/index.html +++ b/public/tag/ziggo-device/index.html @@ -1,6 +1,6 @@ - @@ -4162,19 +4162,19 @@-
+
-⌚ TSNPerf 检测内容及使用表+☀ 某品牌交换机报告- 时间同步测试，流量整形测试，网络配置测试
+ TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动May 1, 2024
ZIGGO-Device
- +@@ -4190,13 +4190,13 @@-
+
-🧠 基础知识列表+👩🏼🏫 准备清单- 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表
+ ZIGGO 软硬件准备清单May 1, 2024
ZIGGO-Device
- +-
+
@@ -4218,19 +4218,19 @@ZIGGO-Device
- +@@ -4246,19 +4246,19 @@-
+
-🆒 Getting start+🎉 How to contribute- ZIGGO device get start document
+ How to report a bug or contribute to ZIGGO's codeMay 1, 2024
ZIGGO-Device
- +@@ -4274,19 +4274,19 @@-
+
-🔨 System Design —— PL & PS Co-operate+🧠 基础知识列表- ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.
+ 使用 ZIGGO-SWITCH/ZIGGO-DEVICE 的基础知识列表May 1, 2024
ZIGGO-Device
- +@@ -4302,19 +4302,19 @@-
+
-📕 ZIGGO Device使用手册+👩🏼🏫 准备清单- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ ZIGGO 软硬件准备清单May 1, 2024
ZIGGO-Device
- +@@ -4330,19 +4330,19 @@-
+
-📕 CNC脚本使用指南+🆒 Getting start- 使用CNC脚本运行ZIGGO系统的7步指南
+ ZIGGO device get start documentMay 1, 2024
ZIGGO-Device
- +@@ -4358,19 +4358,19 @@-
+
-💦 Software:Time Sync + Config for CaaS Device+🔨 System Design —— PL & PS Co-operate- Docs to enable CaaS Device' time synchronization logic and set up pkt gen.
+ ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.May 1, 2024
ZIGGO-Device
- +@@ -4386,19 +4386,19 @@-
+
-👩🏼🏫 准备清单+👍Hardware：Build the CaaS Device- ZIGGO 软硬件准备清单
+ How to build the Caas Device Hardware step by step.May 1, 2024
ZIGGO-Device
- +@@ -4414,19 +4414,19 @@-
+
-👩🏼🏫 准备清单+💦 Software:Time Sync + Config for CaaS Device- ZIGGO 软硬件准备清单
+ Docs to enable CaaS Device' time synchronization logic and set up pkt gen.May 1, 2024
ZIGGO-Device
- +diff --git a/public/tag/ziggo-device/index.xml b/public/tag/ziggo-device/index.xml index fdb87a1..445141f 100644 --- a/public/tag/ziggo-device/index.xml +++ b/public/tag/ziggo-device/index.xml @@ -43,32 +43,221 @@-
+
-👍Hardware：Build the CaaS Device+📕 ZIGGO Device使用手册- How to build the Caas Device Hardware step by step.
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
- -
+ +🎉 How to contribute - http://localhost:1313/switch/contributing/ +📕 CNC脚本使用指南 + http://localhost:1313/device/cnc_manual/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/contributing/ -<h2 id="reporting-a-bug">Reporting a bug</h2> -<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> -<ul> -<li>Search existing issues first, make sure yours hasn’t already been reported.</li> -<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> -<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> -<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> -</ul> + http://localhost:1313/device/cnc_manual/ +<h2 id="1-运行脚本前在batchmjs中要配置好以下变量">1. 运行脚本前，在batch.mjs中要配置好以下变量：</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// IP address format: 192.168.137.* +</span></span></span><span class="line"><span class="cl"><span class="c1">// 测试数据 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">conf_default</span> <span class="o">=</span> <span class="s2">"<需要执行的配置名称>"</span> +</span></span><span class="line"><span class="cl"><span class="c1">// 时钟主节点 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">master</span> <span class="o">=</span> <span class="mi">40</span> +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl"><span class="kr">const</span> <span class="nx">hosts</span> <span class="o">=</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nx">device</span><span class="o">:</span> <span class="p">[</span><span class="mi">43</span><span class="p">,</span> <span class="mi">44</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="k">switch</span><span class="o">:</span> <span class="p">[</span><span class="mi">40</span><span class="p">,</span> <span class="mi">41</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">安装好需要的依赖： +</span></span><span class="line"><span class="cl">```bash +</span></span><span class="line"><span class="cl">sudo npm install -g zx@4.3.0 +</span></span><span class="line"><span class="cl">pip install -r requirements.txt +</span></span><span class="line"><span class="cl">npm install +</span></span></code></pre></div><p>配置好环境变量，在.bashrc中加入：</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">export</span> <span class="nv">PYTHONPATH</span><span class="o">=</span><span class="s2">"/home/<用户名>/scripts"</span> +</span></span></code></pre></div><h2 id="2-下载好switch和tsnperf的软件代码">2. 下载好Switch和TSNPerf的软件代码</h2> <blockquote> -<p>The development team will only answer questions on github issues and reject other forms of questions.</p> +<p>（记得提前配置好树莓派和所有板子之间的ssh public key，方便免密登录）</p> </blockquote> -<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> -<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs clone +</span></span></code></pre></div><h2 id="3-拉取最新的软件代码并同步到远程板子上">3. 拉取最新的软件代码并同步到远程板子上</h2> +<blockquote> +<p>默认时master分支，如果需要指定分支，需要修改batch.mjs文件中的pull()函数，具体参考注释的部分</p> +</blockquote> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// pull all the latest code +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">pull</span> <span class="o">=</span> <span class="kr">async</span> <span class="p">()</span> <span class="p">=></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"><span class="nx">cd</span><span class="p">(</span><span class="sb">`</span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="p">()</span><span class="si">}</span><span class="sb">/repos`</span><span class="p">)</span> +</span></span><span class="line"><span class="cl"><span class="c1">// 如果需要指定分支，类似下面指定qbv-test分支的操作 +</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd pkt_gen_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` +</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd time_sync_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"><span class="kr">await</span> <span class="nb">Promise</span><span class="p">.</span><span class="nx">all</span><span class="p">(</span><span class="nx">hosts</span><span class="p">.</span><span class="nx">all</span><span class="p">.</span><span class="nx">map</span><span class="p">(</span><span class="nx">host</span> <span class="p">=></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="kr">const</span> <span class="nx">type</span> <span class="o">=</span> <span class="nx">hosts</span><span class="p">.</span><span class="nx">device</span><span class="p">.</span><span class="nx">includes</span><span class="p">(</span><span class="nx">host</span><span class="p">)</span> <span class="o">?</span> <span class="s1">'device'</span> <span class="o">:</span> <span class="s1">'switch'</span> +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'device'</span><span class="p">)</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/pkt_gen_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/`</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> <span class="k">else</span> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'switch'</span><span class="p">)</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/time_sync_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/;`</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"><span class="p">}))</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><p>同步到所有板子上：</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs pull +</span></span></code></pre></div><h2 id="4-使远程所有板子编译代码">4. 使远程所有板子编译代码</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs build +</span></span></code></pre></div><h2 id="5-将配置文件下发到所有板子上">5. 将配置文件下发到所有板子上</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs distribute +</span></span></code></pre></div><h2 id="6-开始启动所有板子的程序">6. 开始启动所有板子的程序</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs launch +</span></span></code></pre></div><h2 id="7-收集延迟和抖动的统计信息">7. 收集延迟和抖动的统计信息</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs collect +</span></span></code></pre></div> +- +
+ +📕 ZIGGO Device使用手册 + http://localhost:1313/device/ziggo_device_manual/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/ziggo_device_manual/ +<p>There are two analysis methods for ZIGGO Device:</p> +<blockquote> +<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +</blockquote> +<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> +<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> +<p>Example of <code>packet_log.csv</code>:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency +</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 +</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 +</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 +</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 +</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 +</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 +</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 +</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 +</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 +</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 +</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance +</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 +</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 +</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 +</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 +</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 +</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 +</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 +</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 +</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 +</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 +</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 +</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 +</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> +<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> +<p>Example of packet capture command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng +</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> +<p>Code for analyzing programs is <code>analyze_packet.py</code></p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> +</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> + +- +
@@ -315,371 +504,51 @@ <li>Compile the device tree</li> </ol> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">petalinux-build -c device-tree -</span></span></code></pre></div><ol start="6"> -<li>Modify the device tree</li> -</ol> -<p>The generated device tree is located in <code>components/plnx_workspace/device tree/device tree/pl.dtsi</code> directory, we need to make modifications based on this file to meet some of our peripheral needs. The modified files are stored in the <code>project-spec/meta user/recipes bsp/device tree/files/system-user.dtsi</code> directory.</p> -<blockquote> -<p>Note: Between the <code>//>>></code> and <code>//<<<</code> is the content added between the comments.</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C" data-lang="C"><span class="line"><span class="cl"><span class="o">/</span><span class="n">include</span><span class="o">/</span> <span class="s">"system-conf.dtsi"</span> -</span></span><span class="line"><span class="cl"><span class="o">/</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nl">amba_pl</span><span class="p">:</span> <span class="n">amba_pl</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">dma_proxy</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span><span class="s">"xlnx,dma_proxy"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">dmas</span> <span class="o">=</span> <span class="o"><&</span><span class="n">axi_dma_0</span> <span class="mi">0</span> <span class="o">&</span><span class="n">axi_dma_0</span> <span class="mi">1</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">dma</span><span class="o">-</span><span class="n">names</span> <span class="o">=</span> <span class="s">"dma_proxy_tx"</span><span class="p">,</span> <span class="s">"dma_proxy_rx"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="nl">pkt_gen_controller_0</span><span class="p">:</span> <span class="n">pkt_gen_controller</span><span class="err">@</span><span class="mi">43</span><span class="n">c00000</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c00000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="nl">rtc0</span><span class="p">:</span> <span class="n">time_sync_uio</span><span class="err">@</span><span class="mi">43</span><span class="n">c10000</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c10000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"> <span class="n">chosen</span><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">bootargs</span> <span class="o">=</span> <span class="s">"console=ttyPS0,115200 earlyprintk cma=256M uio_pdrv_genirq.of_id=generic-uio root=/dev/mmcblk0p2 rw rootwait"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">stdout</span><span class="o">-</span><span class="n">path</span> <span class="o">=</span> <span class="s">"serial0:115200n8"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"><span class="p">};</span> -</span></span><span class="line"><span class="cl"><span class="o">&</span><span class="n">gem1</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">local</span><span class="o">-</span><span class="n">mac</span><span class="o">-</span><span class="n">address</span> <span class="o">=</span> <span class="p">[</span><span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">02</span> <span class="mo">01</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">phy</span><span class="o">-</span><span class="n">mode</span> <span class="o">=</span> <span class="s">"gmii"</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">fixed</span><span class="o">-</span><span class="n">link</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="n">speed</span> <span class="o">=</span> <span class="o"><</span><span class="mi">1000</span><span class="o">></span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="n">full</span><span class="o">-</span><span class="n">duplex</span><span class="p">;</span> -</span></span><span class="line"><span class="cl"> <span class="p">};</span> -</span></span><span class="line"><span class="cl"><span class="p">};</span> -</span></span></code></pre></div><ol start="7"> -<li>Complie</li> -</ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-build -</span></span></code></pre></div><ol start="8"> -<li>Pack</li> -</ol> -<p>Here, you need to copy the bitstream file generated by Vivado to the virtual machine. (You can export bitstream file to where you want).</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./export_bitstream.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>Then:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">cd</span> images/linux -</span></span><span class="line"><span class="cl">petalinux-package --boot --fsbl zynq_fsbl.elf --fpga <FPGA bitstream path> --u-boot --force -</span></span></code></pre></div><p>After that, you can get 4 key file: <code>BOOT.BIN</code> <code>boot.scr</code> <code>image.ub</code> <code>rootfs.tar.gz</code></p> -<h3 id="6-sd-card-partition-and-copy-file">6. SD card partition and copy file</h3> -<h4 id="file-downloading">File downloading</h4> -<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/0bbc00543e5b4b82a6ea/" target="_blank" rel="noopener">this</a> public link or from preceding steps:</p> -<ul> -<li>BOOT.BIN</li> -<li>boot.scr</li> -<li>image.ub</li> -<li>rootfs.tar.gz</li> -</ul> -<h4 id="sd-card-partition">SD card partition</h4> -<p>In order to boot the TSNPerf, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted -</span></span><span class="line"><span class="cl">sudo gparted -</span></span></code></pre></div><p>Parition it into two partition below</p> -<ul> -<li> -<p>BOOT: store boot files from petalinux</p> -<p>Free space preceding (MiB): 4</p> -<p>New size (MiB): 500</p> -<p>File system: fat32</p> -<p>Label: BOOT</p> -</li> -<li> -<p>ROOTFS: store debian system rootfs</p> -<p>Free space preceding (MiB): 0</p> -<p>Free space following (MiB): 0</p> -<p>File system: ext4</p> -<p>Label: ROOTFS</p> -</li> -</ul> -<h4 id="copy-files-into-sd-card">Copy files into SD card</h4> -<p>Mound SD card:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ -</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ -</span></span></code></pre></div><p>Remove original files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* -</span></span></code></pre></div><p>Copy files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh -</span></span><span class="line"><span class="cl">sync -</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS -</span></span></code></pre></div><h2 id="launch-the-board-and-log-in">Launch the Board and log in</h2> -<h3 id="1-launch-the-board">1. Launch the Board</h3> -<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<h3 id="2-initialize-ps">2. Initialize PS</h3> -<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> -<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>The default username and password are as follows:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> -</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> -</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment. (<code>hardware/init_os.sh</code>)</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh -</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> -<h3 id="3-connect-to-internet">3. Connect to Internet</h3> -<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> -<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> -<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> -<h3 id="4-run-the-software">4. Run the Software</h3> -<p>Please refer to the software part of this repo for further instructions.</p> - - - -💦 Software:Time Sync + Config for CaaS Device + http://localhost:1313/device/software-build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/software-build/ +<p>This repo contains source code to enable TSN/CaaS TSNPerf’ time synchronization logic and set up packet generation plan.</p> +<h2 id="table-of-content">Table of Content</h2> <ul> -<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> -<li>Bug fixes are always welcome.</li> -<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> -<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> -<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> -<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> -<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> +<li><a href="#table-of-content">Table of Content</a></li> +<li><a href="#1-build">1. Build</a></li> +<li><a href="#2-config">2. Config</a></li> +<li><a href="#3-run">3. Run</a></li> +<li><a href="#4-analyze">4. Analyze</a> +<ul> +<li><a href="#41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</a></li> +<li><a href="#42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</a></li> +</ul> +</li> +</ul> +<h2 id="1-build">1. Build</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build +</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build +</span></span><span class="line"><span class="cl">cmake .. +</span></span><span class="line"><span class="cl">make +</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync” & “pkt_gen”</p> +<h2 id="2-config">2. Config</h2> +<p>The “build” directory contains topology & TSN/CaaS schedule results.</p> +<ul> +<li>config.json: topology file, contains node info (type, mac, ptp ports), link between nodes (with ports), and forwarding table.</li> +<li>schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</li> +</ul> +<p>(Hints: This is similar to a Ziggo Switch)</p> +<h2 id="3-run">3. Run</h2> +<ul> +<li>Start time syncronization</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./time_sync +</span></span></code></pre></div><ul> +<li>Start device critical packet generation</li> </ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./pkt_gen +</span></span></code></pre></div><h2 id="4-analyze">4. Analyze</h2> +<p>There are two analysis methods for TSNPerf:</p> +<blockquote> +<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +</blockquote> +<p>One method is to directly analyze latency and jitter on the TSNPerf.</p> +<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<h3 id="41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</h3> +<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> +<p>You can display the content of the header and the last 5 lines using the following command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 +</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 +</span></span></code></pre></div><h3 id="42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</h3> +<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> +<p>Example of packet capture command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng +</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> +<p>Code for analyzing programs is <code>analyze_packet.py</code></p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> +</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> - -
- -👩🏼🏫 准备清单 - http://localhost:1313/device/require/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/require/ -<h2 id="软件环境清单">软件环境清单</h2> -<h3 id="vivada-开发环境">Vivada 开发环境</h3> -<p>Vivado 是开发板的硬件开发程序。</p> -<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> -<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> -<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> -<h3 id="mobaxterm">MobaXterm</h3> -<p>MobaXterm是串口连接工具，我们在<a href="./hardware_build.md">hardware_build.md</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> -<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> -<h2 id="硬件准备清单">硬件准备清单</h2> -<h3 id="alinx7021开发板">Alinx7021开发板</h3> -<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> -<h3 id="sd启动卡">SD启动卡</h3> -<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> -<h3 id="必要的线材">必要的线材</h3> -<p>包括网线、数据线等。</p> -<h3 id="普通交换机">普通交换机</h3> -<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> - -- -
- -👩🏼🏫 准备清单 - http://localhost:1313/switch/require/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/require/ -<h2 id="软件环境清单">软件环境清单</h2> -<h3 id="vivada-开发环境">Vivada 开发环境</h3> -<p>Vivado 是开发板的硬件开发程序。</p> -<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> -<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> -<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> -<h3 id="mobaxterm">MobaXterm</h3> -<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> -<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> -<h2 id="硬件准备清单">硬件准备清单</h2> -<h3 id="alinx7021开发板">Alinx7021开发板</h3> -<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> -<h3 id="sd启动卡">SD启动卡</h3> -<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> -<h3 id="必要的线材">必要的线材</h3> -<p>包括网线、数据线等。</p> -<h3 id="普通交换机">普通交换机</h3> -<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> - -- -
- -💦 Software:Time Sync + Config for CaaS Device - http://localhost:1313/device/software-build/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/software-build/ -<p>This repo contains source code to enable TSN/CaaS TSNPerf’ time synchronization logic and set up packet generation plan.</p> -<h2 id="table-of-content">Table of Content</h2> -<ul> -<li><a href="#table-of-content">Table of Content</a></li> -<li><a href="#1-build">1. Build</a></li> -<li><a href="#2-config">2. Config</a></li> -<li><a href="#3-run">3. Run</a></li> -<li><a href="#4-analyze">4. Analyze</a> -<ul> -<li><a href="#41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</a></li> -<li><a href="#42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</a></li> -</ul> -</li> -</ul> -<h2 id="1-build">1. Build</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build -</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build -</span></span><span class="line"><span class="cl">cmake .. -</span></span><span class="line"><span class="cl">make -</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync” & “pkt_gen”</p> -<h2 id="2-config">2. Config</h2> -<p>The “build” directory contains topology & TSN/CaaS schedule results.</p> -<ul> -<li>config.json: topology file, contains node info (type, mac, ptp ports), link between nodes (with ports), and forwarding table.</li> -<li>schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</li> -</ul> -<p>(Hints: This is similar to a Ziggo Switch)</p> -<h2 id="3-run">3. Run</h2> -<ul> -<li>Start time syncronization</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./time_sync -</span></span></code></pre></div><ul> -<li>Start device critical packet generation</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./pkt_gen -</span></span></code></pre></div><h2 id="4-analyze">4. Analyze</h2> -<p>There are two analysis methods for TSNPerf:</p> -<blockquote> -<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> -</blockquote> -<p>One method is to directly analyze latency and jitter on the TSNPerf.</p> -<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> -<h3 id="41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</h3> -<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> -<p>You can display the content of the header and the last 5 lines using the following command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 -</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 -</span></span></code></pre></div><h3 id="42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</h3> -<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> -<p>Example of packet capture command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng -</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> -<p>Code for analyzing programs is <code>analyze_packet.py</code></p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> -</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> - -- -
- -📕 CNC脚本使用指南 - http://localhost:1313/device/cnc_manual/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/cnc_manual/ -<h2 id="1-运行脚本前在batchmjs中要配置好以下变量">1. 运行脚本前，在batch.mjs中要配置好以下变量：</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// IP address format: 192.168.137.* -</span></span></span><span class="line"><span class="cl"><span class="c1">// 测试数据 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">conf_default</span> <span class="o">=</span> <span class="s2">"<需要执行的配置名称>"</span> -</span></span><span class="line"><span class="cl"><span class="c1">// 时钟主节点 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">master</span> <span class="o">=</span> <span class="mi">40</span> -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"><span class="kr">const</span> <span class="nx">hosts</span> <span class="o">=</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nx">device</span><span class="o">:</span> <span class="p">[</span><span class="mi">43</span><span class="p">,</span> <span class="mi">44</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="k">switch</span><span class="o">:</span> <span class="p">[</span><span class="mi">40</span><span class="p">,</span> <span class="mi">41</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">安装好需要的依赖： -</span></span><span class="line"><span class="cl">```bash -</span></span><span class="line"><span class="cl">sudo npm install -g zx@4.3.0 -</span></span><span class="line"><span class="cl">pip install -r requirements.txt -</span></span><span class="line"><span class="cl">npm install -</span></span></code></pre></div><p>配置好环境变量，在.bashrc中加入：</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">export</span> <span class="nv">PYTHONPATH</span><span class="o">=</span><span class="s2">"/home/<用户名>/scripts"</span> -</span></span></code></pre></div><h2 id="2-下载好switch和tsnperf的软件代码">2. 下载好Switch和TSNPerf的软件代码</h2> -<blockquote> -<p>（记得提前配置好树莓派和所有板子之间的ssh public key，方便免密登录）</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs clone -</span></span></code></pre></div><h2 id="3-拉取最新的软件代码并同步到远程板子上">3. 拉取最新的软件代码并同步到远程板子上</h2> -<blockquote> -<p>默认时master分支，如果需要指定分支，需要修改batch.mjs文件中的pull()函数，具体参考注释的部分</p> -</blockquote> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-javascript" data-lang="javascript"><span class="line"><span class="cl"><span class="c1">// pull all the latest code -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="kr">const</span> <span class="nx">pull</span> <span class="o">=</span> <span class="kr">async</span> <span class="p">()</span> <span class="p">=></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"><span class="nx">cd</span><span class="p">(</span><span class="sb">`</span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="p">()</span><span class="si">}</span><span class="sb">/repos`</span><span class="p">)</span> -</span></span><span class="line"><span class="cl"><span class="c1">// 如果需要指定分支，类似下面指定qbv-test分支的操作 -</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd pkt_gen_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` -</span></span></span><span class="line"><span class="cl"><span class="c1">// await $`cd time_sync_app; git stash; git checkout qbv-test; git pull origin qbv-test; cd ..` -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"><span class="kr">await</span> <span class="nb">Promise</span><span class="p">.</span><span class="nx">all</span><span class="p">(</span><span class="nx">hosts</span><span class="p">.</span><span class="nx">all</span><span class="p">.</span><span class="nx">map</span><span class="p">(</span><span class="nx">host</span> <span class="p">=></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="kr">const</span> <span class="nx">type</span> <span class="o">=</span> <span class="nx">hosts</span><span class="p">.</span><span class="nx">device</span><span class="p">.</span><span class="nx">includes</span><span class="p">(</span><span class="nx">host</span><span class="p">)</span> <span class="o">?</span> <span class="s1">'device'</span> <span class="o">:</span> <span class="s1">'switch'</span> -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'device'</span><span class="p">)</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/pkt_gen_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/`</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> <span class="k">else</span> <span class="k">if</span> <span class="p">(</span><span class="nx">type</span> <span class="o">===</span> <span class="s1">'switch'</span><span class="p">)</span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="k">return</span> <span class="nx">$</span><span class="sb">`rsync -avPh </span><span class="si">${</span><span class="nx">os</span><span class="p">.</span><span class="nx">homedir</span><span class="si">}</span><span class="sb">/repos/time_sync_app root@192.168.137.</span><span class="si">${</span><span class="nx">host</span><span class="si">}</span><span class="sb">:~/;`</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"><span class="p">}))</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><p>同步到所有板子上：</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs pull -</span></span></code></pre></div><h2 id="4-使远程所有板子编译代码">4. 使远程所有板子编译代码</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs build -</span></span></code></pre></div><h2 id="5-将配置文件下发到所有板子上">5. 将配置文件下发到所有板子上</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs distribute -</span></span></code></pre></div><h2 id="6-开始启动所有板子的程序">6. 开始启动所有板子的程序</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs launch -</span></span></code></pre></div><h2 id="7-收集延迟和抖动的统计信息">7. 收集延迟和抖动的统计信息</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./batch.mjs collect -</span></span></code></pre></div> -- -
@@ -1108,6 +1026,32 @@ +📕 ZIGGO Device使用手册 - http://localhost:1313/device/ziggo_device_manual/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/ziggo_device_manual/ -<p>There are two analysis methods for ZIGGO Device:</p> +</span></span></code></pre></div><ol start="6"> +<li>Modify the device tree</li> +</ol> +<p>The generated device tree is located in <code>components/plnx_workspace/device tree/device tree/pl.dtsi</code> directory, we need to make modifications based on this file to meet some of our peripheral needs. The modified files are stored in the <code>project-spec/meta user/recipes bsp/device tree/files/system-user.dtsi</code> directory.</p> <blockquote> -<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +<p>Note: Between the <code>//>>></code> and <code>//<<<</code> is the content added between the comments.</p> </blockquote> -<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C" data-lang="C"><span class="line"><span class="cl"><span class="o">/</span><span class="n">include</span><span class="o">/</span> <span class="s">"system-conf.dtsi"</span> +</span></span><span class="line"><span class="cl"><span class="o">/</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nl">amba_pl</span><span class="p">:</span> <span class="n">amba_pl</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">dma_proxy</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span><span class="s">"xlnx,dma_proxy"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">dmas</span> <span class="o">=</span> <span class="o"><&</span><span class="n">axi_dma_0</span> <span class="mi">0</span> <span class="o">&</span><span class="n">axi_dma_0</span> <span class="mi">1</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">dma</span><span class="o">-</span><span class="n">names</span> <span class="o">=</span> <span class="s">"dma_proxy_tx"</span><span class="p">,</span> <span class="s">"dma_proxy_rx"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="nl">pkt_gen_controller_0</span><span class="p">:</span> <span class="n">pkt_gen_controller</span><span class="err">@</span><span class="mi">43</span><span class="n">c00000</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c00000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="nl">rtc0</span><span class="p">:</span> <span class="n">time_sync_uio</span><span class="err">@</span><span class="mi">43</span><span class="n">c10000</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">compatible</span> <span class="o">=</span> <span class="s">"generic-uio"</span><span class="p">,</span><span class="s">"uio"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">reg</span> <span class="o">=</span> <span class="o"><</span><span class="mh">0x43c10000</span> <span class="mh">0x10000</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"> <span class="n">chosen</span><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">bootargs</span> <span class="o">=</span> <span class="s">"console=ttyPS0,115200 earlyprintk cma=256M uio_pdrv_genirq.of_id=generic-uio root=/dev/mmcblk0p2 rw rootwait"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">stdout</span><span class="o">-</span><span class="n">path</span> <span class="o">=</span> <span class="s">"serial0:115200n8"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"><span class="p">};</span> +</span></span><span class="line"><span class="cl"><span class="o">&</span><span class="n">gem1</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">local</span><span class="o">-</span><span class="n">mac</span><span class="o">-</span><span class="n">address</span> <span class="o">=</span> <span class="p">[</span><span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">00</span> <span class="mo">02</span> <span class="mo">01</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">phy</span><span class="o">-</span><span class="n">mode</span> <span class="o">=</span> <span class="s">"gmii"</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">fixed</span><span class="o">-</span><span class="n">link</span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="n">speed</span> <span class="o">=</span> <span class="o"><</span><span class="mi">1000</span><span class="o">></span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="n">full</span><span class="o">-</span><span class="n">duplex</span><span class="p">;</span> +</span></span><span class="line"><span class="cl"> <span class="p">};</span> +</span></span><span class="line"><span class="cl"><span class="p">};</span> +</span></span></code></pre></div><ol start="7"> +<li>Complie</li> +</ol> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">petalinux-build +</span></span></code></pre></div><ol start="8"> +<li>Pack</li> +</ol> +<p>Here, you need to copy the bitstream file generated by Vivado to the virtual machine. (You can export bitstream file to where you want).</p> <p> @@ -698,10 +567,60 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./export_bitstream.png" alt="" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<p>Then:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">cd</span> images/linux +</span></span><span class="line"><span class="cl">petalinux-package --boot --fsbl zynq_fsbl.elf --fpga <FPGA bitstream path> --u-boot --force +</span></span></code></pre></div><p>After that, you can get 4 key file: <code>BOOT.BIN</code> <code>boot.scr</code> <code>image.ub</code> <code>rootfs.tar.gz</code></p> +<h3 id="6-sd-card-partition-and-copy-file">6. SD card partition and copy file</h3> +<h4 id="file-downloading">File downloading</h4> +<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/0bbc00543e5b4b82a6ea/" target="_blank" rel="noopener">this</a> public link or from preceding steps:</p> +<ul> +<li>BOOT.BIN</li> +<li>boot.scr</li> +<li>image.ub</li> +<li>rootfs.tar.gz</li> +</ul> +<h4 id="sd-card-partition">SD card partition</h4> +<p>In order to boot the TSNPerf, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted +</span></span><span class="line"><span class="cl">sudo gparted +</span></span></code></pre></div><p>Parition it into two partition below</p> +<ul> +<li> +<p>BOOT: store boot files from petalinux</p> +<p>Free space preceding (MiB): 4</p> +<p>New size (MiB): 500</p> +<p>File system: fat32</p> +<p>Label: BOOT</p> +</li> +<li> +<p>ROOTFS: store debian system rootfs</p> +<p>Free space preceding (MiB): 0</p> +<p>Free space following (MiB): 0</p> +<p>File system: ext4</p> +<p>Label: ROOTFS</p> +</li> +</ul> +<h4 id="copy-files-into-sd-card">Copy files into SD card</h4> +<p>Mound SD card:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ +</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ +</span></span></code></pre></div><p>Remove original files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* +</span></span></code></pre></div><p>Copy files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh +</span></span><span class="line"><span class="cl">sync +</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS +</span></span></code></pre></div><h2 id="launch-the-board-and-log-in">Launch the Board and log in</h2> +<h3 id="1-launch-the-board">1. Launch the Board</h3> +<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> <p> @@ -720,46 +639,45 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> </div></figure> </p> -<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> -<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> -<p>Example of <code>packet_log.csv</code>:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency -</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 -</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 -</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 -</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 -</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 -</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 -</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 -</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 -</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 -</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 -</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance -</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 -</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 -</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 -</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 -</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 -</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 -</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 -</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 -</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 -</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 -</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 -</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 -</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> -<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> -<p>Example of packet capture command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng -</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> -<p>Code for analyzing programs is <code>analyze_packet.py</code></p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> -</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> +<h3 id="2-initialize-ps">2. Initialize PS</h3> +<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> +<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>The default username and password are as follows:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> +</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> +</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment. (<code>hardware/init_os.sh</code>)</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh +</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> +<h3 id="3-connect-to-internet">3. Connect to Internet</h3> +<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> +<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> +<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> +<h3 id="4-run-the-software">4. Run the Software</h3> +<p>Please refer to the software part of this repo for further instructions.</p> - +
+👩🏼🏫 准备清单 + http://localhost:1313/device/require/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/require/ +<h2 id="软件环境清单">软件环境清单</h2> +<h3 id="vivada-开发环境">Vivada 开发环境</h3> +<p>Vivado 是开发板的硬件开发程序。</p> +<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> +<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> +<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> +<h3 id="mobaxterm">MobaXterm</h3> +<p>MobaXterm是串口连接工具，我们在<a href="./hardware_build.md">hardware_build.md</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> +<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> +<h2 id="硬件准备清单">硬件准备清单</h2> +<h3 id="alinx7021开发板">Alinx7021开发板</h3> +<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> +<h3 id="sd启动卡">SD启动卡</h3> +<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> +<h3 id="必要的线材">必要的线材</h3> +<p>包括网线、数据线等。</p> +<h3 id="普通交换机">普通交换机</h3> +<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> + +🧠 基础知识列表 http://localhost:1313/device/basic_knowledge/ @@ -1136,6 +1080,36 @@- +
+🎉 How to contribute + http://localhost:1313/switch/contributing/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/contributing/ +<h2 id="reporting-a-bug">Reporting a bug</h2> +<p>File bugs in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a>. Please follow these guidelines:</p> +<ul> +<li>Search existing issues first, make sure yours hasn’t already been reported.</li> +<li>Consider enabling debug mode so that you can provide as much details as possible when reporting the issue.</li> +<li>Stay on topic, but describe the issue in detail so that others can <strong>reproduce</strong> it.</li> +<li><strong>Provide a screenshot</strong> if possible. A screenshot showing the problem is often more useful than a paragraph describing it.</li> +</ul> +<blockquote> +<p>The development team will only answer questions on github issues and reject other forms of questions.</p> +</blockquote> +<h2 id="contributing-to-ziggos-code">Contributing to ZIGGO’s code</h2> +<p>If you want to start contributing to the project’s code, please follow these guidelines before creating a pull request:</p> +<ul> +<li>The top post of the pull request should contain a full, self-contained explanation of the feature: what it does, how it does it, with examples of usage and screenshots. Also explain why you want to add this - what problem does it solve. Do not simply add a text <code>Implement feature #4345</code> , because the information there will most likely be outdated or confusing (multiple discussions and opinions). The pull request needs to be self-contained.</li> +<li>Bug fixes are always welcome.</li> +<li>A good way to easily start contributing is to pick and work on a good first issue. We try to make these issues as clear as possible and provide basic info on how the code should be changed, and if something is unclear feel free to ask for more information on the issue.</li> +<li>Before adding a new feature, ask about it in the <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch/issues" target="_blank" rel="noopener">Github Issue Tracker</a> , or check if existing discussions exist to make sure the new functionality is desired.</li> +<li>Pull requests that make many changes using an automated tool, like for spell fixing, styling, etc. will not be accepted.</li> +<li>Pull requests that address multiple issues will most likely stall and eventually be closed. This is because we might be fine with one of the changes but not with others and untangling that kind of pull request is too much hassle both for maintainers and the person who submitted it. So most of the time someone gives up and the PR gets closed. So please keep the pull request focused on one issue.</li> +<li><strong>Do not mark your reviewer’s comments as “resolved”</strong>. If you do that, the comments will be hidden and the reviewer will not know what are the pending issues in the pull request. Only the reviewer should resolve the comments.</li> +</ul> + +🧠 基础知识列表 http://localhost:1313/switch/basic_knowledge/ @@ -1161,6 +1135,32 @@ <li>tcl脚本</li> <li>良好的英语阅读基础</li> </ul> + +- +
diff --git a/public/tag/ziggo-device/page/2/index.html b/public/tag/ziggo-device/page/2/index.html index 4ce6154..6e5bd18 100644 --- a/public/tag/ziggo-device/page/2/index.html +++ b/public/tag/ziggo-device/page/2/index.html @@ -1,6 +1,6 @@ - @@ -4162,19 +4162,19 @@👩🏼🏫 准备清单 + http://localhost:1313/switch/require/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/require/ +<h2 id="软件环境清单">软件环境清单</h2> +<h3 id="vivada-开发环境">Vivada 开发环境</h3> +<p>Vivado 是开发板的硬件开发程序。</p> +<p>Vivado 软件的 Xilinx 官方下载地址： <a href="http://china.xilinx.com/support/download.html" target="_blank" rel="noopener">http://china.xilinx.com/support/download.html</a></p> +<p>本开发团队使用的是Vivado <em><strong>2020.1</strong></em>版本，我们建议ZIGGO项目使用者也使用相同版本以免一些不必要的麻烦。</p> +<p>具体的安装流程可以参照 <a href="https://cloud.tsinghua.edu.cn/f/f9f1a4f92a344e8e9c2c/" target="_blank" rel="noopener">ZYNQ应用教程</a> <strong>第三章Vivado开发环境</strong> 进行安装。</p> +<h3 id="mobaxterm">MobaXterm</h3> +<p>MobaXterm是串口连接工具，我们在<a href="http://localhost:1313/switch/hardware-build/">hardware-build</a>中“Launch the Board and log in”这一章节进行了使用介绍。</p> +<p>MobaXterm的官方下载地址：<a href="https://mobaxterm.mobatek.net/download.html" target="_blank" rel="noopener">MobaXterm Xserver with SSH, telnet, RDP, VNC and X11 - Download (mobatek.net)</a></p> +<h2 id="硬件准备清单">硬件准备清单</h2> +<h3 id="alinx7021开发板">Alinx7021开发板</h3> +<img src="./alinx7021.png" alt="Alinx" style="zoom:50%;" /> +<h3 id="sd启动卡">SD启动卡</h3> +<p>SD启动卡中存储着操作系统，建议容量 $\geq$ 32G。</p> +<h3 id="必要的线材">必要的线材</h3> +<p>包括网线、数据线等。</p> +<h3 id="普通交换机">普通交换机</h3> +<p>如果使用的开发板数量较多，可以考虑将所有开发板连接到普通交换机再通过普通交换机连接至PC（通过网线）进行管理和使用。</p> ZIGGO-Device
- +diff --git a/public/tag/ziggo-switch/index.html b/public/tag/ziggo-switch/index.html index b922eb5..e8668de 100644 --- a/public/tag/ziggo-switch/index.html +++ b/public/tag/ziggo-switch/index.html @@ -1,6 +1,6 @@ - @@ -4218,17 +4218,17 @@-
+
-🎉 How to contribute+📕 CNC脚本使用指南- How to report a bug or contribute to ZIGGO's code
+ 使用CNC脚本运行ZIGGO系统的7步指南May 1, 2024
ZIGGO-SWITCH
- +-
+
-💦 互联互通测试TestBed搭建流程+💦 Software:Time Sync + Config for CaaS SwitchesDocs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
May 1, 2024
@@ -4246,17 +4246,17 @@ZIGGO-SWITCH
- +-
+
-💦 Software:Time Sync + Config for CaaS Switches+💦 互联互通测试TestBed搭建流程Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
May 1, 2024
diff --git a/public/tag/ziggo-switch/index.xml b/public/tag/ziggo-switch/index.xml index 4154d52..d2cf68f 100644 --- a/public/tag/ziggo-switch/index.xml +++ b/public/tag/ziggo-switch/index.xml @@ -12,229 +12,6 @@ http://localhost:1313/tag/ziggo-switch/ -- -
-💦 Software:Time Sync + Config for CaaS Switches - http://localhost:1313/switch/software_build/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/software_build/ -<p>This repo contains source code to enable CaaS Switches’ time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).</p> -<h2 id="build">Build</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build -</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build -</span></span><span class="line"><span class="cl">cmake .. -</span></span><span class="line"><span class="cl">make -</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync_app” & “switch_config”</p> -<h2 id="config">Config</h2> -<p>The “config” directory contains topology & TSN/CaaS schedule results.</p> -<p>This document takes the following topology as an example to give example configurations:</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./example_topology.png" alt="topology" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<ul> -<li> -<p>***-config.json: Mainly describes the network’s topology, including the type of each node (device or switch), MAC address, PTP port status, and other node information, topology information, and MAC forwarding table. Example and explanation are as follows (note that the comments in the file are just for explanation, do not have such comments in actual use):</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Used to describe the information of each node in the network -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">3</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Node's PTP port status -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// The quintuple represents the clock status of [local, ETH1, ETH2, ETH3, ETH4] -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Number meaning: (0: MASTER, 1: SLAVE, 2: PASSIVE, 3: DISABLED) -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 1, it means that the node is the master clock node; -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 0, it means that the node is the slave clock node. -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:14"</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:15"</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Topology information, composed of each link, each link is a directed edge -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// link ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Port number of the source node -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// port 0,1,2,3 correspond to ETH1,2,3,4 in reality -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Port number of the destination node -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">2</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Forwarding table, which can be generated by the scheduling algorithm in CNC -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// In the forwarding table where you send to yourself, the port is 4 (caas) / 5 (PS ETH for new hardware) -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Current node ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Output port number -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Entry ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Destination node ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><p>If the master clock selection algorithm is used, only the configuration of nodes is different, and the rest are the same. The newly added <code>externalPortConfigurationEnabled</code> and <code>system_identity</code> fields are optional items, as shown in the example below:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:00:00:00:02:01"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"externalPortConfigurationEnabled"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> <span class="c1">// 1: Manually configure the master-slave relationship, 0: Configure the master-slave relationship through the master clock selection algorithm, if this item is not written, the default is 0, that is, configure the master-slave relationship through the master clock selection -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"system_identity"</span><span class="p">:</span> <span class="p">{</span> <span class="c1">// Clock node's clock parameters, used for comparison in the master clock selection algorithm, if this item is not written, the default is the configuration written below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority1"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// First priority -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockClass"</span><span class="p">:</span> <span class="mi">248</span><span class="p">,</span> <span class="c1">// Clock level -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockAccuracy"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// Clock accuracy -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"offsetScaledLogVariance"</span><span class="p">:</span> <span class="mi">17258</span><span class="p">,</span> <span class="c1">// Clock variance -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority2"</span><span class="p">:</span> <span class="mi">247</span><span class="p">,</span> <span class="c1">// Second priority -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clock_identity"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">]</span> <span class="c1">// Clock identifier, different clocks should have different parameters -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div></li> -<li> -<p>***-schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span><span class="c1">// All switches need to be listed to facilitate software recognition of configuration information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Can be empty, not used -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> <span class="c1">// Type is link, used to describe scheduling information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Output port number -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Scheduling information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> <span class="c1">// Scheduling cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Start time relative to the entire cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">5</span><span class="p">,</span> <span class="c1">// End time relative to the entire cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Job ID in CaaS, if not needed, it can be omitted -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Data stream ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">6</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">1500</span> <span class="c1">// Packet length, if not written, the default is 1500B, this item only exists on the path from Device to Switch -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"><span class="p">]</span> -</span></span></code></pre></div></li> -</ul> -<h2 id="run">Run</h2> -<ul> -<li>Copy topology & schedule file to build dir:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-config.json build/config.json -</span></span><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-schedule.json build/schedule.json -</span></span></code></pre></div><ul> -<li>Start time synchronization and initialize GCL and MAC forwarding table according to the configuration (it is recommended to run the time synchronization program on a core (with <code>taskset -c 1</code> command) to prevent kernel errors and crashes due to time synchronization):</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -</span></span></code></pre></div><ul> -<li>The log output level is categorized into three types: WARN, INFO, and TRACE. The default log output level is TRACE (the most comprehensive output information, including DEBUG logs). The log output level can be set with the -l parameter:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l w <span class="c1"># WARN level</span> -</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l i <span class="c1"># INFO level</span> -</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l t <span class="c1"># TRACE level</span> -</span></span></code></pre></div><p><em>Notice that the time sync logic is supposed to run indefinitely as the node should sync to its neighbors again and again.</em></p> -<ul> -<li>Update GCL & switch forwarding rules:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./switch_config -</span></span></code></pre></div> -💦 互联互通测试TestBed搭建流程 http://localhost:1313/device/testbed/ @@ -533,6 +310,229 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙，- +
+💦 Software:Time Sync + Config for CaaS Switches + http://localhost:1313/switch/software_build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/software_build/ +<p>This repo contains source code to enable CaaS Switches’ time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).</p> +<h2 id="build">Build</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build +</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build +</span></span><span class="line"><span class="cl">cmake .. +</span></span><span class="line"><span class="cl">make +</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync_app” & “switch_config”</p> +<h2 id="config">Config</h2> +<p>The “config” directory contains topology & TSN/CaaS schedule results.</p> +<p>This document takes the following topology as an example to give example configurations:</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./example_topology.png" alt="topology" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<ul> +<li> +<p>***-config.json: Mainly describes the network’s topology, including the type of each node (device or switch), MAC address, PTP port status, and other node information, topology information, and MAC forwarding table. Example and explanation are as follows (note that the comments in the file are just for explanation, do not have such comments in actual use):</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Used to describe the information of each node in the network +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">3</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Node's PTP port status +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// The quintuple represents the clock status of [local, ETH1, ETH2, ETH3, ETH4] +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Number meaning: (0: MASTER, 1: SLAVE, 2: PASSIVE, 3: DISABLED) +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 1, it means that the node is the master clock node; +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 0, it means that the node is the slave clock node. +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:14"</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:15"</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Topology information, composed of each link, each link is a directed edge +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// link ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Port number of the source node +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// port 0,1,2,3 correspond to ETH1,2,3,4 in reality +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Port number of the destination node +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">2</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Forwarding table, which can be generated by the scheduling algorithm in CNC +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// In the forwarding table where you send to yourself, the port is 4 (caas) / 5 (PS ETH for new hardware) +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Current node ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Output port number +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Entry ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Destination node ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><p>If the master clock selection algorithm is used, only the configuration of nodes is different, and the rest are the same. The newly added <code>externalPortConfigurationEnabled</code> and <code>system_identity</code> fields are optional items, as shown in the example below:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:00:00:00:02:01"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"externalPortConfigurationEnabled"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> <span class="c1">// 1: Manually configure the master-slave relationship, 0: Configure the master-slave relationship through the master clock selection algorithm, if this item is not written, the default is 0, that is, configure the master-slave relationship through the master clock selection +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"system_identity"</span><span class="p">:</span> <span class="p">{</span> <span class="c1">// Clock node's clock parameters, used for comparison in the master clock selection algorithm, if this item is not written, the default is the configuration written below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority1"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// First priority +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockClass"</span><span class="p">:</span> <span class="mi">248</span><span class="p">,</span> <span class="c1">// Clock level +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockAccuracy"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// Clock accuracy +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"offsetScaledLogVariance"</span><span class="p">:</span> <span class="mi">17258</span><span class="p">,</span> <span class="c1">// Clock variance +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority2"</span><span class="p">:</span> <span class="mi">247</span><span class="p">,</span> <span class="c1">// Second priority +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clock_identity"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">]</span> <span class="c1">// Clock identifier, different clocks should have different parameters +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div></li> +<li> +<p>***-schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span><span class="c1">// All switches need to be listed to facilitate software recognition of configuration information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Can be empty, not used +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> <span class="c1">// Type is link, used to describe scheduling information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Output port number +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Scheduling information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> <span class="c1">// Scheduling cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Start time relative to the entire cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">5</span><span class="p">,</span> <span class="c1">// End time relative to the entire cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Job ID in CaaS, if not needed, it can be omitted +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Data stream ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">6</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">1500</span> <span class="c1">// Packet length, if not written, the default is 1500B, this item only exists on the path from Device to Switch +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"><span class="p">]</span> +</span></span></code></pre></div></li> +</ul> +<h2 id="run">Run</h2> +<ul> +<li>Copy topology & schedule file to build dir:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-config.json build/config.json +</span></span><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-schedule.json build/schedule.json +</span></span></code></pre></div><ul> +<li>Start time synchronization and initialize GCL and MAC forwarding table according to the configuration (it is recommended to run the time synchronization program on a core (with <code>taskset -c 1</code> command) to prevent kernel errors and crashes due to time synchronization):</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync +</span></span></code></pre></div><ul> +<li>The log output level is categorized into three types: WARN, INFO, and TRACE. The default log output level is TRACE (the most comprehensive output information, including DEBUG logs). The log output level can be set with the -l parameter:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l w <span class="c1"># WARN level</span> +</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l i <span class="c1"># INFO level</span> +</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l t <span class="c1"># TRACE level</span> +</span></span></code></pre></div><p><em>Notice that the time sync logic is supposed to run indefinitely as the node should sync to its neighbors again and again.</em></p> +<ul> +<li>Update GCL & switch forwarding rules:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./switch_config +</span></span></code></pre></div> +💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit http://localhost:1313/switch/hardware-build/ diff --git a/public/tag/ziggo/index.html b/public/tag/ziggo/index.html index bd144cc..1149ea4 100644 --- a/public/tag/ziggo/index.html +++ b/public/tag/ziggo/index.html @@ -1,6 +1,6 @@ - @@ -4162,19 +4162,19 @@ZIGGO
- +@@ -4190,19 +4190,19 @@-
+
-🔨 System Design —— PL & PS Co-operate+📈 TSNPerf 设计原理- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动May 1, 2024
ZIGGO
- +@@ -4218,19 +4218,19 @@-
+
🔨 System Design —— PL & PS Co-operate- ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
ZIGGO
- +@@ -4246,19 +4246,19 @@-
+
-📕 ZIGGO Device使用手册+💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation ToolkitMay 1, 2024
ZIGGO
- +@@ -4302,19 +4302,19 @@-
+
-📈 TSNPerf 设计原理+💦 Software:Time Sync + Config for CaaS Switches- TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
ZIGGO
- +@@ -4330,19 +4330,19 @@-
+
-💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit+🔨 System Design —— PL & PS Co-operate- Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit
+ ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ's both hardware and software programmability.May 1, 2024
ZIGGO
- +@@ -4358,17 +4358,17 @@-
+
-💦 互联互通测试TestBed搭建流程+💦 Software:Time Sync + Config for CaaS Device- Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
+ Docs to enable CaaS Device' time synchronization logic and set up pkt gen.May 1, 2024
ZIGGO
- +-
+
-💦 Software:Time Sync + Config for CaaS Switches+📕 ZIGGO Device使用手册Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).
May 1, 2024
@@ -4386,19 +4386,19 @@ZIGGO
- +@@ -4418,6 +4418,10 @@-
+
-💦 Software:Time Sync + Config for CaaS Device+💦 互联互通测试TestBed搭建流程- Docs to enable CaaS Device' time synchronization logic and set up pkt gen.
+ Docs to enable CaaS Switches' time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).May 1, 2024
ZIGGO
+ + +
+
☀ 某品牌交换机报告diff --git a/public/tag/ziggo/index.xml b/public/tag/ziggo/index.xml index 0a2d526..7d0c3ad 100644 --- a/public/tag/ziggo/index.xml +++ b/public/tag/ziggo/index.xml @@ -13,84 +13,151 @@- -
+ +💦 Software:Time Sync + Config for CaaS Device - http://localhost:1313/device/software-build/ +☀ 某品牌交换机报告 + http://localhost:1313/tsnperf/report/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/software-build/ -<p>This repo contains source code to enable TSN/CaaS TSNPerf’ time synchronization logic and set up packet generation plan.</p> -<h2 id="table-of-content">Table of Content</h2> + http://localhost:1313/tsnperf/report/ +<p>详细报告请查看<a href="http://localhost:1313/pdf/switch_report.pdf">这里</a>。</p> + +- +
- -💦 互联互通测试TestBed搭建流程 + http://localhost:1313/device/testbed/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/testbed/ +<h2 id="目录">目录</h2> <ul> -<li><a href="#table-of-content">Table of Content</a></li> -<li><a href="#1-build">1. Build</a></li> -<li><a href="#2-config">2. Config</a></li> -<li><a href="#3-run">3. Run</a></li> -<li><a href="#4-analyze">4. Analyze</a> +<li><a href="#%e7%9b%ae%e5%bd%95">目录</a></li> +<li><a href="#testbed%e7%ae%80%e5%8d%95%e4%bb%8b%e7%bb%8d">TestBed简单介绍</a></li> +<li><a href="#%e4%ba%92%e8%81%94%e4%ba%92%e9%80%9a%e6%b5%8b%e8%af%95%e9%a1%b9%e7%9b%ae%e4%bb%8b%e7%bb%8d">互联互通测试项目介绍</a> <ul> -<li><a href="#41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</a></li> -<li><a href="#42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</a></li> +<li><a href="#1-%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">1. 基准测试</a></li> +<li><a href="#2-%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">2. 门控能力</a></li> +<li><a href="#3-%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">3. 带宽保证</a></li> +<li><a href="#4-%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">4. 门控精度</a></li> +</ul> +</li> +<li><a href="#%e8%ae%be%e5%a4%87%e5%8f%82%e6%95%b0%e8%ae%be%e7%bd%ae%e4%b8%8e%e9%83%a8%e7%bd%b2">设备参数设置与部署</a></li> +<li><a href="#testbed%e8%bf%90%e8%a1%8c%e6%b5%81%e7%a8%8b">TestBed运行流程</a> +<ul> +<li><a href="#%e5%87%86%e5%a4%87%e5%b7%a5%e4%bd%9c">准备工作</a> +<ul> +<li><a href="#%e6%8e%a7%e5%88%b6%e8%84%9a%e6%9c%ac%e5%87%86%e5%a4%87">控制脚本准备</a></li> +<li><a href="#%e8%83%8c%e6%99%af%e6%b5%81%e9%87%8f%e5%8f%91%e9%80%81">背景流量发送</a></li> </ul> </li> +<li><a href="#%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">基准测试</a></li> +<li><a href="#%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">门控能力</a></li> +<li><a href="#%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">带宽保证</a></li> +<li><a href="#%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">门控精度</a></li> </ul> -<h2 id="1-build">1. Build</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build -</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build -</span></span><span class="line"><span class="cl">cmake .. -</span></span><span class="line"><span class="cl">make -</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync” & “pkt_gen”</p> -<h2 id="2-config">2. Config</h2> -<p>The “build” directory contains topology & TSN/CaaS schedule results.</p> +</li> +</ul> +<h2 id="testbed简单介绍">TestBed简单介绍</h2> +<p>我们内部对自己研发的CaaS-Switch进行了互联互通测试，采用的网络拓扑如下所示。</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./topo.PNG" alt="topo" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>本Demo需要4个FPGA开发板（2个TSNPerf、2个CaaS-Switch）和1台普通PC。如果条件有限/考虑简化拓扑，可以删去一个CaaS-Switch。PC负责发送背景流量，路径为黑色箭头；左侧TSNPerf负责发送测试流量（关键流量），路径为红色箭头。</p> +<p>所有测试项目的流程大致可以分为两个阶段：</p> +<ol> +<li> +<p>时间同步：启动时间同步，保证TSNPerf、CaaS-Switch在一个时钟域下。</p> +<p>注：时间同步程序运行在TSNPerf、CaaS-Switch的系统中。</p> +</li> +<li> +<p>发送测试流量：根据schedule.json文件，TSNPerf进行测试流量发送。</p> +</li> +</ol> +<h2 id="互联互通测试项目介绍">互联互通测试项目介绍</h2> +<h3 id="1-基准测试">1. 基准测试</h3> <ul> -<li>config.json: topology file, contains node info (type, mac, ptp ports), link between nodes (with ports), and forwarding table.</li> -<li>schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</li> +<li>目的：测试无背景流量情况下，高优先级流量的两跳端到端延迟、丢包率、抖动，作为比较基准。</li> +<li>预期：延迟符合规划，抖动较低（100ns左右）。</li> </ul> -<p>(Hints: This is similar to a Ziggo Switch)</p> -<h2 id="3-run">3. Run</h2> +<h3 id="2-门控能力">2. 门控能力</h3> <ul> -<li>Start time syncronization</li> +<li>目的：测试通用情况下流量调度效果，和两个交换机的门控对接能力。</li> +<li>方案： +背景流量（VLAN priority = 0）打到线速，每个调度周期预留长度为 3 的时隙给高优先级流量， +<ol> +<li>每个周期定时发送 4 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录端到端平均延迟、抖动、丢包率、到达顺序</li> +<li>每个周期定时发送 8 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过且仅 n 个包</li> +</ol> +</li> +<li>预期： +<ol> +<li>延迟、抖动、丢包率和基准一致</li> +<li>每个周期定时发送 4 个数据包时，丢包率为0</li> +<li>每个周期定时发送 8 个数据包时，每个周期通过且仅通过 5 个包（每8个包丢3个，因为每个时隙里恰好可以把第五个包发出去，余下三个包丢掉），丢包率为37.5%</li> +</ol> +</li> </ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./time_sync -</span></span></code></pre></div><ul> -<li>Start device critical packet generation</li> +<h3 id="3-带宽保证">3. 带宽保证</h3> +<ul> +<li>目的：测试交换机能够进行带宽预留，且两个交换机优先级映射、运行 cycle 和 offset 基本一致。</li> +<li>方案： +背景流量（VLAN priority = 0）打到线速（1Gbps），配置交换机预留 50% 时隙给高优先级流量（VLAN priority = 1），其余 50% 只允许低优先级流量， +<ol> +<li>测试流量高优先级（VLAN priority = 1）情况下打到线速（经测试，每个周期[33ms]连续发送2752个1500B的包，基本达到1000Mbps），记录端到端平均延迟、抖动、丢包率、到达顺序</li> +<li>测试流量高优先级（VLAN priority = 1）情况下打到50%线速（每个周期[33ms]连续发送1376个1500B的包），记录端到端平均延迟、抖动、丢包率、到达顺序</li> +</ol> +</li> +<li>预期： +<ol> +<li>高优先级测试流量100%线速：延迟、抖动和基准一致，丢包率 50% 左右</li> +<li>高优先级测试流量50%线速：延迟、抖动和基准一致，0丢包率</li> +</ol> +</li> +</ul> +<h3 id="4-门控精度">4. 门控精度</h3> +<ul> +<li>目的：测试门控时隙长度的设置精度</li> +<li>方案：(n=1,2,4,8,…) +<ol> +<li>每个调度周期预留长度为 1 的时隙给高优先级流量</li> +<li>每个周期发送 n 个数据包长度为1/n*1500Byte的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过 n 个包 +<ol> +<li>n=1,</li> +</ol> +</li> +</ol> +</li> +<li>预期： +<ol> +<li>n=1,2,4,8 情况下都能每个周期通过且仅通过 n 个包</li> +</ol> +</li> </ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./pkt_gen -</span></span></code></pre></div><h2 id="4-analyze">4. Analyze</h2> -<p>There are two analysis methods for TSNPerf:</p> <blockquote> -<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +<p>如果您按照下文的配置使用我们开源的ZIGGO交换机和TSNPerf，则您可以在上面四个测试中得到和预期相类似的效果。如果出现了任何问题，欢迎在github上提出issue。</p> </blockquote> -<p>One method is to directly analyze latency and jitter on the TSNPerf.</p> -<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> -<h3 id="41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</h3> -<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> -<p>You can display the content of the header and the last 5 lines using the following command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 -</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 -</span></span></code></pre></div><h3 id="42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</h3> -<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> -<p>Example of packet capture command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng -</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> -<p>Code for analyzing programs is <code>analyze_packet.py</code></p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> -</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> - -- -
- -💦 Software:Time Sync + Config for CaaS Switches - http://localhost:1313/switch/software_build/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/software_build/ -<p>This repo contains source code to enable CaaS Switches’ time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).</p> -<h2 id="build">Build</h2> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build -</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build -</span></span><span class="line"><span class="cl">cmake .. -</span></span><span class="line"><span class="cl">make -</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync_app” & “switch_config”</p> -<h2 id="config">Config</h2> -<p>The “config” directory contains topology & TSN/CaaS schedule results.</p> -<p>This document takes the following topology as an example to give example configurations:</p> +<h2 id="设备参数设置与部署">设备参数设置与部署</h2> +<p>Switch软硬件代码在仓库 <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch" target="_blank" rel="noopener">ZIGGO-Caas-Switch</a> 中，使用主分支即可。</p> +<p>TSNPerf的软硬件代码在本仓库。</p> +<blockquote> +<p>注意：带宽能力测试中的TSNPerf需要使用offline_analyze分支，门控精度测试中的TSNPerf需要使用packet_resize分支【用于自定义测试包大小】。测试中请勿忘记切换分支。</p> +</blockquote> +<p>所有设备的IP、MAC和ID如下所示，与本文档后面提供的JSON配置文件对应：</p> <p> @@ -109,395 +176,50 @@ <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./example_topology.png" alt="topology" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./topo_config.png" alt="topo config" loading="lazy" data-zoomable /></div> </div></figure> </p> -<ul> -<li> -<p>***-config.json: Mainly describes the network’s topology, including the type of each node (device or switch), MAC address, PTP port status, and other node information, topology information, and MAC forwarding table. Example and explanation are as follows (note that the comments in the file are just for explanation, do not have such comments in actual use):</p> +<p>对应的config文件可见<code>config.json</code></p> +<h2 id="testbed运行流程">TestBed运行流程</h2> +<h3 id="准备工作">准备工作</h3> +<h4 id="控制脚本准备">控制脚本准备</h4> +<p>可以参考 <a href="http://localhost:1313/device/cnc_manual/">CNC-User-Manual</a></p> +<h4 id="背景流量发送">背景流量发送</h4> +<p>可以直接在Linux PC中运行<code>send.py</code>脚本。（需要安装scapy,tcpreplay）</p> +<h3 id="基准测试">基准测试</h3> +<p>Switch、TSNPerf 的软硬件都使用主分支。</p> +<p>测试步骤：</p> +<ol> +<li>修改batch.mjs修改正确的配置文件名</li> +<li>./batch.mjs pull（注意分支正确）</li> +<li>./batch.mjs distribute +Device每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： +<code>base/d3s2-baseline-3t-config.json</code>， +<code>base/d3s2-baseline-3t-schedule-base.json</code></li> +<li>./batch.mjs launch （包括了时间同步和数据包发送）</li> +<li>./batch.mjs collect</li> +</ol> +<h3 id="门控能力">门控能力</h3> +<p>Switch、TSNPerf 的软硬件都使用主分支。</p> +<ol> +<li>让背景流量Device发包（基准测试不需要发送背景流量）</li> +<li>修改batch.mjs修改正确的配置文件名</li> +<li>./batch.mjs pull（注意分支正确）</li> +<li>./batch.mjs distribute +Device1每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： +<code>gate/d3s2-baseline-3t-config.json</code>， +<code>gate/d3s2-baseline-3t-schedule-gate.json</code></li> +<li>./batch.mjs launch</li> +<li>./batch.mjs collect</li> +<li>将上述的schedule.json中的Device发包个数从4改为8，再从上述步骤4重新测试，修改后的schedule.json如下所示</li> +</ol> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Used to describe the information of each node in the network -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="mi">3</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Node's PTP port status -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// The quintuple represents the clock status of [local, ETH1, ETH2, ETH3, ETH4] -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Number meaning: (0: MASTER, 1: SLAVE, 2: PASSIVE, 3: DISABLED) -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 1, it means that the node is the master clock node; -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 0, it means that the node is the slave clock node. -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:14"</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:15"</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Topology information, composed of each link, each link is a directed edge -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// link ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Port number of the source node -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// port 0,1,2,3 correspond to ETH1,2,3,4 in reality -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Port number of the destination node -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">2</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Forwarding table, which can be generated by the scheduling algorithm in CNC -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// In the forwarding table where you send to yourself, the port is 4 (caas) / 5 (PS ETH for new hardware) -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Current node ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Output port number -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Entry ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Destination node ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div><p>If the master clock selection algorithm is used, only the configuration of nodes is different, and the rest are the same. The newly added <code>externalPortConfigurationEnabled</code> and <code>system_identity</code> fields are optional items, as shown in the example below:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:00:00:00:02:01"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"externalPortConfigurationEnabled"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> <span class="c1">// 1: Manually configure the master-slave relationship, 0: Configure the master-slave relationship through the master clock selection algorithm, if this item is not written, the default is 0, that is, configure the master-slave relationship through the master clock selection -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"system_identity"</span><span class="p">:</span> <span class="p">{</span> <span class="c1">// Clock node's clock parameters, used for comparison in the master clock selection algorithm, if this item is not written, the default is the configuration written below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority1"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// First priority -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockClass"</span><span class="p">:</span> <span class="mi">248</span><span class="p">,</span> <span class="c1">// Clock level -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockAccuracy"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// Clock accuracy -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"offsetScaledLogVariance"</span><span class="p">:</span> <span class="mi">17258</span><span class="p">,</span> <span class="c1">// Clock variance -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority2"</span><span class="p">:</span> <span class="mi">247</span><span class="p">,</span> <span class="c1">// Second priority -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clock_identity"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">]</span> <span class="c1">// Clock identifier, different clocks should have different parameters -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">],</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"><span class="p">}</span> -</span></span></code></pre></div></li> -<li> -<p>***-schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span><span class="c1">// All switches need to be listed to facilitate software recognition of configuration information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Can be empty, not used -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> <span class="c1">// Type is link, used to describe scheduling information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Output port number -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Scheduling information -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> <span class="c1">// Scheduling cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Start time relative to the entire cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">5</span><span class="p">,</span> <span class="c1">// End time relative to the entire cycle -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Job ID in CaaS, if not needed, it can be omitted -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Data stream ID -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"> <span class="p">},</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> -</span></span><span class="line"><span class="cl"> <span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">6</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">1500</span> <span class="c1">// Packet length, if not written, the default is 1500B, this item only exists on the path from Device to Switch -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> -</span></span><span class="line"><span class="cl"> <span class="p">]</span> -</span></span><span class="line"><span class="cl"> <span class="p">}</span> -</span></span><span class="line"><span class="cl"><span class="p">]</span> -</span></span></code></pre></div></li> -</ul> -<h2 id="run">Run</h2> -<ul> -<li>Copy topology & schedule file to build dir:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-config.json build/config.json -</span></span><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-schedule.json build/schedule.json -</span></span></code></pre></div><ul> -<li>Start time synchronization and initialize GCL and MAC forwarding table according to the configuration (it is recommended to run the time synchronization program on a core (with <code>taskset -c 1</code> command) to prevent kernel errors and crashes due to time synchronization):</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -</span></span></code></pre></div><ul> -<li>The log output level is categorized into three types: WARN, INFO, and TRACE. The default log output level is TRACE (the most comprehensive output information, including DEBUG logs). The log output level can be set with the -l parameter:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l w <span class="c1"># WARN level</span> -</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l i <span class="c1"># INFO level</span> -</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l t <span class="c1"># TRACE level</span> -</span></span></code></pre></div><p><em>Notice that the time sync logic is supposed to run indefinitely as the node should sync to its neighbors again and again.</em></p> -<ul> -<li>Update GCL & switch forwarding rules:</li> -</ul> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./switch_config -</span></span></code></pre></div> -- -
💦 互联互通测试TestBed搭建流程 - http://localhost:1313/device/testbed/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/testbed/ -<h2 id="目录">目录</h2> -<ul> -<li><a href="#%e7%9b%ae%e5%bd%95">目录</a></li> -<li><a href="#testbed%e7%ae%80%e5%8d%95%e4%bb%8b%e7%bb%8d">TestBed简单介绍</a></li> -<li><a href="#%e4%ba%92%e8%81%94%e4%ba%92%e9%80%9a%e6%b5%8b%e8%af%95%e9%a1%b9%e7%9b%ae%e4%bb%8b%e7%bb%8d">互联互通测试项目介绍</a> -<ul> -<li><a href="#1-%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">1. 基准测试</a></li> -<li><a href="#2-%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">2. 门控能力</a></li> -<li><a href="#3-%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">3. 带宽保证</a></li> -<li><a href="#4-%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">4. 门控精度</a></li> -</ul> -</li> -<li><a href="#%e8%ae%be%e5%a4%87%e5%8f%82%e6%95%b0%e8%ae%be%e7%bd%ae%e4%b8%8e%e9%83%a8%e7%bd%b2">设备参数设置与部署</a></li> -<li><a href="#testbed%e8%bf%90%e8%a1%8c%e6%b5%81%e7%a8%8b">TestBed运行流程</a> -<ul> -<li><a href="#%e5%87%86%e5%a4%87%e5%b7%a5%e4%bd%9c">准备工作</a> -<ul> -<li><a href="#%e6%8e%a7%e5%88%b6%e8%84%9a%e6%9c%ac%e5%87%86%e5%a4%87">控制脚本准备</a></li> -<li><a href="#%e8%83%8c%e6%99%af%e6%b5%81%e9%87%8f%e5%8f%91%e9%80%81">背景流量发送</a></li> -</ul> -</li> -<li><a href="#%e5%9f%ba%e5%87%86%e6%b5%8b%e8%af%95">基准测试</a></li> -<li><a href="#%e9%97%a8%e6%8e%a7%e8%83%bd%e5%8a%9b">门控能力</a></li> -<li><a href="#%e5%b8%a6%e5%ae%bd%e4%bf%9d%e8%af%81">带宽保证</a></li> -<li><a href="#%e9%97%a8%e6%8e%a7%e7%b2%be%e5%ba%a6">门控精度</a></li> -</ul> -</li> -</ul> -<h2 id="testbed简单介绍">TestBed简单介绍</h2> -<p>我们内部对自己研发的CaaS-Switch进行了互联互通测试，采用的网络拓扑如下所示。</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./topo.PNG" alt="topo" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>本Demo需要4个FPGA开发板（2个TSNPerf、2个CaaS-Switch）和1台普通PC。如果条件有限/考虑简化拓扑，可以删去一个CaaS-Switch。PC负责发送背景流量，路径为黑色箭头；左侧TSNPerf负责发送测试流量（关键流量），路径为红色箭头。</p> -<p>所有测试项目的流程大致可以分为两个阶段：</p> -<ol> -<li> -<p>时间同步：启动时间同步，保证TSNPerf、CaaS-Switch在一个时钟域下。</p> -<p>注：时间同步程序运行在TSNPerf、CaaS-Switch的系统中。</p> -</li> -<li> -<p>发送测试流量：根据schedule.json文件，TSNPerf进行测试流量发送。</p> -</li> -</ol> -<h2 id="互联互通测试项目介绍">互联互通测试项目介绍</h2> -<h3 id="1-基准测试">1. 基准测试</h3> -<ul> -<li>目的：测试无背景流量情况下，高优先级流量的两跳端到端延迟、丢包率、抖动，作为比较基准。</li> -<li>预期：延迟符合规划，抖动较低（100ns左右）。</li> -</ul> -<h3 id="2-门控能力">2. 门控能力</h3> -<ul> -<li>目的：测试通用情况下流量调度效果，和两个交换机的门控对接能力。</li> -<li>方案： -背景流量（VLAN priority = 0）打到线速，每个调度周期预留长度为 3 的时隙给高优先级流量， -<ol> -<li>每个周期定时发送 4 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录端到端平均延迟、抖动、丢包率、到达顺序</li> -<li>每个周期定时发送 8 个数据包长度为 1500Byte 的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过且仅 n 个包</li> -</ol> -</li> -<li>预期： -<ol> -<li>延迟、抖动、丢包率和基准一致</li> -<li>每个周期定时发送 4 个数据包时，丢包率为0</li> -<li>每个周期定时发送 8 个数据包时，每个周期通过且仅通过 5 个包（每8个包丢3个，因为每个时隙里恰好可以把第五个包发出去，余下三个包丢掉），丢包率为37.5%</li> -</ol> -</li> -</ul> -<h3 id="3-带宽保证">3. 带宽保证</h3> -<ul> -<li>目的：测试交换机能够进行带宽预留，且两个交换机优先级映射、运行 cycle 和 offset 基本一致。</li> -<li>方案： -背景流量（VLAN priority = 0）打到线速（1Gbps），配置交换机预留 50% 时隙给高优先级流量（VLAN priority = 1），其余 50% 只允许低优先级流量， -<ol> -<li>测试流量高优先级（VLAN priority = 1）情况下打到线速（经测试，每个周期[33ms]连续发送2752个1500B的包，基本达到1000Mbps），记录端到端平均延迟、抖动、丢包率、到达顺序</li> -<li>测试流量高优先级（VLAN priority = 1）情况下打到50%线速（每个周期[33ms]连续发送1376个1500B的包），记录端到端平均延迟、抖动、丢包率、到达顺序</li> -</ol> -</li> -<li>预期： -<ol> -<li>高优先级测试流量100%线速：延迟、抖动和基准一致，丢包率 50% 左右</li> -<li>高优先级测试流量50%线速：延迟、抖动和基准一致，0丢包率</li> -</ol> -</li> -</ul> -<h3 id="4-门控精度">4. 门控精度</h3> -<ul> -<li>目的：测试门控时隙长度的设置精度</li> -<li>方案：(n=1,2,4,8,…) -<ol> -<li>每个调度周期预留长度为 1 的时隙给高优先级流量</li> -<li>每个周期发送 n 个数据包长度为1/n*1500Byte的高优先级（VLAN priority = 1）测试流量，记录是否每个周期通过 n 个包 -<ol> -<li>n=1,</li> -</ol> -</li> -</ol> -</li> -<li>预期： -<ol> -<li>n=1,2,4,8 情况下都能每个周期通过且仅通过 n 个包</li> -</ol> -</li> -</ul> -<blockquote> -<p>如果您按照下文的配置使用我们开源的ZIGGO交换机和TSNPerf，则您可以在上面四个测试中得到和预期相类似的效果。如果出现了任何问题，欢迎在github上提出issue。</p> -</blockquote> -<h2 id="设备参数设置与部署">设备参数设置与部署</h2> -<p>Switch软硬件代码在仓库 <a href="https://github.com/Horacehxw/Ziggo-CaaS-Switch" target="_blank" rel="noopener">ZIGGO-Caas-Switch</a> 中，使用主分支即可。</p> -<p>TSNPerf的软硬件代码在本仓库。</p> -<blockquote> -<p>注意：带宽能力测试中的TSNPerf需要使用offline_analyze分支，门控精度测试中的TSNPerf需要使用packet_resize分支【用于自定义测试包大小】。测试中请勿忘记切换分支。</p> -</blockquote> -<p>所有设备的IP、MAC和ID如下所示，与本文档后面提供的JSON配置文件对应：</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./topo_config.png" alt="topo config" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>对应的config文件可见<code>config.json</code></p> -<h2 id="testbed运行流程">TestBed运行流程</h2> -<h3 id="准备工作">准备工作</h3> -<h4 id="控制脚本准备">控制脚本准备</h4> -<p>可以参考 <a href="http://localhost:1313/device/cnc_manual/">CNC-User-Manual</a></p> -<h4 id="背景流量发送">背景流量发送</h4> -<p>可以直接在Linux PC中运行<code>send.py</code>脚本。（需要安装scapy,tcpreplay）</p> -<h3 id="基准测试">基准测试</h3> -<p>Switch、TSNPerf 的软硬件都使用主分支。</p> -<p>测试步骤：</p> -<ol> -<li>修改batch.mjs修改正确的配置文件名</li> -<li>./batch.mjs pull（注意分支正确）</li> -<li>./batch.mjs distribute -Device每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： -<code>base/d3s2-baseline-3t-config.json</code>， -<code>base/d3s2-baseline-3t-schedule-base.json</code></li> -<li>./batch.mjs launch （包括了时间同步和数据包发送）</li> -<li>./batch.mjs collect</li> -</ol> -<h3 id="门控能力">门控能力</h3> -<p>Switch、TSNPerf 的软硬件都使用主分支。</p> -<ol> -<li>让背景流量Device发包（基准测试不需要发送背景流量）</li> -<li>修改batch.mjs修改正确的配置文件名</li> -<li>./batch.mjs pull（注意分支正确）</li> -<li>./batch.mjs distribute -Device1每次发送4个数据包，每个Switch都预留了3个时隙，将以下两个配置文件下发即可： -<code>gate/d3s2-baseline-3t-config.json</code>， -<code>gate/d3s2-baseline-3t-schedule-gate.json</code></li> -<li>./batch.mjs launch</li> -<li>./batch.mjs collect</li> -<li>将上述的schedule.json中的Device发包个数从4改为8，再从上述步骤4重新测试，修改后的schedule.json如下所示</li> -</ol> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">7</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> </span></span><span class="line"><span class="cl"> <span class="p">{</span> </span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> </span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> @@ -598,57 +320,206 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， - -
+ +💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit - http://localhost:1313/switch/hardware-build/ +📕 ZIGGO Device使用手册 + http://localhost:1313/device/ziggo_device_manual/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/ziggo_device_manual/ +<p>There are two analysis methods for ZIGGO Device:</p> +<blockquote> +<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +</blockquote> +<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> +<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> +<p>Example of <code>packet_log.csv</code>:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency +</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 +</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 +</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 +</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 +</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 +</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 +</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 +</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 +</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 +</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 +</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance +</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 +</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 +</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 +</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 +</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 +</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 +</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 +</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 +</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 +</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 +</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 +</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 +</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> +<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> +<p>Example of packet capture command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng +</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> +<p>Code for analyzing programs is <code>analyze_packet.py</code></p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> +</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> + +- +
+ +💦 Software:Time Sync + Config for CaaS Device + http://localhost:1313/device/software-build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/device/software-build/ +<p>This repo contains source code to enable TSN/CaaS TSNPerf’ time synchronization logic and set up packet generation plan.</p> +<h2 id="table-of-content">Table of Content</h2> +<ul> +<li><a href="#table-of-content">Table of Content</a></li> +<li><a href="#1-build">1. Build</a></li> +<li><a href="#2-config">2. Config</a></li> +<li><a href="#3-run">3. Run</a></li> +<li><a href="#4-analyze">4. Analyze</a> +<ul> +<li><a href="#41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</a></li> +<li><a href="#42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</a></li> +</ul> +</li> +</ul> +<h2 id="1-build">1. Build</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build +</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build +</span></span><span class="line"><span class="cl">cmake .. +</span></span><span class="line"><span class="cl">make +</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync” & “pkt_gen”</p> +<h2 id="2-config">2. Config</h2> +<p>The “build” directory contains topology & TSN/CaaS schedule results.</p> +<ul> +<li>config.json: topology file, contains node info (type, mac, ptp ports), link between nodes (with ports), and forwarding table.</li> +<li>schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</li> +</ul> +<p>(Hints: This is similar to a Ziggo Switch)</p> +<h2 id="3-run">3. Run</h2> +<ul> +<li>Start time syncronization</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./time_sync +</span></span></code></pre></div><ul> +<li>Start device critical packet generation</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./pkt_gen +</span></span></code></pre></div><h2 id="4-analyze">4. Analyze</h2> +<p>There are two analysis methods for TSNPerf:</p> +<blockquote> +<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> +</blockquote> +<p>One method is to directly analyze latency and jitter on the TSNPerf.</p> +<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> +<h3 id="41-tsnperf-directly-analyzes-latency-and-jitter">4.1 TSNPerf directly analyzes latency and jitter</h3> +<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> +<p>You can display the content of the header and the last 5 lines using the following command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 +</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 +</span></span></code></pre></div><h3 id="42-offline-analysis-of-latency-and-jitter">4.2 Offline analysis of latency and jitter</h3> +<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> +<p>Example of packet capture command:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng +</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> +<p>Code for analyzing programs is <code>analyze_packet.py</code></p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> +</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> + +- +
@@ -905,229 +935,20 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙，🔨 System Design —— PL & PS Co-operate + http://localhost:1313/device/system-design/Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/switch/hardware-build/ -<p>This repo contains pre-build hardware & system rootfs to boot the <strong>Zynq AX7021</strong> FPGA board from SD card.</p> -<h2 id="file-downloading">File downloading</h2> -<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/8277c491a8bd4e6a8997/" target="_blank" rel="noopener">this</a> public link:</p> + http://localhost:1313/device/system-design/ +<p>ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ’s both hardware and software programmability.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./framework.jpg" alt="framework" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<h2 id="table-of-content">Table of Content</h2> <ul> -<li>BOOT.BIN</li> -<li>boot.scr</li> -<li>image.ub</li> -<li>rootfs.tar.gz</li> -</ul> -<h2 id="sd-card-partition">SD card partition</h2> -<p>In order to boot the CaaS Switch, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted -</span></span><span class="line"><span class="cl">sudo gparted -</span></span></code></pre></div><p>Parition it into two partition below</p> +<li><a href="#table-of-content">Table of Content</a></li> +<li><a href="#evaluation-method">Evaluation Method</a></li> +<li><a href="#test-data-frame-data-structure">Test data frame data structure</a></li> +<li><a href="#module-design">Module Design</a> <ul> -<li> -<p>BOOT: store boot files from petalinux</p> -<p>Free space preceding (MiB): 4</p> -<p>New size (MiB): 500</p> -<p>File system: fat32</p> -<p>Label: BOOT</p> -</li> -<li> -<p>ROOTFS: store debian system rootfs</p> -<p>Free space preceding (MiB): 0</p> -<p>Free space following (MiB): 0</p> -<p>File system: ext4</p> -<p>Label: ROOTFS</p> +<li><a href="#correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</a></li> +<li><a href="#offline-analysis-and-design">Offline Analysis and Design</a></li> +</ul> </li> </ul> -<h2 id="copy-files-into-sd-card">Copy files into SD card</h2> -<p>Mound SD card:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ -</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ -</span></span></code></pre></div><p>Remove original files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* -</span></span></code></pre></div><p>Copy files:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT -</span></span><span class="line"><span class="cl"> -</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh -</span></span><span class="line"><span class="cl">sync -</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS -</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS -</span></span></code></pre></div><h2 id="launch-the-switch">Launch the switch</h2> -<h3 id="1-launch-the-board">1. Launch the Board</h3> -<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> +<h2 id="evaluation-method">Evaluation Method</h2> +<p>The ZIGGO Evaluation Toolkit is used to send and receive test data frames for the purpose of ensuring <code>accurate delay calculations</code>.</p> +<p>To achieve this accuracy, the toolkit needs to <strong>synchronize its time</strong> with the TSN switch and record a <strong>global hardware timestamp</strong> in the test data frames.</p> +<p>As shown in the diagram below, in a data flow link with $n$ network nodes, Node $1$ serves as the source node to send test data frames, Node $n$ acts as the destination node to receive test data frames, and all the intermediate nodes (Node $2$ to Node $n-1$) are TSN switches.</p> +<p>When a test data frame is sent from the source node, the hardware records the timestamp $t^+$ of when the frame was sent in the data frame. Finally, when the data frame arrives at the destination node, the destination node records the timestamp $t^-$ of when the frame entered that node. By calculating $(t^−−t^+)$, we can determine the end-to-end latency of the data frame.</p> <p> @@ -667,12 +538,75 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./device_test_demo.png" alt="device_test_demo" loading="lazy" data-zoomable /></div> </div></figure> </p> -<h3 id="2-initialize-ps">2. Initialize PS</h3> -<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> -<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> +<blockquote> +<p>In this doc, $t^{dir}$ is used to represent the timestamp of data frames entering and leaving the hardware. Here, “dir” represents the direction of data frames entering or leaving the nodes, with " + " indicating data frames leaving the node and " − " indicating data frames entering the node.</p> +</blockquote> +<h2 id="test-data-frame-data-structure">Test data frame data structure</h2> +<p>In order to analyze the end-to-end latency of each data frame on complex network topologies, we have established specific guidelines for the content of data segments in the Ethernet frame structure. The structure of time-sensitive networking test data frames is as shown in the following table.</p> +<table> +<thead> +<tr> +<th>ield</th> +<th>Byte Length</th> +<th>Description</th> +</tr> +</thead> +<tbody> +<tr> +<td>Destination Address</td> +<td>6</td> +<td>Destination node MAC address</td> +</tr> +<tr> +<td>Source Address</td> +<td>6</td> +<td>Source node MAC address</td> +</tr> +<tr> +<td>VLAN Tag</td> +<td>4</td> +<td>Divided into four fields: VLAN Data Frame Type (0x8100), Priority, Canonical Format Indicator, and VLAN Number</td> +</tr> +<tr> +<td>Data Frame Type</td> +<td>2</td> +<td>Used to identify test data frames, set to 0x66ab</td> +</tr> +<tr> +<td>Reserved Bits</td> +<td>2</td> +<td></td> +</tr> +<tr> +<td><code>$t^+$ (TX Timestamp)</code></td> +<td>8</td> +<td>Timestamp when transmitted from the source node</td> +</tr> +<tr> +<td><code>$t^-$ (RX Timestamp)</code></td> +<td>8</td> +<td>Timestamp when received by the destination node</td> +</tr> +<tr> +<td>Data Stream ID (SEQ_ID)</td> +<td>2</td> +<td>Unique identifier for each data stream</td> +</tr> +<tr> +<td>Data Frame ID (PKT_ID)</td> +<td>4</td> +<td>Sequence number of data frames within each data stream, starting from 0</td> +</tr> +</tbody> +</table> +<h2 id="module-design">Module Design</h2> +<p>The overall module design for ZIGGO Evaluation Toolkit is depicted in the following diagram. The Time Synchronization module used by the Toolkit shares a design that is nearly identical to the Switch, and the diagram does not provide extensive details on the time synchronization-related modules.</p> +<p>The configuration module in the PS section (<code>software/pkt_gen_main.cpp</code>) communicates with the Data Frame Generation module by using the UIO driver and AXI4-Lite interface to send the transmission rules for the test data frames to relevant registers in the Data Frame Generation module (specifically, <code>hardware/IP_repo/pkt_gen_controller_v1.1/pkt_gen_controller_1.1/hdl/pkt_gen_controller_v1_1.v</code> is responsible for configuration, and <code>hardwire/HDL/axi_packet_generator.v</code> is responsible for generating and transmitting the data frames) using the global synchronized time as a reference for timing.</p> +<p>The Timestamp Marking module (<code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_tx.v</code> and <code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_rx.v</code>) is located at the send and receive ports of the Ziggo-Evaluation-Toolkit. It is used to record the hardware timestamps of sent and received data frames within the test data frames.</p> +<p>The received data frames are ultimately uploaded to the PS section via a DMA channel (in our design, we currently use a time-synchronized DMA channel for transmitting test data frames) for statistical analysis (handled in the <code>process_critical_frame</code> function in <code>software/pkt_gen_control/pkt_gen.c</code>).</p> <p> @@ -691,21 +625,117 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./device_arch.png" alt="device_arch" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>The default username and password are as follows:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> -</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> -</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh -</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> -<h3 id="3-connect-to-internet">3. Connect to Internet</h3> -<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> -<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> -<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> -<h3 id="4-run-the-software">4. Run the Software</h3> -<p>Please refer to the software part of this repo for further instructions.</p> +<p>The maximum frame transmission period (superperiod parameter in <code>pkt_gen_main.cpp</code>) refers to the upper limit on the periodicity for sending data streams from the toolkit. Within this maximum frame transmission period, the Data Frame Generation module allocates a maximum of 32 time slots for all data streams. Each time slot is used to send all the data frames for the corresponding data stream at the specified transmission time.</p> +<p>As illustrated in the diagram, the evaluation toolkit sends two types of data streams: Stream 𝐹1 with a transmission period of 2𝑇 and Stream 𝐹2 with a transmission period of 4𝑇. The maximum frame transmission period for the evaluation toolkit is 6𝑇. In this scenario, the Data Frame Generation module sets up 5 time slots within the maximum frame transmission period and sends test data frames in sequential order according to the specified time slots.</p> +<p> + + + + + + + + + + + + + + + +<figure > + <div class="flex justify-center "> + <div class="w-100" ><img src="./example_pkt_gen_period.png" alt="example_pkt_gen_period" loading="lazy" data-zoomable /></div> + </div></figure> +</p> +<p>Users can configure the Ziggo-Evaluation-Toolkit to generate multiple data streams, and the configuration parameters for each data stream are as follows, with clear explanations provided in the comments of the <code>pkt_gen.h</code> header file:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// pkt_gen_app\pkt_gen_control\pkt_gen.h +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"><span class="cm">/** +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @brief Set the pkt gen slot object +</span></span></span><span class="line"><span class="cl"><span class="cm"> * +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param slot_id 0~31, indicate a slot in pkt_gen IP core +</span></span></span><span class="line"><span class="cl"><span class="cm"> * IMPORTANT: tx_offset for each slot id should be monotonic increasing +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param seq_id sequence ID that uniquely identify a stream +</span></span></span><span class="line"><span class="cl"><span class="cm"> * To further utilize this field, it may be {job_id: 8bit, flow_id: 8bit} +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_number number of packets in one sent, should be 1 +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_start start of pkt_id +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_update update of next pkt_id +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param tx_offset transmission time inside a period, in ns +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param src_mac 6Byte array +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param dest_mac 6Byte array +</span></span></span><span class="line"><span class="cl"><span class="cm"> * @return int +</span></span></span><span class="line"><span class="cl"><span class="cm"> */</span> +</span></span><span class="line"><span class="cl"><span class="kt">int</span> <span class="nf">set_pkt_gen_slot</span> <span class="p">(</span><span class="kt">int</span> <span class="n">slot_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">seq_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">pkt_number</span><span class="p">,</span> <span class="kt">uint32_t</span> <span class="n">pkt_id_start</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="kt">uint32_t</span> <span class="n">pkt_id_update</span><span class="p">,</span> <span class="kt">int64_t</span> <span class="n">tx_offset</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">src_mac</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">dest_mac</span><span class="p">);</span> +</span></span></code></pre></div><p>The Timestamp Marking Module will write the timestamp of the current synchronized clock into the outgoing data frame just before it is transmitted by the MAC controller of the toolkit. When the MAC controller in the PL (Programmable Logic) receives the first bit of data in the frame from the physical link, the Timestamp Marking Module records the timestamp of the current synchronized clock. It subsequently writes this timestamp into the data frame during the packet reception process and hands it over to the statistical analysis module in the PS (Processing System) section for further analysis and processing.</p> +<h3 id="correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</h3> +<p>The correspondence in terms of time synchronization is the same as in the Ziggo TSN Switch.</p> +<p>In this section, we will primarily focus on the correspondence related to data frame transmission configuration. The software registers’ addresses can be found in <code>software/pkt_gen_control/pkt_gen.c</code>.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// define global register address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define GLOBAL_PERIOD_NS 0x00000000 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define GLOBAL_OFFSET_NS 0x00000008 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_VALID 0x00000010 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_ENABLE_VLAN 0x00000014 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITE_LOCK 0x00000018 +</span></span></span><span class="line"><span class="cl"><span class="cp"></span> +</span></span><span class="line"><span class="cl"><span class="c1">// define write lock value +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define NOT_WRITING 0x00000001 +</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITING 0x00000000 +</span></span></span><span class="line"><span class="cl"><span class="cp"></span> +</span></span><span class="line"><span class="cl"><span class="c1">// define address pointer for sequences +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define SEQ_CONTENT 0x0000001c +</span></span></span></code></pre></div><p>The hardware registers are located in <code>tsn_device\IP_repo\pkt_gen_controller_v1.1\pkt_gen_controller_1.1\hdl\pkt_gen_controller_v1_1_S00_AXI.v</code>.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"><span class="k">if</span> <span class="p">(</span><span class="n">slv_reg_wren</span><span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="k">case</span> <span class="p">(</span> <span class="n">axi_awaddr</span><span class="p">[</span><span class="n">ADDR_LSB</span><span class="o">+</span><span class="nl">OPT_MEM_ADDR_BITS</span><span class="p">:</span><span class="n">ADDR_LSB</span><span class="p">]</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h000</span><span class="p">:</span> +</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 0 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg0</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">end</span> +</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h001</span><span class="p">:</span> +</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 1 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg1</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">end</span> +</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h002</span><span class="p">:</span> +</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> +</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> +</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 2 +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg2</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> +</span></span><span class="line"><span class="cl"> <span class="n">end</span> +</span></span><span class="line"><span class="cl"><span class="p">...</span> +</span></span></code></pre></div><p>In this context, the hardware registers with names starting with “slv_reg” are each 32 bits wide, and their addresses are spaced by 4 bytes. So, for example, if the software-level address is $0x00000018$, you need to divide this address by 4, which results in $ 24/4 = 6$. Therefore, this address corresponds to the hardware register “<code>slv_reg6</code>” in the hardware module. This helps establish the correspondence between software and hardware registers.</p> +<h3 id="offline-analysis-and-design">Offline Analysis and Design</h3> +<p>In the <code>offline_analyze</code> branch of the Toolkit, we perform packet capture and analysis by forwarding packets from the Toolkit to a powerful desktop computer after the timestamps the incoming packets. This method ensures that even at gigabit speeds, no packets are dropped, and there are relatively minor hardware changes.</p> +<p>One aspect of the modification is that timestamps are not added to the data frames when they are transmitted from the toolkit. This can be seen in the <code>HDL/trimode_mac/simple_mac_no_shared.v</code> file where the “tsu_axis_tx” section is commented out.</p> +<p>Another aspect is the modification of the “frame_type” to change the direction of data frames. Previously, both PTP frames and test data frames were uploaded to the PS section via time-synchronized DMA, with IT traffic uploaded to PS_ETH. This split the traffic into two directions (“axis_switch_1_2”). Now, it has been split into three directions (“axis_switch_1_3”). For offline analysis, only PTP frames need to be transferred to the PS, while test data frames need to be separated and sent out from ETH2. This requires a finer-grained separation of traffic.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"> <span class="c1">// separate IT frames, ptp frames and critical frames +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="n">axis_switch_1_3</span> <span class="nf">axis_switch_1_3_inst</span> <span class="p">(</span> +</span></span><span class="line"><span class="cl"> <span class="p">.</span><span class="n">aclk</span><span class="p">(</span><span class="n">rx_fifo_clock</span><span class="p">),</span> <span class="c1">// input wire aclk +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">aresetn</span><span class="p">(</span><span class="n">rx_fifo_resetn</span><span class="p">),</span> <span class="c1">// input wire aresetn +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tvalid</span><span class="p">(</span><span class="n">rx_axis_fifo_tvalid_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tvalid +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tready</span><span class="p">(</span><span class="n">rx_axis_fifo_tready_8</span><span class="p">),</span> <span class="c1">// output wire [0 : 0] s_axis_tready +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdata</span><span class="p">(</span><span class="n">rx_axis_fifo_tdata_8</span><span class="p">),</span> <span class="c1">// input wire [7 : 0] s_axis_tdata +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tlast</span><span class="p">(</span><span class="n">rx_axis_fifo_tlast_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tlast +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdest</span><span class="p">(</span><span class="n">frame_type</span><span class="p">),</span> <span class="c1">// input wire [1 : 0] s_axis_tdest +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tvalid</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tvalid</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tvalid</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tvalid</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tvalid +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tready</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tready</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tready</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tready</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// input wire [2 : 0] m_axis_tready +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdata</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tdata</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tdata</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tdata</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [23 : 0] m_axis_tdata +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tlast</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tlast</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tlast</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tlast</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tlast +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdest</span><span class="p">(),</span> <span class="c1">// output wire [5 : 0] m_axis_tdest +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_decode_err</span><span class="p">()</span> <span class="c1">// output wire [0 : 0] s_decode_err +</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="p">);</span> +</span></span></code></pre></div><p>The <code>tx_axis_fifo_legacy_tdata[1]</code> indicates sending from ETH2.</p> - -
- -📈 TSNPerf 设计原理 - http://localhost:1313/tsnperf/principle/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/tsnperf/principle/ -<h2 id="现有方案的局限">现有方案的局限</h2> -<p>TSNPerf是一款专为时间敏感网络（Time-Sensitive Networking, TSN）设计的性能评测工具。它提供了全面的TSN网络性能评测功能，能够帮助网络工程师和研究人员深入了解并验证TSN网络设备的性能特征。为此，TSNPerf需要能够精准地向网络中发送关键数据包，以测试设备的时间同步性能和流量整形能力。然而，Linux操作系统提供的<code>send()</code>函数只能达到微秒级的发包精度，难以满足TSNPerf对高精度发包的要求。</p> -<p>为了直观地展示<code>send()</code>函数的发包精度限制，我们进行了一项测试。在测试中，我们使用<code>send()</code>函数以1毫秒为设定间隔，连续发送了10000个数据包。然后，我们记录了每两个相邻数据包之间的实际时间间隔，并计算了它们与预期的1毫秒间隔之间的误差。结果显示，即使没有任何背景进程/流量的干扰，相邻数据包的间隔任然达到了<em><strong>最高14微秒</strong></em>左右。接下来我们分析该现象的原因。</p> -<p>如下图所示，在 $t_0$ 时刻，程序调用 <code>send()</code> 函数向网络发送数据包，但实际上，数据包在 $t_1$ 时刻才会被发送到网络中去。这是因为，操作系统的网络协议栈需要花费一定的时间处理该数据包。我们将 $t_1-t_0$ 称之为网络栈的处理时延，这个时延通常在微秒级别。</p> -<p> - - - - - - - - - - - - - - - -<figure id="figure-linux网络栈处理时延"> - <div class="flex justify-center "> - <div class="w-100" ><img src="./principle_basic.png" alt="Linux网络栈处理时延" loading="lazy" data-zoomable /></div> - </div><figcaption> - Linux网络栈处理时延 - </figcaption></figure> -</p> -<h2 id="解决方案">解决方案</h2> -<p>Intel 的 I210 / I225 / I226 网卡，提供了 LaunchTime 功能，可以精准地控制数据包离开网口的时间（理论精度在 32 纳秒级别）。</p> -<p> - - - - - - - - - - - - - - - -<figure id="figure-launchtime原理"> - <div class="flex justify-center "> - <div class="w-100" ><img src="./principle_advanced.png" alt="LaunchTime原理" loading="lazy" data-zoomable /></div> - </div><figcaption> - LaunchTime原理 - </figcaption></figure> -</p> -<p>利用 LaunchTime，可以提高数据包的发送精度。如上图所示，对于一个需要在 $t_0$ 时刻发出的数据包，我们预留一段时间给网络栈的处理流程，提前在 $t_2$ 时刻就调用 <code>send()</code> 函数，保证数据包在 $t_0$ 前就在网卡的出队列口等待，LaunchTime 会在$t_0$时刻打开出队列的门，将数据包发出。</p> -<h2 id="性能验证">性能验证</h2> -<p>类似地，我们开启 LaunchTime 功能，以1毫秒为设定间隔连续发送10000个数据包，记录每两个相邻数据包之间的实际时间间隔与1毫秒之间的误差。 -结果如下图所示，所有数据包的发送时间误差不超过100纳秒，达到了TSNPerf对发包精度的要求</p> -<p> - - - - - - - - - - - - - - - -<figure id="figure-launchtime实验结果"> - <div class="flex justify-center "> - <div class="w-100" ><img src="./principle_advanced_performance.png" alt="LaunchTime实验结果" loading="lazy" data-zoomable /></div> - </div><figcaption> - LaunchTime实验结果 - </figcaption></figure> -</p> - -- -
- -📕 ZIGGO Device使用手册 - http://localhost:1313/device/ziggo_device_manual/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/ziggo_device_manual/ -<p>There are two analysis methods for ZIGGO Device:</p> -<blockquote> -<p>Hint: If you want to use offline anaylze, please switch branch to ‘offline_anaylze’, and you need to link device to anthor PC(linux) by wire.</p> -</blockquote> -<p>One method is to <code>directly</code> analyze latency and jitter on the ZIGGO Device. The advantage of this method is that it is convenient and fast. We can directly count the latency and jitter of all received data frames on the Device. However, due to the limited processing power of the development board CPU, when analyzing a large number of data packets (such as sending more than 10 1500B data packets at a time with a cycle of 33ms), packet loss may occur;</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./online_analyse.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<p>Another method is to use Device to stamp the received packet and forward it from another port to a powerful desktop computer for packet capture analysis. Even if entering the Device at a gigabit rate, there will be no packet loss. The disadvantage is that a separate program needs to be written offline to analyze the delay and jitter of the packet.</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./offline_analyse.png" alt="" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<h2 id="ziggo-device-directly-analyzes-latency-and-jitter">ZIGGO Device directly analyzes latency and jitter</h2> -<p>During the operation of the <code>time sync</code> program, after receiving the test data frame, the program will save the delay information of the data frame in the package under the <code>build/packet_log.csv</code> file, save the batch statistics of latency and jitter in the critical directory under the build directory at the same time in the <code>build/critical_log.csv</code>.</p> -<p>Example of <code>packet_log.csv</code>:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Pkt ID, TX timestamp, RX timestamp, Latency -</span></span><span class="line"><span class="cl">0101, 0, 12683587446, 12683613722, 26276 -</span></span><span class="line"><span class="cl">0101, 1, 12683599662, 12683625970, 26308 -</span></span><span class="line"><span class="cl">0101, 2, 12683611862, 12683638162, 26300 -</span></span><span class="line"><span class="cl">0101, 3, 12683624078, 12683650386, 26308 -</span></span><span class="line"><span class="cl">0101, 4, 12717142039, 12717168273, 26234 -</span></span><span class="line"><span class="cl">0101, 5, 12717154223, 12717180465, 26242 -</span></span><span class="line"><span class="cl">0101, 6, 12717166391, 12717192625, 26234 -</span></span><span class="line"><span class="cl">0101, 7, 12717178575, 12717204825, 26250 -</span></span><span class="line"><span class="cl">0101, 8, 12750696471, 12750722712, 26241 -</span></span><span class="line"><span class="cl">0101, 9, 12750708655, 12750734904, 26249 -</span></span></code></pre></div><p>Example of <code>critical_ log.csv</code>, where Latency Variance is the variance of Latency:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="cl">Seq ID, Received Number, Max pkt_id, Min pkt_id, Loss Rate, Latency Mean, Latency Variance -</span></span><span class="line"><span class="cl">0101, 1000, 0, 999, 0.000000, 26230, 1199 -</span></span><span class="line"><span class="cl">0101, 1000, 1000, 1999, 0.000000, 26218, 2811 -</span></span><span class="line"><span class="cl">0101, 1000, 2000, 2999, 0.000000, 26218, 2808 -</span></span><span class="line"><span class="cl">0101, 1000, 3000, 3999, 0.000000, 26195, 18331 -</span></span><span class="line"><span class="cl">0101, 1000, 4000, 4999, 0.000000, 26233, 921 -</span></span><span class="line"><span class="cl">0101, 1000, 5000, 5999, 0.000000, 26226, 852 -</span></span><span class="line"><span class="cl">0101, 1000, 6000, 6999, 0.000000, 26226, 5080 -</span></span><span class="line"><span class="cl">0101, 1000, 7000, 7999, 0.000000, 26250, 105272 -</span></span><span class="line"><span class="cl">0101, 1000, 8000, 8999, 0.000000, 26204, 7233 -</span></span><span class="line"><span class="cl">0101, 1000, 9000, 9999, 0.000000, 26205, 7361 -</span></span></code></pre></div><p>You can display the content of the header and the last 5 lines using the following command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cat critical.log <span class="p">|</span> head -n1 -</span></span><span class="line"><span class="cl">cat critical.log <span class="p">|</span> tail -n5 -</span></span></code></pre></div><h2 id="offline-analysis-of-latency-and-jitter">Offline analysis of latency and jitter</h2> -<p>If conducting offline analysis, it is important to note that the hardware used is located at <code>offline_analyze</code> branch. This version will stamp the key data with a receive timestamp and forward it from ETH2. We need to use a PC equipped with a Linux system to capture packets for analysis.</p> -<p>Example of packet capture command:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo tcpdump -i enx207bd272812b ether src 00:0a:35:00:00:14 -n -B <span class="m">100000</span> -w packets.pcapng -</span></span></code></pre></div><p><code>Enx207bd272812b</code> is the name of the network card, which can be obtained through ifconfig. <code>Src</code> is used to specify that the captured packet comes from a certain MAC address. <code>-B</code> is used to specify the buffer size. If packet loss needs to be set to a larger size, you can check the information output after packet capture to see if Dropped by kernel: is 0. If it is not 0, it indicates that there is packet loss in the kernel. <code>-W</code> specifies the path to save the file.</p> -<p>Code for analyzing programs is <code>analyze_packet.py</code></p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">python .<span class="se">\a</span>nalyze_packet.py <span class="o">[</span>capture file path<span class="o">]</span> --step <span class="o">[</span>interval<span class="o">]</span> -</span></span></code></pre></div><p>At the same time, a packet will be generated in the current directory (<code>packet_log.csv</code> and <code>critical_log.csv</code>).</p> - -- -
+ +🔨 System Design —— PL & PS Co-operate - http://localhost:1313/device/system-design/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/device/system-design/ -<p>ZIGGO is implemented on ZYNQ-7000 SoC and exploits ZYNQ’s both hardware and software programmability.</p> -<p> - - - - - - - - - - - - - - - -<figure > - <div class="flex justify-center "> - <div class="w-100" ><img src="./framework.jpg" alt="framework" loading="lazy" data-zoomable /></div> - </div></figure> -</p> -<h2 id="table-of-content">Table of Content</h2> -<ul> -<li><a href="#table-of-content">Table of Content</a></li> -<li><a href="#evaluation-method">Evaluation Method</a></li> -<li><a href="#test-data-frame-data-structure">Test data frame data structure</a></li> -<li><a href="#module-design">Module Design</a> -<ul> -<li><a href="#correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</a></li> -<li><a href="#offline-analysis-and-design">Offline Analysis and Design</a></li> -</ul> -</li> -</ul> -<h2 id="evaluation-method">Evaluation Method</h2> -<p>The ZIGGO Evaluation Toolkit is used to send and receive test data frames for the purpose of ensuring <code>accurate delay calculations</code>.</p> -<p>To achieve this accuracy, the toolkit needs to <strong>synchronize its time</strong> with the TSN switch and record a <strong>global hardware timestamp</strong> in the test data frames.</p> -<p>As shown in the diagram below, in a data flow link with $n$ network nodes, Node $1$ serves as the source node to send test data frames, Node $n$ acts as the destination node to receive test data frames, and all the intermediate nodes (Node $2$ to Node $n-1$) are TSN switches.</p> -<p>When a test data frame is sent from the source node, the hardware records the timestamp $t^+$ of when the frame was sent in the data frame. Finally, when the data frame arrives at the destination node, the destination node records the timestamp $t^-$ of when the frame entered that node. By calculating $(t^−−t^+)$, we can determine the end-to-end latency of the data frame.</p> + 💦 Software:Time Sync + Config for CaaS Switches + http://localhost:1313/switch/software_build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/software_build/ +<p>This repo contains source code to enable CaaS Switches’ time synchronization logic and set up TSN GCL (gate control list), switch forwarding rules (including to dual-DMA).</p> +<h2 id="build">Build</h2> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir build +</span></span><span class="line"><span class="cl"><span class="nb">cd</span> build +</span></span><span class="line"><span class="cl">cmake .. +</span></span><span class="line"><span class="cl">make +</span></span></code></pre></div><p>After successfully build, there should be two executables: “time_sync_app” & “switch_config”</p> +<h2 id="config">Config</h2> +<p>The “config” directory contains topology & TSN/CaaS schedule results.</p> +<p>This document takes the following topology as an example to give example configurations:</p> <p> @@ -1146,75 +967,248 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./device_test_demo.png" alt="device_test_demo" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./example_topology.png" alt="topology" loading="lazy" data-zoomable /></div> </div></figure> </p> -<blockquote> -<p>In this doc, $t^{dir}$ is used to represent the timestamp of data frames entering and leaving the hardware. Here, “dir” represents the direction of data frames entering or leaving the nodes, with " + " indicating data frames leaving the node and " − " indicating data frames entering the node.</p> -</blockquote> -<h2 id="test-data-frame-data-structure">Test data frame data structure</h2> -<p>In order to analyze the end-to-end latency of each data frame on complex network topologies, we have established specific guidelines for the content of data segments in the Ethernet frame structure. The structure of time-sensitive networking test data frames is as shown in the following table.</p> -<table> -<thead> -<tr> -<th>ield</th> -<th>Byte Length</th> -<th>Description</th> -</tr> -</thead> -<tbody> -<tr> -<td>Destination Address</td> -<td>6</td> -<td>Destination node MAC address</td> -</tr> -<tr> -<td>Source Address</td> -<td>6</td> -<td>Source node MAC address</td> -</tr> -<tr> -<td>VLAN Tag</td> -<td>4</td> -<td>Divided into four fields: VLAN Data Frame Type (0x8100), Priority, Canonical Format Indicator, and VLAN Number</td> -</tr> -<tr> -<td>Data Frame Type</td> -<td>2</td> -<td>Used to identify test data frames, set to 0x66ab</td> -</tr> -<tr> -<td>Reserved Bits</td> -<td>2</td> -<td></td> -</tr> -<tr> -<td><code>$t^+$ (TX Timestamp)</code></td> -<td>8</td> -<td>Timestamp when transmitted from the source node</td> -</tr> -<tr> -<td><code>$t^-$ (RX Timestamp)</code></td> -<td>8</td> -<td>Timestamp when received by the destination node</td> -</tr> -<tr> -<td>Data Stream ID (SEQ_ID)</td> -<td>2</td> -<td>Unique identifier for each data stream</td> -</tr> -<tr> -<td>Data Frame ID (PKT_ID)</td> -<td>4</td> -<td>Sequence number of data frames within each data stream, starting from 0</td> -</tr> -</tbody> -</table> -<h2 id="module-design">Module Design</h2> -<p>The overall module design for ZIGGO Evaluation Toolkit is depicted in the following diagram. The Time Synchronization module used by the Toolkit shares a design that is nearly identical to the Switch, and the diagram does not provide extensive details on the time synchronization-related modules.</p> -<p>The configuration module in the PS section (<code>software/pkt_gen_main.cpp</code>) communicates with the Data Frame Generation module by using the UIO driver and AXI4-Lite interface to send the transmission rules for the test data frames to relevant registers in the Data Frame Generation module (specifically, <code>hardware/IP_repo/pkt_gen_controller_v1.1/pkt_gen_controller_1.1/hdl/pkt_gen_controller_v1_1.v</code> is responsible for configuration, and <code>hardwire/HDL/axi_packet_generator.v</code> is responsible for generating and transmitting the data frames) using the global synchronized time as a reference for timing.</p> -<p>The Timestamp Marking module (<code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_tx.v</code> and <code>hardwire/HDL/hw_timestamp/tsu/tsu_axis_rx.v</code>) is located at the send and receive ports of the Ziggo-Evaluation-Toolkit. It is used to record the hardware timestamps of sent and received data frames within the test data frames.</p> -<p>The received data frames are ultimately uploaded to the PS section via a DMA channel (in our design, we currently use a time-synchronized DMA channel for transmitting test data frames) for statistical analysis (handled in the <code>process_critical_frame</code> function in <code>software/pkt_gen_control/pkt_gen.c</code>).</p> +<ul> +<li> +<p>***-config.json: Mainly describes the network’s topology, including the type of each node (device or switch), MAC address, PTP port status, and other node information, topology information, and MAC forwarding table. Example and explanation are as follows (note that the comments in the file are just for explanation, do not have such comments in actual use):</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Used to describe the information of each node in the network +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="mi">3</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Node's PTP port status +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// The quintuple represents the clock status of [local, ETH1, ETH2, ETH3, ETH4] +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Number meaning: (0: MASTER, 1: SLAVE, 2: PASSIVE, 3: DISABLED) +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 1, it means that the node is the master clock node; +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// If local is 0, it means that the node is the slave clock node. +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:14"</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"device"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:15"</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Topology information, composed of each link, each link is a directed edge +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// link ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Port number of the source node +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// port 0,1,2,3 correspond to ETH1,2,3,4 in reality +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Port number of the destination node +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst_port"</span><span class="p">:</span> <span class="mi">2</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Forwarding table, which can be generated by the scheduling algorithm in CNC +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// In the forwarding table where you send to yourself, the port is 4 (caas) / 5 (PS ETH for new hardware) +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Current node ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Output port number +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Entry ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Destination node ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">2</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"dst"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"src_port"</span><span class="p">:</span> <span class="mi">0</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div><p>If the master clock selection algorithm is used, only the configuration of nodes is different, and the rest are the same. The newly added <code>externalPortConfigurationEnabled</code> and <code>system_identity</code> fields are optional items, as shown in the example below:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"nodes"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:00:00:00:02:01"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"ptp_ports"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"externalPortConfigurationEnabled"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> <span class="c1">// 1: Manually configure the master-slave relationship, 0: Configure the master-slave relationship through the master clock selection algorithm, if this item is not written, the default is 0, that is, configure the master-slave relationship through the master clock selection +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"system_identity"</span><span class="p">:</span> <span class="p">{</span> <span class="c1">// Clock node's clock parameters, used for comparison in the master clock selection algorithm, if this item is not written, the default is the configuration written below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority1"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// First priority +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockClass"</span><span class="p">:</span> <span class="mi">248</span><span class="p">,</span> <span class="c1">// Clock level +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clockAccuracy"</span><span class="p">:</span> <span class="mi">254</span><span class="p">,</span> <span class="c1">// Clock accuracy +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"offsetScaledLogVariance"</span><span class="p">:</span> <span class="mi">17258</span><span class="p">,</span> <span class="c1">// Clock variance +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"priority2"</span><span class="p">:</span> <span class="mi">247</span><span class="p">,</span> <span class="c1">// Second priority +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"clock_identity"</span><span class="p">:</span> <span class="p">[</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">,</span><span class="mi">0</span><span class="p">]</span> <span class="c1">// Clock identifier, different clocks should have different parameters +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"links"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">],</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"fwd"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"><span class="p">}</span> +</span></span></code></pre></div></li> +<li> +<p>***-schedule.json: schedule file, contains each links’ schedule time interval & each CaaS switch’s computation time interval.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span><span class="c1">// All switches need to be listed to facilitate software recognition of configuration information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"switch"</span><span class="p">,</span> <span class="c1">// Node type, divided into "switch" and "device" +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Node ID, corresponding to "src" and "dst" below +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"mac"</span><span class="p">:</span> <span class="s2">"00:0a:35:00:00:10"</span><span class="p">,</span> <span class="c1">// Node's physical MAC address +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> <span class="c1">// Can be empty, not used +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> <span class="c1">// Type is link, used to describe scheduling information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">14</span><span class="p">,</span> <span class="c1">// Source node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> <span class="c1">// Destination node ID of the link +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Output port number +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">3</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> <span class="c1">// Scheduling information +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> <span class="c1">// Scheduling cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Start time relative to the entire cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">5</span><span class="p">,</span> <span class="c1">// End time relative to the entire cycle +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> <span class="c1">// Job ID in CaaS, if not needed, it can be omitted +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span> <span class="c1">// Data stream ID +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"> <span class="p">},</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"type"</span><span class="p">:</span> <span class="s2">"link"</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from"</span><span class="p">:</span> <span class="mi">10</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"to"</span><span class="p">:</span> <span class="mi">15</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"from_port"</span><span class="p">:</span> <span class="mi">2</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"schedule"</span><span class="p">:</span> <span class="p">[</span> +</span></span><span class="line"><span class="cl"> <span class="p">{</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"period"</span><span class="p">:</span> <span class="mi">2048</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"start"</span><span class="p">:</span> <span class="mi">1</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"end"</span><span class="p">:</span> <span class="mi">6</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"job_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"flow_id"</span><span class="p">:</span> <span class="mi">0</span><span class="p">,</span> +</span></span><span class="line"><span class="cl"> <span class="nt">"pkt_size"</span><span class="p">:</span> <span class="mi">1500</span> <span class="c1">// Packet length, if not written, the default is 1500B, this item only exists on the path from Device to Switch +</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">}</span> +</span></span><span class="line"><span class="cl"> <span class="p">]</span> +</span></span><span class="line"><span class="cl"> <span class="p">}</span> +</span></span><span class="line"><span class="cl"><span class="p">]</span> +</span></span></code></pre></div></li> +</ul> +<h2 id="run">Run</h2> +<ul> +<li>Copy topology & schedule file to build dir:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-config.json build/config.json +</span></span><span class="line"><span class="cl">cp <span class="o">[</span>topology name<span class="o">]</span>-schedule.json build/schedule.json +</span></span></code></pre></div><ul> +<li>Start time synchronization and initialize GCL and MAC forwarding table according to the configuration (it is recommended to run the time synchronization program on a core (with <code>taskset -c 1</code> command) to prevent kernel errors and crashes due to time synchronization):</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync +</span></span></code></pre></div><ul> +<li>The log output level is categorized into three types: WARN, INFO, and TRACE. The default log output level is TRACE (the most comprehensive output information, including DEBUG logs). The log output level can be set with the -l parameter:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l w <span class="c1"># WARN level</span> +</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l i <span class="c1"># INFO level</span> +</span></span><span class="line"><span class="cl">taskset -c <span class="m">1</span> ./time_sync -l t <span class="c1"># TRACE level</span> +</span></span></code></pre></div><p><em>Notice that the time sync logic is supposed to run indefinitely as the node should sync to its neighbors again and again.</em></p> +<ul> +<li>Update GCL & switch forwarding rules:</li> +</ul> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">./switch_config +</span></span></code></pre></div> +- +
@@ -1593,5 +1515,92 @@ Our GCL is represented by 9 bits, with the highest bit representing whether the </span></span></code></pre></div> +💪 Hardware:FPGA bitstream & Petalinux system rootfs for TSN Evaluation Toolkit + http://localhost:1313/switch/hardware-build/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/switch/hardware-build/ +<p>This repo contains pre-build hardware & system rootfs to boot the <strong>Zynq AX7021</strong> FPGA board from SD card.</p> +<h2 id="file-downloading">File downloading</h2> +<p>Download the following file from <a href="https://cloud.tsinghua.edu.cn/d/8277c491a8bd4e6a8997/" target="_blank" rel="noopener">this</a> public link:</p> +<ul> +<li>BOOT.BIN</li> +<li>boot.scr</li> +<li>image.ub</li> +<li>rootfs.tar.gz</li> +</ul> +<h2 id="sd-card-partition">SD card partition</h2> +<p>In order to boot the CaaS Switch, you are supposed to have a micro SD card with >32GiB storage. Then use:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo apt-get install gparted +</span></span><span class="line"><span class="cl">sudo gparted +</span></span></code></pre></div><p>Parition it into two partition below</p> +<ul> +<li> +<p>BOOT: store boot files from petalinux</p> +<p>Free space preceding (MiB): 4</p> +<p>New size (MiB): 500</p> +<p>File system: fat32</p> +<p>Label: BOOT</p> +</li> +<li> +<p>ROOTFS: store debian system rootfs</p> +<p>Free space preceding (MiB): 0</p> +<p>Free space following (MiB): 0</p> +<p>File system: ext4</p> +<p>Label: ROOTFS</p> +</li> +</ul> +<h2 id="copy-files-into-sd-card">Copy files into SD card</h2> +<p>Mound SD card:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo mount /dev/sda1 /media/alinx/BOOT/ +</span></span><span class="line"><span class="cl">sudo mount /dev/sda2 /media/alinx/ROOTFS/ +</span></span></code></pre></div><p>Remove original files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo rm -rf /media/alinx/BOOT/* /media/alinx/ROOTFS/* +</span></span></code></pre></div><p>Copy files:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sudo cp BOOT.BIN boot.scr image.ub /media/alinx/BOOT +</span></span><span class="line"><span class="cl"> +</span></span><span class="line"><span class="cl">sudo tar -zxvf rootfs.tar.gz -C /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo cp -r ~/init_os.sh /media/alinx/ROOTFS/home/root/init_os.sh +</span></span><span class="line"><span class="cl">sync +</span></span><span class="line"><span class="cl">sudo chown root:root /media/alinx/ROOTFS +</span></span><span class="line"><span class="cl">sudo chmod <span class="m">755</span> /media/alinx/ROOTFS +</span></span></code></pre></div><h2 id="launch-the-switch">Launch the switch</h2> +<h3 id="1-launch-the-board">1. Launch the Board</h3> +<p>Plug the SD card into FPGA board, turn the switch to SD card boot mode.</p> <p> @@ -1233,11 +1227,12 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./device_arch.png" alt="device_arch" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./FPGA_boot_mode_switch.png" alt="SD boot" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>The maximum frame transmission period (superperiod parameter in <code>pkt_gen_main.cpp</code>) refers to the upper limit on the periodicity for sending data streams from the toolkit. Within this maximum frame transmission period, the Data Frame Generation module allocates a maximum of 32 time slots for all data streams. Each time slot is used to send all the data frames for the corresponding data stream at the specified transmission time.</p> -<p>As illustrated in the diagram, the evaluation toolkit sends two types of data streams: Stream 𝐹1 with a transmission period of 2𝑇 and Stream 𝐹2 with a transmission period of 4𝑇. The maximum frame transmission period for the evaluation toolkit is 6𝑇. In this scenario, the Data Frame Generation module sets up 5 time slots within the maximum frame transmission period and sends test data frames in sequential order according to the specified time slots.</p> +<h3 id="2-initialize-ps">2. Initialize PS</h3> +<p>Plug in SD card, setup AX7021 board to boot on SD, power on.</p> +<p>Connect a PC to the UART port of the board. We recommend using MobaXterm to connect the serial. Set up the Speed to 115200, Flow Control to None.</p> <p> @@ -1256,94 +1251,21 @@ Device1每次发送1个1500B的数据包，每个Switch都预留了1个时隙， <figure > <div class="flex justify-center "> - <div class="w-100" ><img src="./example_pkt_gen_period.png" alt="example_pkt_gen_period" loading="lazy" data-zoomable /></div> + <div class="w-100" ><img src="./moba_serial.png" alt="MobaXterm" loading="lazy" data-zoomable /></div> </div></figure> </p> -<p>Users can configure the Ziggo-Evaluation-Toolkit to generate multiple data streams, and the configuration parameters for each data stream are as follows, with clear explanations provided in the comments of the <code>pkt_gen.h</code> header file:</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// pkt_gen_app\pkt_gen_control\pkt_gen.h -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> -</span></span><span class="line"><span class="cl"><span class="cm">/** -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @brief Set the pkt gen slot object -</span></span></span><span class="line"><span class="cl"><span class="cm"> * -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param slot_id 0~31, indicate a slot in pkt_gen IP core -</span></span></span><span class="line"><span class="cl"><span class="cm"> * IMPORTANT: tx_offset for each slot id should be monotonic increasing -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param seq_id sequence ID that uniquely identify a stream -</span></span></span><span class="line"><span class="cl"><span class="cm"> * To further utilize this field, it may be {job_id: 8bit, flow_id: 8bit} -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_number number of packets in one sent, should be 1 -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_start start of pkt_id -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param pkt_id_update update of next pkt_id -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param tx_offset transmission time inside a period, in ns -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param src_mac 6Byte array -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @param dest_mac 6Byte array -</span></span></span><span class="line"><span class="cl"><span class="cm"> * @return int -</span></span></span><span class="line"><span class="cl"><span class="cm"> */</span> -</span></span><span class="line"><span class="cl"><span class="kt">int</span> <span class="nf">set_pkt_gen_slot</span> <span class="p">(</span><span class="kt">int</span> <span class="n">slot_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">seq_id</span><span class="p">,</span> <span class="kt">uint16_t</span> <span class="n">pkt_number</span><span class="p">,</span> <span class="kt">uint32_t</span> <span class="n">pkt_id_start</span><span class="p">,</span> -</span></span><span class="line"><span class="cl"> <span class="kt">uint32_t</span> <span class="n">pkt_id_update</span><span class="p">,</span> <span class="kt">int64_t</span> <span class="n">tx_offset</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">src_mac</span><span class="p">,</span> <span class="kt">uint8_t</span> <span class="o">*</span><span class="n">dest_mac</span><span class="p">);</span> -</span></span></code></pre></div><p>The Timestamp Marking Module will write the timestamp of the current synchronized clock into the outgoing data frame just before it is transmitted by the MAC controller of the toolkit. When the MAC controller in the PL (Programmable Logic) receives the first bit of data in the frame from the physical link, the Timestamp Marking Module records the timestamp of the current synchronized clock. It subsequently writes this timestamp into the data frame during the packet reception process and hands it over to the statistical analysis module in the PS (Processing System) section for further analysis and processing.</p> -<h3 id="correspondence-between-software-and-hardware-registers">Correspondence between software and hardware registers</h3> -<p>The correspondence in terms of time synchronization is the same as in the Ziggo TSN Switch.</p> -<p>In this section, we will primarily focus on the correspondence related to data frame transmission configuration. The software registers’ addresses can be found in <code>software/pkt_gen_control/pkt_gen.c</code>.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-C++" data-lang="C++"><span class="line"><span class="cl"><span class="c1">// define global register address -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define GLOBAL_PERIOD_NS 0x00000000 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define GLOBAL_OFFSET_NS 0x00000008 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_VALID 0x00000010 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define SEQ_ENABLE_VLAN 0x00000014 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITE_LOCK 0x00000018 -</span></span></span><span class="line"><span class="cl"><span class="cp"></span> -</span></span><span class="line"><span class="cl"><span class="c1">// define write lock value -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define NOT_WRITING 0x00000001 -</span></span></span><span class="line"><span class="cl"><span class="cp">#define WRITING 0x00000000 -</span></span></span><span class="line"><span class="cl"><span class="cp"></span> -</span></span><span class="line"><span class="cl"><span class="c1">// define address pointer for sequences -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="cp">#define SEQ_CONTENT 0x0000001c -</span></span></span></code></pre></div><p>The hardware registers are located in <code>tsn_device\IP_repo\pkt_gen_controller_v1.1\pkt_gen_controller_1.1\hdl\pkt_gen_controller_v1_1_S00_AXI.v</code>.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"><span class="k">if</span> <span class="p">(</span><span class="n">slv_reg_wren</span><span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="k">case</span> <span class="p">(</span> <span class="n">axi_awaddr</span><span class="p">[</span><span class="n">ADDR_LSB</span><span class="o">+</span><span class="nl">OPT_MEM_ADDR_BITS</span><span class="p">:</span><span class="n">ADDR_LSB</span><span class="p">]</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h000</span><span class="p">:</span> -</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 0 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg0</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">end</span> -</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h001</span><span class="p">:</span> -</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 1 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg1</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">end</span> -</span></span><span class="line"><span class="cl"> <span class="mi">9</span><span class="err">'</span><span class="nl">h002</span><span class="p">:</span> -</span></span><span class="line"><span class="cl"> <span class="k">for</span> <span class="p">(</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="mi">0</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o"><=</span> <span class="p">(</span><span class="n">C_S_AXI_DATA_WIDTH</span><span class="o">/</span><span class="mi">8</span><span class="p">)</span><span class="o">-</span><span class="mi">1</span><span class="p">;</span> <span class="n">byte_index</span> <span class="o">=</span> <span class="n">byte_index</span><span class="o">+</span><span class="mi">1</span> <span class="p">)</span> -</span></span><span class="line"><span class="cl"> <span class="k">if</span> <span class="p">(</span> <span class="n">S_AXI_WSTRB</span><span class="p">[</span><span class="n">byte_index</span><span class="p">]</span> <span class="o">==</span> <span class="mi">1</span> <span class="p">)</span> <span class="n">begin</span> -</span></span><span class="line"><span class="cl"> <span class="c1">// Respective byte enables are asserted as per write strobes -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="c1">// Slave register 2 -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="n">slv_reg2</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">]</span> <span class="o"><=</span> <span class="n">S_AXI_WDATA</span><span class="p">[(</span><span class="n">byte_index</span><span class="o">*</span><span class="mi">8</span><span class="p">)</span> <span class="o">+:</span> <span class="mi">8</span><span class="p">];</span> -</span></span><span class="line"><span class="cl"> <span class="n">end</span> -</span></span><span class="line"><span class="cl"><span class="p">...</span> -</span></span></code></pre></div><p>In this context, the hardware registers with names starting with “slv_reg” are each 32 bits wide, and their addresses are spaced by 4 bytes. So, for example, if the software-level address is $0x00000018$, you need to divide this address by 4, which results in $ 24/4 = 6$. Therefore, this address corresponds to the hardware register “<code>slv_reg6</code>” in the hardware module. This helps establish the correspondence between software and hardware registers.</p> -<h3 id="offline-analysis-and-design">Offline Analysis and Design</h3> -<p>In the <code>offline_analyze</code> branch of the Toolkit, we perform packet capture and analysis by forwarding packets from the Toolkit to a powerful desktop computer after the timestamps the incoming packets. This method ensures that even at gigabit speeds, no packets are dropped, and there are relatively minor hardware changes.</p> -<p>One aspect of the modification is that timestamps are not added to the data frames when they are transmitted from the toolkit. This can be seen in the <code>HDL/trimode_mac/simple_mac_no_shared.v</code> file where the “tsu_axis_tx” section is commented out.</p> -<p>Another aspect is the modification of the “frame_type” to change the direction of data frames. Previously, both PTP frames and test data frames were uploaded to the PS section via time-synchronized DMA, with IT traffic uploaded to PS_ETH. This split the traffic into two directions (“axis_switch_1_2”). Now, it has been split into three directions (“axis_switch_1_3”). For offline analysis, only PTP frames need to be transferred to the PS, while test data frames need to be separated and sent out from ETH2. This requires a finer-grained separation of traffic.</p> -<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c++" data-lang="c++"><span class="line"><span class="cl"> <span class="c1">// separate IT frames, ptp frames and critical frames -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="n">axis_switch_1_3</span> <span class="nf">axis_switch_1_3_inst</span> <span class="p">(</span> -</span></span><span class="line"><span class="cl"> <span class="p">.</span><span class="n">aclk</span><span class="p">(</span><span class="n">rx_fifo_clock</span><span class="p">),</span> <span class="c1">// input wire aclk -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">aresetn</span><span class="p">(</span><span class="n">rx_fifo_resetn</span><span class="p">),</span> <span class="c1">// input wire aresetn -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tvalid</span><span class="p">(</span><span class="n">rx_axis_fifo_tvalid_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tvalid -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tready</span><span class="p">(</span><span class="n">rx_axis_fifo_tready_8</span><span class="p">),</span> <span class="c1">// output wire [0 : 0] s_axis_tready -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdata</span><span class="p">(</span><span class="n">rx_axis_fifo_tdata_8</span><span class="p">),</span> <span class="c1">// input wire [7 : 0] s_axis_tdata -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tlast</span><span class="p">(</span><span class="n">rx_axis_fifo_tlast_8</span><span class="p">),</span> <span class="c1">// input wire [0 : 0] s_axis_tlast -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_axis_tdest</span><span class="p">(</span><span class="n">frame_type</span><span class="p">),</span> <span class="c1">// input wire [1 : 0] s_axis_tdest -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tvalid</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tvalid</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tvalid</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tvalid</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tvalid -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tready</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tready</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tready</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tready</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// input wire [2 : 0] m_axis_tready -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdata</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tdata</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tdata</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tdata</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [23 : 0] m_axis_tdata -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tlast</span><span class="p">({</span><span class="n">rx_axis_it_fifo_tlast</span><span class="p">,</span> <span class="n">rx_axis_ptp_fifo_tlast</span><span class="p">,</span> <span class="n">tx_axis_fifo_legacy_tlast</span><span class="p">[</span><span class="mi">1</span><span class="p">]}),</span> <span class="c1">// output wire [2 : 0] m_axis_tlast -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">m_axis_tdest</span><span class="p">(),</span> <span class="c1">// output wire [5 : 0] m_axis_tdest -</span></span></span><span class="line"><span class="cl"><span class="c1"></span> <span class="p">.</span><span class="n">s_decode_err</span><span class="p">()</span> <span class="c1">// output wire [0 : 0] s_decode_err -</span></span></span><span class="line"><span class="cl"><span class="c1"></span><span class="p">);</span> -</span></span></code></pre></div><p>The <code>tx_axis_fifo_legacy_tdata[1]</code> indicates sending from ETH2.</p> +<p>The default username and password are as follows:</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-json" data-lang="json"><span class="line"><span class="cl"><span class="err">username:</span> <span class="s2">"root"</span> +</span></span><span class="line"><span class="cl"><span class="err">password:</span> <span class="s2">"root"</span> +</span></span></code></pre></div><p>Execute the initilization script to set up the linux environment.</p> +<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">sh init_os.sh +</span></span></code></pre></div><p>You can freely configure the host name, IP address, and MAC address, etc with the script, and can modify the script if needed.</p> +<h3 id="3-connect-to-internet">3. Connect to Internet</h3> +<p>Connect the PC’s network port to the device’s <strong>PS</strong> network port (ETH0).</p> +<p>Set up PC’s corresponding port to be in the same subnet with the device (i.e., 192.168.137.x).</p> +<p>Afterwards, you can connect to the device through <code>ssh</code> and copy any Software files needed.</p> +<h3 id="4-run-the-software">4. Run the Software</h3> +<p>Please refer to the software part of this repo for further instructions.</p> - +
+ diff --git a/public/tags/index.html b/public/tags/index.html index 805c9a4..498b5a1 100644 --- a/public/tags/index.html +++ b/public/tags/index.html @@ -1,6 +1,6 @@ - @@ -4164,7 +4164,7 @@📈 TSNPerf 设计原理 + http://localhost:1313/tsnperf/principle/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/tsnperf/principle/ +<h2 id="现有方案的局限">现有方案的局限</h2> +<p>TSNPerf是一款专为时间敏感网络（Time-Sensitive Networking, TSN）设计的性能评测工具。它提供了全面的TSN网络性能评测功能，能够帮助网络工程师和研究人员深入了解并验证TSN网络设备的性能特征。为此，TSNPerf需要能够精准地向网络中发送关键数据包，以测试设备的时间同步性能和流量整形能力。然而，Linux操作系统提供的<code>send()</code>函数只能达到微秒级的发包精度，难以满足TSNPerf对高精度发包的要求。</p> +<p>为了直观地展示<code>send()</code>函数的发包精度限制，我们进行了一项测试。在测试中，我们使用<code>send()</code>函数以1毫秒为设定间隔，连续发送了10000个数据包。然后，我们记录了每两个相邻数据包之间的实际时间间隔，并计算了它们与预期的1毫秒间隔之间的误差。结果显示，即使没有任何背景进程/流量的干扰，相邻数据包的间隔任然达到了<em><strong>最高14微秒</strong></em>左右。接下来我们分析该现象的原因。</p> +<p>如下图所示，在 $t_0$ 时刻，程序调用 <code>send()</code> 函数向网络发送数据包，但实际上，数据包在 $t_1$ 时刻才会被发送到网络中去。这是因为，操作系统的网络协议栈需要花费一定的时间处理该数据包。我们将 $t_1-t_0$ 称之为网络栈的处理时延，这个时延通常在微秒级别。</p> +<p> + + + + + + + + + + + + + + + +<figure id="figure-linux网络栈处理时延"> + <div class="flex justify-center "> + <div class="w-100" ><img src="./principle_basic.png" alt="Linux网络栈处理时延" loading="lazy" data-zoomable /></div> + </div><figcaption> + Linux网络栈处理时延 + </figcaption></figure> +</p> +<h2 id="解决方案">解决方案</h2> +<p>Intel 的 I210 / I225 / I226 网卡，提供了 LaunchTime 功能，可以精准地控制数据包离开网口的时间（理论精度在 32 纳秒级别）。</p> +<p> + + + + + + + + + + + + + + + +<figure id="figure-launchtime原理"> + <div class="flex justify-center "> + <div class="w-100" ><img src="./principle_advanced.png" alt="LaunchTime原理" loading="lazy" data-zoomable /></div> + </div><figcaption> + LaunchTime原理 + </figcaption></figure> +</p> +<p>利用 LaunchTime，可以提高数据包的发送精度。如上图所示，对于一个需要在 $t_0$ 时刻发出的数据包，我们预留一段时间给网络栈的处理流程，提前在 $t_2$ 时刻就调用 <code>send()</code> 函数，保证数据包在 $t_0$ 前就在网卡的出队列口等待，LaunchTime 会在$t_0$时刻打开出队列的门，将数据包发出。</p> +<h2 id="性能验证">性能验证</h2> +<p>类似地，我们开启 LaunchTime 功能，以1毫秒为设定间隔连续发送10000个数据包，记录每两个相邻数据包之间的实际时间间隔与1毫秒之间的误差。 +结果如下图所示，所有数据包的发送时间误差不超过100纳秒，达到了TSNPerf对发包精度的要求</p> +<p> + + + + + + + + + + + + + + + +<figure id="figure-launchtime实验结果"> + <div class="flex justify-center "> + <div class="w-100" ><img src="./principle_advanced_performance.png" alt="LaunchTime实验结果" loading="lazy" data-zoomable /></div> + </div><figcaption> + LaunchTime实验结果 + </figcaption></figure> +</p> + +Tags
Markdown - 10 + 11 @@ -4178,14 +4178,14 @@Tags
TSNPerf - 10 + 11 ZIGGO - 9 + 10 diff --git a/public/terms/index.html b/public/terms/index.html index f303fd9..6cffd36 100644 --- a/public/terms/index.html +++ b/public/terms/index.html @@ -1,6 +1,6 @@ - @@ -4175,65 +4175,65 @@- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4319,17 +4319,17 @@ @@ -4318,17 +4318,17 @@- ⌚ TSNPerf 检测内容及使用表 + >☀ 某品牌交换机报告
- ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表
- 在Publisher启动接收程序
- + ← ☀ 某品牌交换机报告 + >⌚ TSNPerf 检测内容及使用表 May 1, 2024 diff --git a/public/tsnperf/index.html b/public/tsnperf/index.html index 4691e95..c5bdcc8 100644 --- a/public/tsnperf/index.html +++ b/public/tsnperf/index.html @@ -1,6 +1,6 @@ - @@ -4219,15 +4219,19 @@
ZIGGO TSNPerf
- +@@ -4243,19 +4247,19 @@+ + +
+
-☀ 某品牌交换机报告+⌚ TSNPerf 检测内容及使用表- TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动
+ 时间同步测试，流量整形测试，网络配置测试May 1, 2024
ZIGGO TSNPerf
- +diff --git a/public/tsnperf/index.xml b/public/tsnperf/index.xml index e73c56e..0963fcf 100644 --- a/public/tsnperf/index.xml +++ b/public/tsnperf/index.xml @@ -12,6 +12,15 @@ http://localhost:1313/tsnperf/ +-
+
-⌚ TSNPerf 检测内容及使用表+☀ 某品牌交换机报告- 时间同步测试，流量整形测试，网络配置测试
+ TSNPerf 使用网卡硬件时间戳功能达到纳秒级抖动May 1, 2024
- +
+☀ 某品牌交换机报告 + http://localhost:1313/tsnperf/report/ +Wed, 01 May 2024 00:00:00 +0000 +http://localhost:1313/tsnperf/report/ +<p>详细报告请查看<a href="http://localhost:1313/pdf/switch_report.pdf">这里</a>。</p> + +⌚ TSNPerf 检测内容及使用表 http://localhost:1313/tsnperf/manual/ @@ -167,15 +176,6 @@- -
-☀ 某品牌交换机报告 - http://localhost:1313/tsnperf/report/ -Wed, 01 May 2024 00:00:00 +0000 -http://localhost:1313/tsnperf/report/ -<p>详细报告请查看<a href="http://localhost:1313/tsnperf/report/switch_report.pdf">这里</a>。</p> - -📈 TSNPerf 使用指南 http://localhost:1313/tsnperf/configuration/ diff --git a/public/tsnperf/manual/index.html b/public/tsnperf/manual/index.html index f8109c6..a1e9d0b 100644 --- a/public/tsnperf/manual/index.html +++ b/public/tsnperf/manual/index.html @@ -1,6 +1,6 @@ - @@ -4174,65 +4174,65 @@- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4315,7 +4315,15 @@-- ☀ 某品牌交换机报告 + + +
- -
- ☀ 某品牌交换机报告 - -
- 网络配置测试
- + ☀ 某品牌交换机报告📈 TSNPerf 使用指南 diff --git a/public/tsnperf/principle/index.html b/public/tsnperf/principle/index.html index 67c58ba..91ade7e 100644 --- a/public/tsnperf/principle/index.html +++ b/public/tsnperf/principle/index.html @@ -1,6 +1,6 @@ - @@ -4174,65 +4174,65 @@- 👍Hardware：Build the CaaS Device + >💦 互联互通测试TestBed搭建流程
- 👩🏼🏫 准备清单 + >📕 CNC脚本使用指南
- 💦 Software:Time Sync + Config for CaaS Device + >📕 ZIGGO Device使用手册
- 💦 互联互通测试TestBed搭建流程 + >💦 Software:Time Sync + Config for CaaS Device
- 📕 CNC脚本使用指南 + >👍Hardware：Build the CaaS Device
- 📕 ZIGGO Device使用手册 + >🔨 System Design —— PL & PS Co-operate
- 🔨 System Design —— PL & PS Co-operate + >🆒 Getting start
- 🆒 Getting start + >👩🏼🏫 准备清单
- 🎉 How to contribute - - -
- 👩🏼🏫 准备清单
- 🧠 基础知识列表 + + +
- 👩🏼🏫 准备清单
@@ -4318,17 +4318,17 @@ @@ -4316,15 +4315,7 @@ + @@ -4735,30 +4754,14 @@- + 📈 TSNPerf 使用指南⌚ TSNPerf 检测内容及使用表 diff --git a/public/tsnperf/report/lukas-blazek-mcSDtbWXUZU-unsplash.jpg.crdownload b/public/tsnperf/report/lukas-blazek-mcSDtbWXUZU-unsplash.jpg.crdownload new file mode 100644 index 0000000..248a258 Binary files /dev/null and b/public/tsnperf/report/lukas-blazek-mcSDtbWXUZU-unsplash.jpg.crdownload differ
- +
- -
- -
+