cancel
Showing results for 
Search instead for 
Did you mean: 

Wireless

l4m4l
New Contributor II

Hello,

I am trying to configure the CYBT-343026-01 BLE module for CYSPP mode. I am experiencing what I believe is unexpected behaviour in peripheral mode.

My setup is:

CYBT-343026-01, CYSPP (pin 22) => GND, LP_MODE (pin 4) => VDD.

On initial bootup, the module behaves as expected - passing all data transmitted to characteristic handle 0x11 to my serial terminal (see below)

l4m4l_0-1625284070722.png

Once I disconnect this terminal, the module re-enters API mode (see below)

l4m4l_1-1625284122371.png

This is happening even though I believe have disabled API mode in hardware by grounding the CYSPP pin. If I reconnect to the module, all data is now transmitted through the API mode UART interface (all data now encapsulated with "@E,...,D=data etc) which I would ideally like to avoid.

Would anyone please be able to let me know what is incorrect with my setup or thinking?

Any help would be greatly appreciated. Thank-you.

 

0 Likes
1 Solution
Owen_Zhang123
Moderator
Moderator

Please try to use the latest FW which should be 1.2.29 and see if the problem still happens.

https://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform....

View solution in original post

0 Likes
11 Replies
l4m4l
New Contributor II

Additionally, after about a minute after the first disconnection (and if I haven't re-paired) I receive the following API mode string "@E,000E,ASC,S=00,R=03" which suggests that advertising is being turned off due to a CYSPP state change? But I have left the CYSPP grounded the entire time?

 

/QFV output: "@R,002C,/QFV,0000,E=01010E06,S=05020016,P=0103,H=D1" which I believe is FW version 1.1.14 build 6 if this helps

0 Likes
Owen_Zhang123
Moderator
Moderator

Please try to use the latest FW which should be 1.2.29 and see if the problem still happens.

https://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform....

View solution in original post

0 Likes
l4m4l
New Contributor II

Hi Owen,

Thanks for your response. Is there documentation that you could point me to that provides step-by-step instructions on how to update device firmware?

Thanks again!

Lachlan

0 Likes
l4m4l
New Contributor II

Hi @Owen_Zhang123 

I attempted to update firmware OTA.

I used the most recent EZ Serial FW file at https://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform (ezserial_343026_release-CYBT_343026_EVAL-rom-ram-Wiced-release.ota.bin) and the "WsOtaUpgrade.exe" included in the WICED-Studio 6.6 release. I followed the steps provided in the User Guide in the section "Device Firmware Update Examples".

1. Paired to the CYBT-343026-01 module on my computer

2. Run "WsOtaUpgrade.exe ezserial_343026_release-CYBT_343026_EVAL-rom-ram-Wiced-release.ota.bin"

3. Followed the prompts to update the firmware (see below, includes output from serial connection during update)

l4m4l_0-1625656429728.png

The module is now unresponsive in API mode and CYSPP mode, and I cannot discover any "EZ-Serial" devices with bluetooth scanning. Please advise if there is any way to recover this module or if there is something simple (like a different baud rate?) that changes between 1.1.14 to 1.2.29 that would explain this

Thanks

0 Likes
l4m4l
New Contributor II

Hi Owen,

I ordered an EVAL board with the CYBT-343026-01 module on it and I can confirm that CYSPP mode works as is specified in the datasheet with firmware version 1.2.29.

I now have issues with API mode on this board and I will try to continue to recover my previous devices, but for the purposes of this question updating to firmware version 1.2.29 solved it.

Thanks.

0 Likes
Owen_Zhang123
Moderator
Moderator

Please use the module programmer to program the device: https://community.cypress.com/t5/Knowledge-Base-Articles/WICED-Module-Programmer-User-Guide-KBA22506...

Then program the file ezserial_343026_release-CYBT_343026_EVAL-rom-ram-Wiced-release.hex from here: https://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform

Please check the FW version after the program with the boot log.

0 Likes
l4m4l
New Contributor II

Hi @Owen_Zhang123 

Thanks for your response. I have tried to follow the steps at the link attached using the WICED Module Programmer. I have a USB->UART bridge which is connected to the HCI UART RX and TX pins on the 343026-01 module.

I am attempting to upload the .hex file you have suggested, but the program is erroring with:


08-07-2021 19:05:54.628: WICEDModuleProg: Running test program.
08-07-2021 19:05:54.631: WICEDModuleProg: ToggleComponentsByRunningStatus@2 - Run - Stopped - False
08-07-2021 19:05:54.757: ProgramManager: Selecting_DUT 1/8
08-07-2021 19:05:54.761: ProgramManager: Running_test_program 1/1
08-07-2021 19:05:54.812: Prog[0]COM12 : Write HCI Cmd (COM12): 01 03 0C 00
08-07-2021 19:05:55.327: Prog[0]COM12 : Soft-Reset Fail COM12
08-07-2021 19:05:55.328: Prog[0]COM12 : Failed to reset on baudrate = 115200
08-07-2021 19:05:55.331: Prog[0]COM12 : Failed to reset DUT
08-07-2021 19:05:55.337: ProgramManager: ---->SetResult [1,1] = TestFailed

COM12 is my USB->UART connection. I am assuming the module is running at 115200 baud but have tried all to be sure. I have CTS flow control off.

Is there anything I am missing?

0 Likes
Owen_Zhang123
Moderator
Moderator

You should program the device with flow control enabled. Please connect the cts and rts pin.

Then program the device under recover mode.

Owen_Zhang123_0-1625736141733.png

 

0 Likes
l4m4l
New Contributor II

Hi Owen,

Sorry I should’ve said - I performed the reset and recover steps as specified. I grounded both the XRES and SPI2_MOSI pins, and then released the SPI2_MOSI pin, followed by XRES.

 

My UART->USB does not have cts and rts pins unfortunately, so I cannot do this with my current hardware.

0 Likes
Owen_Zhang123
Moderator
Moderator

The flow control of HCI UART must be enabled. It is hardware controlled. 

Please find a USB to UART tool with CTS and RTS. Then try to program the device again.

0 Likes
l4m4l
New Contributor II

Thanks Owen, do you think it’s likely that the OTA firmware error has more or less bricked the module?

0 Likes