PSoC™ 6 Forum Discussions

Hi,

I am trying to use a piece of code from a co-worker that is communicating with a micro SD by SPI using DMAs. The code was originally running on the CM0+, but for my application, I wanted to have it run on the CM4. I have copied the corresponding blocks from the TopDesign (I am using PSoC Creator) and enabled the interrupts in the CM4 instead of the CM0+. Everything builds fine, but when I try to run the application, I get a fault which seems to happen when the interrupt of the DMA triggers (I never reach the ISR).

I tried to run my application on the CM0+ and everything works fine.

Any idea what might be causing this?

Unfortunately, I cannot share my code, but I hope someone will be able to help me find a way to make it work.

Thanks

Hello,

I have the following warning when running my application on PSoC Creator 4.2:

Programming device 'PSoC 63 CY8C6347BZI-BLD53 (CM4)' with file 'C:\Users\FreddyC\Documents\PSoC Creator\CNN_Project\PSoC 6 CNN_project.cydsn\CortexM4\ARM_GCC_541\Debug\PSoC 6 CNN_project.hex'.

Device ID Check

Warning: The connected PSoC6 MCU device is out of date. Please contact Cypress to get a replacement

I currently have the PSoC 6 BLE Pioneer Kit with the following specifications:

Box Label

CY8CKIT-062-BLE Rev *D

1812SO08026

Board Label

121-60367-01 Rev 13

1811SO01206

I already communicated with several Cypress Semiconductor representatives (Rou Shuang Ong from Inside Sales, and Ajay Basti), and they recommended to get in touch with technical experts because it seems that the board they gave me should have fixed the problem.

I tried using PSoC creator 4.3, but it didn't fix it. I get the same warning sign. Gladly my application is running, but is there a fix to this problem?

Kind regards,

Freddy

I am trying to generate a highly accurate 1PPS signal derivative from a external 100MHZ clock with no luck. I have tried a counter timer in multiple configurations, but I either get a NACK error or the the counter does not increment at all. Any other ideas or more explicit instructions would be very welcomed.

I’m needing 4 audio out channels at 96kHz, no audio inputs.  I don’t care if it is two I2S ports, or one TDM.

1) Unfortunately, there is only one I2S port.  Is there any way to repurpose the unused I2S input as a second output?

2) Unfortunately, the max TDM bit rate is too low, even when running at the max clock.

3) It doesn’t seem that there are enough UDB resources to implement the FIFO in programmable logic.

4) I can consider alternate parts to PSOC 6.

How might I accomplish this?

Thanks!

I am working to implement a High Speed Serial Programmer (HSSP) using a PSoC 6, to program other PSoC 6 devices using SWD.

I haven't found much information on the forum about PSoC 6 implementations.

My starting point is AN73054 "PSoC 3 and PSoC 5LP Programming Using an External Microcontroller (HSSP)", with additional info from the PSoC 6 MCU Programming Specifications Document.

1) Is there a PSoC 6 specific version of the AN73054 document and related code?

2) Are there any notable problems to watch out for when adapting the PSoC 5LP version for use on a PSoC 6 for programming PSoC 6 devices?

3) Is there any existing information on implementing the lifecycle / eFuse programming in an HSSP beyond the PSoC 6 MCU Programming Specs document?

Thanks!

Hi Cypress:

    due to PSOC63 is the cortex M4F + cortexm0 , How to use Jink to debug PSOC63  BLE with SWD mode? please help to advice;

Hi,

I have broken off the KitProg3 part from the main CYPROTO-062-4343W.

I have used jumper wires between the pins on J4 (on the KitProg3) to the 5 pins on the main board (P6.6, P6.7, XRES, GND, VTARG), but I was not able to program the PSoC6. I have tried both ModusToolBox 2.1 and Cypress Programmer 2.1, but no success.

Here is the error log from Modus:

Open On-Chip Debugger 0.10.0+dev-3.0.0.665 (2020-03-20-10:13)

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

** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable

cortex_m reset_config sysresetreq

cortex_m reset_config sysresetreq

Info : Using CMSIS loader 'CY8C6xxA_SMIF' for bank 'psoc6_smif0_cm0' (footprint 6485 bytes)

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 = 0 TDO = 0 nTRST = 0 nRESET = 1

