MPC8560 Linux...

Check the serial driver in the kernel..mainly the UART clock, is it using the processor clock or some diff clock? Check if the debug option enabled inside the kernel.

chill, sudip

Some things to use during board bringups on a limited test equipment environment...(assuming that initd is not getting started or video driver is shot).

1. Identify a test point or LED on your board and write a function to activate these indicator. The more indicators, the quicker you can narrow down to identifying your failure points. Use oscilliscope trigger for HW test points. Use your eye ball(s) for LED ON/OFF.

1. Insert indicator function in various stages of your boot up codes. Recompile, relink, rebuild ramdisk, load it up the kernel into flash (or TFTP or NFS)

2. Make a note of whether the indicator was triggered or not.

1. Repeat step 1, until you get closer to the failure portion of your kernel init routines.

Time-consuming, yes... But great way to identify the hangups (before getting your video driver).

sivam wrote:

Arghh.. Why are you using such an ancient kernel version for current hardware? Use up-to-date sources!

Best regards,

Wolfgang Denk

Hello Guys,

Thanks alot for the advice. It really helped me. I have identified the problem to be relocation address of CCSRBAR. I am still wondering why the kernel didn't take this value from u-boot ?. I have seen the value been hardcoded in the kernel, but the kernel suppose to take this value from u-boot rite ?

Rgds sivam