SAMA5D2 Xplained Board

SoC Features

The Atmel | SMART SAMA5D2 series is a high-performance, ultra-low-power ARM Cortex-A5 processor based MPU. The Cortex A5 processor runs up to 500MHz and features the ARM NEON SIMD engine a 128kB L2 cache and a floating point unit. It supports multiple memories, including latest-generation technologies such as DDR3, LPDDR3, and QSPI Flash. It integrates powerful peripherals for connectivity (EMAC, USB, dual CAN, up to 10 UARTs, etc.) and user interface applications (TFT LCD controller, embedded capacitive touch controller, class D amplifier, audio PLL, CMOS sensor interface, etc.). The devices offer advanced security functions to protect customer code and secure external data transfers. These include ARM TrustZone, tamper detection, secure data storage, hardware encryption engines including private keys, on-the-fly decryption of code stored in external DDR or QSPI memory and a secure boot loader.

SAMA5D2 Chip Features

Kit Information

Kit Overview

SAMA5D2 Xplained

Access the console

The usual serial communication parameters are 115200 8-N-1 :

Baud rate 115200
Data 8 bits
Parity None
Stop 1 bit
Flow control None

Access the console on DEBUG serial port

The serial console can be accessed from two connectors. One is from the DEBUG port with the help of a TTL-to-USB serial cable (marked as DEBUG J1), another is from micro-A USB connector that gives access to the on-board serial-to-USB converter (marked as J14 EDBG-USB).

Using DEBUG on TTL-to-USB connector (DEBUG J1)

  • For Microsoft Windows users: Install the driver of your USB TTL serial cable. FTDI-based ones are the most popular, have a look to this page to get the driver:
  • Open JP2 to enable this DEBUG interface
  • Be sure to connect a 3.3V compatible cable and identify its GND pin. Place it properly according to the silkscreen and connect the cable to the board (J1)
    • For Microsoft Windows users: Identify the USB connection that is established, USB Serial Port should appear in Device Manager. The COMxx number will be used to configure the terminal emulator.
      ftdi serial line
    • For Linux users: Identify the serial USB connection by monitoring the last lines of dmesg command. The /dev/ttyUSBx number will be used to configure the terminal emulator.
      [605576.562740] usb 1-1.1.2: new full-speed USB device number 17 using ehci-pci
      [605576.660920] usb 1-1.1.2: New USB device found, idVendor=0403, idProduct=6001
      [605576.660933] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [605576.660939] usb 1-1.1.2: Product: TTL232R-3V3
      [605576.660944] usb 1-1.1.2: Manufacturer: FTDI
      [605576.660958] usb 1-1.1.2: SerialNumber: FTGNVZ04
      [605576.663092] ftdi_sio 1-1.1.2:1.0: FTDI USB Serial Device converter detected
      [605576.663120] usb 1-1.1.2: Detected FT232RL
      [605576.663122] usb 1-1.1.2: Number of endpoints 2
      [605576.663124] usb 1-1.1.2: Endpoint 1 MaxPacketSize 64
      [605576.663126] usb 1-1.1.2: Endpoint 2 MaxPacketSize 64
      [605576.663128] usb 1-1.1.2: Setting MaxPacketSize 64
      [605576.663483] usb 1-1.1.2: FTDI USB Serial Device converter now attached to ttyUSB0
      A /dev/ttyUSB0 node has been created.
  • Now open your favorite terminal emulator with appropriate settings

Using the micro-A USB connector (J14 EDBG-USB)

