PSoC™ Creator & Designer Forum Discussions
Hi to all,
Greetings for the day.
I'm trying to implement the code for the #11 Buttons, while doing this I'm getting the following errors:-
!E E:\amit\myPRO\MY_CHK~1\MY_CHK~1\main.c(72): insufficient number of arguments to `Capsense_DisplayButtonState'
!E E:\amit\myPRO\MY_CHK~1\MY_CHK~1\main.c(73): insufficient number of arguments to `Capsense_DisplayButtonState'
make: *** [obj/main.o] Error 1
the display function is defined for the 2 BYTEs(#1BYTE-->#1-#8 Buttons, #2BYTE-->#9-#11Buttons)
//display button state
Capsense_DisplayButtonState(CSA_EMC_baSnsOnMask[0]);
Capsense_DisplayButtonState(CSA_EMC_baSnsOnMask[1]);
Thanks & Regards-
Amit
Show LessRecently I have been scouring the web looking for examples on a particular project (C based).
Hi to all, I'm trying to use the bridge control panel for my board. I have connected the BCP to my PC & board as I2C slave.
While doing it I do not know the commands to work through. I know I ought to fiddle on it, in that condition please help me with right path to it. Say the boosts BCP will give me understanding & monitoring the operations on board with I2C.
Put anything that describes the procedure, putting commands & retrieving there outcomes. Monitoring all the parameters like Raw counts, Finger threshold, Baseline etc.
Waiting...........
Thanks & Regards-
Amit
Show LessHi,
I'm pretty new to Cypress PSoC and to Creator. I'm learning how to use it and have done some of the examples.
I have a project that someone else worked on and I'm trying to change the target device so that I can run it on a 5LP development kit. I was able to change the device and clean up a couple errors from the clock module. I'm still getting an error when I build the project regarding the bootloader.
The error is "pft.M0076: The selected device for the Bootloader and Boatloadable projects must match, but don't. Bootloader is targeting 'CY8C5888FNI-LP210' and bootloadable is targeting 'CY8C5868AXI-LP035'."
I've hunted around a lot for a place where I can change the target for the Bootloader but have not been able to find it.
To be clear I'm trying to change the target device from CY8C5888FNI-LP210 to CY8C5868AXI-LP035.
Thanks in advance.
Mike
Show LessDo any of you guys use GitHub for your PSoC Creator 3 workspace projects? What do you guys use in your .gitignore file? What files are neccissary and what are not? Not sure if I should ignore the /Generated_Source folder.
I'm currently considering using the below for my .gitignore:
Show Less.DS_Store*.cywrk.**.cyprj.**.cycdx*.cyfit*.rpt*.uvopt*.uvproj*_timing.html*.cydsn/codegentemp*.cydsn/DP8051*.cydsn/Generated_Source
Just getting started with the PSoC5LP (although I have used other devices for many years) and I'm not sure the best way to implement a state machine inside my ISR.
The situation is that I have a UART that is talking to a WiFi device that transfers 'packets' in each direction between the processor and the device. I want to set up a state machine (on the Rx side) that looks for the start of a packet, builds the packet (taking into account 'escape' values etc.) and sets a flag (for now) to indicate a packet has been received.
As the ISR code is the only thing that needs to know about the state values, buffers etc. with a couple of access functions, I would normally declare these things at the top of the ISR C file. As the ISR code is re-written by the IDE, I can see where I should put the definitions so they are maintained across the new versions. However I want to be able to initialise the state machine and typically that code whould go into the xx_ISR_Start() or xxx_ISR_Enable() functions but they do not have the code protection mechanisms in them.
The alternative is to add my own 'init' function but I cannot see how to add the declaration into the ".h" file as, again, there do not seem to be any of the code protection markers. (I could use 'extern' declarations but I think they are ugly in that I could update the header/c files and forget to update the 'extern' declaractions.)
What is the way this is supopsed to be done?
Thanks
Susan
Show LessI'm just starting out tinkering with my first PSoC project and playing with (what I'm hoping to be) the easy version of programmable logic.
Anyway, comping from a software development background I'm used to rapid edit-compile-debug cycles and tend to get frustrated when running a basic test takes more than ten seconds. Unfortunately in PSoC Creator my simple of introductory tests using a small fraction of the available resources takes several minutes to build, and the graphical designer frequently freezes up for three second stretches.
Basically I'm not certain whether this is normal or whether it is an issue with my particular installation, and I'm a little concerned about how things will scale once my design starts to grow.
Are there any options available which I ought to fiddle with? Perhaps enabling parallel/progressive builds, tweaking cache sizes/garbage collection rate or reducing the number of optimization passes for my small and slowly-clocked debug build?
Alternatively is it time to bite-the-bullet and get used to a new type of workflow and/or get myself a more up-to-date computer?
Show Less