Actions
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 329 subscribers
  • Views 1943 views
  • Users 0 members are here
Related

DTC: non-existing node

suppamax

Hi everybody,

I'd like to write a linux application for microzed.
The Zynq will also use some logic in PL, in particular an AXI_DMA a custom IP (AXI_counter) streaming data to it.

I generated the DTS following this wiki: http://www.wiki.xilinx.com/Build+Device+Tree+Blob

The problem is that when I try to generate the device tree blob I got this error

>dtc -I dts -O dtb -o xilinx.dtb xilinx.dts
ERROR (phandle_references): Reference to non-existent node or label "AXI_counter_0"

ERROR (phandle_references): Reference to non-existent node or label "AXI_counter_0"

ERROR: Input tree has errors, aborting (use -f to force output)


Parents
  • 0

    Hi suppamax,

    Okay, so since your AXI_counter_0 is a piece of custom IP then I assume you are planning to write a driver for it?

    If so, then all you need to do is create an entry in the devicetree that tells the kernel which device driver your AXI_counter_0 instance will use and also point it to where the custom IP is located in memory space.

    As part of our "Implementing Linux on the Zynqu00AE-7000 All Programmable SoC (ISE 14.2)" SpeedWay training.  We showed an example custom IP peripheral called "led-brightness" and a Linux driver which allowed access to that peripheral.  Within the devicetree, an entry was needed to tie the device driver to the area of memory where the custom IP was instantiated.

    led-brightness@412000000 {
       compatible = "avnet,led-brightness";
       reg = <0x41200000 0x20>;
    };

    Regards,

    -Kevin

Reply
  • 0

    Hi suppamax,

    Okay, so since your AXI_counter_0 is a piece of custom IP then I assume you are planning to write a driver for it?

    If so, then all you need to do is create an entry in the devicetree that tells the kernel which device driver your AXI_counter_0 instance will use and also point it to where the custom IP is located in memory space.

    As part of our "Implementing Linux on the Zynqu00AE-7000 All Programmable SoC (ISE 14.2)" SpeedWay training.  We showed an example custom IP peripheral called "led-brightness" and a Linux driver which allowed access to that peripheral.  Within the devicetree, an entry was needed to tie the device driver to the area of memory where the custom IP was instantiated.

    led-brightness@412000000 {
       compatible = "avnet,led-brightness";
       reg = <0x41200000 0x20>;
    };

    Regards,

    -Kevin

Children
No Data