Richard, Can you be more specific on how the MAX6369 WDO and WDI connects to MCF5271's signal? Is it GPIO? ResetIn? Others?
Regards, TsiChung On Mon, Mar 2, 2009 at 3:05 PM, Richard Retanubun < richardretanu...@ruggedcom.com> wrote: > Hi Guys, > > I am using u-boot 2009.03-rc1 and a board based on Coldfire MC5271EVB eval > platform. > Our external watchdog is a MAX6369. > > I have #define CONFIG_HW_WATCHDOG and #undef CONFIG_WATCHDOG in our board's > config file and > have created the hw_watchdog_reset function to toggle the WDI line to pet > the watchdog. > > However, my board keeps resetting at the watchdog timeout. Upon probing, I > found out that > the watchdog toggle line in not being toggled periodically by u-boot. Which > means a regular call > to WATCHDOG_RESET() is not happening. If I execute commands, the WDI will > get toggled and the watchdog > will not timeout, which means that the WATCHDOG_RESET() mapping to > hw_watchdog_reset function is working, it is > just not being called periodically. > > I am looking at the programmable interrupt timer that the get_timer() > function uses, and so far everything checks out. > > I'm also stuck at using u-boot's sleep command, e.g. "sleep 1" will never > return. Which I suspect may be the same root cause. > (this can also be observed on the M5271EVB board). > > What am I missing here? > > Thank you for all your time. > > Regards, > > - Richard Retanubun. > > > _______________________________________________ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot >
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
