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

kernel booting stops at " starting kernel"

Srinivas C
Prodigy 70 points
Other Parts Discussed in Thread: AM3517

I am using beagle board and using u-boot and the kernel built by myself.

The kernel boot stops at " starting kernel"

I tried changing the console type to ttyO2, ttyS2 by setting the boot args using setenv

Even I tried to change the boot options in menuconfig to set the console type to ttyO2 and used the same in bootargs

But no use

Am I doing something wrong while building the kernel?

Can someone help me

Srinivas

  • 0
    Prodigy 20 points

    I am stuck with the same issue :-(

    Have you found a solution to this?

    If I use the prebuilt u-boot, it works. I cannot use a u-boot I compiled myself.

    I can build a kernel that loads using the prebuilt uboot only.

    Using source from u-boot-2010.06-psp04.02.00.07.sdk from ti-sdk-am3517-evm-05.02.00.00

  • 0 in reply to Serge Blais
    TI__Intellectual 1505 points

    Serge Blais said:

    Using source from u-boot-2010.06-psp04.02.00.07.sdk from ti-sdk-am3517-evm-05.02.00.00

    It is not a good idea to use the U-Boot from am3517 on the beagleboard.  The SDK for the beagleboard uses a different (newer) version of U-Boot.

  • 0 in reply to Tom Rini
    Prodigy 20 points

    Sorry for not being clear.

     

    I am seeing the same symptoms but for different board (am3517evm) from which I am using the correct psp.

    As I stated,the precompiled u-boot worked. I have to assume it was built from the same source using the same compiler provided in the sdk.

    I replied to this email because I assumed the issue might be resolved the same way.

     

    A few other posts in here describe that switching compilers may solve this.

    I would hope the arago arm compiler was used to build the provided pre compiled binaries.

    I was able to build an x-loader and a kernel from it.

    I just plugged-in the precompiled uboot to make it go.

  • 0 in reply to Serge Blais
    TI__Intellectual 1505 points

    Serge Blais said:

    I am seeing the same symptoms but for different board (am3517evm) from which I am using the correct psp.

    As I stated,the precompiled u-boot worked. I have to assume it was built from the same source using the same compiler provided in the sdk.

    I replied to this email because I assumed the issue might be resolved the same way.

     

    A few other posts in here describe that switching compilers may solve this.

    I would hope the arago arm compiler was used to build the provided pre compiled binaries.

    I was able to build an x-loader and a kernel from it.

    I just plugged-in the precompiled uboot to make it go.

    You should be able to take the provided sources and use the provided and in your case do the following in the U-Boot sources:

    $ make ARCH=arm CROSS_COMPILE=/path/to/ezsdk/v5.02/ti-sdk-am3517-evm-05.02.00.00/linux-devkit/bin/arm-arago-linux-gnueabi- am3517_evm

    And rebuild U-Boot and similar commands for x-load (am3517evm_config and then all) and the kernel (am3517_evm_defconfig and all) produce functional binaries.

    From that point you can start making modifications and I would highly encourage you to place all of the sources into some form of SCM before you start making changes.  What I personally do after I install any of the SDKs is:

    $ cd ti-sdk-.../psp

    $ git init

    $ git add *

    $ git commit -s -m "Initial import"