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

linux kernel uncompressing issue

Gary Wu
Expert 3313 points
Other Parts Discussed in Thread: OMAPL138

Hi,

   My customer want to boot linux kernel in their own OMAPL138 board.

And when he tried to boot linux, there was an error below.

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

 

And connectting the board with JTAG emulator, there was some log in DDR.

action:

(1)compile linux kernel

(2)check system.map and find "_log_buf"

(3)loacte the address of DDR and the logs were seen below.

The logs are

    Linux version 2.6.35.3-433

    …………
    Console: colour dummy device 80x30
    Calibrating delay loop...
 
 
It seems the kernel stop in the step of "Calibrating delay loop..."
After adding the print function, we find that the value of "jiffies" dosen't increase.
 

 

  • 0
    TI__Prodigy 635 points

    Hi Gary Wu,

    I am not familiar with OMAPL138, but this issue can happen due to,

    1. timer is not configured properly

    2. Interrupt (at least for timer) is not happening

    Regards

    Afzal

  • 0 in reply to Afzal MOHAMMED
    TI__Expert 3313 points

    Hi Afzal,

        Thank you for your reply.

        Could you give me some suggestions how to fixe this issue? Doesn't  linux kernel configure properly? Or something wrong in hareware? 

  • 0 in reply to Gary Wu
    TI__Prodigy 635 points

    Hi Gary Wu,

    Linux configures it properly provided hardware specific things are handled properly.

    A clockevent has to be registered that associates timer hardware.

    Kernel handles clockevent properly, provided timer hardware behaves properly as expected by Kernel.

    Same holds good for interrupt controller also.

    And for clockevent to work properly, interrupts also should happen.

    Probably they can try putting prints in timer (used for clockevent) interrupt handler and see

    whether interrupts are happening. As you mentioned jiffies are not changing, then probably

    interrupt handler is not getting called. It can be because timer is not configured to generate

    events properly and/or interrupts are not setup properly

    Regards

    Afzal