2011/7/28 Sricharan R <r.sricharan@xxxxxx>: >>-----Original Message----- >>From: Arno Steffen [mailto:arno.steffen@xxxxxxxxxxxxxx] >>Sent: Thursday, July 28, 2011 9:13 PM >>To: Sricharan R >>Subject: Re: [Q] No message from Kernel (Howto start debug?) >> >>2011/7/28 Arno Steffen <arno.steffen@xxxxxxxxxxxxxx>: >>> 2011/7/28 Sricharan R <r.sricharan@xxxxxx>: >>>> If you are stuck with Starting kernel ... and do not see >>>> "Uncompressing Linux... done, booting the kernel" means could have >>>> crashed before your kernel in case of uImage. >>>> Check the arch_id that you are passing from the bootloader. >>>> >>>> Also enable early printk. >>>> >>>> >From what I understand kernel starts with start_kernel()). >>>>>What is best way to find out which part is failing? At which point I >>>>>do a printk to see what's going on, or at least set a GPIO Pin of the >>>>>processor? >>>>>How to debug without any external tools like JTAG. >>>>>-- >>>>>To unsubscribe from this list: send the line "unsubscribe linux-omap" > in >>>>>the body of a message to majordomo@xxxxxxxxxxxxxxx >>>>>More majordomo info at http://vger.kernel.org/majordomo-info.html >>>> >>>> Thanks, >>>> Sricharan >>>> >>> >>> You are absolutly right! The strange thing is, uboot can boot my old >>> kernel out of NAND flash. >>> And with the old kernel I can also boot via ethernet. Yepp, probably >>> the arch-id. I will check this. >>> Thanks >>> Arno >>> >> >>To optimistic. :( >>It seems that I have set the MACHINE_START in a proper way. >>What can prevent this message in uboot? Why it can uncompressing the >>old uImages, but not the new one? > > Is the uncompressing done by u-boot in your case? > > I have seen that the uncompress algorithm is built on > Top the Image. U-boot simply jumps to that location and > Rest is taken care by the uncompresser. It also sets up the > Serial port according to the arch > and prints " Uncompressing Linux... done, booting the kernel". > > The serial port number is used for early prints by kernel. > > Also check if your load address passed from u-boot is correct? > >>Seems I have to dig into uboot. >>Thanks >>-Arno > Mh, so it's not a uboot issue. Checking the outputs (see below) are identical, except Linux version and the new image is a bit smaller. Where does the uncompressor knows about which serial port to use? Bytes transferred = 1587592 (183988 hex) ## Booting kernel from Legacy Image at 80000000 ... Image Name: Linux-2.6.37 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1587528 Bytes = 1.5 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Thanks -Arno -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
