Hallo Cypress community,

we have been coding on the CY8KIT-062-BLE before and have some extensive designs running. Now we want to

deploy this code to the new CY8KIT-062 WiFi-BT. We understand that for the wifi coding the tool to use is the

wiced studio. Can we migrate the entire designs to the WICED Studio ? If not, how can the WICED Studio designs / code be joined with the code from the PSoC Creator ? Are the firmware uploads independent i.e. the WICED upload only programs the WiFi component ? If so, how to exchange data from both code bases ?

Any help / quick start on this is greatly appreciated.

Regards

Stefan

Hello, 

I'm new in Bluetooth. 

I try to run Bluetooth Mouse HID Example on kit CY8CPROTO-063-BLE.

- I create new project

- I select target device to CYBLE-416045-02

- I click update components

- I set ports for leds  7.1 7.2 6.3

- I bulid project and program both cores one by one CM0 and then CM4

After that I try to connect to BLE HID Mouse ( it is discoverable by my android phone)

Problem is that: phone can't connect by bluetooth to mouse .

Is anyone knows. What I have to change in example project to makes it work, or what I can do wrong?

( For bluetooth 4.1 and other kit it works fine)

I will be very thankfull for help.

Hey Everyone,

Using PSoC 6 with LBEE59B1LV to design a board for a customer. Just doing the hardware design and I'm confused as to how I make the proper connections for the PSoC to communicate with the 1LV chip to control the internal RF switches. Combing over  LBEE59B1LV  and CYW43012 datasheets, it isn't clear to this non-embedded guy. Also looking at the eval board that Cypress offers and still not sure. 

I'm using the SDIO lines from the PSoC to the 1LV chip for data transfer.  From the eval board schematic 43012 Schematic Carrier Module, I see there's a WL_UART Tx/Rx, but when when you follow those nets, it seems like they go to a NL section of the KitProg3 Secondary UART Multiplexing section. 

Basic question I know. Appreciate the help

Hello.

I have some trouble.

I'm developing a USB mass storage device on psoc6(CY8C6347FMI-BUD53).

There was a sample project for CY8CPROTO-062-4343W :  USB Mass Storage Logger. This sample was nearly I wanted to do and I believed this was very useful for me.

This sample emulate the file system. I tried the sample and worked on the CY8CPROTO-062-4343W board as a USB mass storage device, as I expected to.

Then, I modified the sample for CY8C6347FMI-BUD53, creating the build target. Modified source was built and programmed successfully, and the main loop executed successfully (I checked it by blinking LED).

But when I connected the board to the Windows 10 PC, this was not recognized as USB storage device.

Then I connected it to Linux PC and checked by df and lsusb commands, the board was recognized as mass storage, but not mounted on file system.

The sample source seems to do nothing MCU-dependent, except target device setting. What can I do for the  CY8C6347FMI-BUD53 board to be recognized as USB mass storage device.

I'm developing the board on the Modus Toolbox 2.2.0(Build ID: 2181).

Thank you for reading.

I have enabled interrupts on 2 pins on the same port. Only 1 works. The pins are set to interrupt on a rising edge. The external signal driving the pins is definitely working. I am using PSoC Creator 4.4 on a Cy8C6247BZI-D54. Here is the code:

void Isr_switch(void)
{
volatile uint32_t n1;
volatile uint32_t n2;
n1 = Cy_GPIO_GetInterruptStatus(N1_TACH_OUT_PORT, N1_TACH_OUT_NUM);
n2 = Cy_GPIO_GetInterruptStatus(N2_TACH_OUT_PORT, N2_TACH_OUT_NUM);
if (n1) {
Cy_GPIO_ClearInterrupt(N1_TACH_OUT_PORT, N1_TACH_OUT_NUM);
counter1 = Counter_1_GetCounter();
Counter_1_SetCounter(0);
}
if (n2) {
Cy_GPIO_ClearInterrupt(N2_TACH_OUT_PORT, N2_TACH_OUT_NUM);
counter2 = Counter_2_GetCounter();
Counter_2_SetCounter(0);
}
NVIC_ClearPendingIRQ(SysInt_Switch_cfg.intrSrc);
}

I set a breakpoint in both if statements and only the second ever gets hit. I also set a breakpoint at the line 'n1 = Cy_GPIO_GetInterruptStatus(N1_TACH_OUT_PORT, N1_TACH_OUT_NUM);' and then tried to step into it. The debugger just stepped to the next statement. I can step into that call. I am very confused by this. Any help would be appreciated.

Hello,

I want to use live debugging for my application using GUI. I was using xmc and for that I used micrium probe for xmc. This tool is useful to watch variables live graphically. Does PSoC6 support similar tool?

Thankyou.

For safety critical reasons, I need app1 to periodically check the integrity of its own image at run time. I knew the App0/bootloader was doing this, so I checked out the function it used to do this, Cy_DFU_ValidateApp. I simplified this down to:

bool ValidateApp1( void )
{
  uint32_t appVerifyStartAddress;
  uint32_t appVerifySize;

  cy_en_dfu_status_t status = Cy_DFU_GetAppMetadata(1, &appVerifyStartAddress, &appVerifySize);

  if (status == CY_DFU_SUCCESS)
  {
    uint32_t appCrc = Cy_DFU_DataChecksum((uint8_t *)appVerifyStartAddress, appVerifySize, NULL);
    uint32_t appFooterAddress = (appVerifyStartAddress + appVerifySize);
    status = (*(uint32_t*)appFooterAddress == appCrc) ? CY_DFU_SUCCESS : CY_DFU_ERROR_VERIFY;
  }

  return (status == CY_DFU_SUCCESS);

}

My first attempt to compile this threw the following error:

Build error_ undefined reference to '__cy_boot_metadata_addr'  in file cy_dfu.c.

After a little more tracing through how the App0/bootloader did business, I figured I could resolve this error by adding the line 

#include "dfu_mdk_common.h"

to App1's version of dfu_user.h .

Now when I try to build App1, I get the error:

Build error: expected '(' before 'void'  in file dfu_mdk_common.h at line 109, column 7.

And that line is:

__asm void cy_DFU_mdkAsmDummy(void);

And that error has me totally bewildered.  I believe dfu_mdk_common.h is provided as part of the DFU ecosystem, it seems it should build as-is without an error. And I have absolutely no idea what the compiler is complaining about.

Can anybody give me a suggestion on how to resolve this error?

Thanks, Ed H.

Hi,
I am testing AnyCloud MQTT-Client on CY8CKIT-062S2-43012.
I always got error "MQTT connection failed with error code 0x8060009." 
But the same setting of mqtt_client_config.h and  wifi_config.h on SDK v4-beta release can connect to aws cloud.

Hi:

   I found that the CANFD driver API have the flow tow fuction :

Cy_CANFD_ConfigChangesEnable()

Cy_CANFD_ConfigChangesDisable()

They are used to enable of disable the write access to the protected configuration registers,could you tell me Which registers are the protected configuration registers of the CANFD?

If I want to call the Cy_CANFD_SetInterruptMask API to change the configration of  CANFD intterrupt,should I call the 

Cy_CANFD_ConfigChangesEnable API first?