while working on Xilinx EDK to implement a simple design using embedded softcore IP, we have hit a few hurdles, following is the detailed outline of the problems we are facing.
as per our understanding, we followed the following steps involved for a solution using EDK design flow
step 1- Xilinx ISE
- Create new project
-add new source - select embedded processor, this will lead to opening of XPS, wherein we can select or create a softcore IP.
step 2- Xilinx Platform Studio (xps)
-create new board support package (BSP), enter information about softcore IP , peripherals and other details.
- export hardware design to sdk
step 3- Xilinx SDK
- Create a Hardware Platform- linking hw
- Setting up software Environment- creating xilinx C project
Problem-->
I created a project in xilinx ise, then added an embedded processor using xps, but when I am trying to generate programming file, I get the following error.
ERROR:EDK - INFO:Security:67 - XILINXD_LICENSE_FILE is set to
'/opt/Xilinx/12.1/ISE_DS/EDK/data/core_licenses' in /home/h2o/.flexlmrc.
INFO:Security:68 - Please run the Xilinx License Configuration Manager
ERROR:Security:14 - No feature was available for 'XPS'.
ERROR:EDK:440 - platgen failed with errors!
ERROR:EDK -
Error while running "gmake -f system.make netlist".
ERROR: synthesizing XPS module failed!
To remove the gmake error, I have created an link to make for gmake already, and its there working successfully for sdk, but here it is showing error. to check if link is there or not I ran the "ln" command and got this output
h2o#h2o-Vostro-1015:~$ sudo ln -s /usr/bin/make /usr/bin/gmake
[sudo] password for h2o:
ln: failed to create symbolic link `/usr/bin/gmake': File exists
Also on the license front I am facing the problem, every time I open xps it shows me that license is not present and opens the xilinx license manager. I have registered at xilinx website and obtained the .lic license file, only few days ago.
every time I open xps, I have to follow the same process of adding xilinx.lic file (PFB screens for reference.)
Related
I have created an app in which I want to integrate P2P with Relay server. So I am trying to use Coturn Master project.
I followed the steps below for creating Make File and successfully produced .a file from the CMake project.
In my Terminal from Mac OS, I used below commands.
cd Project Directory
./configure
Make file is generated after this command.
make
Which created a libturnclient.a and turnutils_uclient exe file.
Now I want to use this library in my iOS project.
I need a guidance about how to proceed ahead. As there is a C project already created in Coturn Master.
So how do I use that library and compile that Project from Coturn master to my iOS project?
Path in the project is https://github.com/coturn/coturn/tree/master/src/apps/uclient
If anyone has done work on this can guide me.
Thanks in advance.
I am not used to work with kony platform and I have created simple app but I want to export it and run it as native iOS .xcocdeproj.
Kony Visualizer gives you different ways of building and viewing your app, depending on your needs. In Kony Visualizer Enterprise, you can build your app either from the Product menu, or from a command line. And you can view your built app either by previewing it on a mobile device, or by using device emulators and simulators that you configure. Please refer to this docs link to build for iOS using Kony Visualizer.
Please do this below steps.
once Kar file was build. go to your visualizer installation folder and go to plugins and then you can find com.kony.ios_8.2.28.v201811051627.jar file if you are using 8.2.28 version just for example.
Copy above file and rename it as zip file and unzip it.
once unzip was done inside you can find another zip file please unzip. ( ex: 8.2.28.zip)
you can see folder called VMAppWithKonylib.
now go open command-line tool and go to VMAppWithKonylib location.
now go to gen folder location inside your commandline. gen folder will inside VMAppWithKonylib.
7.now run this command - perl extract.pl konyappiphone.KAR
once extract done now go to VMAppWithKonylib and open project in xcode.
let me know if you are facing any more issues.
I have just updated my AIR SDK from version 23 to 25.
When running the command mxmlc, the following error occurs:
Error: Unable to access jarfile /../lib/mxmlc-cli.jar
Solution 1:
Make sure you have downloaded the Flex SDK and not the AIR SDK.
In the download page, there's link specifying:
Flex users will need to download the original AIR SDK without the new compiler.
Solution 2:
When the Adobe AIR SDK is installed it is sometimes installing files with wrong permissions.
The mxmlc-cli.jar file your lib directory probably has a permissions issue.
Try giving this file full permission and making sure it's not read only and everything should work fine.
If you are using Windows, just right click the files and set up the proper permissions in the security tab, and make sure the file is not read only.
If you are using Unix / Linux, run the following:
$ su -
# cd [AIRSDK install directory]
# chmod -R go+rx *
If you are using Mac OS:
Click the mxmlc-cli.jar file or to select it.
From the File menu, select Get Info. One of the windows shown below
appears. Click the disclosure triangle next to Sharing & Permissions
to display the file's permissions.
Click the lock and authenticate with an administrator account. Use
the menus next to users and groups to change the permissions.
This is an old one, but I've faced this problem several times and the fix is really minor.
You have to edit mxmlc or compile.
In the file there is a row which should be changed to:
SCRIPT_HOME=`dirname "$0"`
The error comes from missing " " around the $0.
I provide a Yocto SDK to cross-build an application for an embedded target. The application itself is built using CMake. The SDK setup script provides many necessary environment variables (like location of the cross-compiler, sysroot, etc.), which so far was enough to build the application.
However, since recently the application has a dependency to the Boost library (through the command find_package(Boost REQUIRED) in the CMakeLists.txt). Now CMake complains that it cannot find the library, even though it's installed in the SDK sysroot. But if I build the application directly in Yocto, it works fine.
After some research it turned out that Yocto generates a toolchain.cmake file which is added to the cmake call. In this file, the variable CMAKE_FIND_ROOT_PATH is set, which CMake needs to find libraries. Using such a toolchain file, I can also build using the SDK.
Now I'm wondering if Yocto provides any mechanism to export such a toolchain file with the SDK. Or alternatively if the SDK provides a script or something to automatically create a toolchain file directly on the SDK build host.
Or shall I just tell the users of the SDK to manually create a toolchain file and add it to their cmake call?
Assuming that you're using the image based SDK, i.e. building it with bitbake <image> -c populate_sdk, adding the following toimage.bb should fix it:
TOOLCHAIN_HOST_TASK += "nativesdk-cmake"
That should give you a OEToolchainConfig.cmake file in the SDK. After sourcing the SDK environment file, cmake will be an alias to cmake -DCMAKE_TOOLCHAIN_FILE=$OECORE_NATIVE_SYSROOT/usr/share/cmake/OEToolchainConfig.cmake to further help your developers.
I'd like to add to Anders answer that while it worked great for me to add nativesdk-cmake this way it did not work when I tried to add nativesdk-python3-numpy. After some googling I found this, suggesting that TOOLCHAIN_HOST_TASK has to be extended using _append instead of +=.
So I already was able to build the .bar file, but now I want to build the .bar file to be sent to the store with the package and signing.
So far I've tried this.
bbwp C:\xampp\htdocs\maddash\packaged\maddash.zip -g (password) -b 1.0.0 -o C:\xampp\htdocs\maddash\packaged\
and my error is..
failed to find signing key file
Did you register your keys from RIM and put them in the default location (%HOMEPATH%\Local Settings\Application Data\Research In Motion for Windows)
Did you update your SDK? Then check your keys in bbwp\bin and rename sigtool to author and move your file to the default location.
If not sufficient, try installing the native IDE and use the UI for managing the keys in the preferences
My personal opinion about this problem.
First. If you have your signing key, great for you, because BB changed the system of signing apps. (Now they use BBtokenID, related with your BBID and, in this moment, the webworks framework is the only one that doesn't support this tokens) (Come on, Hip, Hip, Hurrah! :P).
According to your command, one comment
bbwp C:\xampp\htdocs\maddash\packaged\maddash.zip -g (password) -b 1.0.0 -o C:\xampp\htdocs\maddash\packaged\
In the first paramenter yoy must add the FOLDER of your source code, not your zipped code.
If you have your keys where it corresponds, it will generate a bar file signed.
NOW, you must package it in a zip file. If you need more help with that, tell me :)