Timesys Getting Started Guide for AMD Kria KR260

$FILE

Contents

Introduction

This document will describe in detail the procedures for booting a Linux kernel image and mounting a root file system from an SD Card on the AMD Kria KR260.

Prerequisites

Host Requirements

To properly boot the AMD Kria KR260 using software from Timesys, your host machine must meet the following requirements:
  • Modern GNU/Linux Distribution. Timesys recommends one of the following distributions:
    • Ubuntu (Most recent release or LTS)
    • Fedora (Most recent release)
  • Root or sudo permission on the Development Host.
  • A copy of the Linux Kernel (Image-6.1-ts-aarch64) and Root File System (rootfs.tar.gz) for the Target Board downloaded from Factory. These are found in the output directory of your online build, or in the directory build_aarch64-timesys-linux-<libc>/images/ on the command line.
  • An available USB port on your Development Host.
  • A SD card slot or adapter on your Development Host.

Target Requirements

To boot the AMD Kria KR260, you will need the following items:
  • AMD Kria KR260
  • SD Card
  • Micro USB Cable
Once you have all of the necessary components, you should perform the following steps:
  1. Connect the USB Debug port of the board(J4) to the USB port of your workstation using the Micro USB Cable.
  2. Connect the power supply(12V,3A) to the port J12 of your board.
  3. Set aside the SD card, you will need to intialize it from the Development Host before booting the board.

Preparing the Target

Configuring Serial Communication

The Kria KR260 uses a serial debug port to communicate with the host machine. The commands discussed in this section are meant to be performed by a privileged user account. This requires the root login or prepending each command with sudo.

Using Minicom

  1. Start minicom on your host machine in configuration mode. As root:
    # minicom -o -s -w
  2. A menu of configuration should appear. Use the Down-arrow key to scroll down and select the Serial port setup option, and press Enter.
  3. Verify that the listed serial port is the same one that is connected to the target board. If it is not, press A, and enter the correct device. This is /dev/ttyUSB1 on most Linux distributions.
  4. Set the Bps/Par/Bits option by pressing the letter E and using the next menu to set the appropriate values. You press the key that corresponds to the value 115200, then press Enter.
  5. Set Hardware flow control to No using the F key.
  6. Set Software flow control to No using the G key.
  7. Press Enter to return to the main configuration menu, and then press Esc to exit this menu.
  8. Reset the board, and wait for a moment. If you do not see output from the board, press Enter several times until you see the prompt. If you do not see any output from the board, and have verified that the serial terminal connection is setup correctly, contact your board vendor.
TIP: If you experience an error similar to Device /dev/ttyUSB1 is locked when starting minicom, it usually means that another process is using the serial port (which is usually another instance of minicom). You can find the process that is currently using the serial port by executing the following:

# fuser /dev/ttyUSB1
/dev/ttyUSB1:         28358

# ps 28358
  PID TTY      STAT  TIME COMMAND
  28923 pts/0    S+    0:00 minicom

This process can also be killed directly with fuser as root. Please use this command with caution:

# fuser -k /dev/ttyUSB1

Using GNU Screen

To quickly connect to a board using Gnu Screen, execute the following:

# screen /dev/ttyUSB1 115200

For more information about using screen, please consult the man page, or view the manual online at http://www.gnu.org/software/screen/manual/screen.html

Preparing the Secure Digital Card

The Kria KR260 boots from an SD card. Some kits may be shipped with one that contains a sample kernel and RFS preloaded. We will be replacing these with the kernel and RFS from Factory. If you are using a blank SD card or have trouble replacing the software on the preloaded one, see Partitioning the SD Card. Otherwise, skip directly to Writing Boot Files to the SD Card.

Before you begin, you should determine the name of your SD card on your host system. To do so:

  1. Connect the SD card to your host system. Many modern systems have SD card slots on the case, or you can purchase a USB SD Card Reader for around $15 US.
  2. Determine the device name of the SD Card. This can be done using dmesg. In the following example, the device is /dev/sdX, which contains one partition sdX1.

    $ dmesg | tail
    [88050.184080] sd 4:0:0:0: [sdX] 1990656 512-byte hardware sectors: (1.01 GB/972 MiB)
    [88050.184821] sd 4:0:0:0: [sdX] Write Protect is off
    [88050.184824] sd 4:0:0:0: [sdX] Mode Sense: 03 00 00 00
    [88050.184827] sd 4:0:0:0: [sdX] Assuming drive cache: write through
    [88050.185575] sd 4:0:0:0: [sdX] 1990656 512-byte hardware sectors: (1.01 GB/972 MiB)
    [88050.186323] sd 4:0:0:0: [sdX] Write Protect is off
    [88050.186325] sd 4:0:0:0: [sdX] Mode Sense: 03 00 00 00
    [88050.186327] sd 4:0:0:0: [sdX] Assuming drive cache: write through
    [88050.186330]  sdX: sdX1

