SAMA7G5-EK Board

SoC Features

The SAMA7G54 is a high-performance, ultra-low power Arm Cortex-A7 CPU-based embedded microprocessor (MPU) running up to 1 GHz. It supports multiple memories such as 16-bit DDR2, DDR3, DDR3L, LPDDR2, LPDDR3 with flexible boot options from octal/quad SPI, SD/eMMC as well as 8-bit SLC/MLC NAND Flash.

The SAMA7G54 integrates complete imaging and audio subsystems with 12-bit parallel and/or MIPI-CSI2 camera interfaces supporting up to 8 Mpixels and 720p @ 30 fps, up to four I2S, one SPDIF transmitter and receiver and a 4-stereo channel audio sample rate converter.

The device also features a large number of connectivity options including Dual Ethernet (one Gigabit Ethernet and one 10/100 Ethernet), six CAN-FD and three high-speed USB. Advanced security functions like secure boot, secure key storage, high-performance crypto accelerators for AES, SHA, RSA and ECC are also supported.

Microchip provides an optimized power management solution for the SAMA7G54. The MCP16502 has been fully tested and optimized to provide the best power vs. performance for the SAMA7G54.

Kit Information

Kit Overview

The SAMA7G5 Evaluation Kit (SAMA7G5-EK) provides a versatile Total System Solution platform that highlights Microchip MPU and connectivity ICs.
The board features on-board memories, two Ethernet interfaces, three USB ports, two CAN interfaces, one SD card connector, two mikroBUS™ click interface headers to support over 450 MikroElektronika Click boards™, an RPi CSIcamera to support a camera module, an RPi extension connector to support several extension boards, and provision to solder a Microchip ATWILC3000-MR110xA Wi-Fi/Bluetooth module.

Note: RPi stands for “Raspberry Pi”. Raspberry Pi is a trademark of Raspberry Pi Trading.

The Kit is supported by mainline Linux distribution as well as bare metal software frameworks allowing you to easily get started with your development.

Kit Overview

Kit User Guide


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 the DEBUG port with the help of a TTL-to-USB serial cable (marked as DEBUG J20).

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

  • 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: * 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 (J20)
    • For Microsoft Windows users: identify the USB connection that is established
      JLINK CDC UART Port should appear in Device Manager. The COMxx number will be used to configure the terminal emulator.
    • 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


Demo archives

Media type Board Features Binary Description
Yocto Project / Poky based demo
Boot on eMMC SAMA7G5-EK Headless (~ 131 MB)
md5: 5a46140b3653311da220e2b22c229227
Linux4SAM Yocto Project / Poky based demo
compiled from tag linux4sam-2023.04
Follow procedure: #Flash_the_demo
SD Card image SAMA7G5-EK Headless linux4sam-poky-sama7g5ek-headless-2023.04.img.bz2 (~ 118 MB)
md5: b70102c3c1262993a3ee985fc944a383
Linux4SAM Yocto Project / Poky based demo
compiled from tag linux4sam-2023.04
Follow procedure: #Create_a_SD_card_with_the_demo
BuildRoot based demo
SD Card image SAMA7G5-EK Headless linux4sam-buildroot-sama7g5ek-headless-2023.04.img.bz2 (~ 68 MB)
md5: 0e138e5ca96f1a01222491c570a488a4
Linux4SAM BuildRoot based demo
compiled from tag linux4sam-2023.04
Follow procedure: #Create_a_SD_card_with_the_demo
OpenWrt based demo
SD Card image SAMA7G5-EK Headless openwrt-22.03.5-at91-sama7-microchip_sama7g5-ek-ext4-sdcard.img.gz (~ 6 MB)
md5: ddfdffd076b8799446f2dccae183557c
OpenWrt based demo
released by openwrt community from tag v22.03.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 FAT32 partition with the AT91Bootstrap, U-Boot and the Linux Kernel (zImage and dtb).
  • an EXT4 partition for the rootfs.

Multi-platform procedure

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

  • Insert your SD card and launch Etcher:

Etcher selection step

  1. Select the demo image. They are marked as "SD Card image" in the demo table above.
    Note that you can select a compressed image (like the demos available here). The tool is able to uncompress files on the fly
  2. Select the device corresponding to your SD card (Etcher proposes you the devices that are removable to avoid erasing your system disk)
  3. Click on the Flash! button
  4. On Linux, Etcher finally asks you to enter your root password because it needs access to the hardware (your SD card reader or USB to SD card converter)
  5. then the flashing process begins followed by a verification phase (optional)

