I have some problem using the new creator for debugging as well. But didn't have time to check it. Need to finish a few things with the old creator first.
After de-installation of Creator 2.0 my Project was ruined due to the updater which replaced the modules with the newest.
A new project couldn't compile, because the bootldr had a wrong version. Sounds like a fourtnight holydays...
Can you post your design? I'll take a look at it.
You did not understand me quite right: It is ANY design, even without a module. Debugger exits with the above errormessage.
I have a deadline on monday morning (9:00h utc+1)
Think, I'll gonna file a case...
PSoC Creator should have automatically created a backup of your project in the "backup" folder in "*.cydsn". So, you should not have to redo anything in your previous working environment.
I am not sure about the debugging issue. Sung Pak is the right person for that, and it appears he is investigating already.
I switched, back to Creator 1 (SP2) which was a lot of de- and re-installing and now I can access the projects again. Phew!!!
Probably my PSoC5 processor module for the kit001 is too old. Can that be?
I don't think its an issue with silicon. I assume you are using CY8C5588AXI-60. The same should work for creator v2_0. Also project which was opened in Creator_v2_0 will not work in 1_0. To make it work, you need take up the backed-up project and open in 1_0.
thanx for your effort to help me. I just reviewed:
Using a CY8C5588AX*-60 ES1 (That's what the Miniprog 3 says)
And I red in the Revision Doc for Creator 2: ES1 no longer supported.
Might be the error. If you can get hands on a PSoC5 processor module with ES1 you can try.
Isn't there an exchange-program to current ESes for the modules? (I reside in Germany, how to???)
The migration document for Creator 2.0 explicitely states that CY8C5588AXI-060 ES1 is still supported, since it was delivered to customers.
Ok, so now we know as much as before. I'll install creator 2 on a Vista machine which is connected with a Miniprog3 to a Kit 001a with a working (tested with Creator1) PSoC5 processor module with an ES1 5588 on it. I'll write a small demo project and I'll inform you about the results...
Yes, the error persists, too bad.
Warning: Cannot set breakpoint: 'C:\Cypress\Another Testarea\Cr2Test\Cr2Test.cydsn\main.c:26'. Encountered error (No hardware breakpoint support in the target.).
Error: dbg.M0015: Debugger exited unexpectedly during run. Encountered error (Remote communication error: No error.)
I included the Breakpont-errormessage only for clarity, the debugger exits without a breakpoint as well.
PSoC Creator 2
Cy8c5588 ES1 - Processor module
Similar project works fine with PSoC Creator 1 SP2 under the very same environment
Cr2Test.cywrk.Archive01.zip 913.1 K
Can you check the Miniprog3 clock speed value? The selected speed should not be more than 1/3 rd the value of Bus clock speed of the target device. While slower speeds are possible for debugging, the speed should be at least 1 MHz to program the device. 6 MHz is the highest recommended clock speed.
I'm also having debug problems with PSoC Creator 2.0. The same message appears: "dbg.M0015: Debugger exited unexpectedly during run. Encountered error (Remote communication error: No error.)". I've changed the Debug speed (lower than 1/3 BUS_CLK) and still.
I am using the CY8C3866AXI-040ES2 with the CY8CKIT-001. The device is properly programed but when you try to change to debug mode, the error apears.
Any ideas? Thank's.
I solved the problem for me.
Does your windows-username contain any special (non ASCII) characters? My username was "Jörg". when I installed a new úser (caution:renaming does NOT work) everything went fine. That did cost me hours, indeed!