Partitioning the SD card

If you want to use a different SD card or its contents become corrupted, you can use the fdisk tool to create two partitions on your SD card. Please note that all data on the card will be lost upon completion of these steps.

  1. Unmount the partition if it was automounted by using the umount command.

    $ umount /dev/sdX1

  2. As root, run the fdisk utility on the drive.

    $ sudo fdisk /dev/sdX

  3. In fdisk, Delete the existing partition table and create a new one using the o command.

    Command (m for help): o
    Building a new DOS disklabel with disk identifier 0x8b025602.
    Changes will remain in memory only, until you decide to write them.
    After that, of course, the previous content won't be recoverable.

  4. Create a new primary partition using the n command. The first partition will be a FAT partition for storing the boot files. 64 MB is typically more than enough for this purpose.

    Command (m for help): n
    Partition type:
       p   primary (0 primary, 0 extended, 4 free)
       e   extended
    Select (default p): p
    Partition number (1-4, default 1): 1
    First sector (2048-30679039, default 2048):
    Using default value 2048
    Last sector, +sectors or +sizeK,M,G (2048-30679039, default 30679039): +64M

  5. Set the first partition as W95 FAT32 (LBA) using the t command and entering the Hex code c.

    Command (m for help): t
    Selected partition 1
    Hex code (type L to list codes): c

  6. Set the bootable flag on the first partition using the a command.

    Command (m for help): a
    Partition number (1-4): 1

  7. Create a second primary partition using the n command. This partition will be a linux partition for storing the root filesystem. It will fill the rest of the SD card.

    Command (m for help): n
    Command action
       e   extended
       p   primary partition (1-4)
    p
    Partition number (1-4, default 2): 2
    First sector (133120-30679039, default 133120):
    Using default value 18432
    Last sector, +sectors or +sizeK,M,G (133120-30679039, default 30679039):
    Using default value 30679039

  8. Verify that the partition table is correct by using the p command. It should look similar to the following:

    Command (m for help): p                                                         
                                                                                    
    Disk /dev/sdX: 15.7 GB, 15707668480 bytes
    64 heads, 32 sectors/track, 14980 cylinders, total 30679040 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x6eaae8f8

       Device Boot      Start         End      Blocks   Id  System
    /dev/sdX1   *        2048      133119       65536    c  W95 FAT32 (LBA)
    /dev/sdX2          133120    30679039    14773960   83  Linux

  9. This step will destroy all data on the SD Card - Write the partition table to the card using the w command.

    Command (m for help): w
    The partition table has been altered!

    Calling ioctl() to re-read partition table.

    WARNING: If you have created or modified any DOS 6.x
    partitions, please see the fdisk manual page for additional
    information.
    Syncing disks.

  10. Format the first partition of the SD card with a FAT filesystem using the mkfs.vfat tool.

    $ sudo /sbin/mkfs.vfat -n boot /dev/sdX1

  11. Format the second partition using an ext4 filesystem using the mkfs.ext4 tool.

    $ sudo /sbin/mkfs.ext4 -L rfs /dev/sdX2

Writing Boot Files to the SD Card

  1. Mount the partitions. You can remove and reinsert the card to trigger the automount, or you can use the mount command to mount the partition to an arbitrary location.

    $ sudo mount /dev/sdX1 /media/boot
    $ sudo mount /dev/sdX2 /media/rfs

  2. As root, copy the uImage file, Image-6.1-ts-aarch64, to the boot partition of the card.

    $ sudo cp Image-6.1-ts-aarch64 /media/boot/

  3. As root, copy the Device Tree Blob file, SMK-zynqmp-sck-kr-g-revB.dtb, to the boot partition of the card.

    $ sudo cp SMK-zynqmp-sck-kr-g-revB.dtb /media/boot/

  4. As root, extract the rootfs.tar.gz archive to the mounted directory. This file is located at build_aarch64-timesys-linux-<libc>/images/rfs/ on Desktop Factory builds.

    $ sudo tar xzf rootfs.tar.gz -C /media/rfs

  5. As root, umount the SD Card.

    $ sync
    $ sudo umount /media/boot
    $ sudo umount /media/rfs

  6. Remove the SD Card from the host machine, and insert it into the SD Card slot on the target board microSD. You should hear the card 'click' into place.

