PSoC™ Creator & Designer Forum Discussions
Hi,
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 LessDear all
We have a project based on a PSoC BLE and we build it with PSoC Creator 4.0 on our Build Server: as soon as I commit to SVN, the Build Server starts the PSoC Creator via command line script (as described here http://www.cypress.com/knowledge-base-article/building-psoc-creator-project-command-prompt-kba88169).
Now we'd like to add a bootloader to the project, which requires a second project in the same workspace. This won't work when called via command prompt, as stated in 4. at the aforementioned link.
Is this limitation still active (the link actually refers to PSoC Creator 2.2)?
Can I put the Bootloader in another Workspace in the same Repository and call two different build scripts when I commit or is it mandatory that the Bootloader and the Bootloadable are in the same workspace?
Any suggestions on how to solve this problem?
Kind regards,
Enpa
Show LessI have created a Visual Studio project based on the Bootloader Host application downloaded from your web site.
The application runs Ok both in debug and in release mode.
I have added an Installer project to my solution so that I can create an Install wizzard to allow my customers to install the application on their own computer.
In solution explorer, in the installer project, under 'Detected dependances' it lists CyUSB.DLL and .net framework. It has not detected Bootloader_Utils.DLL resulting in it not being included in the install package.
In an attempt to make Bootloader_Utils.DLL visible to the installer project, I tried adding it under 'References' in my application project, but got the message that it was not a valid DLL.
The DLL was created following the instructions in the document AN73503_USB_HID_Bootloader_for_PSoC_3_and_PSoC_5LP_0.pdf downloaded from your web site using Visual Studio 2015 community edition.
I have tried re-creating the DLL using Visual Studio 2017 community edition and get the same results in both versions
In VS2017, the dialog for creating a new solution is different to that described in the PDF document
I selected the project type as C++ Blank project. There is nothing in the project creation dialog for selecting the project type as a DLL. This was done in the project properties option on the Project menu. under Configuration Properties>General I set Configuration type to DLL and Target Extension to .DLL
After adding all the .H and .C files to the project, I had to add WIN32 to C++>Preprocessor>Preprocessor definitions in the project properties in order for it to compile without errors.
How can I add the DLL into my project so that it is visible as a dependancy in the installer project?
Show LessIt takes too long to download Cypress Psoc 4.2. Is it normal? How to iimprove installation time? Help !