Info : CMSIS-DAP: Interface ready

Info : KitProg3: FW version: 1.20.652

Info : KitProg3: Pipelined transfers enabled

Info : VTarget = 3.298 V

Info : kitprog3: acquiring PSoC device...

Error: kitprog3: failed to acquire PSoC device

Info : clock speed 2000 kHz

Error: DAP 'psoc6.cpu' initialization failed (check connection, power, etc.)

** OpenOCD init failed **

shutdown command invoked

** Program operation failed **

srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst

And here is the error log from Cypress Programmer:

Info : [CyBridge] Start API initialization

Info : [CyBridge] Connected - KitProg3 CMSIS-DAP BULK-09140C1C02179400

Info : [CyBridge] Hardware initialization complete (824 ms)

Info : Selected Device: CY8CPROTO-062-4343W-09140C1C02179400

Info : ** Probe-config: kit_CY8CPROTO-062-4343W.cfg

Info : Open On-Chip Debugger 0.10.0+dev-2.2.0.249 (2019-09-10-10:57)

Info : Licensed under GNU GPL v2

Info : For bug reports, read

Info : http://openocd.org/doc/doxygen/bugs.html

Info : debug_level: 2

Info : C:/Program Files (x86)/Cypress/Cypress Programmer

Info : ./openocd

Info : C:/Program Files (x86)/Cypress/Cypress Programmer/BT

Info : 09140C1C02179400

Info : 1:1

Info : 0

Info : swd

Info : soft

Info : off

Info : 0

Info : adapter speed: 1500 kHz

Info : serial:    09140C1C02179400

Info : transport: swd

Info : rst type:  soft

Info : efuse:     off

Info : sflash restrict: 0

Info : adapter speed: 1000 kHz

Info : ** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable

Info : cortex_m reset_config sysresetreq

Info : cortex_m reset_config vectreset

Info : none separate

Info : SFlash programming disallowed, see 'sflash_restrictions' command

Info : init_target

Info : tcl server disabled

Info : Listening on port 4445 for telnet connections

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 = 0 TDO = 0 nTRST = 0 nRESET = 1

Info : CMSIS-DAP: Interface ready

Info : VTarget = 3.297 V

Info : kitprog3: acquiring PSoC device...

Error: kitprog3: failed to acquire PSoC device

Info : clock speed 1000 kHz

Error: DAP 'psoc6.cpu' initialization failed (check connection, power, etc.)

Error: Failed to connect to the target device

Please advise, thank you.

Hello,

I placed the UART and timer on PSoC 63 as follows.

Looking at the interrupt tab, IRQ46 and IRQ90 respectively.

This "Sysint_Timer" seems to be different from TCPWM.

What is "Sysint_Timer" and what does "CTI" stand for?

Best regards,

Yocchi

Hi Team,

I am using psoc 6. my query is related to the generated code (after compilation). As I am working with ble section.

I got the error "CY_BLE_GATT_ERR_INVALID_OFFSET".

I am using function Cy_BLE_GATTS_SendNotification(&ConnectionHandle, &handleValuePair) for updating any changes to gatt client.

Inside this funcion, there is a function (generated code) named Cy_BLE_GATTS_WriteAttributeValueLocal(const cy_stc_ble_gatt_handle_value_pair_t *handleValuePair). this has structure

cy_stc_ble_gatts_db_attr_val_info_t  param =

        {

            .handleValuePair = *handleValuePair,

            .flags           = CY_BLE_GATT_DB_LOCALLY_INITIATED

        };

this structure instance "param" has other members also apart from the handleValuePair & flags which have not been given any value. e.g. structure members "offset" is also there.

why not all the structure members initializes here?

and finally this structure being passed to function Cy_BLE_GATTS_WriteAttributeValueCCCD(&param) which gives the error "CY_BLE_GATT_ERR_INVALID_OFFSET"

my doubt is here only, if "offset" had been initialized here, then "CY_BLE_GATT_ERR_INVALID_OFFSET" error would not have come.

Is my understanding correct or Could you please get me a resolution of this error?

/Vinay