PSoC™ Creator & Designer Forum Discussions
When I compile my project with PSoC creator 3.0,there are notes that may indicate some problems:
"apr.M0002:Analog signal ... is connected to one terminal only."
The signal is internal to the ADC.
Will it affect the project's functionality?
Ans:
This will not cause any issues with the functionality. There is a mux before Del-Sig ADC to select between the internal and external reference. Since we are using only the internal reference, one input to the AMux will be left unconnected.
Hence, it shows that analog signal is connected to only one terminal.
This will be corrected in the future versions of the component.
MiniProg3 is working with the PSoC Programmer. MiniProg4 communicates with the PSoC Programmer in almost exactly the same way with one exception. The Voltage Setting, however, is grayed out. With MiniProg3 my target powered, but with MiniProg4 my target does not get powered. The Target Power status LED doe not light on MiniProg4. It would seem by the grayed out control and this LED not lighting, my PSoC Programmer/MiniProg4 is not delivering target power. Does anyone know how to change this?
Installed CyInstaller Products:
Bridge Control Panel 1.18.0.3121
Clock Programmer 1.8.0.3121
Device Database 3121
Example Code 3121
PSoC Programmer 3.27.1.3121
USB Bootloader Application 3121
CY4541 CCG4 Daughter Card
Show LessHi there, I've followed the instructions in user guides on how to install the update for PSoC 4700, but even after restarting PSoC Creator 4.2 the PSOC 4700 is not selectable and I still see the option of installing the update. I've repeated this step several times, installed/reinstalled PSoC Creator 4.2/PSoC Programmer 3.28.1 several times, but the update seems to not install every time. Any suggestions? Thank you
Show LessHi,
I'm trying to develop a customizer (yes i'm still trying to design a customizer for my custom component xD), i'm getting a Exception when trying to set a parameter with the SetParamExpr function.
¿Is there anyway to debug the customizer while developing in Creator? I haven't seen someone developing the customizer on VS, running it on Creator and being able to debug it, so if you know a way to debug the customizer please let me know.
I had tried using System.Diagnostigs and Debug.WriteLine function but i can't see the messages being printed. So i'm currently using a Label on the customizer itself to print the messages i need to see.
Attached is the project in case you want to take a look and let me know if i'm doing something wrong (i'm still a newbie with c# and windows forms applications).
To trigger the error i'm getting open the example project, click on the dummy_app component and click the button on the customizer.
Regards,
Carlos
Show LessFirst I see it does not accept Python..the most popular language by most measures.
Visual Basic is not.
So I made the .py into a .EXE.
It runs, outputs, which is captured and displayed in your "output" window.
So far, so good.
But now the script needs an input, a COM port.
How can I get my reply through your output window into my EXE?
Why not just allow .py?
Show LessHello @ll,
If you want to configurate, debug and test your implementation interactive, you can do this with mecrisp-stellaris, an FORTH implementation for several Cypress PSOCs.
Example:
To initiate a PWM there are several API's to do this. One API write the compare value:
To using this API you can call the API in a C-function. To modifies it on the fly you can use the configure menu from PSOC-Creator and translate and flash the whole application.
Alternative you can do following, if you have install mecrisp-stellaris:
100 PWM_1_WriteCompare1() <enter> \ 100 is put on the data stack and the API 'PWM_1_WriteCompare1()' will be calling. /!\ translating and flashing are not necessary
You can also define a word like this:
: MaxDuty1
100
PWM_1_WriteCompare1()
;
or that
: MinDuty1
0
PWM_1_WriteCompare1()
;
... MaxDuty wait MinDuty .... \ for more examples download one of following mecrisp-stellaris implementations:
As already published here, the FORTH development environment 'mecrisp-stellaris' is available for download for the following 7 Cypress PSoC's:
Board: / PSoC:
CY8CKIT-043 -> cy8c4247azi
CY8CKIT-044 -> cy8c4247azi
CY8CKIT-046 -> cy8c4248bzi
CY8CKIT-049 -> cy8c4245axi
CY8CKIT-050 -> cy8c5868axi
CY8CKIT-059 -> cy8c5888lti
FreeSoC2 -> cy8c5888axi
See: https://sourceforge.net/projects/mecrisp/files/Cypress/
If you would like to know more about FORTH, you will find the classic Starting-FORTH and Thinking-FORTH by Leo Brodie:
http://thinking-forth.sourceforge.net/
The Definition of ANS FORTH you can find here: http://lars.nocrew.org/dpans/dpans.htm
If you want to know more about Mecrisp-Stellaris you are right here:
https://www.forth-ev.de/filemgmt_data/files/4d2015-arm.pdf
When PSoC evaboard is not listed and you interest on a Forth for your board, please contact me via the e-mail address provided in README of one of the downloads to clarify the possibility of porting
Klaus
Show LessHi Everyone,
Our customer was using generic DAPLINK hardware along with PSoC programmer 3.27.3 to program their own PSoC6 custom PCBA.
Working without issue until updated to 3.28.x which failed to access the PSoC6 with the same set of hardware worked with 3.27.3.
We would like to confirm if the backward compatibility for DAPlink (old?) is removed since PSoC Programmer 3.28.x
Thanks and Regards,
Kevin
Show LessHi,
I would like to use the PrISM component to change the brightness of a led Matrix.
I have configured the PrISM component with a resolution of 8 bits, the pulse density type as Less Than or Equal.
To change the dimming value, I modify the pulse density with the API function PWM_L_WritePulse0(item), sending and integer from 0 to 255. The dimming is working but is not linear.
I have the following curve:
How can I make the dimming linear?
Show LessHi there,
I recently came across the PSoC Creator (and a distributor's sales pitch), and it looks quite interesting.
Not being completely new to the business, I have the following questions:
1. The FM3 and FM4 Fujitsu/Spansion "legacy" devices are not supported. Is that correct ?
2. What are the general experiences concerning:
- flexibility (covered use cases of peripherals and peripheral combinations) ?
- code bloat and performance loss, compared to a decent hand-written code ?
I have seen & tried similar tools from competitors (e.g. ST and Freescale/NXP), which did not really impress me, for one or the other reason.
Thanks,
Frank
Show LessI am using MiniProg3 and PSoC Creator 4.2 to program my custom board.
Everything was working fine until I changed the 'Programming Mode' to 'Power Cycle'. Not only that I cannot acquire the target, the power on the MiniProg3 just keeps toggling on and off. PSoC Creator is unresponsive during this period and the only way to stop this is to unplug the MiniProg3.
I can successfully flash my target using PSoC Programmer in both 'Power Cycle' mode and 'Reset' mode. I have tried reinstalling PSoC Creator but the settings have not been initialized.
Is there a way to initialize the debug target settings?
Show Less