In my CY8CKIT-062S2-43012 board I looking for expanding RAM for operations of mallocs functions.
I have come across one example (QSPI_F-RAM_Access) where QSPI is used for reading and writing in F-RAM. I am not if this is the best example for expanding the RAM for the above purpose. Is that correct understanding?
I thought F-RAM has support for memory-mapped access of RAM but I can not find any example for that. Please share the link for such an example on any PSoC board.Show Less
Hello, I am currently having trouble trying to complete one of the first tasks for the hello world exercise. Mainly because am using a Macbook and am unfamiliar with how the terminal works here. After opening up the Terminal on MacOS, I am trying to select the KitProg3 COM port and then set the serial port parameters to 8N1 and 115200 baud.Show Less
Hello, I have an inquiry regarding Uart - DMA Interrupt.
I understand that DMA-Rx interrupts depending on the setting value.
For example, if you set the "Number of data elements to send" value to 10, an interrupt occurs when 10 is received.
Then, if you set it to 10 and divide it into 6 or 4 instead of 10, is there a function that can cause interruption for each case?
For ST, Interrupt of Uart may occur when the signal from Rx is in Idle state (=Transmission Interrupt).
If you wait for the DMA buffer to fill, and then generate and process interrupts, a large amount of incoming data is missing.
Is there a way to solve this problem?
Please give me a lot of advice.
HI, I'm trying to configure the USB block in PSOC6 to operate correctly via DMA. The pieces of information are there, but I find obscure how to put them together. I seems that most of the configuration can be done in Modus Toolbox with Device Configurator, but what parts must be completed in user code to get it up and running?.
Also,I can't fine the answer of how to handle some comon situations, like, how to work with data blocks larger than the internal EP buffer, or, how to dynamically adjust for different message lengths.
Is there a working example somewhere ?
This AN228753_DMA_on_PSoC_6_MCU-ApplicationNotes is a good start to understand how DMA works, but it doesn't touch the case of a USB peripheral. I think that this case deserves an application note by itself.
I'm running two tasks on PSoC6 Wifi BT Pionner kit, using FreeRTOS and I would like to get the run time statistics of the tasks and print on the UART terminal.
This is the total 'time' that the task has actually been executing (the total time that the task has been in the Running state). It is up to the user to select a suitable time base for their application
Now, I'm using CY8CPROTO-064B0S3 to emulate our product.
I want to add some features into the bootloader and build it for CY8CPROTO-064B0S3.
However, when I refer to "supported kits" section in "PSoC™ 6 MCU: MCUboot-based basic bootloader" page, CY8CPROTO-064B0S3 seems not to be supported.
Then, is it possible to build for CY8CPROTO-064B0S3 based on mcu-tools/mcuboot.git?
I am working on the CY8CKIT-064S0S2-4343W kit.
As I want to work on peripherals on this device I have tried to import examples from Project Creator 1.40. But there are only 3 examples of this Kit.
Similar board CY8CKIT-064B0S2-4343W has many examples which I can use. Is there a way I can use those examples on the board which I am using?
Dear Sirs and Madams,
Please tell us about the BSDL file of PSoC6.
While researching this community, I found the following KBA:
I understand that PSoC4 does not support JTAG and therefore does not provide a BSDL file, and that PSoC3 / 5 are provided in the programmer's file path.
I referred to the link of PSoC6 in the KBA, however it looks like the BSDL file for PSoC6 is missing.
Is it correct to understand that BSDL files for PSoC 6 is not provided?
I just updated to the latest libraries, and ModusToolbox 2.4, and ran into problems. I tracked them down to the fact that compile_commands.json no longer includes "-DCOMPONENT_CAT1" as part of the compiler command line. It used to define both COMPONENT_CAT1 and COMPONENT_CAT1A, but now only defines COMPONENT_CAT1A.
This breaks, among other things, _cyhal_utils_get_clock_count(), which now returns a value of 1 for all clock types.
I've worked around the problem by adding "CAT1" to the definition of COMPONENTS in my Makefile, but clearly that's not how it's supposed to work.
What happened? Did I do something wrong, or fail to follow some update procedure, or is this an oversight by Cypress developers?