Etcher flashing done!

  • Once writing done, Etcher asks you if you want to burn another demo image:

Etcher flashing done!

  • Your SD card is ready!

Flash the demo

HELP If you need to store the root filesystem on a SD Card, use information contained in StroreRootFSonSD. This is useful for Linux4SAM demos older than 5.6.

ALERT! use SAM-BA 3.5.y onwards. You can download it here: SAM-BA 3.x release page.

Run script to flash the demo

  • download the demo package for the board. They are marked as "Media type: Boot on eMMC" in the table above
  • extract the demo package
  • run your usual terminal emulator and enter the demo directory
  • make sure that the sam-ba application is in your Operating System path so that you can reach it from your demo package directory
  • for Microsoft Windows users: Launch the demo_linux_emmcflash.bat file
  • for Linux users: Launch the file
  • this script runs SAM-BA 3 and the associated QML sam-ba script (demo_linux_emmcflash_usb.qml) with proper parameters
  • when you reach the end of the flashing process (this will take a few minutes), the following line is written:
    -I- === Done. ===
  • connect a serial link on DBGU and open the terminal emulator program as explained just above
  • power cycle the board
  • WARNING: By default, the ROM code on the MPU does not boot from eMMC device (SDMMC0). Please refer to product datasheet on how to configure the ROM code boot configuration to enable booting from SDMMC0, either by writing the OTP (one-time programmable memory) with a boot package to boot from SDMMC0, or to enable emulation mode and in emulation mode to enable booting from SDMMC0. This configuration can be achieved using sam-ba tool.
  • monitor the system while it's booting on the LCD screen or through the serial line

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-7.3.1-2018.05-x86_64_arm-linux-gnueabi.tar.xz
    export CROSS_COMPILE=`pwd`/gcc-linaro-7.3.1-2018.05-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 AT91Bootstrap 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
Cloning into 'at91bootstrap'...
remote: Enumerating objects: 17621, done.
remote: Counting objects: 100% (3324/3324), done.
remote: Compressing objects: 100% (1029/1029), done.
remote: Total 17621 (delta 2465), reused 3102 (delta 2285), pack-reused 14297
Receiving objects: 100% (17621/17621), 5.65 MiB | 4.65 MiB/s, done.
Resolving deltas: 100% (13459/13459), done.
$ cd at91bootstrap/

Configure AT91Bootstrap

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.
Move to <Exit> with arrows and press this button hitting the Enter key to exit from this screen.

Build AT91Bootstrap

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

If the building process is successful, the final .bin image is build/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
       Cloning into 'u-boot-at91'...
       remote: Enumerating objects: 824533, done.
       remote: Counting objects: 100% (71919/71919), done.
       remote: Compressing objects: 100% (15288/15288), done.
       remote: Total 824533 (delta 56145), reused 71765 (delta 56072), pack-reused 752614
       Receiving objects: 100% (824533/824533), 182.52 MiB | 3.67 MiB/s, done.
       Resolving deltas: 100% (677649/677649), done.
       Updating files: 100% (17753/17753), 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-2022.01-at91 -b u-boot-2022.01-at91
       Branch u-boot-2022.01-at91 set up to track remote branch u-boot-2022.01-at91 from origin.
       Switched to a new branch 'u-boot-2022.01-at91'

Cross-compiling U-Boot

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

Warning, important Latest versions of U-boot (2018.07 and newer) have a minimum requirement of 6.0 version of the GCC toolchain. We always recommend to use the latest versions.

Build Kernel from sources

Getting Kernel sources

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

$ git clone
Cloning into 'linux'...
remote: Enumerating objects: 8587836, done.
remote: Total 8587836 (delta 0), reused 0 (delta 0), pack-reused 8587836
Receiving objects: 100% (8587836/8587836), 3.49 GiB | 13.44 MiB/s, done.
Resolving deltas: 100% (7117887/7117887), done.
Updating files: 100% (70687/70687), done.
$ cd linux

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 usual Linux git tree. It will save you a lot of bandwidth and download time:

$ git remote add linux4microchip
$ git remote update linux4microchip
Fetching linux4icrochip
 * [new branch]                linux-5.10-mchp -> linux4microchip/linux-5.10-mchp
 * [new branch]                linux-5.15-mchp -> linux4microchip/linux-5.15-mchp
 * [new branch]                master     -> linux4microchip/master

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

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

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 ARM cross compiler and setup the environment by doing:

