PSoC™ 6 Forum Discussions
Hi,
I have two pieces of code (App1 and App2) that compiled in different FLASH regions (by changing the linker script) and loaded on a PSoC6 MCU (CYBLE-416045-02 device), and I use ResetHandler to determine which code to run based on reset reason.
In App1, there's a function that will call Cy_Flash_WriteRow to write certain data in certain FLASH location, and in App2, it calls this function directly because it knows where this function is located in App1. However, I am always getting CY_FLASH_DRV_ERR_UNC error. Does anyone know what could possibly be the cause?
(Each code has its own startup file (unmodified and provided by Cypress PSoC Creator) compiled and thus they have their own vector tables)
Thanks!
Show LessHello!
Part of application I'm developing needs to be able to store last n advertisement reports in array. How can I do it inside CY_BLE_EVT_GAPC_SCAN_PROGRESS_RESULT event?
Show LessHello
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:
PWM_1_SetCompare0()
Cy_TCPWM_PWM_SetCompare0()
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.
Please help.
Thank you
Show LessHi,
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,
uint8_t *status,
uint8_t command,
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,
NULL, CY_SMIF_CMD_WITHOUT_PARAM,
CY_SMIF_WIDTH_NA, memDevice->slaveSelect,
CY_SMIF_TX_NOT_LAST_BYTE, context);
if (CY_SMIF_SUCCESS == result)
{
result = Cy_SMIF_ReceiveDataBlocking( base, status,
CY_SMIF_READ_ONE_BYTE, memDevice->deviceCfg->readStsRegWipCmd->cmdWidth, context);
}
return(result);
}
Hi all,
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?
Thank you
Oscar
Show LessHi,
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?
Thanks
Show LessHello All,
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.
Thanks!
Show LessHi there,
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.
Many thanks,
Ernesto G.
Show LessOriginally 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-4.1.0.1058 (2020-08-11-03:47)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
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
Hello,
I am trying to use the notificationlogger from the C# cysmart API to analyses the log out of my PSoc6 BLE prototyping kit.
Firstly I had the error message saying "Not a valid CySmart dongle!"... By looking a bit into the forum I found the solution to solve this : replace the .dll files with the ones from the current CySmart application (version 1.3).
Once done, I have another issue : The application fall into the "stop mode" and the following message is displayed :
"It is impossible to load the file or the assembly 'cybledonglecommunicator, Version= 1.3.0.8, Culture=neutral, PublicKeyToken=null' or one of its dependencies "
How can I fix it ?
Thank you in advance for your help,
Regards,
ThDe_4683671
Show Less