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
Avnet Boards General Lab 1.3 not working at the final stage
  • 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 Not Answered
  • Replies 7 replies
  • Subscribers 362 subscribers
  • Views 541 views
  • Users 0 members are here
Related

Lab 1.3 not working at the final stage

Former Member
Former Member over 12 years ago

Hi all,
  
    Just began exploring the Zedboard. I am sure everybody has completed this . My Lab 1.3 fails at the last stage.

    Hit any key to stop autoboot:0
zed-boot> 

    after Hit any key to stop autoboot:0, I do not get the zed-boot>  prompt.

Instead I see a lot of message pertaining to the kernel code..( error / code crash ...)

    What are the files I need to have in the SD ram.

    I have the following:

    1. devicetree.dtb ( renamed factory file in SD card)
    2. boot.bin ( from lab 1.3 output in SD card)
    3. ramdisk32M.image.gz ( renamed factory file )
    4. ZImage ( from factory file in SD card )

    What did I do wrong ???

  Please help!!

Thank you

  • Sign in to reply
  • Cancel
Parents
  • zedhed
    0 zedhed over 12 years ago

    Hi lasur2,

    I have not seen a U-Boot crash at this point before when using the git 14.2 release tag.  Did you press a key during the autoboot countdown?  If not, U-Boot will automatically try to boot Linux, which if you are still on Lab 1.3 would be expected to fail.

    Assuming that you are pressing a key to interrupt autoboot and there is a real crash, perhaps you accidentally ended up on the wrong release tag or board config.  You can see what release tag is currently checked out by changing into the U-Boot folder and checking the status of the local repository.

    $ cd u-boot-xlnx
    $ git status

    Also, be sure that you configured U-Boot for ZedBoard using this command:

    $ make zynq_zed_config

    You can also try the lab solution file boot.bin to see if you see the same error.

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 12 years ago in reply to zedhed

    Hi Kevin,

        Thanks for the response. I am re-doing the lab as I need to get it working !

       $ cd u-boot-xlnx

       $ git status gives me the following o/p

    # On branch xilinx-14.2-build1-trd
    # Changed but not updated:
    #   (use "git add <file>..." to update what will be committed)
    #   (use "git checkout -- <file>..." to discard changes in working directory)
    #
    #tmodified:   include/configs/zynq_zed.h
    #
    no changes added to commit (use "git add" and/or "git commit -a")


       $ make distclean gives me the following O/p
       awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend

       $ make zynq_zed_config gives me
    awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
    Configuring for zynq_zed board...

    Then copy and paste the patch file Now,

    $ git apply 0001-Xilinx-ARM-Experimental-32MB-Ramdisk-on-ZedBoard.patch

    Upto this point is lab1.2 Experiment #2 and I am successful.

    Now when I move to lab1.2 Experiment #3,

    $pwd
    I am in /home/training/u-boot-xlnx

    $ make

    I see the following errors:

    ake: arm-linux-gcc: Command not found
    /bin/sh: arm-linux-gcc: command not found
    dirname: missing operand
    Try `dirname --help' for more information.
    Generating include/autoconf.mk
    /bin/sh: line 3: arm-linux-gcc: command not found
    /bin/sh: arm-linux-gcc: command not found
    dirname: missing operand
    Try `dirname --help' for more information.
    Generating include/autoconf.mk.dep
    /bin/sh: line 3: arm-linux-gcc: command not found
    make: arm-linux-gcc: Command not found
    /bin/sh: arm-linux-gcc: command not found
    dirname: missing operand
    Try `dirname --help' for more information.
    /bin/sh: arm-linux-gcc: command not found
    /bin/sh: arm-linux-ld: command not found
    /bin/sh: arm-linux-gcc: command not found
    dirname: missing operand
    Try `dirname --help' for more information.
    /bin/sh: arm-linux-gcc: command not found
    dirname: missing operand
    Try `dirname --help' for more information.
    arm-linux-gcc -DDO_DEPS_ONLY
    tt-g  -Os   -fno-common -ffixed-r8 -msoft-float   -fno-strict-aliasing  -fno-common -ffixed-r8 -msoft-float  -D__KERNEL__ -I/home/training/u-boot-xlnx/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__         -march=armv5 -march=armv7-a -I/home/training/u-boot-xlnx/board/xilinx/common -I/home/training/u-boot-xlnx/board/xilinx/zynq_common -Wall -Wstrict-prototypes -mno-unaligned-access   
    tt-o lib/asm-offsets.s lib/asm-offsets.c -c -S
    make: arm-linux-gcc: Command not found
    make: *** [lib/asm-offsets.s] Error 127


    This is the cross compiler error I suppose. I am not sure how to fix it. please help!!

    Thank you!!


    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • zedhed
    0 zedhed over 12 years ago in reply to Former Member

    Hi lasur2,

    Those error messages seem to indicate that the cross compiler toolchain cannot be found on your system.  I can think of two likely causes for this.  The first cause would be that the CodeSourcery Toolchain did not get installed correctly during the Lab 0.1 exercises.  The second is that the wrong compiler prefix OR incorrect paths have been specified.

    Both the toolchain and the path to the toolchain must be setup on your system.  Otherwise, at build time, the compiler executable will not be found properly.

    One other thing to note is that I used an Ubuntu machine a while back which required me to specify the cross-compiler prefix as part of the make command.  If you have a similar system, you may need to do something like this:

    $ make ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi-

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 12 years ago in reply to zedhed

    Hi Kevin,

       Thanks for your remote support. I was able to debug with your pointer and got the lab1.3 working ..

       I am currently facing difficulty in getting lab 2.3 work. I am debugging on my own. Shall seek your help and pointers in case I run into problems while debug.

    Thank you very much once again!!

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

    Hi Kevin,

       Thanks for your remote support. I was able to debug with your pointer and got the lab1.3 working ..

       I am currently facing difficulty in getting lab 2.3 work. I am debugging on my own. Shall seek your help and pointers in case I run into problems while debug.

    Thank you very much once again!!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • zedhed
    0 zedhed over 12 years ago in reply to Former Member

    Hi lasur2,

    Glad to hear that you were able to get Lab 1.3 working. If you continue to have problems with Lab 2.3, please repost your 2.3 issue as a new topic so that it is easier for other community members to find.

    Regards,

    -Kevin

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