08-26-2014 09:31 AM
Is there still no way to generate device tree for SDK versions after 2013.4 ?
no device tree folder appears when running the generator from https://github.com/Xilinx/device-tree-xlnx
What is the intended procedure for it? i.e. how will this work in the future?
08-27-2014 07:02 AM
08-26-2014 09:42 AM
no longer supported or maintained that way:
install petalinux 2014.2
use HDF file from vivado export
petalinux-config --get-hw-description
builds the tree
there is NO OTHER WAY (unless full manual!)
works for zynq, works for microblaze
08-26-2014 11:13 AM
I'm not trying to be argumentative, but just wanting to ensure I understand correctly. Are you confident of that and have seen that from Xilinx?
I don't believe that's the intent (and I could be wrong) but want to test it myself as I have not for a while.
The device-tree-xlnx repo on github says for Xilinx SDK (Vivado > 2014.1).
Thanks
John
08-26-2014 11:36 AM
uboot github links, also from inside uboot code point to the maintainers website, that has not been updated for years.
2014.1 should not be used for anything anyway, and in 2014.2 the HDF import works nicely..
thats the story.
and belive me, we have tried the SDK device tree generation, ONLY frustration....
08-27-2014 02:08 AM
Never used PetaLinux before. Can that even be run on Windows?
Is there any way for a Windows user to create a device tree?
08-27-2014 06:00 AM
Hi,
I just downloaded the device-tree-xlnx repo contents from github, added it as a repository to my SDK project in Windowsn (not using Petalinux), and generated the device trees for my project (system.dts, pl.dtsi, and ps.dtsi). They all look reasonable but I still need to test them. I'll let you know how it goes but looks promising so far.
Thanks
John
08-27-2014 06:45 AM
I got as far as getting the repository in SDK, but then it whined about no system.mss file. When I manually provided that it just built seemingly the same things as the normal BSP did, and still no devicetree to be found anywhere.
How did you generate the actual device tree after providing the repository?
Which SDK version are you using?
08-27-2014 06:46 AM
and it generates SAME device tree as petalinux 2014.2 --get-hw-description does?
for Zynq?
and for Microblaze?
I doubt!
08-27-2014 07:02 AM
08-27-2014 07:25 AM
What the.. ?
now it worked suddenly. I don't know what the difference was. Maybe I didn't select the whole folder as repository, only the "device-tree" folder inside of it?
Or maybe the device tree repository has to be in the workspace folder?
Thanks for the help anyway. I don't know if the tree will actually work though, but at least it generates now.
09-22-2014 06:57 AM
@trenz-al wrote:
no longer supported or maintained that way:
install petalinux 2014.2
use HDF file from vivado export
Then how do I have to integrate further devices into the device-tree? Like SPI or I2C slaves that are not in PL but outside of the Zynq? Do I need to use Vivado or can it be done in Petalinux directly?
09-23-2014 09:27 AM
Found out myself:
We can modify subsystems/linux/configs/device-tree/system-top.dts and override parts of the included and autogenerated files. See http://elinux.org/images/a/a3/Elce2013-petazzoni-devicetree-for-dummies.pdf
02-11-2016 02:14 PM
WHen I try the steps mentioned as the right answer, I do get some error. I could be doing something stupid too. Please find the attached figures.
It says Genreation failed and showed the error as shown in attached -jpg
then when i checked the SDK log , i can see that it says drivers and processor is not instantiated. Please do find the sdk.log attached.
Basically, it says processor instance not availble, driver instance not available , OS instance not available. I also see an error shown to TCL script in the sdk.log.
Also, as seen in the jpg, it says "No rule to make target "all".
I am beginer and pretty confused. any help would be grateful.
02-11-2016 02:27 PM
06-12-2017 01:56 AM
Hi I am using petalinux sdk 2017.1 and when i did petalinux-config --get-hw-description .... as it is in the user guide it is not generating any device tree in the plnx-workspace and i have my BSP for zynq in the same project directory on my virtual machine.
I couldnot see system-top.dts anywhere in my petalinux prj directory...
02-13-2019 07:29 AM
So does Xilinx no longer support the SDK flow at all? Are they shoe-horning people into using PetaLinux?
I was able to generate a device tree using SDK (despite the near utter lack of documentation on the process) and I get a system-top.dts, system.dts, pl.dtsi, pcw.dtsi, and zynqmp.dtsi.
Why is there both a system.dts and a system-top.dts? Which am I supposed to use, and what do I do with the other?
Like another poster said, there are large differences between the SDK generated zynqmp.dtsi and the one in the Linux kernel tree. Is the SDK generated device tree in-sync with the kernel version, and if so, why are they so different?