element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
FPGA
  • Technologies
  • More
FPGA
Forum Picozed + FMC2 booting Petalinux 2020.1 from QSPI/eMMC
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join FPGA to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 1 reply
  • Subscribers 558 subscribers
  • Views 1180 views
  • Users 0 members are here
  • fpga
  • petalinux2020
Related

Picozed + FMC2 booting Petalinux 2020.1 from QSPI/eMMC

mesamike
mesamike over 5 years ago

Are there any instructions anywhere for booting Petalinux 2020.1 on a picozed from QSPI and kernel in on-board eMMC?

I've followed various older instructions for building an appropriate BOOT.BIN file and writing that to the QSPI Flash and copying the image.ub file to the onboard eMMC, but I still can't get petalinux to boot up.

When I power up with the switches set to boot from QSPI, the FPGA code apparently gets loaded OK, ,since the blue "FPGA DOne" LED comes on, but the next stages of booting fail.
First, U-Boot detects the QSPI flash, but then gives an error about "bad CRC;

 

U-Boot 2020.01 (Oct 30 2020 - 12:46:02 +0000)

 

CPU:   Zynq 7z020

Silicon: v3.1

DRAM:  ECC disabled 1 GiB

Flash: 0 Bytes

NAND:  0 MiB

MMC:   mmc@e0100000: 0, mmc@e0101000: 1

Loading Environment from SPI Flash... SF: Detected n25q128a13 with page size 256 Bytes, erase size 4 KiB, total 16 MiB

*** Warning - bad CRC, using default environment

 

Continuing on, it gives several 'Wrong image format for for "source" command' errors.

In:     serial@e0001000
Out:   serial@e0001000

Err:   serial@e0001000

Net:

ZYNQ GEM: e000b000, mdio bus e000b000, phyaddr 0, interface rgmii-id

 

Warning: ethernet@e000b000 using MAC address from DT

eth0: ethernet@e000b000

Hit any key to stop autoboot:  0

SF: Detected n25q128a13 with page size 256 Bytes, erase size 4 KiB, total 16 MiB

device 0 offset 0xfc0000, size 0x40000

SF: 262144 bytes @ 0xfc0000 Read: OK

## Executing script at 03000000

Wrong image format for "source" command

SCRIPT FAILED: continuing...

## Executing script at 03000000

Wrong image format for "source" command

SCRIPT FAILED: continuing...

MMC: no card present

switch to partitions #0, OK

mmc1(part 0) is current device

Scanning mmc 1:1...

SF: Detected n25q128a13 with page size 256 Bytes, erase size 4 KiB, total 16 MiB

device 0 offset 0xfc0000, size 0x40000

SF: 262144 bytes @ 0xfc0000 Read: OK

## Executing script at 03000000

Wrong image format for "source" command

SCRIPT FAILED: continuing...

no devices available

SCRIPT FAILED: continuing...

## Executing script at 03000000

Wrong image format for "source" command

SCRIPT FAILED: continuing...



Still it continues, now trying to read an image via TFTP. Eventually it gives up, leaving me at the bootloader prompt:

Starting USB...

Bus usb@e0002000: USB EHCI 1.00

scanning bus usb@e0002000 for devices... 1 USB Device(s) found

       scanning usb for storage devices... 0 Storage Device(s) found

 

Device 0: unknown device

 

Device 1: unknown device

BOOTP broadcast 1

BOOTP broadcast 2

BOOTP broadcast 3

DHCP client bound to address 192.168.2.100 (1149 ms)

*** ERROR: `serverip' not set

Cannot autoload with TFTPGET

missing environment variable: pxeuuid

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/01-00-0a-35-00-1e-53

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A80264

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A8026

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A802

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A80

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A8

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm-zynq-zynq

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm-zynq

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default

*** ERROR: `serverip' not set

Config file not found

BOOTP broadcast 1

DHCP client bound to address 192.168.2.100 (480 ms)

*** ERROR: `serverip' not set

Cannot autoload with TFTPGET

BOOTP broadcast 1

BOOTP broadcast 2

DHCP client bound to address 192.168.2.100 (609 ms)

*** ERROR: `serverip' not set

Cannot autoload with TFTPGET

Zynq>

 

 

It's unclear to me what else I need to do to get my picozed+FMC2 to boot from QSPI and find the kernel image on the onboard eMMC.

  • Sign in to reply
  • Cancel
  • drozwood90
    drozwood90 over 5 years ago

    Hi there,

     

    We have not finished with the 2020.1 branch at this time. We are still working on the specific boot modes for various products.  This release you will see a large addition to the boot mode code.  Expect tags this week. 

    Thank you for posting these details though, I will loop this by the team today.  If it is something they are aware of, we will get you a response.  If not, then please hold up with the 2020.1 branch as it is still in flux (changes expected today/tomorrow, tagging afterwards).  This release has changes specifically in the boot mode area, so it is possible we have seen this and already fixed it.

     

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube