- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I keep on getting this error (see below). I am using a custom board layout with a CY8C3244LTI-130ES2 chip. Does anyone know why this is happening or how to fix it? I have a MiniProg3 Rev5 programmer/debugger and the board is connected to the appropriate 10 pin connector to match. help please?
dbg.M0023: There was an error while programming the device: (PSoC Creator received error (100 - FAILED! Timeout of SPC polling. Lost communication with chip.))
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi maudi,
Is it correct to say that this new board has never been successfully programmed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi maudi,
No easy way out then.
You would have to start with the basics and verify your circuit.
You may want to verify your programmer on a known working board.
If you are using SWD remember the programming clock must 1/3 or less of the PSoC freq.
Good luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please try this workaround:
- Connect Miniprog3 to PC
- Connect Miniprog3 10 pin connector to target
- Open Programmer
- Execute Program Function
- SPC polling Error
- Execute any function other than Program (checksum, read, verify, or erase.)
- Execute Program
- Programming Successful
Let me know if this can work out for you.
Thanks,
--Meng
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I've isolated the problem and created a application to fix this issue.
Problem:
- the System Performance Controller (SPC) times out when the WO latches aren't set to zero.
Solution:
- program the WO latches with all zeroes. PSoCprogrammer doesn't do this once the device is programmed (avoiding overprogramming the latches) so I created a smal .NET utility to fix this.
It can be downloaded here:
http://www.nooteboom.biz/downloads/FixSPCtimeout.zip
Success!
Rolf
- 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
I am using a custom board layout with a CY8C3244LTI-130ES2 chip too. I have the same problem. I install the .NET utility FixSPCtimeout. But it did not help me.
Run the program.
Choose options: 3.3v,Reset,10pin- FIX.
appears:
NVL DATA @ 0xF8 read from Chip:00 00 00 00
NVL DATA olready okay..
Then run the programmer, programming chip. But still keep on getting this error .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have the same problem. I tried this .net app but the error still exists. Was anybody able to resolve this issue?.
Thx,
-/\/\addy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you have more info?
What's the version of your PSoC Programmer and Miniprog?
Was the part already programmed before?
How's the hardware setup, is it a custom made PCB?
Regards,
Rolf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I too have a similar problem.
I moved from PSOC3 ES2 to ES3 in the last few days.
I have a progam which, when it runs, seems to corrupt something critical within the PSoC3.
(It is a port of a Keil uVision4 C project meant for standard 8051s).
The parts program fine the first time but after this they are un-reprogrammable.
When I try to use PSoC Creator to reprogram, I get the following messages:
dbg.M0033: The selected debug target 'CY8C3866LTI-068 UNASSIGNED' is not compatible with the project's selected device 'CY8C3866LTI-068 ES3'.
or
dbg.M0033: The selected debug target 'CY8C3866LTI-068 ES1' is not compatible with the project's selected device 'CY8C3866LTI-068 ES3'.
Using standalone PSoC Programmer:
Auto Detection off:
Program Finished at 13:05:16 |
FAILED! Timeout of SPC polling. Lost communication with chip.
Erase Succeeded
WARNING!---> Debug mode enabled, this should be turned off from PSoC Creator before production.
Device set to CY8C3866LTI-068 at 13:05:02 | 65536 FLASH bytes
Auto Detection on:
Program Finished at 13:11:15 |
| Programming Terminated
WARNING!---> | Debug mode enabled, this should be turned off from PSoC Creator before production.
ERROR!---> | The hex file was built for silicon revision ES3, but the acquired device is revision ES1.
| Use PSoC Creator to generate a hex file for the proper device.
Device set to CY8C3866LTI-068 at 13:11:14 | 65536 FLASH bytes
This has happened on 3 new devices.
Ant ideas on what is being corruoted or how I could "reset" PSoC contents ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pls download the newest Psoc programmer 3.12.4, It fixed this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
today,I have the same problem,the problem described as follows :
Program Finished at 16:21:25 |
| FAILED! Timeout of SPC polling. Lost communication with chip.
| Programming of Flash Starting...
| Erase Succeeded
WARNING!---> | Debug mode enabled, this should be turned off from PSoC Creator before production.
Device set to CY8C3866AXI-040 at 16:21:20 | 65536 FLASH bytes
Device Family set to CY8C38xx at 16:21:20 |
| Automatically Detected Device: CY8C3866AXI-040
the psoc programmer version is 3.12.5.868
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
How many of your samples are giving this message? Is it ES2 or ES3? Are you using Cypress supplied kits or your own Development kit?
I would like you to file a technical support case just so that we can see if there is a need to do failure analysis or something of that sort on this chip.
Thanks,
Vivek