Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

PSoC™ Creator & Designer Forum Discussions

ETRO_SSN583
Level 9
Level 9
100 sign-ins 5 likes given 1000 replies posted
0 Likes
10 Replies
ETRO_SSN583
Level 9
Level 9
100 sign-ins 5 likes given 1000 replies posted

Can't edit first post on thread.

   

 

   

This board shows the following when trying to debug or program, will not program or debug -

   

 

   

0 Likes
EvPa_264126
Level 7
Level 7
500 replies posted 250 replies posted 100 likes received


See this post:   Select Debug Target ...
it helped me.

0 Likes
HeLi_263931
Level 8
Level 8
100 likes received 50 likes received 25 likes received

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.

0 Likes
ETRO_SSN583
Level 9
Level 9
100 sign-ins 5 likes given 1000 replies posted

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.

0 Likes
EvPa_264126
Level 7
Level 7
500 replies posted 250 replies posted 100 likes received


Seems to have had problems with insufficient capacity for capacitors Vcca (1.0mkF) and Vdda (0.1mkF)
...No more ideas ((
 

0 Likes
ETRO_SSN583
Level 9
Level 9
100 sign-ins 5 likes given 1000 replies posted

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.

0 Likes
ETRO_SSN583
Level 9
Level 9
100 sign-ins 5 likes given 1000 replies posted

Bad USB cable, DUH !

   

 

   

Thanks for the help, Dana.

0 Likes
HeLi_263931
Level 8
Level 8
100 likes received 50 likes received 25 likes received

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...)

0 Likes
Bob_Marlowe
Level 10
Level 10
First like given 50 questions asked 10 questions asked

@Dana

   

Thank you for sharing your experiences with us. ;-)) 

   

 

   

Bob

0 Likes
ViDv_264506
Level 5
Level 5
5 solutions authored First solution authored 50 replies posted

 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

0 Likes