SAMA7D65 Curiosity Pro

SoC Features

The SAMA7D65 MPU is a high-performance Arm^® Cortex^®-A7 CPU-based embedded microprocessor (MPU) running up to 1 GHz.

The board allows evaluation of powerful peripherals for connectivity, audio and user interface applications, including MIPI DSI^® and Low-Voltage Differential Signaling (LVDS) with 2D graphics, dual Gigabit Ethernet with Time-Sensitive Networking (TSN), and Controller Area Network with Flexible Data-rate (CAN-FD).

The MPUs offer advanced security functions, like tamper detection, secure boot, secure key storage, True Random Number Generator (TRNG), Physically Unclonable Function (PUF), as well as higher-performance crypto accelerators for Advanced Encryption Standard (AES), and Secure Hash Algorithm (SHA).

Kit Information

Kit Overview

SAMA7D65 Curiosity Pro

Access the Console

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

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 J63).

Using DEBUG on TTL-to-USB Connector (DEBUG J63)

• For Microsoft Windows^® users: 
  • Install the driver of your USB Transistor-Transistor Logic (TTL) serial cable.
  • Be sure to connect a 3.3V compatible cable and identify its ground (GND) pin. Place it properly according to the silkscreen and connect the cable to the board (J63).
  • 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.
    
• 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.
    usb 1-1.1.2: new full-speed USB device number 17 using ehci-pci
    usb 1-1.1.2: New USB device found, idVendor=0403, idProduct=6001
    usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 1-1.1.2: Product: TTL232R-3V3
    usb 1-1.1.2: Manufacturer: FTDI
    usb 1-1.1.2: SerialNumber: FTGNVZ04
    ftdi_sio 1-1.1.2:1.0: FTDI USB Serial Device converter detected
    usb 1-1.1.2: Detected FT232RL
    usb 1-1.1.2: Number of endpoints 2
    usb 1-1.1.2: Endpoint 1 MaxPacketSize 64
    usb 1-1.1.2: Endpoint 2 MaxPacketSize 64
    usb 1-1.1.2: Setting MaxPacketSize 64
    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.

Back to Top

Demo

Demo Archives

Create an SD Card With the Demo

You need a 1 GB (or larger) SD card 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), and
• 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 balenaEtcher. This open-source software tool is useful for obtaining a compressed image as input. Additional information and support can be found on the balenaEtcher website. 

Flash the Demo

Run Script to Flash the Demo