wget -c
tar xf gcc-arm-10.2-2020.11-x86_64-arm-none-linux-gnueabihf.tar.xz
export CROSS_COMPILE=`pwd`/gcc-arm-10.2-2020.11-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-

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 SAM9 (ARM926) series chips
  • sama5_defconfig: for SAMA5 series chips
  • sama7_defconfig: for SAMA7 series chips

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

$ make ARCH=arm menuconfig
Now, in the menuconfig dialog, you can easily add or remove some features. Once done, Move to <Exit> with arrows and press this button hitting the Enter key to exit from this screen.

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-5.15.32-linux4microchip-20
Created:      Wed May  4 21:18:58 2022
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    5069704 Bytes = 4950.88 KiB = 4.83 MiB
Load Address: 20008000
Entry Point:  20008000
  Kernel: arch/arm/boot/uImage is ready

make ARCH=arm dtbs


  DTC     arch/arm/boot/dts/at91-kizbox2-2.dtb
  DTC     arch/arm/boot/dts/at91-kizbox3-hs.dtb
  DTC     arch/arm/boot/dts/at91-nattis-2-natte-2.dtb
  DTC     arch/arm/boot/dts/at91-sama5d27_som1_ek.dtb
  DTC     arch/arm/boot/dts/at91-sama5d27_wlsom1_ek.dtb
  DTC     arch/arm/boot/dts/at91-sama5d2_icp.dtb
  DTC     arch/arm/boot/dts/at91-sama5d2_ptc_ek.dtb
  DTC     arch/arm/boot/dts/at91-sama5d2_xplained.dtb
  DTC     arch/arm/boot/dts/at91-sama5d3_xplained.dtb
  DTC     arch/arm/boot/dts/at91-dvk_som60.dtb
  DTC     arch/arm/boot/dts/at91-gatwick.dtb
  DTC     arch/arm/boot/dts/at91-tse850-3.dtb
  DTC     arch/arm/boot/dts/at91-wb50n.dtb
  DTC     arch/arm/boot/dts/sama5d31ek.dtb
  DTC     arch/arm/boot/dts/sama5d33ek.dtb
  DTC     arch/arm/boot/dts/sama5d34ek.dtb
  DTC     arch/arm/boot/dts/sama5d35ek.dtb
  DTC     arch/arm/boot/dts/sama5d36ek.dtb
  DTC     arch/arm/boot/dts/sama5d36ek_cmp.dtb
  DTC     arch/arm/boot/dts/at91-sama5d4_ma5d4evk.dtb
  DTC     arch/arm/boot/dts/at91-sama5d4_xplained.dtb
  DTC     arch/arm/boot/dts/at91-sama5d4ek.dtb
  DTC     arch/arm/boot/dts/at91-vinco.dtb
  DTC     arch/arm/boot/dts/at91-sama7g5ek.dtb
  DTC     arch/arm/boot/dts/at91-sam9x60_curiosity.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.

Note add git-lfs to the package requirement list from whichever Linux distribution you use.

For instance, on Ubuntu or debian, these packages need to be installed on your development host:

sudo apt-get install gawk wget git-core git-lfs diffstat unzip texinfo gcc-multilib \
     build-essential chrpath socat cpio python3 python3-pip python3-pexpect \
     xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \
     pylint3 xterm

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.

Note starting with Linux4SAM 2021.04 release, the meta-atmel layer supports Yocto templates, so make sure you create a new build environment using oe-init-build-env

This layer provides support for Microchip microprocessors (aka AT91)

For more information about the Microchip MPU product line see:
Linux & Open Source on Microchip microprocessors:

Supported SoCs / MACHINE names
Note that most of the machine names below, have a SD Card variant that can be
built by adding an "-sd" suffix to the machine name.
- SAMA5D2 product family / sama5d2-xplained, sama5d2-xplained-emmc, sama5d27-som1-ek-sd, sama5d27-som1-ek-optee-sd, sama5d2-ptc-ek, sama5d2-icp, sama5d27-wlsom1-ek-sd
- 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
- SAM9X60 / sam9x60ek, sam9x60-curiosity
- SAMA7G5 / sama7g5ek-sd, sama7g5ek-emmc, sama7g5ek-ospi

- meta-atmel
Branch: kirkstone

This Layer depends on :
- poky
Branch: kirkstone

- meta-openembedded
Branch: kirkstone

- meta-arm (for optee components)
Branch: kirkstone

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 && cd poky && \
git checkout -b kirkstone yocto-4.0.9 && cd -

