Dear Infineon,

                     About the CYW20820 UART setting question, could you please check if supports the below parameter? thanks.

1. Baud rate: min. 300, 600, or 1,200 bps, max. support 921,600 bps?
2. parity: none, odd, even?
3. stop bit: 1, 1.5, 2?
4. data bit: 5,6,7,8?
5. flow control: CTS, RTS, DTR, DSR

Hello,

We have firmware that was developed for the CYW20732S. Can this firmware be used to program the CYW20736S since the devices appear to be very similar.

Thank you

hello,

I am trying to understand SPP, so I try to run SPP example code GitHub - Infineon/mtb-example-btsdk-rfcomm-spp: SPP app and when I flash the code, I don't understand, and I even can't detect this Bluetooth device and I also try to follow the readme file instruction, but I stuck at Bluetooth pairing step.

Will appreciate help / pointer in resolving the issue.

Best Regards,

Gautam

Hi.

My SPP project, data loss is occurring.

I want to know the difference between these two status values.

1. spp_rfcomm_control_callback : Status = 19

2. spp_rfcomm_control_callback : Status = 16

The Status = 16 log appeared, and I confirmed that data loss occurs during the subsequent SPP data transmission.

The following is an explanation of the error code values I confirmed in the wiced_bt_rfcomm.h

(/** RFCOMM Result Codes */ enum wiced_bt_rfcomm_result_e)

19 : WICED_BT_RFCOMM_CLOSED

16 : WICED_BT_RFCOMM_PEER_CONNECTION_FAILED

I don't know why the status value is suddenly changing.

Thanks.

We are using the 343026-01 and are trying to write the FLASH from within our product. We are using Infineon FW release 1.2.29 (https://www.infineon.com/dgdl/Infineon-ez_serial_cybt_343026_fw_image_1.2.29-Software-v01_00-EN.zip?fileId=8ac78c8c7d0d8da4017d0f8ad1d2759c&da=t). The BT module is connected to the host via UARTs and we have GPIOs to set the recovery, reset, P0/P34, I2C_SDA, P2/P37/P38 and GPIO3 lines. We have pull-ups on those GPIOS (see attached).

I follow this procedure on the HCI_UART all at 115,200 baud:

1. HCI reset, we get a valid response.

2. DOWNLOAD_MINIDRIVER command. We do not get a response but that is because CTS was low so we were in autobaud mode.

3. WRITE_RAM 16 bytes at a time (i.e. one line of the HEX file at a time). We get a valid response so it "appears" to work.

4. READ_RAM to read back the bytes written in step 3. We get a valid response in the form " 04 0E 14 01 4D FC 00 yy yy yy …" BUT the yy bytes are all wrong. So the flash was NOT written.

5. I ignore the READ_RAM contents and contue issuing WRITE_RAM for the entire payload.

6. Issue LAUCH command.

This flash loading code works correctly when run with the EVAL platform, READ_RAM reads back the correct bytes and the BT firmware image runs correctly as my scan find the BT module. But on the embedded product where the READ_RAM report the wrong bytes the BT firmware image does not run correctly as I my scan does not find the BT module.

QUESTIONS:

1. We are aware that we need to pull recovery & reset low, then release reset and then recovery. But do we also need to set P0/P34, I2C_SDA, P2/P37/P38 and GPIO3 lines to anything in particular?

2. The https://www.infineon.com/dgdl/Infineon-AIROC_HCI_UART_Control_Protocol_ModusToolbox.pdf-Software-v01_00-EN.pdf?fileId=8ac78c8c7e7124d1017e90c005730c5b document only talks about using the reset and CTS lines to go into what they call "Recovery Reset". Would this be sufficient or do I also need to control the recovery line.

3. What can cause my WRITE_RAM to fail? I get a valid response but the READ_RAM reads back different bytes to what I sent down. This tells the FLASH write failed.

Weird observation: With the BT module powered off and RESET or RECOVERY set high, I see VDDIN float to around a volt. The HW engineers think there is some "back powering" through the module. Should this be happening?

Thanks in advance.

Hi Infineon team,

Would you be knowing when the debugging tool given below will become available, or would you be having a later version of the debugging tool?

CY8CKIT-005-A | MiniProg4 Program and Debug Kit - Infineon Technologies

Kind regards,

Remo

Hello,

I would like deactivate sniff mode inside my own program.

I am trying to set new value of parameter "HCI_Write_Link_Policy_Settings" but i got error command results.

I use modus toolbox with next code after stack initialisation:

// Check Link Privacy

#define HCI_GRP_VENDOR (0x003F << 10)
#define HCI_Write_Default_Link_Policy_Settings (0x000F | HCI_GRP_VENDOR)
uint8_t p_trans_buf[2];
p_trans_buf[0] = 0;
p_trans_buf[1] = 0;
result = wiced_bt_dev_vendor_specific_command( HCI_Write_Default_Link_Policy_Settings, 2, p_trans_buf, vendor_specific_command_cb);

I got inside callback status=1

I think, link policy command is a standard command, not a vendor specific command.

I don't understand what is the difference between vendor_specific_command and standard HCI command inside modustoolbox.

Could you explain me the difference and how use standard command inside modustoolbox API ?

Thanks a lot.

Aymeric

Hi

I would like to you if there is a way to send a BLE HCI command through the firmware of a CYW20835 board.

I know that a vendor specific command is available with the API call

wiced_bt_dev_vendor_specific_command

but I have yet to find one for defined BLE HCI commands.

Thanks!