• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 458 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

U-Boot build failed

Eric Chen
Intellectual 810 points

Hi,

     I installed the latest CodeSourcery Lite toolchain in UBUNTU 11.04 and followed the steps described in Linux PSP driver document to build U-Boot. In U-Boot-MIN building, the first steps had no error. When I executed $ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm u-boot.ti to build U-Boot-MIN, lots of error message prompted as the following:

make[1]: arm-none-linux-gnueabi-gcc: Command not found
make[1]: Entering directory `/home/eric/Working/TI814X-LINUX-PSP-04.01.00.05/src/u-boot/u-boot-04.01.00.05/tools'
make[1]: Nothing to be done for `_depend'.

    The PATH is set correctly for CodeSourcery tool and U-Boot. I don't know why such error happened. Could any one give a help?

    I also tried CodeSourcery version 2009q1 and the problem remained.

Regards,

    Eric

  • 0
    TI__Expert 5290 points

    Something is going wrong in how the PATH for the toolchain is set up. What does "$echo $PATH" give before you try to build?

    Regards,

    Vaibhav

  • 0 in reply to Vaibhav Bedia
    Intellectual 810 points

    The CodeSourcery was installed in the default path  /eric/CodeSourcery/Source_G++_Lite, and PSP was extracted in /eric/Working/TI814X-LINUX-PSP-04.01.00.05

     

    I set the PATH according to the document:

    export PATH=/CodeSourcery/Sourcery_G++_Lite/bin:$PATH

    export PATH=/Working/TI814X-LINUX-PSP-04.01.00.05/src/u-boot/u-boot-04.01.00.05/tools

     

    $echo $PATH shows the PATH as

    /Working/TI814X-LINUX-PSP-04.01.00.05/src/u-boot/u-boot-04.01.00.05/tools:/CodeSourcery/Sourcery_G++_Lite/bin:/usr/local/CCSv5/ccsv5/eclipse/jre/bin:/usr/local/CCSv5/ccsv5/eclipse/jre/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

     

    By the way, is building U-Boot in Linux the only way to make image of code written to storage? It's preferred to us to make all the development, code building, debugging and testing in Windows environment.

     

    Thanks.

  • 0 in reply to Eric Chen
    TI__Expert 5290 points

    You need to specify the complete path.

    So this

    Eric Chen said:
    export PATH=/CodeSourcery/Sourcery_G++_Lite/bin:$PATH

    should be

    export PATH=/eric/CodeSourcery/Sourcery_G++_Lite/bin:$PATH

    and so on.

    Eric Chen said:
    is building U-Boot in Linux the only way to make image of code written to storage? It's preferred to us to make all the development, code building, debugging and testing in Windows environment.

    Yes. If you haven't done so already, you could try out Ubuntu inside VirtualBox on Windows or vice-versa.

    Regards,

    Vaibhav

     

  • 0 in reply to Vaibhav Bedia
    Intellectual 810 points

    After set the full path of toolchain, the images could be built. Thank you very much.

     

    Our target is to design our own board (with different components than EVM8148) and our own code for specific purpose. To achieve this, we need to modify U-Boot-MIN for our board and replace the second stage U-Boot by our own code. I have two questions about this process:

    1. Is there any detail description on how to modify the U-Boot-Min for specific board? For example, if our own board is with different DDR2 or SPI flash than EVM8148 test board, how could I modify the source of U-Boot-MIN for correct DDR and flash setting to make a workable image for our board?

    2. The second stage of U-Boot shall finally be replaced by our code. If I build a .out file in CCS, how could I make our board able to boot up alone with our code?

     

    Regards,

        Eric

  • 0 in reply to Eric Chen
    TI__Expert 5290 points

    Can you please create a new thread for this?

    Thanks,

    Vaibhav