From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tabi Timur-B04825 Date: Thu, 3 Mar 2011 12:33:57 +0000 Subject: [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2 In-Reply-To: <4D6F4619.2020201@embedded-sol.com> References: <4D6EDC78.3010909@embedded-sol.com> <45903308677306428B6EE7E6FF5A52040EDA82@039-SN1MPN1-004.039d.mgd.msft.net> <4D6F1723.4040205@freescale.com> <57D3AB35EFB0E542A4326DBD78E17E9512853B@039-SN1MPN1-004.039d.mgd.msft.net> <4D6F4619.2020201@embedded-sol.com> Message-ID: <4D6F8AB5.2050208@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Felix Radensky wrote: > Correct. It works fine in linux. I've even tried to port linux code that > enables watchdog (booke_wdt.c/__booke_wdt_enable()) to u-boot, > but was not successful. Watchdog never triggered, although I did > not refresh it. > > I'd appreciate some advice on what may be different in u-boot > vs. linux. I don't know what to tell you. I would need to try to make it myself in order to see what's going on. Maybe you really didn't program TCR correctly. Or maybe it is working, but the default behavior of U-Boot is to handle everything silently. -- Timur Tabi Linux kernel developer