You can also access the serial console through the on-board serial-to-USB converter. In fact, the Atmel EDBG (Embedded Debugger) chip on the Evaluation Kit acts as a serial-to-USB converter and is loaded with a firmware that is able to talk USB-CDC protocol.

  • For Microsoft Windows users: Install USB drivers for Atmel and Segger tools. No need to install a driver on any regular Linux distribution.
  • Open JP1 to enable EDBG
  • Close JP2 to disable de DEBUG port J1 (needed to avoid conflict on the UART TX line)
  • Connect the USB cable to the board (J14 EDBG-USB)
    • For Microsoft Windows users: identify the USB connection that is established
      EDBG Virtual COM Port should appear in Device Manager. The COMxx number will be used to configure the terminal emulator.
      EDBG CDC UART Port
    • For Linux users: identify the USB connection by monitoring the last lines of dmesg command. The /dev/ttyACMx number will be used to configure the terminal emulator:
      usb 1-1.1.1: new high-speed USB device number 20 using ehci-pci
      usb 1-1.1.1: New USB device found, idVendor=03eb, idProduct=2111
      usb 1-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      usb 1-1.1.1: Product: EDBG CMSIS-DAP
      usb 1-1.1.1: Manufacturer: Atmel Corp.
      usb 1-1.1.1: SerialNumber: ATML0000001989463039
      hid-generic 0003:03EB:2111.0007: hiddev0,hidraw3: USB HID v1.11 Device [Atmel Corp. EDBG CMSIS-DAP] on usb-0000:00:1a.0-1.1.1/input0
      cdc_acm 1-1.1.1:1.1: ttyACM0: USB ACM device
  • Now open your favorite terminal emulator with appropriate settings


Demo archives

Media type Board Screen Binary Description
Yocto / Poky based demo
Boot on SPI Flash
+ rootfs on SD Card
SAMA5D2 Xplained - (~ 122 MB)
md5: 3cad7bf72f0956b58b0913dceb309e8e
Linux4SAM Yocto / Poky based demo
compiled from tag linux4sam_5.5
Follow procedure: #Flash_the_demo
PDA 4.3" (~ 141 MB)
md5: 34f54de52f95efad554a7d1d4e2e6fb5
PDA 7"
TM7000 (~ 141 MB)
md5: e7a2263d7cd06798d4bf5bbd753cb75b
PDA 7"
TM7000B (~ 141 MB)
md5: 47969f2fe6911622bd61c97df5b37d4c
SD Card image SAMA5D2 Xplained - linux4sam-poky-sama5d2_xplained-5.5.img.bz2 (~ 111 MB)
md5: a6291544511eec126ad89114b858968f
Linux4SAM Yocto / Poky based demo
compiled from tag linux4sam_5.5
Follow procedure: #Create_a_SD_card_with_the_demo
PDA 4.3" linux4sam-poky-sama5d2_xplained_pda4-5.5.img.bz2 (~ 133 MB)
md5: 957349bc761aebe25cdf9781b5912769
PDA 7"
linux4sam-poky-sama5d2_xplained_pda7-5.5.img.bz2 (~ 133 MB)
md5: c3d8d93cd8a0339c0796215ecd2c5f03
PDA 7"
linux4sam-poky-sama5d2_xplained_pda7b-5.5.img.bz2 (~ 133 MB)
md5: 264dfd11e11a2b5721f6bf6201953b97
BuildRoot based demo
SD Card image SAMA5D2 Xplained - linux4sam-buildroot-sama5d2_xplained-5.5.img.bz2 (~ 23 MB)
md5: 65fc33e1001f8fefc791ab5a0078ffe1
Linux4SAM BuildRoot based demo
compiled from tag linux4sam_5.5
Follow procedure: #Create_a_SD_card_with_the_demo

Create a SD card with the demo

You need a 1 GB SD card (or more) and to download the image of the demo. The image is compressed to reduce the amount of data to download. This image contains:

  • a FAT16 partition with the AT91Bootstrap, U-Boot and the Linux Kernel (zImage and dtb).
  • an ext4 partition for the rootfs.

Windows procedure

To write the compressed image on the SD card, you will have to download and install Rawrite32. This tool, which is a free software, is useful since it allows to get a compressed image as input. More information and extra help available on the Rawrite32 website

  • Insert your sdcard and launch Rawrite32:


  1. Select the demo image.
  2. Check if the image is not corrupted with the md5 provided in the Demo Archive section.
  3. Select the device corresponding to your SD card.
  4. Click on Write to disk... A pop-up will remain you that you will destroy all the data on your SD card.

  • Once writing done, Windows should detect the boot partition:

Boot partition

  • Your SD card is ready!

Linux procedure

  • Uncompress the image:

bunzip2 linux4sam-poky-sama5d2_xplained-5.0.img.bz2

The compressed image will be removed and you will get the uncompressed image named linux4sam-poky-sama5d2_xplained-5.0.img.

  • Insert your SD card. To identify the device, use the dmesg command.

