CCS/LAUNCHXL-CC3235SF: local_ota example watchdog timer settings?

Hi Robert,

Look inside the local_ota.syscfg file, and you will find the Watchdog settings and can configure the period.

BR,

Vince 

Hi Vince,

I set the Watchdog Period = 30000 (30 Seconds) in local_ota.syscfg in both the installed (running) and ota (downloaded) programs.

After ota download,  the time between calling PRCMHibernateCycleTrigger() to watchdog reset (MAP_PRCMSysResetCauseGet() == PRCM_WDT_RESET) is consistently ~16 sec. (ota commit fails about 95% of the time)

I also set the period to 5000 (5 sec.) and it was still ~16 sec, no change.

The syscfg watchdog setting does not change the ota watchdog timeout.

Any suggestions on how to increase the timeout? I am running out of troubleshooting ideas for the extremely unreliable local_ota example.

Hi Robert,

Can you try periodically calling PowerCC32XX_reset(PowerCC32XX_PERIPH_WDT); to see if we are able to control the Watchdog? I think calling this once halfway through should be good enough.

BR,

Vince 

Hi Vince,

Thanks for the info.

I was able to determine that the WDT period is set in the mcubootinfo.bin file. The default count value was set to 16 sec. I was able to modified it to 32 sec. (count  = last 4 bytes of the .bin file) which solved the premature timeout problem, but other issues still remain for reliable ota downloads in AP mode.

I could not find any information on how the mcubootinfo.bin file is created or used by the ota so I don't know if modifying it by hand will cause other issues.