CC2674P10: Watchdog in services or in driverlib ?

Hi Geoffrey,

There shouldn't be any "true" differences. These are just copies of each other at some point in time.

If you need to use Watchdog, I recommend to use the one which is used in <SDK>/source/ti/drivers.
This should be the same driver which is used in the Watchdog example: https://dev.ti.com/tirex/explore/node?node=A__AFAUvTag5SM1MPL74GE0cQ__com.ti.SIMPLELINK_CC13XX_CC26XX_SDK__BSEc4rl__LATEST

Recommend to use CC1354P10 LP for development of CC2674 applications.
(Refer to migration guide: https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_7_41_00_17/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/migration-cc13xx_cc26xx.html)

Thanks,
Toby

Hi Toby, 

OK thanks.

Another thing : I assume the watchdog in sysconfig is driverlib/watchdog. It seems like the callback function passed as a parameter to the watchdog is never called when the watchdog expires. (the idea is to be able to do something before the watchdog reset the CPU). 

Do you manage on your side to do so ?  

Regards

Geoffrey

Hi Geoffrey,

For CC2674P10 (and generally all CC13x4/CC26x4), it is using <sdk>/source/ti/drivers/watchdog/WatchdogCC26X4.c/h.

The WatchdogCC26X4.h has this comment:

I am confirming with the team whether this is a limitation within the device itself or within the driver.

Thanks,
Toby

Hi Geoffrey,

There are actually 2 Watchdog modules on the CC2674:

1. One is the same which is used on CC26x2, which is able to generate an interrupt the first time.
2. The other is AON_WDT, which is new in CC26x4. This one cannot generate an interrupt, and is the default used if you add Watchdog with SysConfig.

If you want to use the CC26x2-like Watchdog, the code is still available in <sdk>/source/ti/drivers/watchdog/WatchdogCC26XX.c/h.
These may be copied to your local CCS project.

Thanks,
Toby