If you have an integrated SD card reader, you should have something like this:

[74402.090920] mmc0: new high speed SDXC card at address 0007
[74402.091329] mmcblk0: mmc0:0007 SD64G 58.1 GiB
[74402.092653]  mmcblk0: p1 p2

The device is mmcblk0.

If you have a usb adapter, you should have something like this:

[74450.341001] usb 2-1.2: new high-speed USB device number 7 using ehci-pci
[74450.434871] usb 2-1.2: New USB device found, idVendor=058f, idProduct=6366
[74450.434877] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[74450.434880] usb 2-1.2: Product: Mass Storage Device
[74450.434883] usb 2-1.2: Manufacturer: Generic
[74450.434885] usb 2-1.2: SerialNumber: 058F63666433
[74450.435551] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[74450.435765] scsi host10: usb-storage 2-1.2:1.0
[74451.567171] scsi 10:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 0
[74451.568032] sd 10:0:0:0: Attached scsi generic sg3 type 0
[74452.338367] sd 10:0:0:0: [sdc] 121864192 512-byte logical blocks: (62.3 GB/58.1 GiB)

The device is sdc.

  • Once you have identified the your SD device you can write the image on it with the dd command.

ALERT! Warning: Be careful to not make any mistake about the device. You can lost your data if you write the image to your hard drive(s) which are usually /dev/sda or /dev/sdb.

sudo dd if=linux4sam-poky-sama5d2_xplained-5.0.img of=/dev/mmcblk0

  • Your SD card is ready!

Flash the demo

Store root filesystem on a SD card

The default boot environment is built to run form the first partition of an ext4 formated SD card. It is seen as mmcblk1p1 from the target.
Warning, important this operation is risky for your development host: you can simply crash your system. Please pay attention while running these actions.

  • format the SD card as an ext4 volume
  • mount the SD card on your host
  • as superuser, extract the rootfs archive on the SD card:
    # cd <SD card mount point>
    # sudo tar xvaf atmel-xplained-demo-image-sama5d2-xplained.tar.gz
  • unmount the SD card to synchronize its content:
    # umount <SD card mount point>
  • insert the SD card in the board's SD slot

Connect the USB to the board before launching SAM-BA

  • Short the JP9 (BOOT_DIS) to prevents booting from eMMC or serial Flash by disabling Flash Chip Selects
  • Connect a USB micro-A cable to the board (J23 A5-USB-A). It powers the board
  • Open the JP9 (BOOT_DIS) to allow access to the on-board Flash devices
  • check whether the board is found in your PC as a USB device:
    • For Microsoft Windows users: verify that the USB connection is well established
      AT91 USB to Serial Converter should appear in Device Manager. If it shows a unknown device you need to download and install the driver: AT91SAM USB CDC driver
      AT91 USB to Serial Converter
    • For Linux users: check /dev/ttyACMx by monitoring the last lines of dmesg command:
      [172677.700868] usb 2-1.4.4: new full-speed USB device number 31 using ehci-pci
      [172677.792677] usb 2-1.4.4: not running at top speed; connect to a high speed hub
      [172677.793418] usb 2-1.4.4: New USB device found, idVendor=03eb, idProduct=6124
      [172677.793424] usb 2-1.4.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
      [172677.793897] cdc_acm 2-1.4.4:1.0: This device cannot do calls on its own. It is not a modem.
      [172677.793924] cdc_acm 2-1.4.4:1.0: ttyACM0: USB ACM device
      idVendor=03eb, idProduct=6124: from this message you can see it's Atmel EK board USB connection.

Run script to flash the demo

  • download the demo package for the board
  • extract the demo package
  • run your usual terminal emulator
  • make sure that the sam-ba application is in your Operating System path so that you can reach it from your demo package directory
  • run the QML sam-ba script that has been written to flash binaries on the board's serial flash:
    # sam-ba -x demo_linux_serialflash.qml
  • When you reach the end of the flashing process (this will take a few minutes), the following line is written:
    ===== Done. =====
  • power cycle the board
  • monitor the system while it's booting on the LCD screen or through the serial line

Play with the demo

Build From source code

