Error while programming

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

cross mob
Anonymous
Not applicable

Hello,

   

I use a custom board with a PSOC5. Until now, the board run perfectly. From one day to the next the board has no function - supply is OK, we had no overvoltage, etc ...
I can not successfully program this board. The current consumption of the device is 26 mA at 12V (with a voltage regulator down to 3.3V)

   

PSCO Creator OUTPUT :

   

Programming started for device: 'PSoC 5LP CY8C5667LTI-LP041'.
Device ID Check
WARNING! JTAG/SWD communication for PSoC3/5 is not stable with the clock above 3.2 MHz! Please select lower clock option in case of failures.
Erasing...
Programming of Flash Starting...
Error: dbg.M0023: There was an error while programming the device: PSoC Programmer reported error (103 - Failed to program the chip!)

   


Does anyone have an idea or solution approaches?

   

Thank you
 

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

Did you select a lower clock as suggested?

   

There is a chip protection option which will, when used once, deny any further programming.

   

Are you using a miniprog3? Power set to "external", acquire set to "Reset"

   

 

   

Bob

0 Likes
Anonymous
Not applicable

Thanks for the reply - I will test it

0 Likes
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable

May we offer you our best wishes for the New Year. After the conclusion of another project I was finally able to test the advice. I have reduced the clock speed to 0.2 MHz (Tools\Options\Program/Debug\Port Configuration), but this has not succeeded. In the output window (see attachment) - is still the warning with the speed. Have I reduced the wrong speed? Now I have with the same modul a second error (see attachment). This indicates to me that the checksum is not correct - It does not matter with what speed I set. Have i destroyed the chip? I use KitProg Programmer.

   

Chris

0 Likes
emen_2218296
Level 4
Level 4
25 replies posted 10 replies posted 5 replies posted

1. Does your custom board has supply caps (the 0.1 uF and 1 uFs) placed close to supply pins ?

   

2. Can you try with one more MiniProg3 ?

   

3. If MiniProg3 is being connected to board using long wires, avoid using this set up. Have a 5-pin connector placed on board.

0 Likes
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable

Thank you for your answer.

   

1. Custom board has supply caps, but no 1 uF caps - see attachment. We don't believe, that has anything to do with the missing capacitor

   

2. Yes, i tried it with another programmer, but it's the same

   

3. Cable length is approx. 0.5 m (has also been tested with a shorter cable 0,1m - same problem) and we use the 5 pin connector - see attachment

0 Likes
emen_2218296
Level 4
Level 4
25 replies posted 10 replies posted 5 replies posted

That is way too long a cable for SWD communication. Put your programmer directly onto your board. Use USB cable to connect your programmer to your PC. 

0 Likes
Anonymous
Not applicable

I would exclude that:

   
        
  1. it works with other electronics
  2.     
  3. it has already been programmed several times without an error
  4.     
  5. it has worked for one month and then suddenly the electronics have failed - no more function and the electronic has now this programming error
  6.    
   

What interesting about this error, is that the electronics has run perfectly before. See point 3.

0 Likes
Anonymous
Not applicable

We are using CY8C5267AXI-LP051 in our designs. We are facing issue in programming the device through SWD interface when we try to program through CLI(command line interface), whereas through GUI , we face no issue.

   

We are using CLI programmer version 3.23.1.2145.

   

I am attaching the log file with error for your kind reference.

   

Kindly suggest where could be the issue.

   

C:\Program Files (x86)\Cypress\Programmer>PPCLI "-- runfile D:\\ate_devlopment\

   

\trunk\\PCBA_Level\\GPTS\\MPPT\\LabView\\Source_Code\\Tools\\Cypress_Prog.txt"

   

GetPorts

   

<MiniProg3/1606BB000E89

   

0 OK

   

OpenPort MiniProg3/1606BB000E89 .

   

<

   

0 OK

   

SetAcquireMode Power

   

<

   

0 OK

   

SetProtocol 8

   

<

   

0 OK

   

SetPowerVoltage 5.0

   

<

   

0 OK

   

HEX_ReadFile "C:\\MPPT.hex"

   

<0x00020000

   

0 OK

   

SetHexFile "C:\\MPPT.hex"

   

<

   

0 OK

   

SetProtocol 8

   

<

   

0 OK

   

Program

   

E

   

Device is not in ISSP mode.

   

Program returned 80004005

   

80004005 OK

   

Verify

   

E

   

Device is not in ISSP mode.

   

Verify returned 80004005

   

80004005 OK

   

ReleaseChip

   

E

   

FW Version is up-to-date. No need of Upgrade. Hex: 2.05 MiniProg3: 2.05

   

ReleaseChip returned 80004005

   

80004005 OK

   

ClosePort

   

<

   

0 OK

   

quit

   

<OK

   

<OK

   

C:\Program Files (x86)\Cypress\Programmer>

   

3.23.1.2145

0 Likes
Anonymous
Not applicable

I have the same problem. Despite useing command "Set Protocol 8" with ppcli.exe it won't change to SWD and I get error as below.  Programmer updated. The same result on Windows 7 64 bit and Windows XP 32 bit. Did you found a solution?

   

version
<version 3.25.0
1 OK
GetPorts
<MiniProg3/1443DD00051D
KitProg/0F20083201324400
0 OK
OpenPort MiniProg3/1443DD00051D .
<
0 OK
GetProgrammerCapabilities
<0x0007-0x0007-0x0001-0x0002-0x002f-0x000f
0 OK
SetProtocol 8
<
0 OK
SetAcquireMode Reset
<
0 OK
PowerOn
<
0 OK
SetPowerVoltage 3.3
<
0 OK
SetProtocolConnector 1
<
0 OK
Acquire
E
Device is not in ISSP mode.
Acquire returned 80004005
80004005 OK
quit
<OK
<OK

0 Likes
emen_2218296
Level 4
Level 4
25 replies posted 10 replies posted 5 replies posted

Hi c.rotkroepfl_1662056,

   

I noticed something in your schematic which I had not noticed before. 

   

Why is VCCD and VCCA connected to any supply ? Only caps need to be added to these pins. 

   

   

 

   

Also, I strongly suggest to cut down wire length. Directly attach programmer to the board. Use USB cable to connect to PC. 

   

I know it was working for you before. However, connecting 3.3 V to VCCD and VCCA is wrong and also length needs to shortened. 

   

0 Likes
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable

Thank your embedded.engg for your helpful tip. I’ve totally missed the exact Power Supply Pin description.

   

The VCCD and VCCA pins were held at 3.3V which is not even near the allowed Range (1.71 V – 1.89 V) in addition this are Power output pins instead of inputs.

   

See http://www.cypress.com/file/45936/download, Page 26 - so i update the schematic (see attachment).

   

Thanks a lot for your help, I will redo the PCB and inform you if it works now.

0 Likes
SAJO_1338106
Level 4
Level 4
25 replies posted 10 replies posted 5 replies posted

Hi,

   

 

   

Did you find any success after the modification? Let us know.

0 Likes
Anonymous
Not applicable

Hello

   

It is currently in the test. The last circuit is after approximately 1-2 months failed. It seems this was the bug,

   

Thanks to the community

0 Likes
SAJO_1338106
Level 4
Level 4
25 replies posted 10 replies posted 5 replies posted

Let us know the results after testing it.

0 Likes
alli_264371
Level 4
Level 4
25 replies posted 10 replies posted 10 questions asked

I have the same problem, after add the 1uF VDD-GND capacitor close to chip programmer work well


I cannot confirm email and add messages due to a bug on your site, the email section is not active
0 Likes