Preparing the Host

No additional host setup is required to boot from SD.

Booting the Board

Set Environment Variables

You must set a few environment variables in order to boot the board from the SD card. This is done with the setenv command in U-Boot.

On the target, set the following environment variables:

Variable Value          
bootargs 'xilinx_tsn_ep.st_pcp=4 earlycon console=ttyPS1,115200 clk_ignore_unused init_fatal_sh=1 cma=900M root=/dev/sda2 rootwait'          
load_kernel fatload USB 0 0x00200000 Image-6.1-ts-aarch64          
load_dtb fatload USB 0 0x00100000 SMK-zynqmp-sck-kr-g-revB.dtb          
bootcmd run load_kernel load_dtb booti 0x00200000 - 0x00100000          

Example

> setenv bootargs 'xilinx_tsn_ep.st_pcp=4 earlycon console=ttyPS1,115200 clk_ignore_unused init_fatal_sh=1 cma=900M root=/dev/sda2 rootwait'
> setenv load_kernel fatload USB 0 0x00200000 Image-6.1-ts-aarch64
> setenv load_dtb fatload USB 0 0x00100000 SMK-zynqmp-sck-kr-g-revB.dtb
> setenv bootcmd run load_kernel load_dtb booti 0x00200000 - 0x00100000

Load The Kernel

You can use the USB subsystem to load the kernel from the SD card.

Example

> fatload USB 0 0x00200000 Image-6.1-ts-aarch64
reading Image-6.1-ts-aarch64

21885440 bytes read

Load The Device Tree

You can use the USB subsystem to load the device tree file (dtb) from the SD card.

Example

> fatload USB 0 0x00100000 SMK-zynqmp-sck-kr-g-revB.dtb
reading SMK-zynqmp-sck-kr-g-revB.dtb

44711 bytes read

Boot the Kernel

The booti command is used to boot the kernel. It loads the file that was previously loaded using the fatload command.

Example

> booti 0x00200000 - 0x00100000
## Flattened Device Tree blob at 00100000
   Booting using the fdt blob at 0x100000
Working FDT set to 100000
   Loading Device Tree to 000000000fff2000, end 000000000ffffea6 ... OK
Working FDT set to fff2000

Starting kernel ...

Flashing Bootloader

Boot FW management via xmutil

For Flashing Bootloader you need to follow below steps:

Transfer the U-Boot binary (BOOT.bin) to your SD card. In Desktop Factory, this file is located at: build_aarch64-timesys-linux-<libc>/images/bootloaders/BOOT.bin.

sudo cp BOOT.bin /media/boot

To use xmutil you need to choose 'xmutil-xilinx' package in Desktop factory. After booting the board xmutil provides a utility to help in the update of the on-target boot, copy the BOOT.bin file to SD and follow the below steps to boot it. First check the status of the bootfw using command "xmutil bootfw_status"

# xmutil bootfw_status
Image A: Bootable
Image B: Non Bootable
Requested Boot Image: Image B
Last Booted Image: Image A
XilinxSom_QspiImage_v2.0_06030313
ImageA Revision Info: K26-BootFW-01.00-12029f58
ImageB Revision Info: K26-BootFW-01.00-12029f58

To update the on-target boot use command "xmutil bootfw_update -i <path to boot.bin>"

# xmutil bootfw_update -i /media/sdb1/BOOT.bin
Marking last booted image as bootable
Reading Image file
Updating Image B
Marking target image as non bootable
Writing Image to Image B partition
Marking target image as non bootable and requested image
Clearing multiboot register value
/media/sdb1/BOOT.bin successfully updated to Image B partition
#

After the image write is completed issue reset the board with button on the board and check the status of bootfw using command "xmutil bootfw_status". And verify that Linux fully boots with the new boot FW to verify functionality

# xmutil bootfw_status
Image A: Bootable
Image B: Non Bootable
Requested Boot Image: Image B
Last Booted Image: Image B
XilinxSom_QspiImage_v2.0_06030313
ImageA Revision Info: K26-BootFW-01.00-12029f58
ImageB Revision Info: K26-BootFW-01.00-12029f58
#

For futher information about booting through xmutil you can refer below link

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+SOMs+Starter+Kits#Boot-FW-Update-Process

It also has boot image recovery tool which is small application in the AMD provided Starter Kit QSPI image,It provides a simple Ethernet-based interface and application for updating the boot firmware if Linux is not functional. For details on how to use the boot image recovery tool refer the below link

https://docs.amd.com/r/en-US/ug1089-kv260-starter-kit/Boot-Image-Recovery-Tool

Additional Information

Factory Documentation