How do I add a custom font to the emwin library and GUI?
I have generated a .c file from a font using the Segger font converter. But I can't get it to work with the library. My setup is the CY8CKIT-062-WIFI-BT with a TFT display. The display works fine without the custom font.
I have used PSoC 4 and 5 and the APIs are very clear.
I am trying to use PWM in PSOC6 (instance name PWM_1) and the functions available for say changing compare values are:
Which one to use? What's the difference?
Also, the PDL reference does not mention PWM_1_Start(), but it's available in the dropdown list when typing in functions. Where can I find the list of all APIs.
I am beginning with PSOC-6 but have used PSOC-4 and 5 for a long time.
Thank youShow Less
I tried to use Cy_SMIF_MemWrite() with ModusToolbox and it always returned a timeout error.
I have QSPI FRAM configured for full QSPI operation.
The problem is in Cy_SMIF_MemCmdReadStatus() function as it only uses CY_SMIF_WIDTH_SINGLE for WIP flag reading.
I have modified the function and it now works correctly:
cy_en_smif_status_t Cy_SMIF_MemCmdReadStatus(SMIF_Type *base,
cy_stc_smif_mem_config_t const *memDevice,
cy_stc_smif_context_t const *context)
cy_en_smif_status_t result = CY_SMIF_CMD_NOT_FOUND;
/* Read the memory status register */
result = Cy_SMIF_TransmitCommand( base, command, memDevice->deviceCfg->readStsRegWipCmd->cmdWidth,
if (CY_SMIF_SUCCESS == result)
result = Cy_SMIF_ReceiveDataBlocking( base, status,
CY_SMIF_READ_ONE_BYTE, memDevice->deviceCfg->readStsRegWipCmd->cmdWidth, context);
I'm trying to use the two services CTS and ANCS, to update the clock and to receive notifications from iOS.
On event CY_BLE_EVT_GATTC_DISCOVERY_COMPLETE:
If I only call the function Cy_BLE_CTSC_SetCharacteristicDescriptor, it works
If I only call the function Cy_BLE_ANCSC_SetCharacteristicDescriptor, it works
if I call them both, the second returns the error 0x160002
what could be the mistake I make?
I'd like to wake up from deep-sleep when counter's capture interrupt event occurs. I think this interrupt source cannot wake the device from deep-sleep mode, correct me if I'm wrong. If this is the case, is there a way (trick) to accomplish this?
I am currently using the PSoC6 and have downloaded the mtb-anycloud-wifi-bluetooth-tester. I am measuring packet rates at have achieved around 15 to 16 kbps. Is there a way that I can increase this to 40 kbps?Show Less
I have a CY8CKIT-062-WIFI-BT dev kit and recently have come across a persistent annoying error even during compilation of a sample application such as snip.scan. While making sure other processes and applications weren't running that would use OpenOCD drivers, the console output during a build of snip.scan still complains. Here is a sample of the latest output. Any edits I've attempted to make would only be on the snip.c source file which is only adding print statements.
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Please advise - this hasn't happened before when I worked on this devkit but I feel I might be overlooking something with my build targets ("snip.scan-CY8CKIT_062 download_apps download run" and " snip.scan-CY8CKIT_062 download run ") or setup of the devkit. Very rarely, the build will complete without this error. WICED version is 6.6
I am reaching out as I have been having some trouble while using the UDB document tool in the component creator. I am trying to get the count7 to output the terminal count to an external pin. However, I can only get one pule on a reset of the device (This means I probably have the connection to the pin correct). I have also tried to include a button input to Reset of the counter and have seen no change.
Cypress's has an example on youtube called "How to Create a Traffic Light Controller using UDBs with PSoC 5LP (Part 1)" but they don't go into detail of how to setup the count 7 component. But I followed what I saw the guy do in the UDB document.
I am looking for some direction on how to use the tool or any good documentation on the use of this tool. Or if this development tool meant to work the the PSoC 6s at all?
I have also attached a copy of the test component that I have created when using the CYBLE-416045-02 if anyone can try to replicate this issue.
Recently we are trying to develop a prototype using the CY8CMOD-062S2-43012, once we downloaded the hardware info, we realized that there is no pin diagram for the carrier module footprint, in that sense, we don't know what's pin number 1 so we are tempted to follow the standard pin distribution, just like the CY8CMOD-062S2-4343W ( Schematics can be found https://www.cypress.com/file/457816/download) as shown in sheet 7. So, we would like to have a confirmation on which one is the pin 1 in this module because the schematic for it does not show the pin arrangement for the castellated pads, and the info is not present in the gerbers files as it is for the 4343W module.
Any help would be appreciated.
Ernesto G.Show Less
Originally very normal, suddenly unable to download the code, the following is the console display info？
Started by GNU MCU Eclipse
Open On-Chip Debugger 0.10.0+dev-22.214.171.1248 (2020-08-11-03:47)
Licensed under GNU GPL v2
For bug reports, read
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
adapter speed: 2000 kHz
adapter srst delay: 25
adapter srst pulse_width: 25
** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable
cortex_m reset_config sysresetreq
Warn : SFlash programming allowed for regions: USER, TOC, KEY
Info : CMSIS-DAP: SWD Supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.21.1005
Info : KitProg3: Pipelined transfers enabled
Info : VTarget = 3.328 V
Info : kitprog3: acquiring the device...
Error: kitprog3: failed to acquire the device
Info : clock speed 2000 kHz
Error: DAP 'psoc6.cpu' initialization failed (check connection, power, etc.)
Info : psoc6.dap: powering down debug domain...
Warn : Failed to power down Debug Domains