- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This obviously is an error in the internal chip-property-definition for the CY8C29466 and should be fixed asap! I found at least one example for a device where the Watchdog Timer could be enabled. Since the 29466 HAS got a WDT it was clearly only forgotten. I'm going to file a tech case.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This obviously is an error in the internal chip-property-definition for the CY8C29466 and should be fixed asap! I found at least one example for a device where the Watchdog Timer could be enabled. Since the 29466 HAS got a WDT it was clearly only forgotten. I'm going to file a tech case.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I indeed did file a tech case and got a response immediately (on a sunday!!) that Cypress is going to work on that to solve it asap.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
This is a bug really. Thanks for reporting this to us. It will be fixed in the next release of PSoC Designer. Any more feedback/suggestions are welcome.
As a workaround, following macro can be executing in application code if WatchDog is needed:
M8C_EnableWatchDog ;
More information of how this can be done and Clocks and Global Resources configuration of PSoC1 devices can be found in AN32200. http://www.cypress.com/?rID=2773
Thanks,
Roy