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 U-Boot Issues
  • 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 5 replies
  • Subscribers 357 subscribers
  • Views 426 views
  • Users 0 members are here
Related

U-Boot Issues

Former Member
Former Member over 12 years ago


I'm following the instructions on the Build U-Boot wiki (www.wiki.xilinx.com/Build+U-Boot) and am running into some issues.

The first errors kept saying that it couldn't find the command for "arm-linux-ar" or "arm-linux-gcc", etc. I fixed this by making a soft link to "arm-linux-gnueabi-ar", "arm-linux-gnueabi-gcc", etc. (for example: sudo ln -s /usr/bin/arm-linux-gnueabi-gcc /usr/bin/arm-linux-gcc). That made everything compile correctly (with no errors) when I executed the "make -j zynq_zed" command.

However, the wiki says that after this completes, the u-boot elf file should be located in the top level source directory, and that the mkimage utility is created in the tools directory. This is not the case. Neither file is anywhere to be found... I'm not getting any errors during the build, and I'm confused on why this isn't working... Please help!

Thanks in advance.

  • Sign in to reply
  • Cancel
  • Former Member
    0 Former Member over 12 years ago

    Here are the exact error messages I get when I remove the symbolic links:

    zackshef@ubuntu:~/xilinx/u-boot-xlnx-master$ make -j zynq_zed > makefile_output.txt
    /bin/bash: arm-linux-gcc: command not found
    /bin/bash: arm-linux-gcc: command not found
    dirname: missing operand
    Try `dirname --help' for more information.
    /bin/bash: line 3: arm-linux-gcc: command not found
    /bin/bash: line 3: arm-linux-gcc: command not found
    /bin/bash: arm-linux-gcc: command not found
    /bin/bash: arm-linux-gcc: command not found
    dirname: missing operand
    Try `dirname --help' for more information.
    /bin/bash: arm-linux-gcc: command not found
    /bin/bash: arm-linux-ld: command not found
    /bin/bash: arm-linux-gcc: command not found
    make[1]: *** [lib/asm-offsets.s] Error 127
    make[1]: *** Waiting for unfinished jobs....
    make[1]: *** wait: No child processes.  Stop.
    make: *** [zynq_zed] Error 2
    zackshef@ubuntu:~/xilinx/u-boot-xlnx-master$

    I got similar error messages for:
    arm-linux-ld
    arm-linux-ar
    arm-linux-objdump
    arm-linux-objcopy
    arm-linux-nm

    I used these commands to et rid of those errors:
    sudo ln -s arm-linux-gnueabi-gcc arm-linux-gcc
    sudo ln -s arm-linux-gnueabi-ld arm-linux-ld
    sudo ln -s arm-linux-gnueabi-ar arm-linux-ar
    sudo ln -s arm-linux-gnueabi-objdump arm-linux-objdump
    sudo ln -s arm-linux-gnueabi-objcopy arm-linux-objcopy
    sudo ln -s arm-linux-gnueabi-nm arm-linux-nm

    It got rid of the error messages but failed to create the u-boot elf and the mkimage utility...

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

    Haa!

    Well it turns out if I DON'T make a SYMBOLIC link, but a hard link instead (which means, remove the "-s" from "sudo ln -s arm-linux-gnueabi-ggcc arm linux-gcc" and such), everything works out perfectly. u-boot elf is here as well as the mkimage in the tools directory.

    Thanks for the help! :P

    • 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 Former Member

    This works great for the u-boot cross build, but not for the kernel. I found (and I hadn't previously) the library that contained the arm-xilinx-linux-gnueabi- tools.

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

    Instead of using hard/soft-links you could use set CROSS_COMPILE:
    export CROSS_COMPILE=arm-xilinx-linux-gnueabi-
    or
    export CROSS_COMPILE=arm-linux-gnueabi-

    • 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 Former Member

    Thanks for the reply vanmierlo.

    The problem was that I didn't have the cross compile toolchain installed from code sourcery. I had read somewhere that it came with the Xilinx design suite, but it doesn't. I found the link to install the tools on one of the speedway labs.

    When I tried to compile the kernel with arm-linux-gnueabi-, it would seize up and I'd have to restart. For some reason, the arm-xilinx-linux-gnueabi- is a little smoother for kernel corss-compilation.

    • 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