03-04-2016 02:39 AM
Hello! i am starter for xilinx and i need your help,
i'm using the SDSoC environment, after using petalinux, i'm going to create the 'sw.pfm' file for SDSoC, but i don't have ideas about generating this file, can you help me please?
03-04-2016 05:26 AM
03-04-2016 06:16 AM
yes i'm referencing to this document, but i don't know when i should insert '<xd:libraryFiles' and when i should insert more than one '<xd:bootFiles' ?
06-14-2016 11:45 AM
Typically, you create one xd:bootFiles element for each OS your platform supports. For example, if your platform supports Linux (sdscc/sds++ -target-os linux option) and standalone (sdscc/sds++ -target-os standalone option), create one xd:bootFiles element with xd:os="linux" and one xd:bootFiles element with xd:os="standalone". For Linux, you typically also define values for xd:bif, xd:devicetree, xd:linuxImage and xd:ramdisk.
The xd:libraryFiles element is used when your software platform contains libraries, header files or other files required to compile and link the applications that run on your platform.
For example, if your software platform contains libraries (located in a subfolder of your platform) required to link the ELF, specify the xd:libDir value with the path to the folder containing the libraries (multiple paths can be separated by the colon character ':'). When SDSoC links your application, it adds -L <path_specified_by_xd:libDir> option for you. The user can specify -l <library_name> in the SDSoC GUI or makefile to specify platform libraries, or if xd:libName is defined, SDSoC will add -l <library_specified_by_xd:libName> as a linker option.
Similarly, include paths for header files found in the platform can be specified using xd:includeDir.
For descriptions of the software platform elements and schema, see the document "SDSoC Environment Platforms and Libraries (UG1146)" Chapter 2 SDSoC platforms.