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 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.Show Less
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?
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).
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?Show Less
I followed the following guidence to create a "customer BSP".
But I can't create a "Empty PSoC 6 App" project because there are no this item for me to select.
One thing make me feel confused is ,,, in the guidence there have "Empty PSoC 6 App" item. But in my MTB, no this item.
Attached pictures are my process. Could you please help me to check it ?!
Do you have a suitable method that can guide me to develop a BSP ?!
Thank you so much.Show Less
I can't find anything about the DMA Registers in the CY8C61x6, CY8C61x7 TRM.
Should I refer to the PSoC62 TRM for now?
Thanks and Regards,
We are trying to solve a problem with the BLE system randomly failing while the device is connected to a peripheral and sending data. Upon failure Cy_BLE_GATT_GetBusyStatus() returns CY_BLE_STACK_STATE_BUSY indefinitely. We have tried to reset the BLE system but it does not advertise or scan after the reset.
Note: Resetting BLE was tested independently of the busy stack issue by manually triggering the soft and hard resets.
Any clues as to why the stack is busy in the first place or why the resetting process is not working would be appreciated.Show Less