PSoC™ 6

I update CC0_BUFF, The output waveform is as follows. What is the appropriate reason? thanks!

Goodmorning,

I took over a PsoC6 project from an ex colleague and I simply need to run it on the board (Psoc6 WiFi-BT Pioneer Kit). I must say I have zero experience with embedded development, but I only need to run the latest version of our code. My colleague left some notes, but after I follow successfully the first steps of building the project and pressing the Debug button I get the error "Error: unable to find a matching CMSIS-DAP device". The board is, of course, connected. 

I am feel bad for asking for help for a silly issue like this one, but I also don't want to waste more time trying to fix something I have absolutely no knowledge of.

Thank you

Stefano Bider

I am using CY8CKIT-062S2-43012 and add a falling edge interrupt on P6_5 (with is MCU_TDI) and facing some problem .
The debug mode is set to SWD in "device configurator"->"system"->"debug", so i think we can usd that pin as normal gpio.

But if i use HAL 2.x, interrupt tigger will fail and i can only used HAL 1.6 to let it work.
If i didn't inital that pin in my code as a gpio, it will be high not low(other pin will be low).

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. 

Hi,

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?

Thanks,

Dear Receiver,

I use "Device Configurator" to add ADC module in the MTB. The target board I used is CY8CKIT-062S2-43012.

I add ADC module sucessfully because I can save it without error messages.

But,,, I don't know how to do next in the main.c. For example,,,

How to write initial code ?! How to start ADC conversion?! How to get ADC results ?! How to use ADC interrupt ?!... etc.

Because I can't find any related example codes if I added  ADC modules from "Device Configurator".

Thank you so much.

Hi.

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?

Thanks,

-Nick

Hi,

I am successfully able to run the example emFile_Filesystem  by importing it to ModusToolbox. 

I have tried the .txt and .log files and FS_FOpen does not return NULL. I assume open operation is successful. Now if I try to open .ico or .h264 file FS_FOpen  returns with NULL. Please find below the API for reference.  

Update : I have tried with flag "rb" but no success. 

inputFil = FS_FOpen(INPUT_FILE, "r");
if (inputFil == NULL)
{
       printf("Error opening input file");
}

Are there some flags that need to be given in Open API for opening files that are not text files?