We have object code that is built targeting CY8C4247LTQ-M475 and everything works fine. With shortages of chips we found availability of CY8C4248LTQ-L485. Does anyone know if our object code will work on the CY8C4248LTQ-L485 without rebuilding it targeting the new chip? From what I can tell the M series seems to be a scaled down version of the L series.Show Less
A pleasant day to you all!
I humbly request for a technical support from this community regarding my cuurent predicament. Attached herewith is my simple implementation of an instrumentation project, using the CY8CKIT-145-40XX PSoC 4 module. It involves voltage measurement (using PSoC4 ADC block) and serial communication. The master controller is a PLC, with RS485 connection. My CY8CKIT-145-40XX is connected to a TTL-to-RS485 converter. This is just a single node point-to-point communication. The sequence is as follows:
1.) PSoc4 will send an initial command string to the PLC (e.g. "ABCD\r"). In return, the PLC will turn on and turn off some relays. After the relay actions, the PLC will send back some string to PSoC4, in which the PSoC4 will send back the acquired readings to the PLC, as a result.
2.) Initially, I used the baud rate of 9600 bps, but I intentionally set it to the lowest acceptable baud rate of the PLC of 1200 bps. This is due to the fact that I am yet currently finding the cause of the miscommunication, and at the same time, I have just a digital multimeter for various signal tracing and measurements.
3.) I implemented the UART block, with RX interrupt. First, with external interrupt to no avail. Lately, I switched to internal interrupt, but the result is the same. The PLC promptly receives the string command coming from PSoC4, and the PLC sends back the command. This is where it is getting weird.
4.) The CY8CKIT-145-40XX cannot be triggered by the incoming serial data from the PLC. But, a voltage disturbance is observed on the kit's pins (P3.0 as RX, P3.1 as TX). This validates that the PLC is indeed sending serial data. However, I observed that the interrupt service routine/handler is somewhat triggered by the transmit action only, and not by the PLC. Whenever the PSoC4 sends out the string, the interrupt is triggered altogether. So, I know that the interrupt handler is working as expected, albeit the RX interrupt from the PLC is not received properly.
5.) I referred to similar problems in this community, but my situation is quite different. And honestly, I even tried some recommendations on some threads (regarding PSoC4 UART RX) to my project, but the result is still the same, RX interrupt cannot be triggered by the PLC. In the past, I have used PSoC5LP and PSoC4 using I2C, and not UART, with no problems at all.
Please find time to check on what I am doing is wrong, or lacking. Your most prompt and positive response will be highly appreciated.
Thanks and Best Regards,
I am working on PSoC 4 project. i have an issue with CapSense_SetParam
i changed the value for finger threshold through this API
and then i read it with this API
.. it successfully changed the value for finger threshold .
but after power reset of device when i read it again it goes back to values which was flashed through program.
CapSense_SetParam is not changing the value permanently or may be i am missing somethingShow Less
Can chip signals be changed in a project?
I want to change another chip signal, but I don't want to change the program under the current project unless it is necessary.Show Less
I have added code.
I modified the configuration。
I recompiled the code and the added code was lost. How to set , the code I added is not lost?Show Less
Can the cpu frequency only use the internal low precision clock? Can the external crystal oscillator only be used for the Bluetooth module?
I am facing some troubles with the Die temperature sensor in a PSoC4 4100PS (CY8C4145LQI-PS433, Kit 147).
I implemented the sensor together with an SAR ADC as described in the DieTemperature Datasheet in a design by my own. Additionally, I tried to transfer the example "ADC_SAR_Seq_DieTemp" to the device.
In both cases, I am reading non-useful values back, at room temperature the function gives me something like -20 °C from the ADC value. I already corrected the ADC value as described in the datasheet because of the 1.2 V reference voltage.
The attached screenshot shows the ADC settings which I am using in the "ADC_SAR_..." example. Compared to the key parameters according the DieTemp Datasheet I think this should be fine. Actually, I measure aroung 650 mV at room temperature, with rising temperature the voltage slightly increases. Unfortunately the datasheet is not giving any information on the behaviour of the sensor.
Any idea what I am doing wrong? Thanks for your help!