Discussions regarding PSoC and MCU products.
Discussions regarding PSoC and MCU products.
Universal Serial Bus (USB) forums have discussions regarding Low-Full & High Speed Peripherals, Superspeed Peripherals, USB Hosts Hubs Transceivers, and USB EZ-PD Type C product solutions for PCs and consumer device topics.
Memory Discussion Forums discussions regarding NOR Flash, SRAM, nvSRAM and F-RAM - performance and reliability with discrete memory densities ranging from 4K-bit to 2G-bit topics.
Discussion forum regarding Other Technologies including Power Management and Clocks topics.
I am creating a project to utilize the ADC of the PSoC6 as a thermistor circuit and the CapSense separately. When I try to generate the application I get analog pin errors. Can the PSoC6 only support either the ADC or CapSense at once? And if so does anyone have a recommendation on easy to interface external ADC's?Show Less
I'm looking for reference code to run MIPI interface of the AR0144 Demo 3 Head board with FX3.
Will appreciate any assistance.
Itay CohenShow Less
I have a DAVE project that I am trying to flash over the air. If I use a Segger debug probe from within the DAVE IDE to flash it, it boots and runs fine. If I power reset without the Segger debug probe attached, it also boots and runs fine. If I use the Infineon supplied XMCLoad over a serial port to flash it, it flashes without error, but won’t boot and run. The .hex file I am flashing using XMCLoad is from the debug build directory of the DAVE project.
I’m not sure if there is some setting in the DAVE IDE that I need to specify in order to get it to flash using XMCLoad correctly or if the problem lies elsewhere. Does anyone have any ideas?Show Less
Hello everybody ,
I use Parallels on MacOS to be able to use PSoC software, in particular I use Bridge Control Panel for UART communications. Everything always worked fine until I installed parallels version 17.1.0.
Now I have problems with the associated COM port, PSoC is detected, I can send data via UART, but I can no longer receive data.
Has anyone encountered the same problem and managed to fix it?
I'm creating a component which uses a rising edge trigger input. The component uses two states. In the first state, the inputs are saved and the internal state machine switches to the next state on trigger, does some calculation and then switches back to the first state.
I wonder if storing the values in the first state should always be performed, leaving the trigger event to only change the internal state or saving the inputs only when the trigger is detected. Currently I can't see no difference, but my experience with hardware description is quite low.
Maybe someone can give pro/contra for each approach?
I need to write synchronously to a DAC. No samples can be skipped. This requires multiple threads ping-ponging, just as it does on reading. However...
According to https://community.cypress.com/t5/USB-Superspeed-Peripherals/GPFI-II-question/m-p/84212 there is a bug in GPIF Designer which requires an extra state to be inserted between driving on thread0 and driving on thread1. Without this extra state, GPIF Designer reports:
"'Thread Number' in action 'DR_DATA' of state-'WRITE_TH1' need to be same as 'Thread number' of action 'DR_DATA0' in state 'WRITE_TH0'"
This extra state causes the GPIF to not write anything for one clock cycle each DMA buffer, which is a problem.
1) Is this a bug in GPIF Designer or in the GPIF state machine? If the former, can we get a fix? If the latter, is there a workaround?
2) Is there documentation available about the waveform states so I can work around the GPIF Designer bug and write my own state machine? I've tried reverse engineering the bits, but don't want to burn days investigating something which may never work.
I've attached two images--the first is the state machine I want, but GPIF Designer will not let me have. The second is the state machine I can get, but does not work due to the skipped GPIF driving samples.
Thanks for the help!Show Less
I am using BTN8982TA IC. In that IC, i am getting voltage as 1.93 in IS pin, and i am using Rs as 3.6K.
How to calculate IL load current by using these values?
How to find the dkilis value?Show Less
I am using the CY8CPROTO-062-4343W and am attempting to design a module that takes BLE data from several devices and then passes that data along via MQTT. I am trying to use the M0 core for BLE as this is battery powered and I understand this saves quite a bit of power. The issue I am having is that despite starting with any example (BLE or WiFi or dual core) when I try to pull in the libs from the other projects I end up with many includes or build errors. I am using ModusToolbox 2.4
Is it possible to get a shell of a project with these libs that will build?
I have tried copying every file over in the workspace and updating the Makefile to include anything from one Example program to the next but I still get many of these errors even when I run the Lib manager 1.4 to update.
./libs/psoc6hal/include/cyhal_hwmgr.h:61:10: fatal error: cyhal_hw_types.h: No such file or directory
/mtw/Empty_PSoC6_App/build/CY8CKIT-062-BLE/Debug/CM4/Source_Files/linkedList.o] Error 1
make: *** [libs/psoc6make/make/core/main.mk:414: secondstage_build] Error 2
for our application we would like to use USB virtual com port to send/receive status messages with FX3s. My understanding is that I will need a MANUAL_IN DMA channel to transfer messages to the FX3 CPU and a MANUAL_OUT buffer to send messages to the host PC. I have modified the USBUart example project, but have encountered a lot of errors.
Can someone please help us understand the steps needed to produce/consume data with manual DMA channels?