Setup ARM Cross Compiler

  • Ubuntu:
    In Ubuntu, you can install the ARM Cross Compiler by doing:
    sudo apt-get install gcc-arm-linux-gnueabi
    export CROSS_COMPILE=arm-linux-gnueabi-

  • Others:
    For others, you can download the Linaro cross compiler and setup the environment by doing:
    wget -c
    tar xf gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabi.tar.xz
    export CROSS_COMPILE=`pwd`/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabi/bin/arm-linux-gnueabi-

Build AT91Bootstrap from sources

This section describes how to get source code from the git repository, how to configure with the default configuration, how to customize AT91Bootstrap based on the default configuration and finally to build AT91Bootstrap to produce the binary. take the default configuration to download U-Boot from NandFlash for example.

Get AT91Boostrap Source Code

You can easily download AT91Bootstrap source code on the at91bootstrap git repository.

To get the source code, you should clone the repository by doing:

$ git clone git://
Cloning into 'at91bootstrap'...
remote: Reusing existing pack: 2476, done.
remote: Counting objects: 167, done.
remote: Compressing objects: 100% (167/167), done.
remote: Total 2643 (delta 135), reused 0 (delta 0)
Receiving objects: 100% (2643/2643), 2.06 MiB | 270 KiB/s, done.
Resolving deltas: 100% (1809/1809), done.
$ cd at91bootstrap/

Configure AT91Boostrap

Assuming you are at the AT91Bootstrap root directory, you will find a board/sama5d2_xplained folder which contains several default configuration files:


TIP Tips: nf means to read nandflash, df means to read serial flash, sd means to read mmc card.

You can configure AT91Bootstrap to load U-Boot binary from SPI flash by doing:

$ make mrproper
$ make sama5d2_xplaineddf_uboot_defconfig
If the configuring process is successful, the .config file can be found at AT91Bootstrap root directory.

Customize AT91Bootstrap

If the default configuration doesn't meet your need, after configuring with the default configuration, you can customize it by doing:
$ make menuconfig
Now, in the menuconfig dialog, you can easily add or remove some features to/from AT91Bootstrap as the same way as kernel configuration.

Build AT91Bootstrap

Then you can build the AT91Bootstrap binary by doing:
$ make

If the building process is successful, the final .bin image is binaries/at91bootstrap.bin.

Build U-Boot from sources

Getting U-Boot sources

Dedicated page on U-Boot wiki:

You can easily download U-Boot source code from Linux4SAM GitHub U-Boot repository:

  • clone the Linux4sam GitHub U-Boot repository
       $ git clone git://
       Cloning into 'u-boot-at91'...
       remote: Counting objects: 219350, done.
       remote: Compressing objects: 100% (40142/40142), done.
       remote: Total 219350 (delta 175755), reused 219350 (delta 175755)
       Receiving objects: 100% (219350/219350), 56.01 MiB | 1.24 MiB/s, done.
       Resolving deltas: 100% (175755/175755), done.
       $ cd u-boot-at91

  • The source code has been taken from the master branch which is pointing to the latest branch we use. If you want to use the other branch, you can list them and use one of them by doing:
       $ git branch -r
       origin/HEAD -> origin/master
       $ git checkout origin/u-boot-2016.03-at91 -b u-boot-2016.03-at91
       Branch u-boot-2016.03-at91 set up to track remote branch u-boot-2016.03-at91 from origin.
       Switched to a new branch 'u-boot-2016.03-at91'

Cross-compiling U-Boot

Before compile the U-Boot, you need setup cross compile toolchain in the section.

Once the AT91 U-Boot sources available, cross-compile U-Boot is made in two steps : configuration and compiling. Check the Configuration chapter in U-Boot reference manual.

Pointing hand Go to the configs/ to find the exact target when invoking make.

The U-Boot environment variables can be store in different media, above config files can specified where to store the U-Boot environment.

   # To put environment variables in serial flash:
   # To put environment variables in SD/MMC card:

Here are the building steps for the SAMA5D2-Xplained board:

# You can change the config according to your needs.
make sama5d2_xplained_spiflash_defconfig

The result of these operations is a fresh U-Boot binary called u-boot.bin corresponding to the binary ELF file u-boot.

  • u-boot.bin is the file you should store on the board
  • u-boot is the ELF format binary file you may use to debug U-Boot through a JTag link for instance.

