PSoC™ 5, 3 & 1 Forum Discussions
I have a board I designed according to the CapSense design rules and I'm hoping somebody would be able to help me out with the issue I am having (I have attached a partial image of the board just to show its design for reference).
So, here is my issue. When I set my CapSense module to manual I get strong readings on all buttons and the slider, but seeing that we don't have time to do manual calibration for every single item these go in, this isn't very feasible especially with environmental factors having effect of the readings. When I set my CapSense to manual with run-time tuning the reading I get for my furthest button isn't as strong but is still plenty to set as a touch. Now the issue is that when I set my CapSense to SmartSense it barely gets a reading from this button at all.
Is there anything I can do to make this reading stronger when using SmartSense? When I use manual or manual with run-time tuning I get a very strong reading so I doubt this is a board design issue and could probably be fixed somewhere in software, I just dont really know how.
Show LessHi All,
I am using CY8CKIT-050 Development Board for my project purposes. I intend to generate a PSFB PWM signals from the PSFB block such that the phase shift is like a sine wave. To explain it in another way, I want my phase shift to gradually increase from 0 to maximum value and then reduce to 0 within 10 ms (half wave of a 50 Hz sine wave). It is similar to a sinusoidal PWM where the ON time of PWM increases from 0 to maximum and then reduces to 0 in 10 ms. The only difference here is that I need my phase shift to change the way a sinusoidal PWM changes.
My PWM signal is 10 kHz i.e. 10^(-4)s. My phase shift to increase from 0 and then return back to zero in 10 ms. So there would be 100 PWM signals (.01s/.0001s). From this information I came up with the sine table as given below after having a look at this article 'http://microcontrollerslab.com/spwm-generation-using-pic16f877a-microcontroller/'.
uint8 sine_table[101] = {255, 254, 253, 252, 251, 250, 248, 246, 244, 242, 239, 237, 233, 230,
227, 223, 219, 215, 210, 206, 201, 196, 191, 185, 180, 174, 168, 162,
156, 149, 143, 136, 129, 122, 115, 108, 101, 93, 86, 78, 71, 63, 55, 47,
39, 31, 23, 16, 8, 0, 0, 8, 16, 23, 31, 39, 47, 55, 63, 71, 78, 86, 93,
101, 108, 115, 122, 129, 136, 143, 149, 156, 162, 168, 174, 180, 185, 191,
196, 201, 206, 210, 215, 219, 223, 227, 230, 233, 237, 239, 242, 244, 246,
248, 250, 251, 252, 253, 254, 255};
I have included my code along with this post. Please have a look at it and do point me in the right direction so that I can sort out this issue at the earliest.
Thanks in advance.
Show LessHello All,
I'm trying to use a CY8CKIT-050 to read a hex file from an SD card and flash a PSOC4. I can read from the SD card and push text to the LCD screen that comes with the kit so I know that part is working. I can Aquire the device, verify the silicon ID and kind of erase the flash.
An error occurs just after "Write_IO (CPUSS_SYSREQ, SROM_SYSREQ_BIT | SROM_CMD_ERASE_ALL);",
When I read from the SROM, I get a checksum zero fault returned.
Continuing the oddness, after running to this point if I power cycle my PSOC 5, my code times out trying to verify the silicon ID. Specifically it times out trying to read the SROM after doing "Write_IO (CPUSS_SYSREQ, SROM_SYSREQ_BIT | SROM_CMD_GET_SILICON_ID);"
If I check my PSOC4 using the MiniProg3, I can read the silicon ID using PSOC Programmer 3.22.0. I can also see that the flash has been set to 0s.
I tried powering my PSOC4 off of the PSOC5 kit and a power supply (tried 3.3V-5.5V, supply rated @ 28A ) with the results being the same.
Anyone have an idea or a gut feeling to start from? I appreciate the help.
Show LessHi there - first time poster. I'm using a 68-QFN part from the CY8C58LP family.
I would like to use P12[7] as a rising-edge triggered interrupt. This is an SIO pin whose corresponding bank voltage (VDDIO1) is 3.3V. The source driving this pin is a digital 1.8V.
What I would like to do is use a Vref for the SIO input threshold, and configure the Vref component to Vccd (1.8V SIO Only).
My question is - when using a Vref as an SIO input threshold, what are the relative Vih and Vil voltages?
The "Pin" component datasheet (http://www.cypress.com/file/137401/download) lists on page 31 a few Vih/Vil settings but the GPIO values listed are relative to the VDDIO voltage. If I'm using a reference voltage Vref (instead of the CMOS default), what values can I expect?
Thanks in advance -
Parker
Show LessHi,
I'm writing PSOC5 UART driver with PSOC Creator4.When I build project,message shows en error which is UART_RX_STS_FIFO_NOTEMPTY undeclared.Additionally,message says that 'UART_XXX_DisabelRxInt','UART_XXX_EnableRxInt','UART_XXX_DisabelTxInt'and'UART_XXX_EnableTxInt' are all implicit declaration.
Show LessProblem statement:
CY8CKIT is not responding to the CANape command, When the CY8CKIT is unplugged and plugged in again in the COM port.
Expected behavior: CY8CKIT should respond for CANape command
Actual behavior: CY8CKIT not receiving command from CANape (But CANape sent the command to COM port ).
Note: If CANape is reopened (Close and opened newly), after CY8CKIT is unplugged and plugged in USB port, it working fine (CANape can able to connect and read variable successfully from CY8CKIT)
Here, CANape sent the “connect” command to CY8CKIT after plug in CY8CKIT. But CY8CKIT is not receiving any command from CANape.
Kindly refer attachment for code reference
1) Could please give solution for this problem?
2) Why the CANape command is not received in CY8CKIT when CY8CKIT is unplugged and plugged in USB port
Hello,
I am trying to debug a CY8CKIT-059 (CY8C5888LTI-LP097 device) programmed with a code example from Cypress with a MiniProg3 and PSoC creator 4.0 .
The programmer and device target are visible and I am able to connect to the device (using external or 3.3/5Vtarg power supply). The project builds well and I get an output in the command window that says that the target has been properly programmed.
Then, when it tries to switch to debug mode I get this error:
"error: dbg.M0015: Debugger exited unexpectedly during run. Encountered error (Target disconnected See output window for more information."
and the show details tab:
"There was an unhandled error during the debug session. This has forced the debugger to shutdown. Try again."
Even if I try again it does not work at all.
Then I tried with PSoC Creator 3.3 and I am able to debug. Is somebody able to fix that problem on PSoC Creator 4.0?
Regards,
Xavier
Show LessHello everyone,
I am currently using a PSoC 5LP CY8C5888LT*-LP097 (dev kit) and I am trying to do a simple "Hello World" test with the DF-ROBOT lcd shield V2.0 and keep failing.
The symptoms are :
- The LCD seems to receive commands from the mcu but instead of having the expected behavior, it randomly move the cursor, write distorted characters and sometimes does not even display the two lines. My guess is that the commands used in the library are not being read correctly in the LCD even if it is supposed to use HD44780.
There is nothing special in the psoc creator project as I simply added the LCD_CHAR component and set the pins on the correct LCD port.
*The LCD is connected with parallel communication using the P0[7:1] port: DB4 0[1] to DB7 0[4], E 0[5] and RS 0[6].
* The R/W pin on the lcd is connected to ground so it is always in "write" mode.
* The R/!W on the Mcu isn't connected.
* The display is powered and back light is on.
* I have tried many projects found on this forum without success.
Am I missing something ?
Show Less