![Phytec phyBoard Wega AM335x Application Manual Download Page 101](http://html1.mh-extra.com/html/phytec/phyboard-wega-am335x/phyboard-wega-am335x_application-manual_1554191101.webp)
Advanced
Information
©
PHYTEC Messtechnik GmbH 2014 L-792e_1
85
4.5.1.3
Set the Git Configuration
The Board Support Package is strongly based on
Git
.
Git
needs some information from you
as a user to be able to identify which changes were done by whom. So at least set the
name
and
in your
Git
configuration, otherwise building the BSP generates many warnings.
Enter the following two commands to directly set them
git
config
‐‐
global
user.email
git
config
‐‐
global
user.name
“name
surname”
4.5.1.4
Build the Board Support Package and Install the SDK
In this chapter we build our Board Support Package with the help of the
Yocto Project
.
First we create a folder for the BSP in our example we use the path as it is in our virtual
machine hard disk image.
Enter the following commands:
sudo
mkdir
‐
p
/opt/PHYTEC_BSPs/phyBOARD
‐
WEGA/
sudo
chmod
‐
R
777
/opt/PHYTEC_BSPs/
cd
/opt/PHYTEC_BSPs/phyBOARD
‐
WEGA/
Download the
phyLinux
script and set execution privileges:
wget
+x
./phyLinux
The
phyLinux
script is a basic management tool for PHYTEC
Yocto
BSP releases. It is mainly a
tool to get started with the BSP structure. You can get all the BSP sources without the need
of interacting with repo or git.
Start the phyLinux script
./phyLinux
init
During the execution of the init command, you need to choose your processor platform
(am335x), PHYTEC's BSP release number (PD15.1.1) and the hardware you are working on
(phyboard-wega-am335x-1, or phyboard-wega-am335x-2).
After you downloaded all the meta data with
phyLinux
, you have to set up the shell
environment variables. This needs to be done every time you open a new shell for starting
builds. We use the shell script provided by poky in its default configuration.
Type:
source
sources/poky/oe
‐
init
‐
build
‐
env