PSoC™ Creator & Designer Forum Discussions

Hi all, I'm wondering what the current state of C++ support is in the latest versions of PSoC Creator?  I see some traffic about limited support, but that was quite some time ago.  Has anything improved?

Thanks!
Chris
 

I just upgraded to PSoC Creator 4.3.  I am running on Mac, version 10.12.6.

I am running VMWare Fusion 10.1.6.

Under PSoC Creator 4.2, using KitProg 2.3.3, I can debug my project with a Windows 7 Virtual Machine when the project contains a USBUART with the 0x4b4, 0xf32 standard default settings, and the unsigned driver loaded into the operating system, with NO issues (other than standard connect/disconnect/debug restart issues which are understandable) when the USBUART is plugged into the PSoC5LP USB IO ports.

Under PSoC Creator 4.3, using KitProg 2.3.3, when I start a debug session, IF the USBUART is plugged into the Macintosh USB port, AND I *START* a Debug Session, *EVERY* SINGLE USB PORT RESETS AND THEN RECONNECTS.  I loose 3 USB 3 drives.  I loose my USB mouse.  I loose *everything*.  Everything reconnects, lots of warning messages from MacOS, debug can continue.

IF the USBUART  *is NOT* plugged into the Macintosh USB port, then NO PROBLEMS!!!!  No USB Reset, everything works fine.

To summarize: With USBUART plugged into the Mac from a PSOC5LP, under PSoC Creator 4.3, all USB devices go offline.  With PSoC Creator 4.2, this does NOT happen. 

Please look at the code changes in the PSoC 4.3 creator *Debug Start* sequence relative to the PSoC 4.2 creator *Debug Start* sequence and you should find it easily.

100% reproducible.  If necessary I can do a video and let you see it happen.  It is not my imagination.  I don't think this is a PICNIC problem. (Problem in Chair, Not in Computer).

Thanks!

About 85% of the time after the device outputs  "...successfully programmed at..."  I receive 2 errors  (see below). I get these errors on multiple devices (PSoC 4200L and  PSoC 4200M). This happens even when I use example code from Cypress.

Currently I am using PSoC Creator 4.2 on windows 7 and encounter the problem in multiple example projects/codes such as I2C_SCB_Master, I2C_SCB_Slave, Breathing_LED, etc.

The debug select in the system tab of the  .CYDWR file is set to SWD (serial wire debug).

I've used example code from cypress, and made sure only one device is plugged in at a time.

I'm not using sleep or deep sleep modes

I've tried different USB cables, and different USB ports.

To my knowledge PSoC creator is whitelisted on AV software (also not getting any red flags in AV software) and disabling AV software is not an option .

The only solution I have found thus far is to unplug the device wait a second and re-plug in the device, and then I usually have to select the target and click port acquire multiple times in order to acquire the target and connect.

The errors:

PSoC Creator Error dbg.M0007

The run request failed. Encountered error (Invalid thread id: 1)

The request to run the application on the target failed. Make sure that your code is valid and that the selected target supports debugging.

PSoC Creator Error dbg.M0015

Debugger exited unexpectedly during run. Encountered error (Remote communication error. Target disconnected.: No error.)

There was an unhanded error during the debug session. This has forced the debugger to shutdown. Try again.

Unless there is some sort of register I need to clear, I'm out of ideas and searching for the errors hasn't proved fruitful.

Can anyone point me in the right direction for dealing with these errors?

Thanks in advance