PSoC™ 6 Forum Discussions

OS WINDOWS 10

IDE PSoC creator 4.2

using CYSMART 1.3 for windows PC

MCU CYBLE-416045-02

it take a long time for the ble device to connect ot the cysmart app when I discover attributes it also takes a long time. It used to take only a few seconds

I am not sure which settings I have in cysmart or if the issue is in my ble component in PSoC creator 4.2

what are the proper settings for CYSMART?

I cannot program the target with my PSoC 6 Pioneer board.

Often the target is not recognised by the programmer and when it does it starts programming and fails half way.

LEDs 2 & 4 very erratic.

The KitProg 3 is always shown in Windows Device Manager.

I followed a suggestion I saw online to uninstall the driver and then re-install but that did not help.

I opened up PSoC programmer and noticed that the Voltage reading on the programmer tab was visibly flatulating all over the place.

PSoC programmer once told me that I needed to upgrade which I did successfully, but the problem still existed.

Any ideas anybody please?

Hi,

could you please inform about planned availability date of PSoC 62 chip with 1MB RAM in 100-WLCSP package (4.1 x 3.9 x 0.5 mm, pitch 0.35 mm)?

This chip is listed as CY8C624AFNI-S2D43 in the Ordering Information section of the latest datasheet.

With best regards, Alexei

I am about half way through a project and I would like to see how much RAM and FLASH (for code) has been used up. In most other IDEs I can find this information in the map file produced by the linker. But so far I haven't been able to find this in the map file created by Creator 4.3 or anywhere else in the reports, tabs, etc. that are available.

Can anyone point out to me where I can find this information?

Thanks,

Ed H.

Hi,

I have a problem implementing a SPI slave on a PSoC 6 device (CYBLE-416045-02). I have an interrupt routine on the Rx FIFO Not Empty event. It is working fine receiving data from the master. The problem is that when sending data back to the master, the bytes placed into the TX FIFO occur on MISO one byte later than expected.

I am clearing the TX FIFO at the beginning of a SPI frame using an interrupt on the SS line. Then, at the SPI interrupt after receiving the first byte, I place a byte into the TX FIFO (using Cy_SCB_SPI_Write) and expect that byte to appear on MISO when the next byte is clocked by the master, but it does not appear then, it only appears on the byte following the next one.

Attached is the code, and also an analyzer trace. Note that I am outputting some additional debug signals on spare pins to show when events are occurring.

I have tried many combinations of API calls to clear the FIFO at different times but nothing seems to fix this problem. I have also tried slowing down the clock from the master, which also increases the inter-byte spacing, but that also makes no difference. I have seen in other posts some talk of there being some inherent delay with writes to the TX FIFO, but I cannot find any hard information on this.

Any help with this would be very much appreciated.

Peter

I tried to connect the board CY8CPROTO-064S1-SB with ModusToolbox IDE 2.1

But the BSP for CY8CPROTO-064S1-SB is unavailable.

please find the screenshot for the issue below:

P.S. As per the discussion in the community, find the link here: https://community.cypress.com/thread/53959

It was mentioned to use ModusToolbox IDE for PSoC64 device.

Could you help me solve this issue.

Aadarsh Kumar Singh

Hi..

I am having a problem with using the PP_COM_Wrapper.dll.

I have PSoC Programmer 3.28.7 installed on my Desktop PC. The application works well. However when I moved the whole folder including exe file the Wrapper dll file. It no longer works. I have found this thread PSoC Programmer example exe does not run on another PC and it seems I have to reference the PP_COM_Wrapper file that is accompanied with the installed PSoC Programmer Folder (like on my Laptop which has PSoC Programmer 3.28.6). Additional information that the DLL cannot be registered as it is missing a DllRegisterServer entry.

I want to unify the program to work on any computer even if it doesn't have PSoC Programmer installed.

I read the suggesstion by SanjeevG_16 . I tried it using PsocProgrammerCOMLib. I have version 39.0 using Visual Studio 2019, and I am having this error

System.TypeInitializationException

  HResult=0x80131534

  Message=The type initializer for 'C_Sharp.Program' threw an exception.

  Source=<Cannot evaluate the exception source>

  StackTrace:

<Cannot evaluate the exception stack trace>

Inner Exception 1:

BadImageFormatException: Could not load file or assembly 'Interop.PSoCProgrammerCOMLib, Version=39.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

Thank you

Hi,

I think the documentation of Cy_IPC_Pipe_SendMessage should be clearer, specifically for the parameter void * msgPtr.

I thought at first that it can be any type of structure, but by stepping through the code, the first element of the structure is actually a scratchpad provided to the PDL. Even in CE223820, the structure ipc_msg_t defines the fields for that, but no comment clarifies it, so I just ignored this structure when I first tried implementing IPC messages.

Even the Function Usage section of the PDL documentation only seems to "suggest" the uint32 array instead of insisting on the fact that the first element must be a uint32 populated with the fields client, user, intrmask.

For anyone wondering, here's my message structure, which works with the function call scheme used in CE223820:

typedef enum {

     MSG_TYPE_1,

     MSG_TYPE_2

} MsgType;

typedef struct {

     uint32_t scratchpad;

     MsgType type;

     uint8_t* data;

} IpcSharedMsg;

// CM4 code

volatile IpcSharedMsg msg;

ipcMsg.scratchpad = _VAL2FLD(CY_IPC_PIPE_MSG_CLIENT , CY_IPC_EP_CYPIPE_ADDR)

                  | _VAL2FLD(CY_IPC_PIPE_MSG_USR    , 0)

                  | _VAL2FLD(CY_IPC_PIPE_MSG_RELEASE, CY_IPC_CYPIPE_INTR_MASK);

// CM0+ code

volatile IpcSharedMsg msg;

ipcMsg.scratchpad = _VAL2FLD(CY_IPC_PIPE_MSG_CLIENT , CY_IPC_EP_CYPIPE_ADDR)

                  | _VAL2FLD(CY_IPC_PIPE_MSG_USR    , 0)

                  | _VAL2FLD(CY_IPC_PIPE_MSG_RELEASE, CY_IPC_CYPIPE_INTR_MASK);

And then I only change the type and data fields, depending on the message.

Thanks,

Fred

Hey All,

I have been programming a custom board with the CY8C6247BZI-D54 chip through the SWD interface using the Kitprog3 breakout board from CYPROTO-062-4343W-BLE-WIFI development board.

For a while it was not recognizing the target device until I changed :

-c "source [find interface/kitprog3.cfg]" to -c "source [find interface/cmsis-dap.cfg]"

and now it stops working as says "Error: DAP 'psoc6.cpu' initialization failed (check connection, power, etc.)"

I have checked that the power and the configuration pins are set correctly.

Info : CMSIS-DAP: SWD  Supported

Info : CMSIS-DAP: FW Version = 1.2.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 : clock speed 1000 kHz

The only other information I am given is that :

"

Failed to execute MI command:

-target-select remote localhost:3333

Error message from debugger back end:

localhost:3333: No connection could be made because the target machine actively refused it.

"

But I'm not sure how to address the issue above. I have read that it might be a race condition ?

Hello.

I am wondering how can I flash both the PSoC 6 M0+ and M4 cores using CLI ppcli.exe without the need for the PSoC Programmer GUI. I am need to do this to automate the process of flashing devices. I am already able to build the project and generate a hex file for each core using cyprjmgr.exe. The kit is connected through KitProg3, thus SWD Protocol with 10pins.

Thank you