Menu
▾
▴
Re: [Gumstix-users] Watchdog timer not working in gumstix overo
|
From: Akram H. <ak...@aq...> - 2011-12-05 23:47:04
|
Update 2: It's probably not a fair test (my kernel is customised somewhat), but 2.6.36-r100 does not restart properly after the watchdog bites even with the newer u-boot & x-load that definitely work with Steve's kernel 3.0-pm Might be we have to move our platform to the newer kernel, though I'll try with a non-customised 2.6.36 and see what happens. -----Original Message----- From: Steve Sakoman [mailto:sa...@gm...] Sent: Monday, 5 December 2011 3:21 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Watchdog timer not working in gumstix overo On Sun, Dec 4, 2011 at 6:19 PM, Akram Hameed <ak...@aq...> wrote: > Tried the factory MLO from here (1.5.0): > http://cumulus.gumstix.org/images/angstrom/factory/2011-08-30-1058/ > > Makes no difference, still 'hangs' after WD should have tickled reboot. Could you try a console image using the script from my site: http://www.sakoman.com/category/8-gnome-daily-builds-r13.html Follow the instructions on that page, but specify console instead of gnome. Also be sure to write the same x-load to nand -- after booting into u-boot from the SD card prepared above do: nand erase 0 80000 mmc rescan 0 fatload mmc 0 82000000 mlo nandecc hw nand write 82000000 0 20000 nand write 82000000 20000 20000 nand write 82000000 40000 20000 nand write 82000000 60000 20000 With the above setup I get successful watchdog reboots on 35XX COMs. If it doesn't work for you could you attach the u-boot banner so that I can see what version of processor you have? Steve > -----Original Message----- > From: Akram Hameed [mailto:ak...@aq...] > Sent: Monday, 5 December 2011 12:12 PM > To: General mailing list for gumstix users. > Subject: RE: [Gumstix-users] Watchdog timer not working in gumstix overo > > My issue is happening on an OMAP-based Overo Water that's sitting on a > TOBI board, for reference. > > -----Original Message----- > From: Akram Hameed [mailto:ak...@aq...] > Sent: Monday, 5 December 2011 11:50 AM > To: General mailing list for gumstix users. > Subject: RE: [Gumstix-users] Watchdog timer not working in gumstix overo > > I'm experiencing the same issue as the OP, though interestingly only after > updating my x-loader in NAND (it worked fine with x-loader 1.4.2). > > Kernel 2.6.36-r100 with some minor customisations (all through OE). I had > x-load 1.4.2 in NAND previously and it was not detecting DRAM properly > (128 instead of 256) after the omap_wdt triggered. I therefore replaced > MLO with one I built with OE earlier this year (1.4.4s). Copied to the > flash following these instructions: > http://gumstix.org/how-to/70-writing-images-to-flash.html > > Now if I nuke the watchdog process I get the typical omap_wdt message > about not stopping but the system appears to hang at this point. > > I can confirm that the 1.4.4 x-loader is working from NAND; removing the > microSD prompts the system to boot from NAND and it loads the 'fail safe' > u-boot and kernel from NAND no trouble. > > So, question is what is going on here? Advice welcome. > > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Monday, 5 December 2011 4:28 AM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] Watchdog timer not working in gumstix overo > > On Fri, Dec 2, 2011 at 9:30 AM, tybandara <tyb...@gm...> wrote: >> Hello all, I have a gumstix air com and a pinto board. I've compiled the >> 2.6.14 linux kernel to this. And I have selected only omap_wdt driver in > the >> watchdog timer driver list when compiling the kernel. > > I suspect there is a typo in the version number since 2.6.14 pre-dates > Overo support. Perhaps you meant 2.6.34? > >> I'm using a very basic >> test program to open the /dev/watchdog node and it says if I don't write >> anything to the node system will restart in 60 seconds by default. But > what >> I noticed was that my system simply halts, but doesn't restart after 60 >> seconds. I don't think that there are any good search results in the >> internet too. I'm sure most of you have faced this issue? How have you >> solved this? Or, is this a device dependent issue? Thanx a lot > > Does your COM have NAND? If so, is there a copy of x-loader written to > NAND? > > IIRC, the OMAP attempts to boot from NAND after a watchdog reset. If > you don't have a copy of x-loader in NAND then the system will appear > to freeze since it can't find any boot code. > > Frankly, I'm not sure if there is a workaround for systems without > NAND. Perhaps someone on the list knows this. Otherwise I'll look > through the OMAP3 TRM later this week to see if I can discover > anything. > > Using my GNOME or console image > (http://www.sakoman.com/category/8-gnome-daily-builds-r13.html) with a > copy of x-loader in NAND things seem to work as expected: > > root@omap3-multi:~# echo 1 > /dev/watchdog > omap_wdt: Unexpected close, not stopping! > root@omap3-multi:~# > > <one minute later> > > Texas Instruments X-Loader 1.5.1 (Nov 28 2011 - 13:07:54) > OMAP3503-GP ES3.1 > Board revision: 0 > Reading boot sector > Loading u-boot.bin from mmc > > > U-Boot 2011.09 (Nov 28 2011 - 13:09:07) > > OMAP3503-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz > Gumstix Overo board + LPDDR/NAND > I2C: ready > DRAM: 256 MiB > NAND: 256 MiB > MMC: OMAP SD/MMC: 0 > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serial > Board revision: 0 > Tranceiver detected on mmc2 > No EEPROM on expansion board > Die ID #52e800040000000004032d460d00e01d > Net: No ethernet found. > Hit any key to stop autoboot: 0 > reading boot.scr > > ** Unable to read "boot.scr" from mmc 0:1 ** > reading uImage > > 3143384 bytes read > Booting from mmc ... > ## Booting kernel from Legacy Image at 82000000 ... > Image Name: Angstrom/3.0/omap3-multi > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 3143320 Bytes = 3 MiB > Load Address: 80008000 > Entry Point: 80008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > Linux version 3.0.0 (sakoman@quadra) (gcc version 4.5.3 20110311 > (prerelease) (GCC) ) #1 Thu Dec 1 13:23:45 PST 2011 > > -------------------------------------------------------------------------- > ---- > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -------------------------------------------------------------------------- ---- > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users -------------------------------------------------------------------------- ---- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |