If you have just purchased a phyCORE-AM64x development kit, start your development here.


Basic Evaluation Requirements

This Quickstart guide walks through booting the phyCORE-AM64x development kit into Linux and how to establish a console session with it using a Windows Host Machine. Host system requirements are minimal for basic serial communication, and for the purposes of this Quickstart, any modern computer could be used. PHYTEC recommends using a native Windows environment to establish serial communication with the development kit and leaving the bulk of development tasks for a dedicated Ubuntu 18.04 build server or Virtual Machine.


Host system requirements for the more process-intense development tasks are detailed in the BSP Development guide, but you won’t need those Host system requirements to follow this Quickstart or to follow the Interface Guides.

Check the Board Configuration

The board should have been pre-configured during manufacturing, but we will double check it together as an exercise:

  • Press firmly down on the SOM with equal pressure on both sides to ensure that it is seated properly

  • Ensure that an SD Card is inserted into the SD card slot. This SD card was flashed during manufacturing and should feature the latest phyCORE-AM64x Linux image.

  • Check that the boot switches (S3, S4) are set to boot the system from SD card.

  • Check that the boot switch S10 is set to ON to overide default boot settings.

SD Boot Settings

SD Boot Switch phyBOARD-AM64 close-up boot switches


Board orientation is rotated for ease of viewing switches

Serial Communication Setup

  • Connect the provided micro-USB Serial cable to the Serial Debug Port X20 on the development kit and the other end to a USB port on your Host Machine.

serial connection

Windows 10 Instructions


If your native operating system is something other than Windows 10, please feel free to reach out on PHYTEC’s Support Portal for more options and instructions.

After the phyCORE-AM64x development kit is connected to your windows host machine, you will need to determine the COM ports associated with it.

  • Open your system’s Device Manager and expand Ports (COM & LPT).

Windows Device Manager
  • Note the COM port number of the “Silcon Labs Dual CP2105 USB to UART Bridge,” there should be two that appear.


Due to a known issue with our development kit’s CP2105 USB to UART Bridge implementation, the active COM port used for USB Debug can be randomly assigned on either of the two COM ports. In the following steps, it may be a good idea to setup and observe two terminal sessions for both COM ports when first booting your hardware.

Configure your Terminal Session:

  • Download or open the terminal emulator of your preference. There are many options such as PuTTY and TeraTerm.


This guide will use TeraTerm. Configuration of your terminal will vary slightly depending on the terminal emulator software you are using.

  • Create a new session using your preferred terminal emulator and specify the COM port to connect to (found in previous steps):

Open a New Terminal Session


The COM port will most likely be the second of the two COM ports but you may want to setup a terminal for both the first time.

  • Other parameters include: 115200 Baud, 8 bit data, no parity bits, 1 stop bit and no flow control.

Setup Serial Port Terminal Settings
  • Once you have an empty terminal session, your host system is effectively listening for console data over the COM port you selected. The documentation for the phyCORE-AM64x, outlined throughout this wiki, will generally refer to this serial session as the “Target Console”.

Power the Board

Use the included power supply (12V/2A) to provide power to the phyCORE-AM64x development kit’s X5 power connector. The system will automatically boot.

Terminal Output Linux

On your serial console you should reach a login prompt.

Expected output
phyboard-electra-am64xx-1 login:

Login using “root” (no password is required).


You may find that commands and text in the terminal wrap over themselves if they extend too far on a single line in your Terminal Window. To improve usability and to prevent text from wrapping over itself use the following command:

Target (Linux)
shopt -s checkwinsize && resize

Safe Shutdown

Before removing power from the development kit, you must make sure that the operating system has safely shutdown. This will help to avoid things like filesystem corruption which can prevent the hardware from booting the next time it is needed.

  • To initiate a shutdown run the following command:

Target (Linux)
  • Once you have seen “Reached target shutdown” it is safe to remove power from the development kit.

Expected Output
Reached target Shutdown


For technical support, please visit PHYTEC’s Support Portal!