Page History

• 
  

  Hide If
  special @anonymous
  Status colour Yellow title MOVED .BSP Development Guide vPD16.1.0

...

...

This Quickstart provides you with the tools and know-how to install and work with the Linux Board Support Package (BSP) for the phyCORE-AM57x Rapid Development Kit. This Quickstart shows you how to do everything from installing the appropriate tools and source, to building custom kernels, to deploying the OS, to exercising the software and hardware. Please refer to the phyCORE-AM57x Hardware Manual for specific information on board-level features such as jumper configuration, memory mapping and pin layout for the phyCORE-AM57x System on Module (SOM) and baseboard. Additionally, gain access to the SOM and baseboard schematics for the phyCORE-AM57x Rapid Development Kit by registering at the following: http://phytec.com/support/registration/. 

...

Yocto development requires certain packages to be installed. Run the following commands to ensure you have the packages installed: 

sudo apt-get install git build-essential diffstat texinfo gawk chrpath doxygen dos2unix lib32stdc++6 lib32ncurses5 lib32z1 libc6-dev-i386 cpio

...

sudo dpkg-reconfigure dash 
# Respond "No" to the prompt asking "Install dash as /bin/sh?"
bash

Repo Tool

...

Download and install the repo tool. This tool is used to obtain Yocto source from Git.

...

Note

The Code Composer Studio (CCS) package that is required for the build cannot be downloaded automatically. Download it here: https://www.ti.com/licreg/docs/swlicexportcontrol.tsp?form_type=2&prod_no=CCS6.1.3.00033_linux.tar.gz&ref_url=http://software-dl.ti.com/ccs/esd/CCSv6/CCS_6_1_3/ You will need to create a TI account to access the file. Once the file has been downloaded, move it to /opt/PHYTEC_BSPs/yocto_dl, then run the following command: Code Block touch /opt/PHYTEC_BSPs/yocto_dl/CCS6.1.3.00033_linux.tar.gz.done This will tell the Yocto build that the file has already been downloaded.

...

Note

The binutils package that is required for the build has been moved and can be downloaded here: http://releases.linaro.org/archive/15.01/components/toolchain/binutils-linaro/binutils-linaro-2.25.0-2015.01-2.tar.xz Once the file has been downloaded, move it to /opt/PHYTEC_BSPs/yocto_dl, then run the following command: Code Block touch /opt/PHYTEC_BSPs/yocto_dl/binutils-linaro-2.25.0-2015.01-2.tar.xz.done This will tell the Yocto build that the file has already been downloaded.

...

Note
The leading whitespace between the " and the package name is necessary for the append command.

...

If you need to add a layer to the BSP, clone or extract it to the $YOCTO_DIR/sources/ directory. Then, modify $YOCTO_DIR/build/conf/bblayers.conf to include this new layer in BBLAYERS:

...

1. If modifying the root filesystem, remove the existing:

   Code Block
   sudo rm -rf /media/rootfs/*

   
   

2. Load the new filesystem to the SD Card. 

   Code Block
   sudo tar -zxf tisdk-rootfs-image-am57xx-phycore-rdk-20160128044033.rootfs.tar.gz -C /media/rootfs; sync;

    

    

   
   

   
   

Kernel

...

• ipaddr - A dedicated IP address for the SOM. This is crucial if TFTP will be used for updating the device's images at any point.

• serverip - IP address of the host or another machine. serverip corresponds to where the TFTP directory, if it exists, is located.

• gatewayip - Gateway IP for the network. This is only necessary if the TFTP directory is located on another network.

• netmask - Netmask for the network: typically 255.255.255.0. This is only necessary if the TFTP directory is located on another network.

• tftploc (required for TFTP) - Location of the path to the images on the TFTP server on the host system, setup in Section 4.4.1TFTP. Set the variable accordingly by referencing the following examples:

  File Path	U-Boot Command
  /var/lib/tftpboot/PHYTEC/am57xx/PD16.1.0	setenv tftploc PHYTEC
  /var/lib/tftpboot	setenv tftploc

  
  

• rootpath (required for NFS) - Location of the path to the NFS Directory on the host system, set up in Section 4.4.2NFS. Ex: /home/<user>/NFS

Use the following command to verify that all of the environment variables are set as intended:

...

setenv bootcmd 'run boot_mmc'
saveenv

...

Custom Boot

Unique boot configurations can be created by defining the desired environment variable settings and setting bootcmd to run its contents. The following is an example:

...

The images to be flashed will need to be copied to the /boot  or /rootfs/boot/ partition of a properly formatted SD card as described in the Creating a Bootable SD CardCreatingaBootableSDCard section of the Quickstart.

...

uuidgen
<first UUID generated>
 
uuidgen
<second UUID generated>
 
uuidgen
<third UUID generated>

...

After making all required connections, power on the board and enter U-Boot. Set the UUIDs for the disk and rootfs to the generated values:

...