Build Kernel from sources

Getting Kernel sources

To get the source code, you have to clone the repository:

$ git clone git://
Cloning into 'linux-sama9x5-github'...
remote: Counting objects: 4524288, done.
remote: Compressing objects: 100% (721/721), done.
remote: Total 4524288 (delta 385), reused 1 (delta 1), pack-reused 4523564
Receiving objects: 100% (4524288/4524288), 1.22 GiB | 1.35 MiB/s, done.
Resolving deltas: 100% (3777338/3777338), done.
Checking connectivity... done.
Checking out files: 100% (49565/49565), done.

The source code has been taken from the master branch which is pointing on the latest branch we use.

Pointing hand Note that you can also add this Linux4SAM repository as a remote GIT repository to your usu

$ git remote add linux4sam git://
$ git remote update linux4sam
Fetching linux4sam
From git://
 * [new branch]                linux-2.6.39-at91 -> linux4sam/linux-2.6.39-at91
 * [new branch]                linux-3.10-at91 -> linux4sam/linux-3.10-at91
 * [new branch]                linux-3.15-at91 -> linux4sam/linux-3.15-at91
 * [new branch]                linux-3.18-at91 -> linux4sam/linux-3.18-at91
 * [new branch]                linux-3.4.9-at91 -> linux4sam/linux-3.4.9-at91
 * [new branch]                linux-3.6.9-at91 -> linux4sam/linux-3.6.9-at91
 * [new branch]                linux-4.1-at91 -> linux4sam/linux-4.1-at91
 * [new branch]                linux-4.4-at91 -> linux4sam/linux-4.4-at91
 * [new branch]                master     -> linux4sam/master

If you want to use an other branch, you can list them and use one of them by doing this:

$ git branch -r
  origin/HEAD -> origin/master
$ git checkout origin/linux-4.4-at91 -b linux-4.4-at91
Branch linux-4.1-at91 set up to track remote branch linux-4.4-at91 from origin.
Switched to a new branch 'linux-4.4-at91'

Configure and Build the Linux kernel

Now you have to configure the Linux kernel according to your hardware. We have two default configuration at91 SoC in arch/arm/configs

  • at91_dt_defconfig: for at91sam ARM926 series chips
  • sama5_defconfig: for SAMA5 series chips

Now we Configure and Build kernel for sama5d2_xplained board:

$ make ARCH=arm sama5_defconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/
  HOSTLD  scripts/kconfig/conf
# configuration written to .config

At this step, you can modify default configuration using the menuconfig

$ make ARCH=arm menuconfig

And build the Linux kernel image, before you build you need set up the cross compile toolchain, check this section.

$ make ARCH=arm


  Kernel: arch/arm/boot/Image is ready
  Kernel: arch/arm/boot/zImage is ready

Now you have an usable compressed kernel image zImage.

If you need an uImage you can run this additional step:

make ARCH=arm uImage LOADADDR=0x20008000


  Kernel: arch/arm/boot/zImage is ready
  UIMAGE  arch/arm/boot/uImage
Image Name:   Linux-4.1.0-linux4sam_5.3+
Created:      Fri Sep  9 17:02:45 2016
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3441072 Bytes = 3360.42 kB = 3.28 MB
Load Address: 20008000
Entry Point:  20008000
  Image arch/arm/boot/uImage is ready

