Can you please send a screenshot of PSoC Programmer log when you program the device and MiniProg3 Port Configuration window of PSoC Creator which can be accessed as shown -
Tools -> Options -> Program/Debug -> Port Configuration -> MiniProg3
Please ensure that the VDDA, VDDD, VDDIO voltages are set at 5.0 V under Operating Conditions in System tab in PSoC Creator.
Refer to the following thread for further details regarding the same -
Thanks and Regards,
Rakshith M B
... and check in Creator-> .dwr file-> System view: that debug interface is set to swd and not to GPIO.
Thanks for answering, sorry I didn't respond quicker was busy.
Yes the settings match and I am quite familiar with SWD as I have debugged many M0 arms before, so I have to assume something else is not satisfied here that the debugger is looking for as opposed to what the programmer is looking for.
I tried this again.
When i select "select debug target" it takes 30 seconds before the dialog comes up???
If i hit any button it waits a long time before i get a response, so that has got to indicate a problem here..
System is Win 10 unfortunately, stuck with it. why is this so slow?
How is your reset line? We had this problem once, the circuit did not respond to debug operations and the cause was we had a big capacitor (do not remember value) in the reset line. When we removed this and put a smaller value capacitor, the circuit started to work for debug.
There is no cap on the reset line. I tried a pullup but that did not help.
Data sheet says this part will program at 2.8-5V, however we have not
been able to program it at 5 volts, always fails for some reason. Always
programs at 3.3V ok..Could there be something wrong here with the chip
Since you can program the device with PSoC Programmer,
I think that the connection must be sound.
So I suspected a couple of things
(1) Port Setting of the Debugger
(2) The project under test
Since CY8C4245AXI-483 is same device on a CY8CKIT042,
I tested with my CY8CKIT-042 and MiniProg3.
I tried with some port settings using MiniProg3 with and without on board KitProg,
as far as the setting was correct I could program and debug the device.
So, right now, I would suspect the project you are using.
How about trying with my project attached?
Note: If you are using P0 for other purpose,
please change the pin to something else safe to assign.
If my project can be programmed without problem,
there might be something wrong with your current project.
I'd suggest you to create a new project and re-use source/header files.
If my project can not be programmed either.
Right now I don't have a good suggestion for you.
Following is/are what I tried this morning.
You can skip them if you are busy ;-)
I created a minimum project
Only 1 LED (P0)
I connected MiniProg3 and CY8CKIT-042 with 10pin cable.
At first my port config was set to 5pin (unintentionally)
The response of Select Debug Target was extremely slow and I could not see the device.
Then seeing the 10pin cable I changed the Connector setting to 10 pin
meantime, I removed the USB cable from the board to avoid KitProg and MiniProg3 conflict.
So I changed the Power to 5.0 V.
Then I could see the device
And I could start debugger
Next thing I tried was reset the Power to External and connected the USB cable to the board again.
Then, still I could see the device and start debugger
Just to make sure I used PSoC Programmer and set pin to 5, which did not allow me to proceed further.
Then returning to the pin to 10, I could program the device.
I will try this later when i get a chance