10-23-2014 11:39 AM
I am using SDK 2014.3 and trying to generate the device tree using this post http://www.wiki.xilinx.com/Build+Device+Tree+Blob.
Hardware design was generated using the Vivado 2014.2 and since then I upgraded it to 2014.3.
This is fairly easy and simple guide to follow. But when I'm trying to build it, I am getting follwing error.
ERROR : [Hsi 55-1457] File C:\zc706\device_tree_bsp_0\system.mss doesn't exist on disk
[Hsi 55-1535] Parsing MSS file C:\zc706\device_tree_bsp_0\system.mss failed
I don't understand why this error occurs.
02-04-2015 11:41 AM
Did you ever find a solution for this?
I'm using Vivado 2014.4 on Win7-64, and am unable to launch the SDK. The SDK is still looking for the old XML file. I know the .hwdef and .sysdef are archives containg an XML file, but that doesn't work.
I'm getting the same error messages that you reported, that is:
The following errors were found parsing W:\EFA0130\StandaloneBSP\system.mss
ERROR: [Hsi 55-1457] File W:\EFA0130\StandaloneBSP\system.mss doesn't exist on disk
ERROR: [Hsi 55-1535] Parsing MSS file W:\EFA0130\StandaloneBSP\system.mss failed
How did you resolve that?
Thanks for helping!
02-05-2015 10:22 AM
OK. The problem is because my Microblaze IP Integrator block design is set as an Out-Of-Context (OOC) module. I did that to reduce synthesis time but Vivado doesn't like it.
Setting the block design as a standard module (NOT OOC) resolves the problem.
02-08-2015 04:34 PM - edited 02-08-2015 04:34 PM
since the issue is resolved, can you mark this post as accepeted solution? this might be useful for other users too.
12-08-2015 02:46 AM
# Otherwise for SDK 2014.2 use this repo: git clone git://github.com/Xilinx/device-tree-xlnx.git
SDK Menu: Xilinx Tools > Repositories > New... (<bsp repo>) > OK
SDK Menu: File > New > Board Support Package > Board Support Package OS: device-tree > Finish
The .dts/.dtsi files are now located in <SDK workspace>/device_tree_bsp_0/ folder.
*** e.g. console=<tty>,<baudrate> root=/dev/ram rw ip=:::::eth0:dhcp earlyprintk
*** Some example values for <tty> are ttyPS0 when using Zynq, ttyUL0 when using the UART Lite soft ip, or ttyS0 when using the UART16550 soft ip.