Did you already try to update the kitprog using PSoC Programmer (latest version) by following the Kitprog guide.
Yes I have already updated the KitProg firmware by using PSoC Programmer.
and also already checked the connection of from KitProg to my Target Board.
Have you tried programming the device from PSoC Programmer? What's the result?
No I haven't tried by using PSoC Programmer. Actually I don't
have it. It is very costly. So i am using KitProg which is Snapped Away
Programmer from CY8CKIT-059 PSoC® 5LP Prototyping Kit. It
is clearly written in CY8CKIT-059 PSoC® 5LP Prototyping Kit page
that "When snapped away, this tiny USB board can be used as a KitProg
programmer and debugger with any PSoC 3, PSoC 4 or PSoC 5LP device."
I meant, have you tried programming the device through your snapped KitProg board from PSoC Programmer software and see any error (not referring to programming through MiniProg3)?
From the attached screenshot, it looks like the KitProg is detecting the attached device as PSoC 5LP. Now in the PSoC Programmer, disable the AutoDetection option and select the PSoC 4 device from the drop-down (as shown in the below image) and try programming. Make sure that your board is powered. See if that helps.
You are saying that KitProg is Auto Detecting attached device as PSoC 5LP.
But it is not true. If we keep auto detection feature ON, the Programmer will
auto detect the part of the attached device. I have already tried your Auto
Detection feature OFF suggestion before. But still tried this again but failed.
I have tried by keeping Auto Detection feature OFF. My Target board gets
its Power Supply from Kit Prog. My Target board is very small. It doesn't
require much current.
ScreenShot1.jpg 196.3 K
If the communication between KitProg and the target device is successful, you are unlikely to see such errors.
If you are using long jumper wires (say 5-inch) to connect KitProg's SWD lines to the target board, shorten them try.
Actually I am not using any Kind of Jumper wires. I am using Header (Berg Strip) in
both PCBs. I mean Female Header in KitProg and Male Header in my target board.
1 of 1 people found this helpful
I ran into the same problem, some time ago.
The point is, that the CY8C4014SXI - 421 does not have a dedicated XRES pin.
It's written in the documentation, that pin 1.6 has a temporary XRES function while booting, but in fact it does not work yet. An errata about this issue exists.
Therefore, the SO8, SO16 and QFN16 can be programmed / reset by power-cycle only.
Unfortunately, the KitProg does not have the ability to make a power-cycle.
So, until Cypress has made a repair for the temporary XRES function on pin 1.6, you need the MiniProg3.
There's a work-around to use the XRES output on KitProg, to put a PNP-Transistor in-line with VCC of PSoC 4014, and dis-connect it in that way from VCC and make so the power-on RESET. Needs a little bit of soldering.
Hope this information helps.
Thank. This may be perfect solution. I was also thinking
that KitProg won't be able to program CY8C4014SXI. Because
when I was using PSoC Programmer software while KitProg
connected to PC, Power Cycle Option was not available to
select with this KitProg Programmer. I will try this suggestion.
But can I have circuit diagram? To perform this solution given
I tried the circuit suggested by you. But still having some issue.
Please check the circuit screenshot. and check PSoC Programmer
screenshot. When I attached that Transistor based circuit with KitProg,
KitProg gets in Bootloader mode automatically. Please check my schematic.
See which Transistor I have used.