• Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 376 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Watchdog on OMAP3530 2.6.31 Linux kernel

lorenzo centurellli
Prodigy 30 points
Other Parts Discussed in Thread: OMAP3530

Hi everybody,

I'm working with an omap3530,  2.6.31 Linux kernel, and I'm facing this problem: watchdog timer doesn't restart my board when it breaks. I enabled watchdog in the configuration of the SDK, but it doesn't work. 

What is the problem?

 

Thank you

 

Regards

Lorenzo

  • Prodigy 100 points

    Hello Lorenzo,

     

    Did you make the watchdog device using the mknod command? (mknod /dev/watchdog c 10 130)

    Did you run a userspace program that opens the device and writes to it? (Busybox supplies such a process, named 'watchdog'). I think the best thing is to add the watchdog process to the init.d scripts.

    I'm working with the omap 2.6.34 kernel, and it seems to be working fine.

     

    Dan.

  • in reply to Dan Jordan
    Expert 1070 points

    Dan,

     

    I am wanting to do the same thing.  I do not have access to Busybox.  Are there examples on how to write a watchdog equivalent (process)?

     

    Loren