- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm using Kitprog2 which took from CY8CKIT-149 to program the CY8C4127AZI-S453 which is on the board we designed.
The PSoC programmer can connect to Kitprog2:
Successfully Connected to KitProg2 (CMSIS-DAP/244532) at 11:01:00 | CMSIS-DAP Version 1.10
But when I try to program, it notice me the following:
Programming Terminated
Detected SiliconID: 25 94 12 B5 is not in database
Error paring device information from database
PSoC Device (25 94 12 B5) is not in the DataBase
Does it mean Kitprog2 can't support CY8C4127AZI-S453? Any change needed for this programming? Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I think that I saw similar problems with PSoC 41xx before.
At that time it was required to download and install the newest PSoC Programmer.
https://www.cypress.com/documentation/software-and-drivers/psoc-programmer-archive
I don't know if this fix the problem but I hope trying it won't cause harm.
moto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Kitprog2 could support the chip : CY8C4127AZI-S453.
No change need to do with the KitProg2 when program CY8C4127AZI-S453.
Maybe your chip has been broken.
1:Could you help to measure the VCCD output when power the chip?
2:Could you show us the power part schematic about your test board?
3: Whether you try to program different boards receive the same result?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As Lingling mentioned, Programmer supports CY8C4127AZI-S453.
You may have selected CY8C4127AXI-S453 by mistake.
Check that you have selected:
Device Family: CY8C41xx-S
Device: CY8C4127AZI-S453
And provide the info requested by Lingling.
Most important, keep the SWD wires short length between Kitprog2 and the target. 5cm length works very well. Over 10cm is unreliable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks BiBi and Lingling's reply.
I'm facing the same programming issue in PSoc Creator. As you can see in below picture, selected device part no. is correct, and the device part no. shown in Select debug target (port acquire) window is also correct.
I have tried to shorten the wire connected between kitprog2 and board, but it doesn't help.
The VCCD output is 1.77V as measured.
Same issue observed on all two boards I have.
The power part schematic is shown as below:
We use the VTARG of Kitprog2 (4.8V as measured) as the power input for my board, is it okay? As checked in datasheet, the power supply can be 1.8~5.5V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In select debug target window, the Cypress ID is shown and target is acquired.
But when programming the micro, it says this ID is not in the DataBase.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had exact same issue when using Creator to program CY8C4013SXI-410. It did not have the part in its database, even though Creator was used to develop software for it. I solved this by using the other Cypress software called Programmer 3.28.
If you've tried Programmer 3.28, I would un-install it. Then, download a fresh copy from Cypress and re-install.
Then, select:
Device Family: CY8C41xx-S
Device: CY8C4127AZI-S453
and try again. Let us know your results.
Your schematic power/ground connections look okay (a bit confusing with non-matching PSoC symbol).
I'm surprised Kitprog2 could acquire the PSoC since you don't have PSoC XRES connected to Kitprog2 debug connector. It should be connected. Creator/Debug/Program and Programmer 3.28, can both show bizarre failure windows when XRES is not connected.
Let us know your progress.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I think that I saw similar problems with PSoC 41xx before.
At that time it was required to download and install the newest PSoC Programmer.
https://www.cypress.com/documentation/software-and-drivers/psoc-programmer-archive
I don't know if this fix the problem but I hope trying it won't cause harm.
moto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Motoo and BiBi, I download and install the newest PSoC Programmer, now it works.