• Download the demo package for the board.
• 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_nandflash.bat file.
• For Linux users: Launch the demo_linux_nandflash.sh file.
• This script runs SAM-BA software v3 and the associated QML sam-ba script (demo_linux_nandflash_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.
• Monitor the system while it is booting on the LCD screen or through the serial line.

Run Script to Boot in Emulation Mode

• Make sure the SD card is removed.
• Run the following script to boot the board in emulation mode.
• Microsoft users: Run the demo_linux_nandflash_emul.bat file.
• Linux users: Run the demo_linux_nandflash_emul.sh file.
• The script writes the boot configuration packet and the board should boot from NAND flash.

Back to Top

Build From Source Code

Set Up Arm Cross Compiler

Back to Top

Back to Top

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, how to build AT91Bootstrap to produce the binary. Take the default configuration to download U-Boot from !NandFlash, for example.

SAM-BA Software Tool

The SAM-BA software tool is required to add a header in the at91bootstrap image (for both manual compilation and through build systems like Buildroot or Yocto Project^®). Download the SAM-BA software.

Uncompress the tgz file in your workspace by executing:

Make sure to add the SAMB-BA application to your $PATH and verify that you have the correct
version:

Get AT91Bootstrap Source Code

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

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

Configure AT91Bootstrap

Assuming you are at the AT91Bootstrap root directory, you will find a configs folder that contains several default configuration files:

You can configure AT91Bootstrap to load the U-Boot binary from the SD card by executing:

If the configuration process is successful, the .config file can be found at the AT91Bootstrap root directory.

Customize AT91Bootstrap

If the default configuration doesn't meet your needs, after configuring with the default configuration, you can customize it by executing:

Now, in the menuconfig dialog,  you can easily add or remove some features to/from AT91Bootstrap in the same way you configure the kernel. Use the arrow keys to navigate to <Exit> and press this button, pressing the Enter key to exit from this screen.

Build AT91Bootstrap

Then you can build the AT91Bootstrap binary by executing:

If the building process is successful, the final BIN image is build/binaries/boot-plaintextimg.bin. The boot-plaintextimg.bin is the boot format to be used for booting the sama7d65 SoC.

Build U-Boot From Sources

Getting U-Boot Sources

Dedicated page on U-Boot wiki: http://www.denx.de/wiki/U-Boot/SourceCode

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

• clone the Linux4microchip GitHub U-Boot repository
      $ git clone https://github.com/linux4microchip/u-boot-mchp.git
   Cloning into 'u-boot-mchp'...
   remote: Enumerating objects: 951876, done.
   remote: Counting objects: 100% (17718/17718), done.
   remote: Compressing objects: 100% (5735/5735), done.
   remote: Total 951876 (delta 12391), reused 15314 (delta 11846), pack-reused 934158
   Receiving objects: 100% (951876/951876), 164.77 MiB | 401.00 KiB/s, done.
   Resolving deltas: 100% (790362/790362), done.
     $ cd u-boot-mchp/

• 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
    origin/dev/tony/sama7g5ek_optee
    origin/master
    origin/sam9x60_curiosity_early
    origin/sam9x60_early
    origin/sam9x60_iar
    origin/sam9x7_early
    origin/sama5d27wlsom1ek_ear
    origin/sama7g5_early
    origin/u-boot-2012.10-at91
    origin/u-boot-2013.07-at91
    origin/u-boot-2014.07-at91
    origin/u-boot-2015.01-at91
    origin/u-boot-2016.01-at91
    origin/u-boot-2016.03-at91
    origin/u-boot-2017.03-at91
    origin/u-boot-2018.07-at91
    origin/u-boot-2019.04-at91
    origin/u-boot-2020.01-at91
    origin/u-boot-2021.04-at91
    origin/u-boot-2022.01-at91
    origin/u-boot-2023.07-mchp
    origin/u-boot-2024.07-mchp
    origin/uboot_5series_1.x
  
     $ git checkout origin/u-boot-2024.07-mchp -b u-boot-2024.07-mchp
    Branch 'u-boot-2024.07-mchp' set up to track remote branch 'u-boot-2024.07-mchp' from 'origin'.
    Switched to a new branch 'u-boot-2024.07-mchp'

Cross-Compiling U-Boot

Before compiling the U-Boot, you need to set up the cross-compile toolchain in the "Set Up Arm Cross Compiler" section.

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

The U-Boot environment variables can be stored in different media; the config files below can specify where to store the U-Boot environment.

Here are the building steps for the SAMA7D65 Curiosity Pro board:

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

Required Packages

You must install essential host packages on your build host. These requirements are listed in the Linux kernel documentation with the "Install build requirements" chapter. You must follow this process, which includes, but is not limited to, the following packages:

• build-essential
• flex
• bison
• git
• perl-base
• libssl-dev
• libncurses5-dev
• libncursesw5-dev
• ncurses-dev

Getting Kernel Sources

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

The source code has been taken from the master branch. You must switch to the specified tag by executing:

Set Up Arm Cross Compiler

Back to Top

Back to Top

Configure and Build the Linux Kernel

Now you have to configure the Linux kernel according to your hardware. We have two default configurations for the 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

You can modify default configuration using the menuconfig.

Back to Top

Build Yocto Project rootfs From Sources

Support for the Microchip MPU SoC family is included in a particular Yocto Project layer, meta-mchp. The source for this layer is hosted on the Linux4Microchip GitHub account on the "Microchip Yocto Project BSP" page.

Building Environment

A step-by-step, comprehensive installation is explained on the "Yocto Project Quick Build" page. The following lines should be considered as an add-on that is MPU-specific or that can facilitate your setup.

Step-by-Step Build Procedure

OpenEmbedded/Yocto Project BSP Layer for Microchip's SoCs

• Description
  • The meta-mchp-common layer consolidates common Board Support Package (BSP) components and metadata for Microchip platforms, streamlining development across various Microchip devices for use with OpenEmbedded and/or Yocto Project.
• Supported Machines
  • The meta-mchp-common layer provides support for various Microchip platforms. For detailed information about supported machines, please refer to the documentation in the relevant sub-layers:
    • MPU layer README
• Prerequisites
  • Before starting, please refer to the Required Packages for Build Host section in the Yocto Project Documentation to install required dependencies for the build environment:

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

• Usage

  • To integrate this layer into your Yocto Project build environment:

  Clone the necessary repositories.

  Create an empty directory to hold the workspace:

  mkdir yocto-dev
  cd yocto-dev

  Use the repo tool to fetch all the required repositories.

  Information

  Note: Make sure to install the repo utility first.

  repo init -u https://github.com/linux4microchip/meta-mchp-manifest.git -b <branch> -m <target>/default.xml

  Replace and with the Yocto Project release branch and the manifest required. For example:

  repo init -u https://github.com/linux4microchip/meta-mchp-manifest.git -b scarthgap -m mpu/default.xml

  Fetch all the required repositories using the following repo command:

  repo sync

  Back to Top

  ---

  Initialize the build environment.

  The meta-mchp repository provides sample configuration templates that help set up BitBake layers and key configuration files in the Yocto Project build directory.

  Set the TEMPLATECONF environment variable to point to the appropriate configuration template before initializing the build environment:

  export TEMPLATECONF=${TEMPLATECONF:-../meta-mchp/<meta-layer>/conf/templates/default}

  Replace meta-layer above with the desired layer based on your target platform. For example:

  export TEMPLATECONF=${TEMPLATECONF:-../meta-mchp/meta-mchp-mpu/conf/templates/default}

  Information

  Note: Setting TEMPLATECONF is only needed the first time you will run the source command.

  Then initialize the Yocto Project build environment:

  source openembedded-core/oe-init-build-env

  Back to Top

  ---

  Set the target machine and build the image.

  MACHINE=<machine> bitbake core-image-minimal

  Each sub-layer provides several images that include demos and applications tailored for its respective platform.

  For more information on the supported images, please refer to the MPU layer README.

  • Layer Dependencies

    This layer depends on the following layers:

    - meta-openembedded
     - URI: git://git.openembedded.org/meta-openembedded
     - Layers: meta-oe, meta-networking, meta-python
    
    - openembedded-core
     - URI: git://git.openembedded.org/openembedded-core
     - Layers: meta

  For information on the specific revisions used, refer to the meta-mchp manifest repository.

  Back to Top

  ---

• Licensing
  • The contents of this layer are licensed under the MIT License. See COPYING.MIT for details
• Contributing 

• If you want to contribute changes, you can send GitHub pull requests. See CONTRIBUTING.md for additional information about contribution guidelines.

Back to Top

Using SAM-BA Software to Flash Components to the Board

NAND Flash Demo - Memory Map

Install SAM-BA Software In Your PC

We maintain information about SAM-BA in the "SoftwareTools" page.

Launch SAM-BA Software Tools

In addition to the Qt^® 5 QML language for scripting used for flashing the demos, the most common SAM-BA software actions can be done using the SAM-BA software command line.

For browsing information on the SAM-BA software command line usage, please see the command line documentation available in the SAM-BA software installation directory, doc/index.html or doc/cmdline.html.

SAM-BA software includes a 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 --help command:

If you get the following error, it indicates a symbol mismatch or unresolved symbol when the sam-ba executable is being loaded:

Check for Qt libraries inside the extracted SAM-BA software directory.

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:

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

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

Back to Top

Configure NAND ECC

Using Default PMECC Parameters

When choosing the board variant with the -b parameter of the SAM-BA software, the default PMECC configuration for the NAND populated on the board is valid. You can verify its value by running the command that reads one byte in a dummy file (named test.bin in the following command):

You can figure out that the default PMECC parameter for this SAMA7D65 Curiosity board is 0xc1e04e07.

If you connect a serial console to the SoC RomCode default UART, you can see even more details about the NAND ECC parameters given by the SAM-BA applet:

If you want to change the default PMECC parameters, you can specify another value on the SAM-BA command line with the -a nandflash argument as shown:

By reading this in-line documentation, we can specify the NAND PMECC parameter with this command:

Back to Top

Programming Components Into NAND

Program AT91Bootstrap Binary

Run the SAM-BA software tool with USB connection (equivalent to serial) and erase the beginning of the NAND flash, and then write AT91Bootstrap binary:

Program U-Boot Binary

Run SAM-BA with USB connection (equivalent to serial) and erase the U-Boot section in the NAND flash memory map and then write U-Boot binary:

Back to Top

Recent FAQ

• SAMA7D65 ready-made Buildroot images &amp; BSR
• How to patch Device Tree Blob in U-boot using Overlays
• Using the SAMA5D2-compatible ADC device
• Using systemd
• Thermal management support on SAMA7G5
• U-Boot FAQ
• How to use the Atmel KMS/DRM LCD driver
• How to use U-boot with FIT image to load overlays

Back to Top