Visible to Intel only — GUID: fbu1629812453681
Ixiasoft
1. About the Time-Sensitive Networking for Drive-on-Chip Design Example
2. Getting Started with the TSN for Drive-on-Chip Design Example
3. Porting the Intel MAX 10 Drive-On-Chip design to the Cyclone V SoC Development Board
4. Running HPS Software for the TSN Drive-on-Chip Design
5. Connecting the Cyclone V SoC Development board to the Tandem 48 V Motion-Power board
6. Running the Program
7. TSN Configuration Example
8. Document Revision History for AN 957: Time-Sensitive Networking for Drive-on-Chip Design Example
A. Example .qsf for Pin Assignments and Attributes
B. Top-level Verilog HDL File Example
C. YOCTO Build Patch File (cvsx_doc_tsn_2_3-rt) for the TSN Drive-on-Chip Design Example
D. Script to read and change MAC addresses from Cyclone V SoC EEPROM
2.1. Hardware Requirements for the TSN for Drive-on-Chip Design Example
2.2. Software Requirements for the TSN for Drive-on-Chip Design Example
2.3. Configuring the Cyclone V SoC Development Board for the TSN for Drive-on-Chip Design Example
2.4. Programming the FPGA for the TSN for Drive-on-Chip Design Example
2.5. Creating an SD Card Image for the TSN for Drive-on-Chip Design Example
2.6. Turning on the Cyclone V SoC Development Board for the TSN for Drive-on-Chip Design Example
2.7. Configuring the TSN IP
3.1. Changing File Names, Revision Name, and Target Device for the TSN Drive-on-Chip Design Example
3.2. Modifying the Drive-On-Chip Qsys System
3.3. Adding the TTTech TSN IP to the Qsys system
3.4. Connecting the TSN and Drive-on-Chip Subsystems
3.5. Compiling the Quartus Prime Design and Top-Level Module
3.6. Generating the Preloader
3.7. Generating a .jic file
3.8. Compiling the Drive-on-Chip Design Software in Nios II Software Build Tools
3.9. Launching a YOCTO Build
3.10. Building an SD Card Image for the TSN Drive-on-Chip Design Example
3.11. Changing MAC Addresses
3.12. Reading and Checking Physical Addresses on the Cyclone V SoC Development Board
Visible to Intel only — GUID: fbu1629812453681
Ixiasoft
3.4. Connecting the TSN and Drive-on-Chip Subsystems
When connected, the HPS can control the TSN drive-on-chip design. You connect them via shared memory mechanism.
Intel recommends three connections.
- Connect the port h2f-axi_master of the block hps_0 of the TSN subsystem to the one port of the sys_console_debug_ram block.
- Enable Dual_port access in the sys_console_debug_ram block.
The first memory mapped slave port (s1) connects to the HPS. The second port (s2) connects to the Nios II soft processor. The drive-on-chip subsystem reads position, speed, configurations commands for the drives from this memory.Figure 25. Turn on Share memory Dual-port access
- Enable Dual_port access in the sys_console_debug_ram block.
- Optionally, create a connection between the HPS and the FPGA DDR3 memory.
- Connect the h2f_axi_master master port of the HPS to the avl_0 port of the mem_if_ddr3_emif_0 (external memory interface).
This connection allows the access to the drive-on-chip subsystem DDR3 memory from the HPS (from Linux)
- Connect the h2f_axi_master master port of the HPS to the avl_0 port of the mem_if_ddr3_emif_0 (external memory interface).
- To expose some peripherals of the TSN subsystem to the JTAG chain, add a connection between port s0 (Avalon MM Slave) of the mm_bridge_0 (TSN subsystem) to the port master of the jtag_master block in the drive-on-chip subsystem.
Figure 26. Qsys System
- Click Generate HDL.
Related Information