Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
|
From: Sudhangathan B S <sudhangathan@gm...> - 2013-09-03 19:11:10
Attachments:
Message as HTML
|
Hey there..! I'm working on a project which needs power management on the kernel. For some reason the kernel does not boot. I'm using Yocto, Overo-Fire-Summit setup. It does not continue after: Starting kernel ... Uncompressing Linux... done, booting the kernel. I have checked the serial port configuration.. it all appears fine.! Can I know which u-boot version should be used with 2.6.39 linux-omap-pm..?? I'm currently bitbaking with u-boot-sakoman 2012.07...!! Can you also please suggest which kernel version is best to take up power management.. I mean to ask for the stable PM versions.? And also the corresponding u-boot version..? Any views in this regard..? Thanks, --------------------------------- Sudhangathan BS Ph:(+91) 9731-905-205 --------------------------------- |
|
From: Scott Ellis <scott@ju...> - 2013-09-05 12:50:56
|
Did you get this figured out? If not, you might check whether it's a ttyS2 vs ttyO2 issue. The change happened somewhere around the 2.6.39 kernels. Setting console to tty02,1152008n1 in the u-boot environment should work. That's a capital 'O' not a zero. -- View this message in context: http://gumstix.8.x6.nabble.com/Kernel-does-not-continue-after-done-booting-kernel-tp4967863p4967868.html Sent from the Gumstix mailing list archive at Nabble.com. |
|
From: Sudhangathan B S <sudhangathan@gm...> - 2013-09-05 14:24:28
Attachments:
Message as HTML
|
A huge thanks for replying Scott, I Always made that check..! I have made it to ttyO2 and also have saved to nand flash.. i.e i have done "saveenv"... This is the command that i use to do that.! :: "setenv console ttyO2,115200n8" I also tried tty02,1152008n1 as you have told, thought of it as a typo.. Still didn't work.. >From this link: http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux I thought it could be cause #2.. So I even tried setting CONFIG_DEBUG_LL in defconfig file.. But i could see no debug msg either.. But i'm not sure the CONFIG_DEBUG_LL really worked. Should i use menuconfig in yocto.? Below is the console output, if it is of any use to you. === Overo # printenv baudrate=115200 bootcmd=if mmc rescan ${mmcdev}; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi bootdelay=5 bootscript=echo Running bootscript from mmc ...; source ${loadaddr} console=ttyO2,115200n8 defaultdisplay=dvi dieid#=6a2800040000000004038e6e0b01401d dvimode=1024x768MR-16@... loadaddr=0x82000000 loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage mmcargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype} mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr} mmcdev=0 mmcroot=/dev/mmcblk0p2 rw mmcrootfstype=ext3 rootwait mpurate=500 nandargs=setenv bootargs console=${console} ${optargs} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype} nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr} nandroot=ubi0:rootfs ubi.mtd=4 nandrootfstype=ubifs vram=12M stdin=serial stdout=serial stderr=serial Environment size: 1242/131068 bytes Overo # boot reading boot.scr ** Unable to read "boot.scr" from mmc 0:1 ** reading uImage 1923460 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 82000000 ... Image Name: Linux-2.6.39 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1923396 Bytes = 1.8 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. === Don't you think there is any mismatch between u-boot and the kernel..? --------------------------------- Sudhangathan BS Ph:(+91) 9731-905-205 --------------------------------- On Thu, Sep 5, 2013 at 6:20 PM, Scott Ellis <scott@...> wrote: > Did you get this figured out? > > If not, you might check whether it's a ttyS2 vs ttyO2 issue. The change > happened > somewhere around the 2.6.39 kernels. > > Setting console to tty02,1152008n1 in the u-boot environment should work. > > That's a capital 'O' not a zero. > > > > -- > View this message in context: > http://gumstix.8.x6.nabble.com/Kernel-does-not-continue-after-done-booting-kernel-tp4967863p4967868.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
|
From: Scott Ellis <scott@ju...> - 2013-09-05 14:43:01
|
I've never tried that DEBUG_LL stuff. Can't help you. To be clear, you have also tried with ttyS2 in u-boot? -- View this message in context: http://gumstix.8.x6.nabble.com/Kernel-does-not-continue-after-done-booting-kernel-tp4967863p4967870.html Sent from the Gumstix mailing list archive at Nabble.com. |
|
From: Sudhangathan B S <sudhangathan@gm...> - 2013-09-06 00:08:27
Attachments:
Message as HTML
|
Yes I have tried ttyS2 too.. There is no difference.. And Scott, I did one more observation.. the blue LED is turned ON and stops flickering immediately after it prints the message "done booting the kernel".. Inference may be that the kernel is stuck somewhere.!..?? --------------------------------- Sudhangathan BS Ph:(+91) 9731-905-205 --------------------------------- On Thu, Sep 5, 2013 at 8:12 PM, Scott Ellis <scott@...> wrote: > I've never tried that DEBUG_LL stuff. Can't help you. > > To be clear, you have also tried with ttyS2 in u-boot? > > > > > -- > View this message in context: > http://gumstix.8.x6.nabble.com/Kernel-does-not-continue-after-done-booting-kernel-tp4967863p4967870.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! > Discover the easy way to master current and previous Microsoft technologies > and advance your career. Get an incredible 1,500+ hours of step-by-step > tutorial videos with LearnDevNow. Subscribe today and save! > http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
|
From: Scott Ellis <scott@ju...> - 2013-09-06 09:00:47
|
I agree it sounds like your kernel is hanging. I have no easy suggestions on how to go about debugging it. Good luck, Scott -- View this message in context: http://gumstix.8.x6.nabble.com/Kernel-does-not-continue-after-done-booting-kernel-tp4967863p4967878.html Sent from the Gumstix mailing list archive at Nabble.com. |