Now Enrolling
  • Start Date
  • End Date
  • Roadtesters Needed 5
  • Applicants 30
Buy now Buy Product

Enrollment closes in

Days 0 Hours 0 Mins 0 Secs 0

  • Author Author: srutledge
  • Views 29393 views
  • Likes 21 likes
  • Comments 18 comments
Group Actions
Related Products
RoadTests in Progress
Other RoadTest Reviews
RoadTest Product Reviewers

AMD Xilinx Kria KV260 Vision AI Starter Kit

srutledge

Table of contents

RoadTest Goals
A) Produce a 2 to 3 minute unboxing video. Here are two examples: Example 1 Example 2
B) Test the out-of-box experience of the product.
C) Build a project and show how you did it.

Product Variants
• SK-KV260-G — this is the one used in this roadtest
• SK-KV260-G-ED

Description

The first starter kit in the KriaTm portfolio, the KV260 Vision AI Starter Kit is an out-ofthe-box platform for advanced vision application development. It is equipped with a non-production version of the production K26 SOM. This SOM and fansink are mounted to an evaluation carrier card optimized for vision applications, featuring multi-camera support via ON Semiconductor Imager Access System (IAS) and Raspberry Pi connectors. Enabled by a growing ecosystem of accelerated applications for the KV260 Vision AI Starter Kit, developers of all types can get applications up and running in under 1 hour, with no FPGA experience needed. From there, customization and differentiation can be added via preferred design environments, at any level of abstraction—from application software to AI model to FPGA design. With both hardware and software development requirements simplified, the KV260 Vision AI Starter Kit is the fastest and easiest platform for application development with the goal of volume deployment on Kria K26 SOMs.

Features

Kit Contents

  • KV260 Development platform for Kria K26 SOMs
  • Accessory pack for the Kria KV260 Vision AI Starter Kit:
    • KV260 Power Supply & Adapter
    • USB-A to micro-B Cable
    • Ethernet Cable
    • HDMI Cable (Male to Male)
    • MicroSD card and MicroSD to SD Adapter
    • 13MP Auto Focus RGB Camera Module

Additional Information
• Product Brief
• Datasheet
• User Guide
• Getting Started Guide
• Github Applications
• Kria SOM Github
• Avnet Page Brief
• Getting Started Video

Important Dates 

Begin enrollment:  Nov 30 2022
End enrollment:  Dec 30 2022
Select roadtesters:  Jan 3 2023
Ship unit: Jan 26 2023
Begin Roadtesting:  Jan 27 2023
Element14 follow up: Feb 27, 2023
Post Reviews by:  Mar 27, 2023

Official Roadtesters

  • feiticeir0  (due date April 17)
  • skruglewicz (due date Mar 27)
  • digital_pat (due date Mar 27)
  • jasonwier92 (due date Mar 27)
  • work14 (suspend due date as of Feb 28th; roadtester reported board failure)

Terms and Conditions
Click Here to read the Terms and Conditions.

RoadTest Reviews
Comment List
Anonymous
Parents

  • Just looking to see if anyone got their board to boot yet with Ubuntu.  From what I can tell you download the special Ubuntu for the Xilinx, but the instructions say download the image. We, there is not an image.  There are two rootfs to be placed on an ext4 filesystem, depending on your preference of compression (and to add to the confusion) and a System-boot based on a FAT filesystem.  So I took an SD card and made a system-boot FAT and put that there and created an EXT4 and put the rootfs there.

    Booting starts here...

    switch to partitions #0, OK
    mmc1 is current device
    Scanning mmc 1:1...
    Found U-Boot script /boot.scr.uimg
    5980 bytes read in 16 ms (364.3 KiB/s)
    ## Executing script at 20000000
    Configuring the cma value based on the board type
    ZynqMP SMK-K26 Rev1/B/A: No match
    ZynqMP SMK-K26 Rev1/B/A: No match
    cma=1000M
    Loading image.fit
    74448580 bytes read in 8963 ms (7.9 MiB/s)
    ## Loading kernel from FIT Image at 10000000 ...
    Using 'conf-zynqmp-smk-k26-revA' configuration
    Trying 'kernel-1' kernel subimage
    Description: Ubuntu kernel

    Booting fails here...

    [ 6.351160] 0x000002240000-0x000002250000 : "SHA256"
    [ 6.364173] 0x000002250000-0x000004000000 : "User"
    [ 6.496472] random: fast init done
    [ 6.501701] da9121 0-0033: Device detected (device-ID: 0x05, var-ID: 0x21, DA9131)
    [ 6.551966] da9121 0-0032: Device detected (device-ID: 0x05, var-ID: 0x20, DA9130)
    [ 6.919637] random: crng init done
    [ 8.751137] async_tx: api initialized (async)
    [ 35.820889] da9131_buck1: disabling

    This is my first attempt and I will be testing more today, but if someone has something working already, please share.

  • in reply to jasonwier92

    Answering some of my own questions..

    1. Need to update the firmware. I did this via the firmware button and web interface
    2. Have to change the label on the SD Card (ext4 partition) to "writable"

    Now I have it booted to a root@ubuntu: command prompt

  • in reply to jasonwier92

    Some might say I talk to myself too much, but that is okay, because it is true.

    Success!  I have the Ubuntu GUI up and running. I had problems with the ubuntu user password, so I took out the SD Card and put in my computer and edited the /etc/shadow to have no password for root and ubuntu.  Booted back and get maintenance mode where I set the root and ubuntu passwords to my liking.  

    Now to have fun!

  • in reply to jasonwier92

    I found the same issue. Xilinx did note the need to update the firmware in their getting started guide. This note did not link to directions, so a level of research was needed just to boot. 

    In Xilinx's defence, it is critical to have the first stage boot loader and the operating system in sync. There are many settings that define how the device works that can only be modified during the first stage. This is a hard problem considering these are stored in different memories, one non-volatile and one removable.

    It would be nice to have a clear link in the note to the instructions to fix this with a "clear use this version with this version of Ubuntu". Even better would be to add the steps to update to the start guide. It would also be nice to have a special image that only installed the updated firmware on boot. So the instructions would be burn this, boot, burn Ubuntu, boot.

    Ultimately the information to fix this was published and available; this allowed both of us to overcome this issue and boot Ubuntu.

Comment
  • in reply to jasonwier92

    I found the same issue. Xilinx did note the need to update the firmware in their getting started guide. This note did not link to directions, so a level of research was needed just to boot. 

    In Xilinx's defence, it is critical to have the first stage boot loader and the operating system in sync. There are many settings that define how the device works that can only be modified during the first stage. This is a hard problem considering these are stored in different memories, one non-volatile and one removable.

    It would be nice to have a clear link in the note to the instructions to fix this with a "clear use this version with this version of Ubuntu". Even better would be to add the steps to update to the start guide. It would also be nice to have a special image that only installed the updated firmware on boot. So the instructions would be burn this, boot, burn Ubuntu, boot.

    Ultimately the information to fix this was published and available; this allowed both of us to overcome this issue and boot Ubuntu.

Children
No Data