Is there a way for you to redefine a value in code?
For instance, if I have "#define CapSense_AUTOCALIBRATION_ENABLE (1u)" set by my CapSense module, is there a way in my code to re-define this to (0u) depending on a specific input? If so, how could I possibly go about doing this?
I'm attempting to use the CapSense_CSD_P4 to enable a proximity sensor. I downloaded and ran the example project and all goes well. If I try to add a simple button everything breaks.
The proximity sensor reads fine until you press the button, which then causes the proximity sensor to read its max value 255 indefinitaly.
Attached is an example project. All I did was take the example proj from Cypress and add a debouncer with pin. So if you run it with a proximity attached and a button here is what happens:
1. Code loads fine
2. As you move your hand closer to proxmity sensor red LED on pioneer board changes intensity (working fine)
3. If you press the button the led goes to full bright
4. Proximity sensor no longers works. Code is in some type of deadlock.
I'm trying to make a QR Code Scanner & Decoder.
I referred some material on Atmel's "SAM4S PIR Camera Reference Design" which uses a combination of PIR sensor + CMOS sensor to detect motion & take a VGA-compatible snapshot respectively.
The CY8CKIT-048 also has a PIR sensor. I want to know if a CMOS sensor can be used to obtain a similar functionality.
My primary objective is a QR code scanner, so, higher resolution is not a necessity.
Also, please let me know if there are other ways to do so using the CY8CKIT-048 or any other PSoC.
====================================================================================
Links to files:
"AT01180: Barcode and QR code scanner User Guide" - http://www.atmel.com/tools/SAM4S-WPIR-RD.aspx?tab=documents
Hi,
I have tested the UART comm with P7.0 P7.1 on cypress CY8CKIT-043, its working good able to get the debug messages.
But I need to configure other UART also.
I have configured the set of pins P6.0, P6.1 and P5.0,P5.1.
I can able to detect the UART port with serial to USB connector with UART Rx,Tx, gnd lines connected,
but I am getting garbage data. I have configured the baud rate to 115200, but its not giving correct data.
Is there anything need to configure for uart?
Right now I have to navigate to the Bootloader.hex and program it to my device, then navigate to my Program.hex and program that to my device for it to work.
Is there a way using PSoC Programmer to program my device with the Bootloader.hex and Program.hex at the same time?
Hi!
There is a project that requires communication between a battery and the inverter attached to the battery. The battery has an in built chip for communication. I am involved in designing the inverter. I have decided to use a PSoC-4M chip for inverter control.
The communication between the battery and inverter needs to happen over Modbus and/or CAN. Modbus is compulsary, CAN may or may not be included. The problem is that I have never used any of the two up till now. After searching, I found two PSoC-4M chips that have a CAN driver. But I can't find one with a Modbus driver. Neither can I find Modbus interface IC. Like we have SCB for I2C, UART, SPI etc. don't we have one for Modbus? Please help me find a way of implementing modbus support on PSoC-4M.
Thank you
I'm looking into using Die Temperaturep [v1.0] block on a PSOC 4 CY8C4245PVS-482.
This is an extended temp PSOC 4 that I'm using for a high temp application. When I open the data sheet for this block I notice the first thing it says in the Features section is "Valid operating range from -40 degrees C to +85 degrees C".
I'm wondering if this documentation is incorrect or if the software/hardware limits the internal measuring range of the die temp measurement to max of +85 degrees C.
The data sheet of the the CY8C4245PVS-482 says the max operating temp of the junction for that micro is +105 degrees C.
I would expect the Die Temperature feature to measure up to that +105 degrees C temp and not saturate at +85 degrees C. I'm going to test this out as soon as my board arrives from our contract manufacturer.
I just want to check with Cypress that any temp readings above +85 degrees C will be in spec of the parts reading capabilities for that function of the PSOC.
I've attached a screen shot of the data sheet I'm referring to.
Thanks,
Kyle
Hi. I'm trying to simultaneously (well, interleaved, to be more accurate) read multiple SAR ADC channels into two separate buffers via DMA on a PSOC 4, but I'm having a hard time seeing how. I wouldn't even mind if they wound up interleaved in the buffer, but don't see how to do that either.
Specifically, the DMA_Start function takes a SrcAddress parameter, which lets me successfully configure and DMA from any one ADC channel by providing, for example, ADC_SAR_CHAN0_RESULT_PTR as SrcAddress. This works great. But there's no option to specify multiple source addresses. I've tried chaining the DMA descriptors in a loop, but unsurprisingly, I just don't get any data from channel 1, it always reads 0. I can't run DMA_Start twice -- whichever SrcAddress is last, I get data only on that channel.
None of the examples I've found actually do this either. But I'm sure it must work -- not much point in a sequencing ADC if you can't actually get multiple channels of data out!
Hi all,
I am working on a project that needs a fast GPIO bit-banging of around 4MHz.
Seeing 48MHz system clock on the datasheet, I thought I give CY8CKIT-049 a go.
After googling, I found that the fastest toggling can be achieved by using this (from an app note):
for(;;)
{
CY_SYS_PINS_SET_PIN(LED__DR,LED_SHIFT);
CY_SYS_PINS_CLEAR_PIN(LED__DR,LED_SHIFT);
}
I also changed the internal main oscillator (IMO) from 24MHz to 48MHz in PSoC Creator 4.
Using the above code and my oscilloscope, I found that the high-period lasted for 200ns which is way too slow for my application.
Forgive my ignorance, but, can someone advise me on how to get the fastest GPIO manipulation?
Thank you.
Hi,
I added an SCB SPI channel in one of my projects on the PSOC 4200M of the CY8CKIT-043.
After some hours of debugging, I figured out that the chip does not clock out new data as it gets written into the transmit register. Data just accumulates in the FIFO.
So, my guess was to look closer at the clock for the SCB SPI block. Instead of the internal clock (8MHz with a /3 divider from HFCLK, 8 times oversampling), I added an external clock 8MHz. And indeed, now, data gets clocked out correctly.
I have compared my setup of the SCB SPI channel with the one provided in example "SCB_SpiCommMaster01". In this example, the internal clock works for me. The settings in my own project are identical.
What could the reason be that in my own project, the internal clock does not get connected (?) correctly to the SCB SPI block? I would prefer using the internal clock source instead of wasting an external clock element.
Best,
Severin
Hello, I have been using the PSoC 4 M-Series Pioneer Kit for a while without any problems. Now I'm having trouble connecting to the board. When I try to enter Debug mode it gives me an error saying the "Port Acquire Failed". I have rebooted my laptop several times and have tried different USB ports. When I plug the board into the USB port it does power on and runs the last program I executed.
Has anyone had this trouble or may have some suggestions on how to connect to the board, if so please let me know.
Thanks,
Joe
Hi,
I have tried looking for documentation regarding what does the coloring of clock sources mean in PSoC Top Design.
See the image attached.
The new clock color is white but after compilation it changes to purple. What do these colors signify?
-Best Regards
hi,
I want to program the cypress kit CY8CKIT-043 to communicate with ESP8266 wifi module to get wifi connection.
I have tested with Arduino UNO board using AT commands to communicate with ESP8266 module.
I have configured the UART pins P6.0 and P6.1 pins as UART comm for this module.
I want write program for communicating with ESP8266 module on UART.
Can anyone suggest how to approach or give me some example programs.docs.
Hi;
I have observed that there is no measurement instruments in PSoC creator 4. I designed a circuit and wanted to monitor my current and voltage, but it looks like there is no multi-meter in PSoC 4 Gui.
Is there any possibility to monitor your design or is there any other cypress product which has that functionality ?
May anyone provide me a sample of code to handle an interrupt on an external pin that coexists with DeepSleep mode?
Compared to previous versions Psoc Creator 4 has introduced some difference in this regard ?
TNX
I am using CYBLE-012011-00 Chip . I want to change the operating Conditions (Operating Conditions) like VDD and VDDR to 2.0 volt current setting is 3.3 volt .( I have included screenshot )
I want to know whether changing operating conditions can damage my chip ??.
I want to drive a char LCD with the CY8CKIT-048 Kit. Do the CharLCD_V_2_20 component works with the Analog Coprocessor?
Hi!
There is a project that requires communication between a battery and the inverter attached to the battery. The battery has an in built chip for communication. I am involved in designing the inverter. I have decided to use a PSoC-4M chip for inverter control.
The communication between the battery and inverter needs to happen over Modbus and/or CAN. Modbus is compulsary, CAN may or may not be included. The problem is that I have never used any of the two up till now. After searching, I found two PSoC-4M chips that have a CAN driver. But I can't find one with a Modbus driver. Neither can I find Modbus interface IC. Like we have SCB for I2C, UART, SPI etc. don't we have one for Modbus? Please help me find a way of implementing modbus support on PSoC-4M.
Thank you
Hi,
I was wondering why my "ARM GCC 4.9-2015-q1-update" does not push all ISR's working registers onto the stack.
This obviously causes any kind of random behavior and painstaking debug. I have not seen this behavior before on any other compiler. Below a code snipped of one of my ISRs (r2 and r3 are not pushed onto the stack, but used in the ISR; they are of course also used in the main program).
0x00000CA0 <PWM_Drive_ISR>:
287: * Return:
288: * void
289: *
290: *******************************************************************************/
291: CY_ISR(PWM_Drive_ISR)
292: {
0x00000CA0 push {r4, r7, lr}
0x00000CA2 sub sp, #c
0x00000CA4 add r7, sp, #0
293: uint16 curTimeStamep = 0;
0x00000CA6 adds r3, r7, #6
0x00000CA8 movs r2, #0
0x00000CAA strh r2, [r3, #0]
294: uint16 curPeriod = 0;
0x00000CAC adds r3, r7, #4
0x00000CAE movs r2, #0
0x00000CB0 strh r2, [r3, #0]
What am I missing here? I cannot believe this is a bug, but have no other explanation. Is there any other version of GCC that is available for update in PSOC Creator 4.0 (4.0.0.432).
Best,
Severin
I'm currently looking to use CapSense in a proximity sensing application. The hoped for range is 30 cm with a 100 Hz sample rate.
Looking at old Research, if you use a Capaciflector it may be possible to extend the range of the sensor. Basically behind the sensor you place another sensor (with a further ground plane behind that one) and at the same time send the same excitation signal to both sensors.
(It seems that it may be possible using the PSOC Mutual Capacitance mode (CSX) to send the same signals to both sensors synchronously) <- Not true.
Driving the second sensor using the Shield Signal seems like one way to emulate this technology (Synchronous with sensor signal).
On another level, we may build our own sensor, just to confirm how effective this is. Does a proximity sensor shield exist which uses the above multi-layer sensor idea, exist?
