cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC™ 5, 3 & 1

ViDv_264506
Contributor II

Hi,

   

My first CY8CKIT-050B recognizes by programing not the correct CPU. In place of correct CPU type ... only Cortex-M3 and the .... message ... This device was recognized, but PSoC Creator does not support using it at this time ... Info ... This target device is already in use by another client.

   

My second CY8CKIT-050B works on the same PC and same conditions OK.

   

Any help?

   

Regards, 

   

Viktor

0 Likes
7 Replies
ViDv_264506
Contributor II

Hi,

   

problem reproduced but not solved. By programming PSoC 5LP needs for recognizing correct CPU Master Clock and Bus clock RUNNING. By using external digital OCXO clock signal you need to configure Cy_Pins Version 1.80, Digital Input, HW Connection, Show External Terminal and Input declared as "TRANSPARENT" in any case NOT "DOUBLE_SYNC".

   

Is there a solution to REVERT once programmed the input pin as DOUBLE_SYNC  to  TRANSPARENT.

   

In other words .... General PSoC 5LP chip erase method to factory default state by software or hardware methods ????

   

Regards,

   

Viktor

0 Likes
Anonymous
Not applicable
0 Likes
Anonymous
Not applicable

Open PSoC Programmer. Up top there's an option "Erase Flash." This will erase the PSoC, like you asked, and fix the faulty clock problem.

0 Likes
EvPa_264126
Valued Contributor II


I encountered this problem.
The reason seems to be this:
I programmed IMO for Digital Signal, on an empty contact.

   

Thank you so much, PrestonM!!!
 

0 Likes
ETRO_SSN583
Esteemed Contributor

Erased flash, converted back to internal clock, same result,

   

still part ID not recognized.

   

 

   

Regards, Dana.

0 Likes
Bob_Marlowe
Expert II

I once had a similar error which was related to leftovers from a de-install. I filed a case and after 3 days got help with a program that analyzed my registry and deleted wrong entries. All under the help of Cypress.

   

 

   

Bob

0 Likes
ETRO_SSN583
Esteemed Contributor

Bad USB cable.

   

 

   

Regards, Dana.

0 Likes