Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I've been trying to make UART interrupts work on the PSOC6 CM0P processor without success; I have been able to get CM4 to work. This is all on Modus ...
I've been trying to make UART interrupts work on the PSOC6 CM0P processor without success; I have been able to get CM4 to work. This is all on Modus toolbox 2.3, pdl2.2.1, and just using pdl and low level uart apis (no HAL).
I took a simple Cypress PSOC6 UART dma demo project that runs on CM4 and modified it, removing the dma functionality. For this simple test I am using the Cypress CY8CPROTO-063-BLE board and its debug uart. The app receives and prints any received char from the terminal, and will make a trivial check for a flag set in the UART ISR. I have arbitrary set multiple tx and rx fifo interrupt conditions to force lots of interrupts.
Debugging in Eclipse IDE, the UART fires in CM4 project, I can break in the ISR, and everything works as expected.
I modified the project for CM0 (following Cypress guides and appnotes) mainly by:
Setting CORE=CM0P in Makefile
Adjusting the linker scripts to increase flash and sram for Cm0 app
Adjusting the interrupt cfg structures for CM0
Assigning (arbitrary) CM0 NVIC Mux 9 for the interrupt cm0pSrc
The app compiles and works on both processors with regards to echoing received chars to to the terminal.
On CM4 the interrupt fires, isr flag is set, and I break in the ISR routine.
But on CM0P no interrupt fires, no isr flag is set, and I can't break in the ISR.
I have attached both projects here for reference. What am I missing?
I am using modustoolbox with PSoC6. I am using the latest pdl libraries. I am not getting any warning or error when I am compiling code, but the...
I am using modustoolbox with PSoC6. I am using the latest pdl libraries. I am not getting any warning or error when I am compiling code, but there is some message in IDE showing "ambiguous". Please have a look at the screenshot attached.
to integrate and use ML based application on PSOC6. But since it has main.c and not cpp, it does not allow me to include the files directly. Is there a workaround? I want to use .tflite models with PSOC6 and develop an application using standard TFLite c++ library. Is the issue because of C vs C++?
I modified AnyCloud_OTA_Using_HTTPS in MTB2.2 to use external flash for OTA and its working properly. Now I am trying to run this project on anoth...
I modified AnyCloud_OTA_Using_HTTPS in MTB2.2 to use external flash for OTA and its working properly. Now I am trying to run this project on another laptop with MTB 2.2. I copied the project and imported it in MTB. When I tried to build it is throwing the following error:
Import Error: No module named Keys
Following is the snippet of error log:
File "C:\USER\Work\mtb_shared\anycloud-ota\release-v2.0.0\source\mcuboot\scripts\imgtool\main.py", line 21, in <module>
I am trying to use HAL functions to init a quadrature decoder on the CY8CPROTO-062-4343W board. I have created a custom BSP based on the generic PSoC6...
I am trying to use HAL functions to init a quadrature decoder on the CY8CPROTO-062-4343W board. I have created a custom BSP based on the generic PSoC6 as in docs, and can build and program my code successfully. My problem is in choosing pins for cyhal_quaddec_init. There seem to be no pins available on the proto board that can be used with the 32-bit TCPWMs, and no way to direct the init function to choose one of the other 16-bit TCPWMs. The 16-bit ones do have available pins on the proto board, but the init function seems to just choose the first open TCPWM, rather than try to find an available TCPWM that can access the pins given as arguments to ...init().
I have started to look at the PDL functions instead, thinking that the HAL layer is just not finished yet, but even in the PDL I don't see a way to specify which type of TCPWM (16-bit or 32-bit) should be used.
I obviously am missing something, hope you can clear it up for me.