2/ Clone meta-openembedded git repository with the proper branch ready
git clone git:// && \
cd meta-openembedded && git checkout -b kirkstone df452d && cd -

3/ Clone meta-atmel layer with the proper branch ready
git clone -b kirkstone

4/ Clone meta-arm layer with the proper branch ready
git clone && cd meta-arm && \
git checkout -b kirkstone yocto-4.0.1 && cd -

5/ Enter the poky directory to configure the build system and start the build process
cd poky
If not created yet, add a new "build-microchip" directory:
mkdir build-microchip
Else, if it's the first time you use Yocto Project templates, and if the
build-microchip directory remains from a previous use, we advise you to start
from a fresh directory. Keep your build-microchip/conf/local.conf file for

6/ Inside the .templateconf file, you will need to modify the TEMPLATECONF
variable to match the path to the meta-atmel layer "conf" directory:
export TEMPLATECONF=${TEMPLATECONF:-../meta-atmel/conf}

7/ Initialize build directory
source oe-init-build-env build-microchip

8/ To build a small image provided by Yocto Project:
[MACHINE=] bitbake core-image-minimal

Example for sama5d2-xplained-sd SD card image:
MACHINE=sama5d2-xplained-sd bitbake core-image-minimal

9/ To build the microchip image with no graphics support:
[MACHINE=] bitbake microchip-headless-image

Example for sama5d2-xplained-sd SD card image:
MACHINE=sama5d2-xplained-sd bitbake microchip-headless-image

10/ To build the microchip image with graphics support (EGT):
[MACHINE=] bitbake microchip-graphics-image

Example for sama5d2-xplained-sd SD card image:
MACHINE=sama5d2-xplained-sd bitbake microchip-graphics-image

Typical bitbake output
Build Configuration:
BB_VERSION           = "2.0.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "sam9x60-curiosity-sd"
DISTRO               = "poky-atmel"
DISTRO_VERSION       = "4.0.9"
TUNE_FEATURES        = "arm armv5 thumb dsp"
TARGET_FPU           = "soft"
meta-yocto-bsp       = "HEAD:09def309f91929f47c6cce386016ccb777bd2cfc"
meta-initramfs       = "kirkstone:df452d9d98659b49888fa8a5428a0a8bd3e3aaec"
meta-atmel           = "kirkstone:aeeb0d2e90c6b6546fa5b9cb20bf7e58020e3df9"
meta-multimedia      = "kirkstone:df452d9d98659b49888fa8a5428a0a8bd3e3aaec"
meta-arm-toolchain   = "kirkstone:bafd1d013c2470bcec123ba4eb8232ab879b2660"

To contribute to this layer you should submit the patches for review to:
the github pull-request facility directly or the forum. Anyway, don't forget to
Cc the maintainers.

Microchip Forum:

for some useful guidelines to be followed when submitting patches:

Hari Prasath G E 
Nicolas Ferre 

When creating patches insert the [meta-atmel] tag in the subject, for example
use something like:
git format-patch -s --subject-prefix='meta-atmel][PATCH' 

Using SAM-BA to flash components to board

eMMC Flash demo

The layout of the eMMC Flash Demo is the same as on SD-Card.

Install SAM-BA software in your PC

In addition to the official SAM-BA pages on, we maintain information about SAM-BA in the SoftwareTools page.

ALERT! use SAM-BA 3.5.y onwards. You can download it here: SAM-BA 3.x release page.

Launch SAM-BA tools

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

In addition to the Qt5 QML language for scripting used for flashing the demos, most common SAM-BA action can be done using SAM-BA command line.

For browsing information on the SAM-BA command line usage, please see the Command Line Documentation that is available in the SAM-BA installation directory: doc/index.html or doc/cmdline.html .

SAM-BA includes command line interface that provides support for the most common actions:

  • reading / writing to arbitrary memory addresses and/or peripherals
  • uploading applets and using them to erase/read/write external memories

The command line interface is designed to be self-documenting.

The main commands can be listed using the "sam-ba --help" command:

SAM-BA Command Line Tool v3.5
Copyright 2018 Microchip Technology

Usage: ./sam-ba [options]
SAM-BA Command Line Tool

  -v, --version                          Displays version information.
  -h, --help                             Displays this help.
  -t, --tracelevel <trace_level>         Set trace level to <trace_level>.
  -L, --applet-buffer-limit <SIZE>       Set applet buffer limit to <SIZE>