make ARCH=arm dtbs


  DTC     arch/arm/boot/dts/at91rm9200ek.dtb
  DTC     arch/arm/boot/dts/mpa1600.dtb
  DTC     arch/arm/boot/dts/animeo_ip.dtb
  DTC     arch/arm/boot/dts/at91-qil_a9260.dtb
  DTC     arch/arm/boot/dts/aks-cdu.dtb
  DTC     arch/arm/boot/dts/ethernut5.dtb
  DTC     arch/arm/boot/dts/evk-pro3.dtb
  DTC     arch/arm/boot/dts/tny_a9260.dtb
  DTC     arch/arm/boot/dts/usb_a9260.dtb
  DTC     arch/arm/boot/dts/at91sam9261ek.dtb
  DTC     arch/arm/boot/dts/at91sam9263ek.dtb
  DTC     arch/arm/boot/dts/tny_a9263.dtb
  DTC     arch/arm/boot/dts/usb_a9263.dtb
  DTC     arch/arm/boot/dts/at91-foxg20.dtb
  DTC     arch/arm/boot/dts/at91-kizbox.dtb
  DTC     arch/arm/boot/dts/at91sam9g20ek.dtb
  DTC     arch/arm/boot/dts/at91sam9g20ek_2mmc.dtb
  DTC     arch/arm/boot/dts/tny_a9g20.dtb
  DTC     arch/arm/boot/dts/usb_a9g20.dtb
  DTC     arch/arm/boot/dts/usb_a9g20_lpw.dtb
  DTC     arch/arm/boot/dts/at91sam9m10g45ek.dtb
  DTC     arch/arm/boot/dts/pm9g45.dtb
  DTC     arch/arm/boot/dts/at91sam9n12ek.dtb
  DTC     arch/arm/boot/dts/at91sam9rlek.dtb
  DTC     arch/arm/boot/dts/at91-ariag25.dtb
  DTC     arch/arm/boot/dts/at91-ariettag25.dtb
  DTC     arch/arm/boot/dts/at91-cosino_mega2560.dtb
  DTC     arch/arm/boot/dts/at91-kizboxmini.dtb
  DTC     arch/arm/boot/dts/at91sam9g15ek.dtb
  DTC     arch/arm/boot/dts/at91sam9g25ek.dtb
  DTC     arch/arm/boot/dts/at91sam9g35ek.dtb
  DTC     arch/arm/boot/dts/at91sam9x25ek.dtb
  DTC     arch/arm/boot/dts/at91sam9x35ek.dtb

If the building process is successful, the final images can be found under arch/arm/boot/ directory.

Build Yocto/Poky rootfs from sources

Note that building an entire distribution is a long process. It also requires a big amount of free disk space.

The support for Atmel AT91 SoC family is included in a particular Yocto layer: meta-atmel. The source for this layer are hosted on Linux4SAM GitHub account:

Building environment

A step-by-step comprehensive installation is explained in the Yocto Project Quick Start. The following lines have to be considered as an add-on that is AT91 specific or that can facilitate your setup.


Here are the reference pages for setting up a Yocto building environment: What You Need and How You Get It.

Step by step build procedure

Note here is a copy of the README procedure available directly in the meta-atmel layer. This file in the meta-atmel layer repository must be considered as the reference and the following copy can be out-of-sync.

Supported SoCs / MACHINE names
- SAMA5D2 product family / sama5d2-xplained
- SAMA5D4 product family / sama5d4ek, sama5d4-xplained
- SAMA5D3 product family / sama5d3xek, sama5d3-xplained
- AT91SAM9x5 product family (AT91SAM9G15, AT91SAM9G25, AT91SAM9X25, AT91SAM9G35 and AT91SAM9X35) / at91sam9x5ek
- AT91SAM9RL / at91sam9rlek
- AT91SAM9G45 / at91sam9m10g45ek

- meta-atmel
URI: git://
Branch: krogoth

This Layer depends on :
- meta-openembedded
URI: git://
Branch: krogoth

- meta-qt5
URI: git://
Branch: krogoth

Build procedure
0/ Create a directory
mkdir my_dir
cd my_dir

1/ Clone yocto/poky git repository with the proper branch ready
git clone git:// -b krogoth

2/ Clone meta-openembedded git repository with the proper branch ready
git clone git:// -b krogoth

3/ Clone meta-qt5 git repository with the proper branch ready
git clone git:// -b krogoth

4/ Clone meta-atmel layer with the proper branch ready
git clone git:// -b krogoth

5/ Enter the poky directory to configure the build system and start the build process
cd poky

6/ Initialize build directory
source oe-init-build-env build-atmel

7/ Add meta-atmel layer to bblayer configuration file
vim conf/bblayers.conf

# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly


BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True)) + '/../../..')}"

  ${BSPDIR}/poky/meta \
  ${BSPDIR}/poky/meta-poky \
  ${BSPDIR}/poky/meta-yocto-bsp \
  ${BSPDIR}/meta-atmel \
  ${BSPDIR}/meta-openembedded/meta-oe \
  ${BSPDIR}/meta-openembedded/meta-networking \
  ${BSPDIR}/meta-openembedded/meta-python \
  ${BSPDIR}/meta-openembedded/meta-ruby \
  ${BSPDIR}/meta-openembedded/meta-multimedia \
  ${BSPDIR}/meta-qt5 \

  ${BSPDIR}/poky/meta \
  ${BSPDIR}/poky/meta-poky \

