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
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • 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 & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
ZedBoard Hardware Design linux is not booting on the 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 6 replies
  • Subscribers 340 subscribers
  • Views 1449 views
  • Users 0 members are here
Related

linux is not booting on the zedboard

100aditya
100aditya over 9 years ago

Hi,

   I have done first partition of mine Zedbaord and given it name Boot and i copied following things here:-

BOOT.bin                 
uEnv.txt                        
devicetree.dtb      
uImage
uramdisk.image.gz     
 
Now i am trying to boot it from SD card but it is not happening and i am getting the following message. In this message i have highlighted the error message specially along with other relevant message that i have got in mine tty terminal.
 
  U-Boot 2014.01 (Oct 08 2016 - 12:33:09)
   
  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
  *** Warning - bad CRC, using default environment
   
  In:    serial
  Out:   serial
  Err:   serial
  Net:   Gem.e000b000
  Hit any key to stop autoboot:  3  2  1  0 
  Device: zynq_sdhci
  Manufacturer ID: 27
  OEM: 5048
  Name: SD04G
  Tran Speed: 50000000
  Rd Block Len: 512
  SD version 3.0
  High Capacity: Yes
  Capacity: 3.7 GiB
  Bus Width: 4-bit
  reading uEnv.txt
  226 bytes read in 7 ms (31.3 KiB/s)
  Loaded environment from uEnv.txt
  Importing environment from SD ...
  Running uenvcmd ...
  Device: zynq_sdhci
  Manufacturer ID: 27
  OEM: 5048
  Name: SD04G
  Tran Speed: 50000000
  Rd Block Len: 512
  SD version 3.0
  High Capacity: Yes
  Capacity: 3.7 GiB
  Bus Width: 4-bit
  reading uImage
  4150864 bytes read in 399 ms (9.9 MiB/s)
  reading devicetree.dtb
  9275 bytes read in 16 ms (565.4 KiB/s)
  reading uramdisk.image.gz
  18047061 bytes read in 1698 ms (10.1 MiB/s)
  Wrong Image Format for bootm command
  ERROR: can't get kernel image!
  Copying Linux from SD to RAM...
  reading uImage
  4150864 bytes read in 399 ms (9.9 MiB/s)
  reading devicetree.dtb
  9275 bytes read in 16 ms (565.4 KiB/s)
  reading uramdisk.image.gz
  18047061 bytes read in 1698 ms (10.1 MiB/s)
  Wrong Image Format for bootm command
  ERROR: can't get kernel image!
  zynq-uboot> 
   
   
  The content of mine uenv.txt file is as follows:-
   
 
   boot_Zed=mmcinfo;fatload mmc 0 0x3000000 ${kernel_image}; fatload mmc 0 0x2A00000 ${devicetree_image}; fatload mmc 0 0x2000000 ${ramdisk_image}; bootm 0x3000000 0x2000000 0x2A00000
 
   uenvcmd=run boot_Zed
 
    
 
   I have created the ramdiskimage by following command:-
 
   mkimage -A ARM -T ramdisk -C gzip -n 'ZED filesystem' -d ramdisk.image.gz uramdisk.image.gz
 
    
 
   Upon execution of above command i got the following message:-
 
    
 
    
 
  
    Image Name:   ZED filesystem
  
    Created:      Mon Oct 24 10:40:13 2016
  
    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  
    Data Size:    18046997 Bytes = 17624.02 kB = 17.21 MB
  
    Load Address: 00000000
  
    Entry Point:  00000000
  
     
  
     
  
    So based on mine above information please can u please tell/suggest me the solution of mine problem.
  
     
  
    Regards
  
    Aditya
 
 
    
 
    
 
    
 
  • Sign in to reply
  • Cancel
Parents
  • zedhed
    0 zedhed over 9 years ago

    Hi Aditya,

    Unfortunately, it looks like the kernel crash arises due to some problem within drivers/clk/zynq/clkc.c which can be very difficult to track down.

    One method to track this down is to undo all of your hardware platform and devicetree changes to get back to a known working point.  Slowly adding pieces back in until it fails is usually one of the only ways to find out which setting can be causing issues resulting in the crash you reported.

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • zedhed
    0 zedhed over 9 years ago

    Hi Aditya,

    Unfortunately, it looks like the kernel crash arises due to some problem within drivers/clk/zynq/clkc.c which can be very difficult to track down.

    One method to track this down is to undo all of your hardware platform and devicetree changes to get back to a known working point.  Slowly adding pieces back in until it fails is usually one of the only ways to find out which setting can be causing issues resulting in the crash you reported.

    Regards,

    -Kevin

    • 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