Use PSoC programmer with the miniprog3 to check for a required update.
What version of Creator are you running? Latest is 4.0 SP1
But the CYBLE contain a PSoC4-BLE, which _is_ a Cortex-M0. Otherwise you should the supply voltages whether they are stable (you have decoupling caps, right?). Also, use a scope to check that the programming signals are clean.
I did what you suggested with the miniprog3 and PSoC programmer and it cam back as the firmware version is up-to-date.
Hex: 2.05 Miniprog3:2.05
I am running PSoC Creator 4.0 Update 1 and I did change for updates as well and everything is up-to-date.
Thank you for the suggestions, and others?
Yes I am supplying the voltages that are necessary to the pins that needed. I am using the the recommended host schematic for a single supply. I do have a main decoupling cap from the voltage regulator that I am using.
I did use a scope to check the programming signals and everything looks good.
Thank you for the suggestions, other thoughts?
1 of 1 people found this helpful
No, not really. There seems to be a SWD connection, but the programmer doesn't get get the device ID. This might be an issue with the BLE module, or with the programmer. When you have another MiniProg3, try it. Maybe use another USB cable. Maybe use PSoC programmer instead of Creator.
(Since you looked at the signald with a scope we can probably rule out that something else is connected to any of the SWD lines, or that Vdd is not clean)