8/ Edit local.conf to specify the machine, location of source archived, package type (rpm, deb or ipk)
Pick one MACHINE name from the "Supported SoCs / MACHINE names" chapter above
and edit the "local.conf" file. Here is an example:

vim conf/local.conf
MACHINE ??= "sama5d3-xplained"
DL_DIR ?= "your_download_directory_path"
PACKAGE_CLASSES ?= "package_ipk"
USER_CLASSES ?= "buildstats image-mklibs"

To get better performance, use the "poky-atmel" distribution by also adding that
DISTRO = "poky-atmel"

9/ Build core minimal image
bitbake core-image-minimal

10/ We found that additional local.conf changes are needed for our QT demo
image. You can add these two lines at the end of the file:
vim conf/local.conf

11/ Build Atmel demo images
bitbake atmel-qt5-demo-image

Typical bitbake output
Build Configuration:
BB_VERSION        = "1.30.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "sama5d2-xplained"
DISTRO            = "poky-atmel"
TUNE_FEATURES     = "arm armv7a vfp thumb neon       callconvention-hard       cortexa5"
TARGET_FPU        = "hard"
meta-yocto-bsp    = "krogoth:6c1c01392d91f512e2949ad1d57a75a8077478ba"
meta-atmel        = "krogoth:28c4b5d70f3f7df6f8b108a01f621ca0cf23c1a4"
meta-oe           = "krogoth:abd1795729501a13608da67054b9cbf185404be3"
meta-qt5          = "krogoth:4ec27e218d725677279d265ac1fc256443d665f7"

Using SAM-BA to flash components to board

Launch SAM-BA tools

  • According to this section make sure that the chip can execute the SAM-BA Monitor.

Recent FAQ


USBGadget Config: Configure AT91 USB Gadget on Linux and Endpoint order management (composite USB). (Kernel, linux-4.4-at91)
Connect Module From PDA: How to connect LCD module from PDA to the Xplained Boards. (Kernel)
SDCard Boot Notice: How to boot up the board from SD card. (AT91Bootstrap)
Crypto Config: How to configure Crypto driver. (Kernel, linux-3.18-at91, linux-4.1-at91, linux-4.4-at91)
Driver Model In UBoot: How to enable U-Boot driver model, using Sama5d2Xplained as an example. (U-Boot)
Using Atmel DRMDriver: Using Atmel KMS/DRM LCD driver. (Kernel, linux-3.18-at91, linux-4.1-at91, linux-4.4-at91)
PDMICAudio Record: Using the PDMIC to record audio stream. (Kernel, linux-4.1-at91, linux-4.4-at91)
Using SAMA5 D2 ADCDevice: Using the SAMA5D2-compatible ADC device. (Kernel, linux-4.1-at91, linux-4.4-at91)
Using Ultra Low Power Mode 1: Using Ultra Low Power mode 1 (ULP1). (Kernel, linux-4.1-at91, linux-4.4-at91)
Yocto Project FAQ: Some Yocto Project FAQ entries. (YoctoProject)
Gui Solutions: Presentation of some GUI solutions. (YoctoProject)
Using Max Touch: Introduction for how to use MaxTouch. (Kernel, linux-3.18-at91, linux-4.1-at91)
Iio Adc Driver: Adc IIO driver introduction. (Kernel, linux-3.10-at91, linux-3.18-at91, linux-4.1-at91)
r4 - 03 Feb 2016 - 16:48:37 - LudovicDesroches
Linux & Open Source related information for AT91 Smart ARM Microcontrollers

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Atmel® and others, are registered trademarks or trademarks of Atmel Corporation or its subsidiaries. This site is powered by the TWiki collaboration platform

ARM® and others are registered trademarks or trademarks of ARM Ltd. Other terms and product names may be trademarks of others.

Ideas, requests, contributions ? Connect to LinksToCommunities page.

Syndicate this siteRSS ATOM