PSoC™ Creator & Designer Forum Discussions
text.format{('custom.tabs.no.results')}
My copy of Creator 3.3 lets me cut and paste from Creator code examples to Word. Creator 4.3 allows the same action BUT it blots out the code as though it is being redacted. Would someone tell me what this is called and how to fix it? I attached a Word file with an example of each.
Thank you very much.
Tim Miner
Show LessHi 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
Hi Cypress Community,
Please I'm looking for some help on PSoC Creator 4 editor related to selection of the schematic sheet size and creating schematics
with more sheets. Is there any user manual or video tutorial or application note where to find out:
- how to select or change the size of the schematic drawing sheet
- how to add new sheets and what IN-page and OUT-page symbols are used to transmit the signals between the schematic sheets
- is there a user guide where to look for all you need to create a design with PSoC Creator?
Thank you for any comment that could help,
Dan Radut
Hello,
Is there a cyelftool for MAC / Linux (not cymcuelftool!). The PSoC Creator version is needed for adjusting the .elf file's sections. Why doesn't Cypress provide an open-source version or create a build for Linux and MAC? It would be handy if we can use PSoC5 on different platforms. Everything is there, the IDE, compiler, programmer, debugger. Only cyelftool which is probably a c / cpp tool which could be easily migrated to another playform. Or why not make it open-source? That would increase usability without any costs imho.
Or does Cypress want to keep the cymeta block proprietary? Don't think so the meta block just consist of:
AA AA BB BB BB BB CC CC CC CC
A = HEX version (16 bit)
B = Silicon ID (32 bit)
C = Cypress proprietary: Silicon ID + Checksum (32 bit)
Also, what about stripping out the schematic editor / DWR from PSoC Creator (or making it open source). I mean, the sources aren't obfuscated.
Regards,
Rolf
Show LessI 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!
Show LessAbout 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
Show LessWhen an additional include directory is specified in the Compiler General settings: (see ..\..\MyIncFiles\include),
it does show up before the "Generated_Source\PSoC6" includes (see the command line settings in the dark grey preview area):
However when I inspect the generated Export/ExampleCortexM0p.ipcf file, the added include directory is missing, while all the PSoC6 includes are mentioned:
All directories are in the <includePath>, EXCEPT for the one specified under the "Additional Include Directories".
Of course the work around is to manually add the include directories after using the ipcf configuration, but that gets annoying after the second time...
Show LessI am having the same problem as discussed in this thread:
Multiple definitions of component
However, when I follow the suggested solution and disable the 4.2 Dependencies, I get compile errors, where the components in the project still try to reference the component in the 4.2 folder.
"Error in customizer for component "CapSense_v3_0" : Loading : (4.3 path) cannot be loaded because an assembly with the same name ("CapSense_v3_0") is already loaded: (4.2 path).
I get this error for BLE_PDL_v2_10, CapSense_v3_0, and Scan_ADC_v3_10.
Is there any way to solve this error and use the components in the proper 4.3 folder?
Show Less