• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 296 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.

New to Embedded Linux

Thangadurai
Prodigy 50 points

Other Parts Discussed in Thread: OMAP3530

Hi,

I am new to embedded linux.

I have TI OMAP3530 processor Board with 128MB NAND Flash and 128MB SDRAM

I need to compile my own image for x-loader,u-boot,kernal2.6.28 and filesystem.

Please help me to do this.

Thanks in advance...

By,

Thangadurai

  • 0
    TI__Mastermind 41665 points

    Which board do you have? For the most part there should be documentation included with your board somewhere that covers rebuilding the boot loaders and kernel, in the case of the Mistral OMAP3 EVM there are some instructions in the getting started guide.

  • 0 in reply to Bernie Thompson TI
    Prodigy 50 points

    Hi,

    I have DevKit8000 OMAP3530 Processor Kit.

    They provided the image and source code for x-loader,u-boot1.3.3,kernal2.6.28,filesystem.

    I checked the images they provide is working.

    i compiled the Source for x-loader,u-boot,kernal,filesystem its compiled without error.

    x-loader and u-boot i compiled is not working properly but the kernal and filesystemi compiled

    is working with existing x-loader and u-boot image.

    i cant figure it out the problem

    What shall i do to correct this?

    the command i use to compile the u-boot1.3.3

    make distclean

    make omap3devkit8000_config

    make

  • 0 in reply to Thangadurai
    TI__Expert 4590 points

    If the vendor provided xloader and u-boot binaries are working then, there has to be some environmental problems.

    Though I cannot be sure about your environment but I suspect that your code may not be getting cross compiled.

    Can you try the following:

    1) Ensure that a cross compiler tool chain (e.g. codesourcery) is in your PATH

    2) Use the commands (assuming coudesourcery; you may have to adapt accordingly):

    make CROSS_COMPILE=arm-none-linux-gnueabi- disclean

    make CROSS_COMPILE=arm-none-linux-gnueabi- omap3devkit_config

    make CROSS_COMPILE=arm-none-linux-gnueabi-

    3) Paste the log from the terminal window - to see what error(s) you are getting.

    I also suggest you use MMC/SD card as your boot medium for these experiments... so as to fall back on the manufacturer provided (working) images on the flash.

    Best regards,
    Sanjeev