bytes (default 131072). -x, --execute <script.qml> Execute script <script.qml>. -p, --port <port[:options:...]> Communicate with device using <port>. -d, --device <device[:options:...]> Connected device is <device>. -b, --board <board[:options:...]> Connected board is <board>. -m, --monitor <command[:options:...]> Run monitor command <command>. -a, --applet <applet[:options:...]> Load and initialize applet <applet>. -c, --command <command[:args:...]> Run command <command>. -w, --working-directory <DIR> Set working directory to <DIR>.

Additional help can be obtained for most commands by supplying a "help" parameter that will display their usage.

For example "sam-ba --port help" will display:

Known ports: j-link, serial, secure

Command that take an argument with options (port, monitor, applet) will display even more documentation when called with "help" as option value.

For example "sam-ba --port serial:help" will display:

    serial                serial port (will use first AT91 USB if found otherwise first serial port)
    serial:COM80          serial port on COM80
    serial:ttyUSB0:57600  serial port on /dev/ttyUSB0, baudrate 57600

Programming components into eMMC flash

Program rootfs file

With SAM-BA you can directly program SD/MMC images to the on-board eMMC. These images are named *.img or *.wic for the ones generated by Yocto Project.

# sam-ba -p serial -b sama7g5-ek -a sdmmc -c write:microchip-demo-image-sama7g5ek.wic
Opening serial port 'ttyACM0'
Connection opened.
Detected memory size is 3925868544 bytes.
Page size is 512 bytes.
Buffer is 88576 bytes (173 pages) at address 0x0022a5a0.
Executing command 'write:microchip-demo-image-sama7g5ek.wic'
Wrote 88576 bytes at address 0x00000000 (0.02%)
Wrote 88576 bytes at address 0x00015a00 (0.04%)
Wrote 88576 bytes at address 0x0002b400 (0.05%)
Wrote 88576 bytes at address 0x00040e00 (0.07%)
Wrote 88576 bytes at address 0x00056800 (0.09%)
Wrote 88576 bytes at address 0x1d4e8600 (99.98%)
Wrote 88576 bytes at address 0x1d4fe000 (100.00%)
Wrote 4608 bytes at address 0x1d513a00 (100.00%)
Connection closed.

HELP Note that programming a rootfs of several hundreds of MiB will take a few minutes to complete.

Recent FAQ


Using SAMA 5 D 2 ADCDevice: Using the SAMA5D2-compatible ADC device. (Kernel, linux-5.15-mchp, linux-6.1-mchp)
Sama 7 g 5 Ov 7740: Interfacing sama7g5 with parallel omnivision ov7740 sensor.. (Kernel, linux-5.15-mchp, linux-6.1-mchp)
Sama 7 g 5 Xisc: Detailed explanation of the sama7g5 image acquisition pipeline. (Kernel, linux-5.15-mchp, linux-6.1-mchp)
Using ASRC: How to use ASRC. (Kernel, linux-5.15-mchp, linux-6.1-mchp)
Thermal Faq: Thermal management support on SAMA7G5. (Kernel, linux-5.15-mchp, linux-6.1-mchp)
Using I 2 SC: How to use I2SC. (linux-5.10-at91, linux-5.15-mchp, linux-6.1-mchp)
ISCWhite Balance Features: White balance features of the Image sensor controller.. (Kernel, linux-4.19-at91, linux-5.4-at91, linux-5.10-at91, linux-5.15-mchp, linux-6.1-mchp)
Sama 7 g 5 Imx 274: using Sony IMX274 sensor with sama7g5. (linux-5.15-mchp, linux-6.1-mchp)
Media Controller: What is Media controller and how to use it with SAM products.. (linux-5.15-mchp, linux-6.1-mchp)
Build Issue Buildroot G 1: Buildroot gst1-at91-gstreamer. (BuildRoot)
Using FITwith Overlays: How to use U-boot with FIT image to load overlays. (U-Boot, Kernel)
Wilc Faq: How to use WILC3000 on SAM development boards. (Kernel)
Patching DTin Uboot: How to apply DTBOs in U-boot. (U-Boot, Kernel)
U-Boot FAQ: Some U-Boot FAQ entries. (U-Boot)
r2 - 13 May 2022 - 12:01:37 - EugenHristev
Linux & Open Source for AT91 Microchip Microprocessors

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.

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

Arm® and others are registered trademarks or trademarks of Arm Limited (or its affiliates). Other terms and product names may be trademarks of others.

Ideas, requests, contributions ? Connect to LinksToCommunities page.

Syndicate this siteRSS ATOM