-
Notifications
You must be signed in to change notification settings - Fork 2
AWB example setup command line
All manipulations of a project using the awb tools are done in the context of a workspace. The command line tool for manipulating an awb worksapce is awb-shell.
We first use awb-shell to create a workspace (called demo) and then to check out a basic set of packages needed to build a simple design. Note awb-shell can be used either with the command specified directly on the command line or interactively in a shell-like mode (with TAB completion).
// Optionally create a directory to hold workspaces % mkdir workspaces % cd workspaces // Create a new workspace % awb-shell create workspace demo % cd demo
You will probably see the following message about using a default workspace. This is fine, because you haven’t yet created a workspace.
Warning: No valid workspace found!!!
Check the value of $AWBLOCAL and your ~/.asimrc file
A default value of /usr/local/etc/asim/ws/HEAD is being used.
You may also see an error message complaining that it cannot locate the file libawb.so.0. In this case, you will need to run ‘ldconfig’ as root to fix the problem.
One of the useful features of awb is the ability to combine source modules from various source code repositories. The source trees checked out are called packages in awb’s terminology. So, now we will use interactive mode to check out some packages.
// Checkout some packages (in interactive mode) % awb-shell awb> clone package asimcore awb> clone package leap awb> clone package leap-platforms awb> clone package leap-multifpga awb> quit
Occasionally, you should update all your packages to reflect checked in changes to the repositories. That can be accomplished with the following command:
% awb-shell update package all
All of these actions can be performed with here the GUI version of awb-shell. See how awb example setup GUI
You can now look at the examples of how to build and run a design using the command line or GUI.