- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can't edit first post on thread.
This board shows the following when trying to debug or program, will not program or debug -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you have an older DVK? One with the PSoC5 Engineering Sample (ES1 or ES2) on it? These are not supported by the newest Creator, you would need to use Creator 2.2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Erased flash, converted back to internal clock, same result,
still part ID not recognized. Rebooted......
DVK not older, no ES designation on board chip.
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems to have had problems with insufficient capacity for capacitors Vcca (1.0mkF) and Vdda (0.1mkF)
...No more ideas ((
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Its both the DVK - 050 and DVK -001, both reporting same issue.
Chip is CY8C5568-AXI-060 (not in device catalog in Creator 3.0 SP2 for -001 board.
Chip is CY8C5568AXI-060 (not in device catalog in Creator 3.0 SP2 for -001 board using Miniprog3
Chip is CY8C5868-LP-035 ( in device catalog in Creator 3.0 SP2 for -050 board. using USB programming/debug interface
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bad USB cable, DUH !
Thanks for the help, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
First rule of problem-solving: start with the easy-to-resolve problems.
(And had I looked at who is reporting that problem I would not have guessed on the too-old-PSoC problem...)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Dana
Thank you for sharing your experiences with us. ;-))
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I have had a similar problem a year ago. Erasing the whole 050B Kit flash CPU memory by the external PSoC programmer solved the situation.
Regards,
Viktor