• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 1534 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.

stop watchdog in Processor SDK u-boot

Kzk
Genius 5785 points

Hello,

I'm evaluating Processor SDKv1 of AM335x. I stop the autoboot of u-boot and connect target for CCSv6.1 with XDS200/560v2STM. Then after 50~60 seconds, I see u-boot sends a message for reboot in the console window in spite of halting by CCS. I think it's originated by watchdog. I'd like to quit the reboot for kernel stop mode debug. How do I realize it? I changed the following line to a comment out, but the reboot ran yet. Please give me some advice.

u-boot-2014.07-g7e537bf/include/configs$ gedit ti_am335x_common.h
/*#define CONFIG_HW_WATCHDOG*/

Regards,
Kazu

  • 0
    TI__Guru** 116100 points
    Hi,

    Then after 50~60 seconds, I see u-boot sends a message for reboot in the console window in spite of halting by CCS.

    Could you attach the screen shot of this.
    It is automatically issuing reboot after connecting CCS to target (~60) ?
    Or are you doing "disconnect" the CCS or issuing any reset command from CCS ?
    Did you see this behavior in earlier SDK versions ?
    Are you using custom board or TI EVM ?
  • 0 in reply to Titusrathinaraj Stalin
    Genius 5785 points

    Hello Titus,

    I'm using ti-processor-sdk-linux-am335x-evm-01.00.00.00 and EVM3358 without GEL. I didn't see this behavior when I used Linux SDKv6 before. I attach screen shot below for this procedure.

    I guess I found a way out of the problem. I changed header file in a previous post and switched MLO. I've not seen the reboot. Also If I remove the comment out ("#define CONFIG_HW_WATCHDOG" is alive.) and change the following source code, the reboot interval is about 25 seconds. What do you think?

    u-boot-2014.07-g7e537bf/drivers/watchdog/omap_wdt.c
    /* Hardware timeout in seconds */
    //#define WDT_HW_TIMEOUT 60
    #define WDT_HW_TIMEOUT 30

    Regards,
    Kazu

    1) stop autoboot

    2) connect target

    3) after 50~60 seconds, reboot automatically

    4) resume automatically