• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 440 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.

[OMAP-L138] Question about booting the kernel

Zhang Jingpo
Intellectual 280 points
Other Parts Discussed in Thread: DA8XX

Dear all :

I match a new problem about booting the kernel, please see the infomation below:

Booting with TI UBL

Device OPP (300MHz, 1.2V)

U-Boot 2009.11 (Aug 27 2010 - 13:25:48)

I2C:   ready

DRAM:  64 MB

NAND:  1024 MiB

Bad block table found at page 524160, version 0x01

Bad block table found at page 524032, version 0x01

In:    serial

Out:   serial

Err:   serial

ARM Clock : 300000000 Hz

DDR Clock : 150000000 Hz

Net:   Ethernet PHY: GENERIC @ 0x00

Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x200000, size 0x400000

 4194304 bytes read: OK

Loading from NAND 1GiB 3,3V 8-bit, offset 0x200000

   Image Name:   Linux-2.6.33-rc4

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2500448 Bytes =  2.4 MB

   Load Address: c0008000

   Entry Point:  c0008000

## Booting kernel from Legacy Image at c0700000 ...

   Image Name:   Linux-2.6.33-rc4

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2500448 Bytes =  2.4 MB

   Load Address: c0008000

   Entry Point:  c0008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

 

It stop here.

I have 3 boards and one work well, one can  successfully boot  and sometimes not, the third one doesn't work well, just stop at the 'booting the kernel.'

so what is the problem exist? the hardware or the software? how to check it?

  • 0
    TI__Mastermind 41665 points

    Zhang Jingpo said:

    I have 3 boards and one work well, one can  successfully boot  and sometimes not, the third one doesn't work well, just stop at the 'booting the kernel.'

    so what is the problem exist? the hardware or the software? how to check it?

    What are your U-Boot environment variables (i.e. printenv)? In particular your bootargs variable? Usually when you get to this point that the kernel was uncompressed and is being booted but you don't see anything it implies there is something wrong with your bootargs (such as no console=ttyS0,115200n8).

    Since the U-Boot is printing out successfully, I suspect this is just a software problem, either with the bootargs as suggested above, or something more deeply wrong with your kernel image (it can do this if it is not the right target and has a different UART driver in theory).

  • 0 in reply to Bernie Thompson TI
    Intellectual 280 points

    Dear Bernie:

    please see the following messeage, I cut part of the printed messeage:

    ......

    regulator: VDCDC1: 3200 <--> 3300 mV at 3300 mV

    regulator: VDCDC2: 1750 <--> 3300 mV at 3300 mV

    regulator: VDCDC3: 950 <--> 1375 mV at 1200 mV

    regulator: LDO1: 1800 mV

    regulator: LDO2: 1150 <--> 1300 mV at 1200 mV

    pca953x 1-0020: failed reading register

    i2c-gpio i2c-gpio.1: using pins 20 (SDA) and 21 (SCL)

    Switching to clocksource timer0_1，------well worked boards can go through all the steps, but some boards stopped here, I don't know why.

    musb_hdrc: version 6.0, cppi4.1-dma, host, debug=0

    Waiting for USB PHY clock good...

    musb_hdrc: USB Host mode controller at fee00000 using DMA, IRQ 58

    ......

    any suggestions?  thanks

    Br. 

  • 0 in reply to Zhang Jingpo
    Intellectual 900 points

     

    I have this behavior on a custom board.

    Looking on the google someone have the same problem with hawckboard and post the solution on [1].

    You can't apply directly the patch but is easy to see the line that you have to change.

    The patch is :

    diff --git a/arch/arm/mach-davinci/board-da850-hawk.c b/arch/arm/mach-davinci/board-da850-hawk.c
    index 442ccef..031313c 100644
    --- a/arch/arm/mach-davinci/board-da850-hawk.c
    +++ b/arch/arm/mach-davinci/board-da850-hawk.c
    @@ -582,9 +582,11 @@ static __init void da850_hawk_init(void)
            // Default hawkboard doesn't have RTC battery - so CONFIG_RTC_DRV_OMAP
            //  should be disabled by default

    +#if 0
             ret = da8xx_register_rtc();
            if (ret)
                    pr_warning("da850_hawk_init: rtc setup failed: %d\n", ret);
    +#endif

            // Generic da850(.c) CPUFREQ support ok as long as CONFIG_REGULATOR disabled
             ret = da850_register_cpufreq();

     

    [1] - http://groups.google.com/group/hawkboard/browse_thread/thread/a1830c69f89296d2/3cf0045ed7aa0492?#3cf0045ed7aa049

  • 0 in reply to Aníbal Pinto
    Intellectual 280 points

    Dear Aníbal

    Thank you for your suggestion, but this problem still unsolved. and I can't access the URL you provided, I don't know why. can you send email to me ? thanks.

    zhangjp2008@sina.com

    BR.

    zhang

  • 0 in reply to Bernie Thompson TI
    Intellectual 280 points

    Bernie Thompson said:

    I have 3 boards and one work well, one can  successfully boot  and sometimes not, the third one doesn't work well, just stop at the 'booting the kernel.'

    so what is the problem exist? the hardware or the software? how to check it?

    What are your U-Boot environment variables (i.e. printenv)? In particular your bootargs variable? Usually when you get to this point that the kernel was uncompressed and is being booted but you don't see anything it implies there is something wrong with your bootargs (such as no console=ttyS0,115200n8).

    Since the U-Boot is printing out successfully, I suspect this is just a software problem, either with the bootargs as suggested above, or something more deeply wrong with your kernel image (it can do this if it is not the right target and has a different UART driver in theory).

    [/quote]

    Dear Bernie:

    please check the following:

    baudrate=115200
    bootfile=uImage
    ethaddr=00:00:f8:ea:0a:c1
    ethact=
    bootargs=mem=60m console=tty0 root=/dev/mtdblock4 rw rootfstype=yaffs2 ip=192.16
    8.0.138
    filesize=25B508
    fileaddr=C0700000
    ipaddr=192.168.0.138
    serverip=192.168.0.145
    bootcmd=nboot.e 0xc0700000 0 0x200000; bootm
    bootdelay=1
    stdin=serial
    stdout=serial
    stderr=serial
    ver=U-Boot 2009.08 (Jun 18 2010 - 10:02:40)

    Environment size: 374/262140 bytes

     

    BR.

    zhang

     

  • 0 in reply to Zhang Jingpo
    Intellectual 900 points

     

    Sorry for that, I have missed the paste.

    The correct link :

    - http://groups.google.com/group/hawkboard/browse_thread/thread/a1830c69f89296d2/3cf0045ed7aa0492?#3cf0045ed7aa0492