Intel® FPGA SDK for OpenCL™: Intel® Arria® 10 SoC Development Kit Reference Platform Porting Guide

ID 683788
Date 10/08/2019
Public
Document Table of Contents

3.1. Compiling the Device Tree Blob

You must compile the device tree blob contained in the FAT partition to match your Intel® Arria® 10 SoC Development Kit Reference Platform. Use the Device Tree Generator (sopc2dts) and the Device Tree Compiler (dtc) to generate the necessary device tree blob.
For detailed information on how to generate the device tree blob, refer to Rocketboards.org.
  1. Run base revision compile (aoc -bsp-flow=base) with your a10soc development kit BSP in the following location:
    $INTELFPGAOCLSDKROOT/board/a10soc
  2. Start an Embedded Command Shell and navigate to the Quartus project directory from your base revision compile.
  3. Invoke the following command to generate the .dts Device Tree file, which is a text representation of the Device Tree:
    sopc2dts --input board/board.sopcinfo  \
    --output a10soc.dts  \
    --board hps_a10_common_board_info.xml \
    --board hps_a10_devkit_board_info.xml \
    --board qsys_top_board_info.xml \
    --bridge-removal all --clocks

    The board.sopcinfo file is generated during the base revision compilation of your FPGA design. You may download the XML files from the Intel® Arria® 10 GHRD on Rocketboards.org.

    Attention: Ensure that the name of the Intel® Arria® 10 Hard Processor System in your board.qsys file matches the name used in Intel® Arria® 10 GHRD project you are downloading the XML files from. At the time this document was written, the name of the Intel® Arria® 10 Hard Processor System in board.qsys and in Intel® Arria® 10 GHRD project was a10_hps.

    Create your copy of the Intel® Arria® 10 SoC BSP from the SDK, and rename the instance of the Intel® Arria® 10 Hard Processor System in board.qsys to a10_hps.

  4. After you generate the .dts file, modify its contents by performing the following tasks:
    1. In the Device Tree (a10soc.dts), change the compatible field setting to altr, socfpga.
      board_irq_ctrl_0: unknown@0x10000cfa0 {
             compatible = "altr,socfpga";
      
             reg = <0x00000001 0x0000cfa0 0x00000004>,
                   <0x00000001 0x0000cf90 0x00000004>;
             reg-names = "IRQ_Mask_Slave", "IRQ_Read_Slave";
             interrupt-parent = <&a10_hps_arm_gic_0>;
             interrupts = <0 19 4>;
             interrupt-controller;
             #interrupt-cells = <1>;
             clocks = <&config_clk>;
      }; //end unknown@0x10000cfa0 (board_irq_ctrl_0)
      Note:

      The compatible field setting in a10soc.dts must match the driver code in aclsoc.c. If the two strings do not match, the driver installation process does not allow the kernel to probe the device. As a result, the interrupt is not registered and the host code fails.

      Code snippet in the aclsoc.c file:

      static const struct of_device_id aclsoc_of_match[] = {
           { .compatible = "altr,socfpga", },
           { /* end of list */ },
      };
  5. After you modify the .dts file and it is ready to probed by the platform driver, compile the device tree blob by invoking the following Device Tree Compiler command:
    dtc -f -I dts -O dtb –o a10soc.dtb a10soc.dts

    This command generates the a10soc.dtb file.

  6. Rename the a10soc.dtb file to socfpga_arria10_socdk_sdmmc.dtb.
    The socfpga_arria10_socdk_sdmmc.dtb file is needed later in Building the SD Card Image.
  7. If you modify any of the HPS settings in the design, you must regenerate the uboot.

Did you find the information on this page useful?

Characters remaining:

Feedback Message