Recent discussions
Overcurrent Protection No hardware shutdown. Software interrupts do not have the highest priority, why?
The optimal solution should be a hardware shutdown.
Show Less
Hello Guys I am biginer at Psoc4 and i am tring to impliment IR reciver RC5 protocol with CY8C4245 AXI 483 . and with attached code every time i am reciving same address for all key and same command for all key..that is not actual.
also i attached my logic analyzer snpshot.
Can anyone have idea how can i solve this.
Show Less
Hi,
I'm using a PSoC 4 (CYBLE-214015-01 32-SMT) as a heart rate collector. I'm using the heart rate collector example code (attached).
I'm trying to connect to a BLE heart Rate sensor but am given a "CYBLE_EVT_GAP_AUTH_FAILED, reason: 0x5" error.
This sensor easily connects to any smartphone App so I'm at a loss as to the issue.
Chris
Dear sir,
I have a question about VBUS terminal processing for PSOC4L.
When using the DP/DM ports in this device as GPIO (not using USBFS), can I leave VBUS open? Or should it be fixed to VDD?
I thought that if these ports for USBFS were completely separated from VDDIO, they might not function as GPIO unless VBUS was applied.
Is it correct to understand that the DP/DM port can be used as GPIO without depending on VBUS processing?
Best regards,
Show Less
We are in the evaluation phase of our project so one of the parameter to select the MCU is by comparing ADC error rate. So, I would like to know how to calculate total ADC error rate of CY8C4148AZI-S443 from the different errors provided in the datasheet.
Show LessI recently posted this question that was answered by Gautami_12, however, the answer was not clear and the site will not allow me to post a reply. Gautami_12 shared the following images from the datasheet that shows CY8C4248LTQ-L485 is an alternate part to CY8C4247LTQ-M475. What I don't know is if the code has to be recompiled. Currently the PSOC creator project is targeting CY8C4247LTQ-M475. Will the object code compiled targeting CY8C4247LTQ-M475 work on CY8C4248LTQ-L485, or does the project need to be updated to target CY8C4248LTQ-L485 and the code recompiled? Because the code is in production, recompiling the code presents configuration control challenges. We likely do not want to purchase these alternate chips if the code will need to be compiled again to target the new chip.
The originally posted question:
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 LessI have implemented the procedure to manage a emulated EEPROM with non-blocking feature but in my timer interrupt (located in RAM) when the microcontroller executes the yellow instruction
a Hard Fault interrupt is generated.
When the timer interrupt function is located in FLASH, the Hard Fault is not generated and the code is executed properly
Correct execution:
Thanks for your support
Lucky
Show Less
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 LessHi,
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,
dudeskie
Show Less