- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When a psoc chip on an external board is connected to the kitprog programmer hardware, does psoc creator / psoc programmer automatically detect the new chip connection? Will I have to restart the software with kitprog already connected to the chip on an external board? Psoc creator currently detects the kitprog, but it "fails to acquire device" every time I try to connect. It may be a faulty soldering issue but I just want to confirm that it isn't an issue from the software side, thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We got the KitProg to finally work, it was most likely a hardware issue. Thanks for your help everyone!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The kitprog is delivering power to the target, check the voltages. The target device will be controlled by the kitprog, except when the target was programmed to set the SWD pins to GPIO. Check the XRES connection (active low) from kitprog to target.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
please check the VDDA/VDDD/VCCD pin voltage of target device and check the electrical connection state of 5-wires.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all, happy Thanksgiving. We soldered a new PCB and checked the voltages again which seem fine. However, the following errors came up again. Do you think it is a hardware issue due to the PCB design or soldering or is it an issue underlying with the KitProg or PSoC Creator? We're soldering the BGA PSoC by hand so that may be what's causing the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We got the KitProg to finally work, it was most likely a hardware issue. Thanks for your help everyone!