Wireless Connectivity Forum Discussions

Hi. 

I am using project hello_sensor in CYW20706,  SDK3.2ver.

In wiced_hal_sflash.h I find some API about FLASH control.

I upgrade FW in Flash Data Section1 (0x4000), and call API wiced_hal_sflash_erase(0x42000, 0x3e000); to clean Data section2, 

It will happen whole Flash data erase, so next time reset chip it will have no FW to use.

Although I didn't call wiced_hal_sflash_set_size() before wiced_hal_sflash_erase, 

Is there any example to guide hotw to use these Flash control API?

I want to erase Data Section2 when I using FW in Data Section1, in th other hand when I using FW in Data Section 2 I want to erase Data Section 1 .

What is the expected Bluetooth Classic range between two CYBT-343026-01 modules?

I am using the EZ-Serial firmware on the CYBT-343026-01 and making a bluetooth connection using SPP. I can make a Bluetooth Classic connection between two CYBT-343026-01 modules from about 100 feet away maximum. I was expecting a range closer to 300 feet.

Hi 

I am testing Spp RFCOMM_Serial_Port_MultiPort[cyw20706] .

and I check the two device connections by following the instructions on github.

but I check only when I trying to connect from client contol(cyw20706 tool) to the second device

if I trying to connect from second device, connection is failed.

According to AirLog, when secibd device trying to connect ,cyw2070 becomes Test mode

I want cyw20706 to check if multi-connection works even if it tries from peer device(ex_Smart phone)

Thank you

Hi,

Is there a way to find out which product category a specific product falls into without consulting SRRC?

Above question is based on a Q&A from the following post.

Thanks!!

Hi~ 

Our customer developed WIFI &BT Combo module.

They want to fix some channel to increase connection speed for AP.

They tried to change channel table like as below.

freq_list=5745 5765

network={

        ssid="KMH_AP_5G"

        psk="1qaz2wsx"

        proto=RSN

        key_mgmt=WPA-PSK

        pairwise=CCMP

        group=CCMP TKIP

        auth_alg=OPEN

        scan_freq=5745 5765

But It doesn't seem to work properly.

Is there any method to solve that issue?

Thanks alot

BRs

Daniel Lim

Hi All,

We are using CYBLE-013025 bluetooth module and communicating with it via USART interface from another microcontroller.

While using an example 19 (page 39) from Infineon-EZ-Serial_BLE_Firmware_Platform_User_Guide_V1.1.2-Software-v01_00-EN.pdf document on evaluation board using serial console it worked as expected.

Though we found that using API provided via ezsapi.c file is different from what is specified for gatts_create_attr (/CAC, ID=5/1) command at page 86 in the above document. Even the number of parameters is different.

So, on the first step we are trying to create a Customer primary service attribute with UUID =  65333333-A115-11E2-9E9A-0800200CB100   and that customer service will have type UUID = 0x2800.

Here is an example of the command that we are trying to run:

longuint8a_t payload = {.length = 0x12, .data = {0x00, 0x28, 0x00, 0xB1, 0x0C, 0x20, 0x00, 0x08, 0x9A, 0x9E, 0xE2, 0x11, 0x15, 0xA1, 0x33, 0x33, 0x33, 0x65}};
/* create new service */
if ((packet = EZS_SEND_AND_WAIT(ezs_cmd_gatts_create_attr(0, 0x01, 0x00, 0x00, 0x14, &payload), COMMAND_TIMEOUT_MS)) == 0)
{
PRINTF("Failed to create new service\n");
}
else
{
PRINTF("Created new service\n");
}

In the command above, type=0, read_permission=1, write_permission=0, char_properties=0, length=0x14 followed by data which comprises by 2 bytes length=0x12, then actual data of type UUID + service UUID.

The response is: RX: rsp_gatts_create_attr: result=020c, attr_handle=0000, valid=0000

This means it has failed as correct response would come back with an attribute handle and valid=1.

I have also compared two commands on serial wire.

Here is command sent out manually while using a terminal and it works  with CYBLE-013025 bluetooth module (all in hex):

C0 18 05 01 00 02 12 00 12 00 00 28 00 B1 0C 20 00 08 9A 9E E2 11 15 A1 33 33 33 65 89

And this is supposed to be the same command generated via ezs_cmd_gatts_create_attr() API method:
C0 1B 05 01 00 00 01 00 00 14 00 12 00 00 28 00 B1 0C 20 00 08 9A 9E E2 11 15 A1 33 33 33 65 8D

These are clearly different, so the last one doesn't work. This would indicate that ezsapi API we are using is incorrect. 

We are using Infineon-EZ-Serial_Host_API_Protocol_Library-Software-v01_00-EN.zip where inside the archive readme file indicates: "EZ-Serial BLE Firmware platform release V1.1.1. The protocol version implemented
in these files is V1.3."

Is it a correct serial host API version to use with CYBLE-013025 bluetooth module? 

Here is system query firmware version response from the module: RX: rsp_system_query_firmware_version: app=0101021f, stack=02020355, protocol=0103, hardware=b1

I would greatly appreciate if someone can help by providing an example on how to use ezs_cmd_gatts_create_attr() command from ezsapi or at least point out what is wrong with the command above?

Thank you.

Do you have antenna field test report for CYBT-343026-01?

Lab ask for such report for CE certification, but I can't find it in KBA220396

We developed most of our firmware using the PSoC6 BLE Pioneer Board. Central to this is the CE216767 example which gives us DFU OTA over BLE, and has worked well for months. Due to physical limitations, our target device is the physically smaller CY8C6347FMI-BLD53 and we have been porting our code over, making adjustments to i/o.

Everything works as on the Pioneer, except we have trouble with BLE on the target board. BLE runs fine on the Pioneer. There is a 32MHz crystal on the Pioneer board and 16MHz on the target, so we found that we had to make the adjustment to ECO to 16MHz in the Clocks tab in Topdesign. We had some other testbed projects, and adjusting the ECO clock frequency was all we needed to do, but on the CE216767 project, this does not work and the bootloader halts almost right away reporting:

Error: dbg.M0006: The start request failed. Encountered error (Error '' received while attempting to read memory 0x402102C0-0x402102C4)

A similar problem was observed on the simpler projects before we adjusted the frequency of ECO in TopDesign.

Using one of our testbed apps, we traced the issue to the initialisation of the BLE Stack in the bootloader. It runs through Cy_SysPm_RegisterCallback(&bleDeepSleepCallback);
Cy_BLE_EnablePrivacyFeature();
Cy_BLE_StackSetFeatureConfig(&stackInitParam.stackConfig);
and that all seems to run okay, but then it gets to
Cy_BLE_StackInit(&stackInitParam);
this calls a this function calls a static library of precompiled code and hangs.

One thing I have noted is that as illustrated here, PSoC Creator shows ECO as 24MHz in our DFU app and as 16 in the simpler ones, even though there appears to be no difference in ECO's entries in <project>.cdwr.

This is how ECO is set up for both projects.

We would appreciate any advice!

We are using PSoC Creator V4.4 with PDL V3.1.5 and ARM GCC 5.4-2016-q2-update. The example DFU project comes with these build settings for the PDL.

Thanks, Simon M

Hi,

I want to develop a tool on windows to allow the loading of firmware through BLE.

I use exlusively Cypress DFU BLE Libs and to do firmware loading I use Cysmart with ble dongle for now.

I want to develop custom app to do it.

Can you please provide documentation on how we can send .cyacd2 files using BLE ?

Do you have example app with source code for this ?

Thank you for your support,

Kind regards