element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • 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 Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • 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
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Software Application Development Booting/InstallingLinux on Zedboard
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 8 replies
  • Subscribers 331 subscribers
  • Views 2624 views
  • Users 0 members are here
Related

Booting/InstallingLinux on Zedboard

Former Member
Former Member over 9 years ago

Hi

I am very new with the embedded software world and I am currently trying to boot Linux Kernel on Zedboard from SD CARD. I had about a week back tried to install on a zybo board and it was working. I had followed the same steps but however ended up running into issues. Currently , I am able to connect to the uboot bootup console via usb-uart and the following is the log.

Further details on how I have done this:

1) Obtained the linux uImage

2) Compiled devicetree.dtb from linux-digilent-dev branch

3)Created a base design in Vivado consisting of the processing system and axi gpio. In the Xilinx SDK created a new zyng fsbl(didn't do any changes to any files). 

4) From Xilinx Tools , create boot image i added the systemwrapper.bit , the fsbl. elf and uboot.elf to create boot.bin.

5) Partioned the SD card into 4 mb space left at start, 1 gb fat partition and rest as ext4 partition.

6) Copied the uImage, boot.bin and devicetree.dtb with same names into the 1gb partition.

7) Set JP9 and JP8 to 3V3 amd JP7 ,JP8 and JP11 to GND.

8) Connected the usb-art ,inserted SD card in the slot and powered on.

9) I can see the following output via minicom console.

U-Boot 2014.01 (Aug 09 2016 - 17:17:22)
 
I2C:   ready
Memory: ECC disabled
DRAM:  512 MiB
MMC:   zynq_sdhci: 0
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
In:    serial
Out:   serial
Err:   serial
Net:   Gem.e000b000
Hit any key to stop autoboot:  0 
Configure PL and booting Linux from TFTP...
Device: zynq_sdhci
Manufacturer ID: 3
OEM: 5344
Name: SU04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
Xilinx Device
Descriptor @ 0x1ffbaa54
Family:         Zynq PL
Interface type: Device configuration interface (Zynq)
Device Size:    4045564 bytes
Cookie:         0x20 (32)
Device name:    7z020
No Device Function Table.
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000: No link.
fpga - loadable FPGA image support
 
Usage:
fpga [operation type] [device number] [image address] [image size]
fpga operations:
  dump  [dev]                   Load device to memory buffer
  info  [dev]                   list known device information
  load  [dev] [address] [size]  Load device from memory buffer
  loadp [dev] [address] [size]  Load device from memory buffer with partial bitstream
  loadb [dev] [address] [size]  Load device from bitstream buffer (Xilinx only)
  loadbp        [dev] [address] [size]  Load device from bitstream buffer with partial bitstream(Xilinx only)
  loadmk [dev] [address]        Load device generated with mkimage
        For loadmk operating on FIT format uImage address must include
        subimage unit name in the form of addr:<subimg_uname>
Load device from filesystem (FAT by default) (Xilinx only)
  loadfs [dev] [address] [image size] [blocksize] <interface>
        [<dev[:part]>] <filename>
 
Gem.e000b000:0 is connected to Gem.e000b000.  Reconnecting to Gem.e000b000
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000: No link.
Gem.e000b000:0 is connected to Gem.e000b000.  Reconnecting to Gem.e000b000
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000: No link.
Gem.e000b000:0 is connected to Gem.e000b000.  Reconnecting to Gem.e000b000
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000: No link.
Wrong Image Format for bootm command
ERROR: can't get kernel image!
zynq-uboot> 
 
The bolded text above has got me wondering why is that it is saying loading from tftp despite i have setup jumpers to boot from sd card? I went to the zynq-common.h bootfile in uboot-digilent-dev-master-next and noticed that if it boots from sd_card the following needs to be done:
 
 
  sdboot=if mmcinfo; then " \
  "run uenvboot; " \
  "echo Copying Linux from SD to RAM... && " \
  "fatload mmc 0 0x3000000 ${kernel_image} && " \
  "fatload mmc 0 0x2A00000 ${devicetree_image} && " \
  "bootm 0x3000000 0x2000000 0x2A00000; " \
  "fi\0" \
   
  so something like copying linux from sd to ram should come up.  Can someone help me with this? I also wanted to know what exactly is being done in the uboot. Has the pl been initialized?
 
  • Sign in to reply
  • Cancel
Parents
  • casey.mcmullen.ice-aec
    0 casey.mcmullen.ice-aec over 7 years ago

    I had the same problem with my microzed board. Doing "fatload,fatload,bootm" at the zynq boot prompt also worked for me, but that's not a full solution.

     

    Found a solution here: https://forums.xilinx.com/t5/Embedded-Linux/Kernel-Boot-Failing-on-Zynq-in-U-Boot/td-p/703136

    It says, make sure your SD clock speed is 50 MHz and not 25 MHz. Mine was indeed set to 25, rebuilding at 50 MHz solved it and now my board boots just fine unassisted.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • casey.mcmullen.ice-aec
    0 casey.mcmullen.ice-aec over 7 years ago

    I had the same problem with my microzed board. Doing "fatload,fatload,bootm" at the zynq boot prompt also worked for me, but that's not a full solution.

     

    Found a solution here: https://forums.xilinx.com/t5/Embedded-Linux/Kernel-Boot-Failing-on-Zynq-in-U-Boot/td-p/703136

    It says, make sure your SD clock speed is 50 MHz and not 25 MHz. Mine was indeed set to 25, rebuilding at 50 MHz solved it and now my board boots just fine unassisted.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
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