You are here

am i just doing something wrong or missing a setting for debugging with miniprog? | Cypress Semiconductor

am i just doing something wrong or missing a setting for debugging with miniprog?

Summary: 5 Replies, Latest post by charliex on 11 Feb 2015 12:51 AM PST
Verified Answers: 0
Last post
Log in to post new comments.
charliex's picture
3 posts


Everytime i compile and flash, the debug window for acquire and connect pops up, it takes me a menu selection, and three mouse clicks on different places to do the actual flash ? where am i going wrong, why isn't it remembering the settings or keeping the acquire?  I can't seem to find a default device type of dialog anywhere.

I do select debug target, select it acquire it, then select program flash, if i say instantly repeat program flash, it brings me back to select debug target, which i just selected 30 seconds ago. 



user_14586677's picture
7646 posts

Try exiting PSOC Creator and re-entering, maybe Creator trashed its config

memory. Also try inside Creator seperately selecting Debug target, "Debug",

"Select Debug Target"......


In the worst case you could try reinstalling Creator, but thats very time consuming.


Regards, Dana.


user_343349849's picture
314 posts

 This may not be directly related to your issue but one thing I note is when I change projects, the options for debugger remain from last project.

ie. I use SWD debugging for PSOC 4 and change to 5LP project and when I go to debug it is still using SWD, and visa versa.

debug type seems to be set in 2 places. system settings and debug options.

Would be GREAT if the debug settings were saved with project

Other minprog 3 issues I noted to be aware of (you probably already are)

If the speed chosen is too high it will not work

If wrong version of Device is selected it will not work.  

charliex's picture
3 posts

 same behaviour on different computers, seems unlikely its related to the install. But i can give it the old college try.

So i'm not nuts right? once you do acquireconnect it should just stay connected and let me flash as many times as i want without a re-acquire/connect

user_1377889's picture
9284 posts

Can it be that you use in your project the SWD-pins, so that the communication with the debugger ceases and has to be re-established? Or that your programmed configuration does disable the debug-part of the chip?

Best would be to load one of the example projects unmodified and see if it behaves similarily.



charliex's picture
3 posts

 i'll try it, but it seems to happen all the time , regardless of project/machine.



Log in to post new comments.