Comments on: PSoC4 Watch Dog Timer https://iotexpert.com/psoc4-watch-dog-timer/ Engineering for the Internet of Things Sun, 18 Nov 2018 11:50:04 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Alan Hawse https://iotexpert.com/psoc4-watch-dog-timer/#comment-9012 Sun, 18 Nov 2018 11:50:04 +0000 https://iotexpert.com/?p=3225#comment-9012 In reply to John Griswold.

You are welcome… not to be argumentative, actually I think that Cypress overall does an excellent job with our documentation. Obviously we have holes in the experience, but we do put a significant amount of effort into it.

]]> By: John Griswold https://iotexpert.com/psoc4-watch-dog-timer/#comment-8979 Fri, 16 Nov 2018 18:28:23 +0000 https://iotexpert.com/?p=3225#comment-8979 I am glad I stumbled upon this. The Cypress docs are rather underwhelming in their lack of detail. Thanks, Alan.

]]> By: Alan Hawse https://iotexpert.com/psoc4-watch-dog-timer/#comment-4065 Tue, 21 Nov 2017 14:26:45 +0000 https://iotexpert.com/?p=3225#comment-4065 In reply to Alan Hawse.

Here is an article about it. https://iotexpert.com/2017/11/21/psoc-4200m-wdt-long-deep-sleep/

]]> By: Alan Hawse https://iotexpert.com/psoc4-watch-dog-timer/#comment-4033 Fri, 17 Nov 2017 19:15:20 +0000 https://iotexpert.com/?p=3225#comment-4033 In reply to Jagir.

Sure. You can cascade the WDTs together using the CySysWdtSetCascade(CY_SYS_WDT_CASCADE_01); You can read about this win the LFClock reference guide. Ill also post an example next week on Tuesday.

]]> By: Jagir https://iotexpert.com/psoc4-watch-dog-timer/#comment-4017 Thu, 16 Nov 2017 03:32:24 +0000 https://iotexpert.com/?p=3225#comment-4017 Can we generate more than 2 sec of deep sleep interval by watchdog timers?

]]> By: Alan Hawse https://iotexpert.com/psoc4-watch-dog-timer/#comment-2243 Tue, 25 Apr 2017 12:00:21 +0000 https://iotexpert.com/?p=3225#comment-2243 In reply to Holger.

I think that your summary is spot on. The callback scheme is for sure slower, a few function calls and returns… but it offers connivence. The reality is that the same tasks need to be done and it is a choice to let Creator do it for you… or you have to do it yourself. I suppose that unless I have something really timing critical I probably use the callback scheme.

]]> By: Holger https://iotexpert.com/psoc4-watch-dog-timer/#comment-2224 Mon, 24 Apr 2017 09:00:06 +0000 https://iotexpert.com/?p=3225#comment-2224 Hi Alan,
I like your blog and the information given on the WDT/Timer. Thanks!
Please can you comment on the (dis)advantages of Callback vs. Custom ISR. Basically in both examples you have used your customized function to toggle the LED.

In my opinion:

Callback:
+ Start/activation of ISR is done automatically
+ No need to take care of clearing the IRQ flag
– The IRQ priority cannot be set individually (BTW, which priority is used for this method?)
– The used IRQ is not shown within the schematic
– Longer latency time

Custom ISR
+ IRQ is shown in the schematic
+ The IRQ priority can be set within the Interrupt tab of the *.cydwr
+ Shorter latency time
– Interrupt handler needs to be started manually
– interrupt flag must be cleared manually

Well, beside of the priority level and maybe the latency time impact I do not really see that big difference between both methods.
Please, if there is more than listed above, highlight pros and cons for each.

Again thanks for your blog. it’s great!

Holger

]]>