I am currently working with the Xilinx Platform Studio(XPS) tool to make an automated design with command line tools (without using GUI). I know how to build project using XPS in GUI mode, but don't know how to build a project with command line tools. I got some information about the command line tools usage from the "Embedded System Tools Reference Manual" and the "Command Line Tools User Guide".
But, I didn't get any information about following things:
How to select Bus interconnect type.
How to select Clock
How to select processor
How to select BRAM memory
How to make signals external
How to import our peripheral
How to select address
I did all the following steps in XPS command line
Creating a new .xmp project
Adding architecture, device, package speed
Language setting,simulation setting
loading ucf file
I don't know how to add peripheral, processor and interconnect bus type.
I am struggling at this stage only - I know how to synthesize, implementation, and Bitfile generation.
If anybody knows information about these things using command line tools or any documents, Kindly reply to this post
I am afraid I do not know how to do this in XPS, but with Vivado all of these actions may be done via Tcl commands. Vivado works so much better than XPS. Unfortunately, Vivado does not support older Xilinx devices, so this may not be an option for you.
Related
Has anyone managed to connect a MicroBlaze instantiated in a Xilinx FPGA to anything other than the Xilinx tools (SDK or Vitis) for download and debugging?
I'm targeting a VCU29 and have licenses from Xilinx for Vivado etc; I have already extracted the libraries, source and GCC tools and constructed a makefile that will build my applications.
I'm resigned to using Vitis to load the initial bitfile but would really like to download the code and operate the JTAG from a tool that better matches SW development flow - Eclipse with OpenOCD? Perhaps over the built-in USB->Serial->JTAG interface? I believe I'd be content with just the interface offered through GDB.
I'd really like to know if anyone has tried this with either success or failure or maybe has one of those "Why don't you just..." lateral thinking ways of solving the problem.
Yes, my team does not use Vitis or SDK to build, deploy, or connect to MicroBlazes.
If you generate your BSP and a linker script with Vitis, you can then build using mb-gcc and link with mb-ld directly. To get these into your PATH, just source the settings script that Xilinx provides with their tools in <Vitis_root>/settings64.sh.
As for loading and debugging - if you source the same script, then you will have access to xsdb. Once you have XVC running (i.e. connecting to your board with Vivado HW manager), then you can launch xsdb and inside run connect or connect -xvc-url <host>::<port> if you are running on a different host. While connected, you can run targets to identify your MicroBlaze, and then select the MicroBlaze with target 5.
While you have the MicroBlaze selected, you can load <path to elf> and run a number of debugging commands. Just run help while connected to see your options.
I'm currently working on a project in IAR Embedded Workbench, and I've run into a problem that I can't seem to figure out.
I have written a program that interacts with hardware to get information from the board to perform calculations. The calculations are correct, and are being printed out to the Terminal I/O from the program.
I would like to know if it's possible to access these calculations for use in a third-party program.
We are expanding on a previous project which utilized additional hardware to send the information to a third-party program, but at this stage, it's not exactly an option.
Does IAR Embedded Workbench store this information somewhere, or are there settings I can reconfigure to allow for exporting data?
If you use the full DLIB library, and you run the application in the C-SPY debugger, you can use 'fopen', 'fprintf' and friends to write to a file on the host machine.
This work both when using the IDE or when running in batch mode using 'cspybat'.
I am using IAR Embedded Workbench IDE to develop an embedded solution for the Renesas RL78/G13. I am able to compile and run the project in debug mode. Now I would like to burn the program to flash in release mode. Can someone tell me how to do this?
Maybe the answer is a little bit late, but another option straight from IAR is to go to Make [F7 key] the project and the go to Menu Project -> Download -> Download active application.
Be carefull that the Reset line of the microncontroller is free so nothing sets it to OV, which will stop the microcontroller from running
IAR version for RL78 1.40.1
Certainly, you can use the Renesas Flash Programmer for downloading the hex file into the microcontroller. The Renesas flash Programmer install package, you can get from the website from supplier.
Is there a way to run same test(for example Lightweight Hotspots) multiple times in Intel VTune Amplifier XE ??? It is annoying to do multiple clicks to perform a single test. I have looked though documentation, but found nothing.
Thanks !
There are two things to advice:
First, once you have set up a project and collected Lightweight Hotspots for it, you should be able to just right-click the project in the Project Navigator (if you are using the standalone GUI) or Solution Explorer (if you are using Visual Studio integration) and click the recently used analysis type to run it again.
Second, if you are running really many collections, it may be that using amplxe-cl command line is the way to go. The easiest way to set up the command line to collect the data is to use Get Command Line dialog available from New Analysis window by clicking a button at the right-bottom corner. A copy-paste to a console should be mostly enough.
A couple of screenshot below should support the two bullets above.
Running a recent analysis again from Project Navigator:
Generating a command line for VTune collection with amplxe-cl:
This is my first question after leeching over here for some time.. So spare me.
I need to apply the iZotope Vinyl VST effect to some audio files via CLI or C++ (so language doesn't really matter), it has to work on a Mac or on a Unix based system. I've researched all over the webs and can't find any working solution.
I've tried using MissWatson, a command line utility, this works but my result audio files are silent...
./MissWatson -plugin=Vinyl -input-file="/Users/Sjaq/Desktop/test.wav" -output-file="/Users/Sjaq/Downloads/MissWatson-v1.0-mac/res.wav" -parameter=1:0.6,2:0.6,11:0.4
Then I tried using the Steinberg VST SDK by creating a host application, starting from the vstvalidator provided by the SDK. But when I try to load the VST I get this error:
2010-12-01 16:57:40.774 vstvalidator[4654:903] Error loading /Library/Audio/Plug-Ins/VST/Vinyl.vst/Contents/MacOS/Vinyl: dlopen(/Library/Audio/Plug-Ins/VST/Vinyl.vst/Contents/MacOS/Vinyl, 262): no suitable image found. Did find:
/Library/Audio/Plug-Ins/VST/Vinyl.vst/Contents/MacOS/Vinyl: no matching architecture in universal wrapper
And I don't know what to do. I'm pretty new to C++ and and made a few apps without any issues, but this time I've hit a dead end.
I've read about pyvst but it seems to need a DLL for the VST so that didn't work either.
I'm the author of MissWatson, and as you probably noticed on the webpage, I unfortunately was required to close-source the code, so I can't really ask you for more diagnostic information, since I wouldn't be able to patch MissWatson if it's a bug there. However, I would recommend running MissWatson with the -verbose switch and perhaps logging that output to file if that floods your terminal. You might find something in that output which helps you to diagnose the problem.
Anyways, as for the error in your VST host, I have a feeling that you are compiling your app as a 64-bit executable and trying to load a 32-bit plugin. Since hardly any VST/AU plugins (and also sequencers, for that matter) have made the leap to 64-bit, you'd be better off just compiling your app as a 32-bit x86 binary.
By default, the "debug" configuration in Xcode only builds your app for the native architecture of your machine to save time during compilation. I would advise that you disable this feature in your project's build settings and always build with the architectures you plan to ship with. This will prevent weird cross-architecture types of errors like the one you saw above.
Edit: I have since started a new command-line VST host to replace MissWatson which is called MrsWatson. You should try using this tool instead.
Perhaps you can port the source code of this open source vst host to match your platforms?
http://www.hermannseib.com/english/vsthost.htm
Scroll down to the bottom of the page.
Hope it helps.